At a glance
- Treat the vendor invoice, repair order, parts ledger and GL as one chain, not as separate AP and inventory chores.
- Month-end differences can trace to timing: an invoice, credit, price change or open ticket that one record has and another does not yet.
- Use 3-way matching where goods are received and 2-way matching where a repair order stands in for the receipt.
- For a multi-rooftop group, map every store to one chart of accounts and one vendor list before automating.
- The controller approves every variance and every payment; the agent proposes and routes.
Why don't my parts inventory numbers match my general ledger at month-end?
Parts reconciliation to the GL means comparing the parts system's ending inventory value with the GL balance for the same date, then explaining each difference. The two records are updated by different events, so they drift apart between postings.
Withum, an accounting firm, lists reasons for accounting and inventory discrepancies in an article published October 18, 2024. IntelliDealer, a dealer software product, adds more in its help documentation. The list below draws on both.
- Late invoices: Withum's example is a purchase where accounting does not "receive the invoice for those parts until the 3rd of the new month".[1]
- Price changes: "Every month, the manufacturer will adjust the costs of certain parts."[1]
- Returns and credits: "When a return is created, parts are removed from the pad and, thus parts inventory," while "Accounting usually doesn’t learn of the return until the credit is received".[1]
- Open tickets: on parts counter tickets, "the value isn’t deducted from the general ledger until the ticket is closed".[1]
- Receipting and credit differences: IntelliDealer's (VitalEdge) help documentation notes that "Parts bought in bulk and sold in smaller increments are easy to mis-receipt", and that "If credit and cost differ, accounting must post the difference to the correct accounts so inventory and G/L stay aligned."[2]
Core charges and warranty-return credits may belong on the same list. Where a core or warranty return is credited after the part leaves inventory, we recommend tracking it as an open item with an age until the credit posts. An agent can keep that list current, so month-end starts with named differences instead of one unexplained balance.
The reconciliation chain: repair order invoice matching and parts-to-GL reconciliation
This table is our own framework, not a published standard. It follows one purchase through four records and a fifth row for credits. Adapt the variance types and owners to your own stores.
| Stage | What an AI agent matches | Variance to expect | Who resolves it |
|---|---|---|---|
| Vendor invoice | Reads each line and checks vendor, invoice number, part number, quantity and price against the open order or statement. | Duplicate invoice, price above the order, quantity not ordered, missing line. | AP clerk for data fixes; parts manager for price and quantity questions. |
| Repair order | Links service and sublet invoice lines to the repair order they were bought for, and compares cost and parts used. | Invoice with no repair order, line billed to the wrong RO, cost differs from what the RO recorded. | Service advisor or service manager; controller if the RO is closed. |
| Parts ledger | Compares received and invoiced quantities and cost with the parts system's receipts and on-hand value. | Received not invoiced, invoiced not received, cost mismatch, unit-of-measure error. | Parts manager. |
| General ledger | Compares the parts system's ending inventory value with the GL balance and lists each reconciling item with its source. | Late invoice, unposted price change, open ticket, unposted return, wrong account. | Controller or accounting manager approves each adjustment before it posts. |
| Credits (cores and returns) | Pairs each return or core with the vendor credit that should follow, and ages the ones still open. | Credit missing, credit smaller than the return, credit booked to the wrong account. | Parts manager chases the vendor; controller approves the posting. |
Can AI reconcile repair order invoices automatically without manual data entry?
For documents that match cleanly, yes: an agent can read the invoice, pull the lines and propose a match without anyone retyping them. Yooz, an AP vendor, says on its CDK page that "Yooz uses AI and OCR to capture invoice data automatically."[5] That is a vendor statement about capture, not a measured result.
Anything unclear, partial or outside a tolerance you set goes to a person with the evidence attached. Approval of a variance or payment is a human step by design. The pattern is described on the financial reconciliation automation page.
How do I catch duplicate or incorrect vendor invoices before paying them?
Run the checks before an invoice reaches the payment queue, not after. The steps below are our recommended order.
- Build a duplicate key
Combine vendor, invoice number, invoice date and amount. Also compare near-matches, such as the same amount and date with a retyped invoice number.
- Check against open and paid items
Compare each new invoice with invoices already paid and with invoices waiting for approval, across every store in the group.
- Check the lines
Compare price and quantity with the order or repair order. Flag lines with no matching order.
- Hold and route
Put flagged invoices on hold with the reason and the matching documents attached, and send them to the owner in the table.
What's the difference between 2-way and 3-way invoice matching?
Two-way matching compares an invoice with the order it belongs to. Three-way matching adds a receipt. Ottimate's documentation says of two-way matching that "The PO is matched directly against an invoice, skipping the receipt step."[3] For three-way matching it says "The PO is matched against both a receipt and an invoice."[3]
The same documentation explains the purpose: "This ensures that what was ordered, received, and billed all agree before payment is released."[3] On receipts it says "Each receipt must reference an existing PO."[4]
| Match type | Documents compared | Where it fits in a dealership | What it can miss |
|---|---|---|---|
| 2-way | Invoice and order (a repair order for sublet or outside work, or a purchase order). | Sublet and outside-service invoices, where the repair order records the work. | Billed work that was never performed, if nobody checks the repair order. |
| 3-way | Invoice, purchase order and receiving record from the parts system. | Stocked parts, special orders and other goods that are checked in at the parts counter. | A receipt keyed to the wrong quantity, since the receipt itself is trusted. |
We recommend 3-way matching for stocked parts and 2-way matching where a repair order stands in for the receipt. Where receiving is inconsistent, fix the receiving step first; a 3-way match is only as good as the receipt.
How do dealer groups reconcile parts invoices consistently across multiple rooftops on different DMS platforms?
Reconcile against one group standard, not against each store's DMS. If each store codes the same vendor differently, the group needs one definition of a match. These are our recommendations.
- One chart of accounts map: map each store's accounts to a single group structure, so a parts purchase lands in the same place everywhere.
- One vendor list: keep one record per vendor with the aliases each store uses, so duplicates are caught across stores and not just within one.
- One invoice format: convert invoices from every store into the same fields before matching, whatever the DMS.
- One set of tolerances: set price and quantity tolerances once for the group, with store-level exceptions written down.
- One exceptions queue: route variances to named owners per store, with the group controller seeing the whole list.
The DMS remains the system of record in every store. We suggest starting with read access to each one and adding write-back only after the matching rules have run cleanly on closed months. The auto dealerships overview covers the wider back-office picture.
Working with CDK and Reynolds and Reynolds
For this chain, an agent needs three things from each DMS: open repair orders, parts receipts and GL balances. We recommend read access first. The quotes below are what vendors say on their own pages.
Fortellis, CDK's developer site, says "Leverage our modern APIs and developer tools to build solutions that drive the industry."[6] Yooz's CDK page says "Invoices are routed to the appropriate dealership managers for approval" and "Approved invoices sync directly into CDK accounting."[5] Both are vendor statements, and neither says which of those three data sets a given access route covers.
- Reynolds and Reynolds: this article doesn't cover Reynolds and Reynolds' integration options. Ask Reynolds which routes apply to your stores.
- Any added layer: Ottimate's documentation says "your ERP remains the authoritative source for purchase order data."[3] We recommend the same stance here: the DMS stays authoritative.
When this doesn't apply
- A single store with a modest invoice count, where the DMS or your AP tool already matches invoices and your monthly reconciliation is quick enough that a new tool would not repay the setup.
- Vendors that already send structured data into your DMS. A fixed rule or built-in report is simpler and easier to audit than an agent.
- Receiving or repair-order closing that is inconsistent. Fix those habits first; an agent matches the records you have.
- Anything that needs a judgment call, such as accepting a price dispute. That stays with your people.
Frequently asked questions
Why don't my parts inventory numbers match my general ledger at month-end?
The parts system and the GL are updated by different events. A late vendor invoice, a manufacturer price change, an unposted return or an open parts ticket can sit in one record and not the other. List each reconciling item with its source and age so the difference is explained, not just totaled.
How do I catch duplicate or incorrect vendor invoices before paying them?
Check each invoice before it reaches the payment queue. Compare vendor, invoice number, date and amount with paid and pending items across every store, then compare lines with the order or repair order. Put anything flagged on hold with the evidence attached for an AP or parts owner.
What's the difference between 2-way and 3-way invoice matching?
Two-way matching compares an invoice with its order. Three-way matching compares the invoice, the order and a receipt, confirming that what was ordered, received and billed agree before payment. Use 3-way for stocked parts that are checked in, and 2-way where a repair order records the work.
Can AI reconcile repair order invoices automatically without manual data entry?
For clean documents, an agent can read an invoice, extract the lines and propose a match to the repair order without retyping. Unclear or out-of-tolerance items go to a person with evidence attached. The controller still approves variances and payments, so the process reduces data entry, not oversight.
How do dealer groups reconcile parts invoices consistently across multiple rooftops on different DMS platforms?
Reconcile against one group standard instead of each store's DMS. Map every store to one chart of accounts, keep one vendor list with store aliases, convert invoices to the same fields, set tolerances once and route exceptions to named owners. Each DMS stays the system of record.
Related reading
- Financial reconciliation automation covers the matching-and-exceptions pattern in depth.
- Document review with human approval covers reading documents with a person approving the result.
- AI agent implementation covers how a chosen workflow is built and handed over.
- Reconciliation match rules and exceptions covers the general match-type and exception framework.
- Auto dealerships sets this workflow beside the rest of the dealership back office.
Sources
- Withum, "Parts Reconciliation to the Rescue!" (October 18, 2024) — Parts Pad to General Ledger reconciliation intro paragraph (late invoices); Common Reasons for Accounting and Inventory Discrepancies: appreciation, rejected parts returns, pending parts invoices (accessed 2026-10-30)
- IntelliDealer, "Reconciling the General Ledger to your parts inventory" — Parts Returns; Breaking Bulk Units (accessed 2026-10-30)
- Ottimate, "Purchase Orders" (product documentation) — How purchase orders work in Ottimate, Two-way and Three-way matching; page-top Info callout (source of PO data) (accessed 2026-10-30)
- Ottimate, "Purchase Receipts" (product documentation) — Linking receipts to purchase orders; How receipts work in Ottimate (accessed 2026-10-30)
- Yooz, "Yooz AP automation for CDK" — FAQ (accessed 2026-10-30)
- CDK Global, "Fortellis" — Fortellis home page (accessed 2026-10-30)
More in Finance operations
Deal Jacket and Title/Registration Automation for Multi-Rooftop Dealer Groups
Deal jacket and title/registration automation for multi-rooftop dealer groups: a completeness checklist table, audit-gap handling and cross-store standards.
Auto DealershipsFranchise Brand-Standards Audit Documentation: Automating the Paper Trail Behind the Inspection
Franchise brand-standards audit documentation: how an agent turns photos, PDFs, forms and emailed fixes into one packet per location, ready when asked.
Multi-Unit Franchise OperatorsGroup and Folio Billing Audit: Catching the Leak Types a Normal Error Check Misses
A group and folio billing audit for hotel management companies: a leak-type table of rate code mismatches, missing closes, adjustments, orphaned charges.
Hotel Management Companies