Invoice reconciliation services
Invoice reconciliation, run as a service
Roughly 86% of invoices reconcile themselves. The work is the other 14% — price variances, quantity mismatches, missing credits, and GL coding errors that block your close. We run the exception queue.
The match is not the problem — the exceptions are
The invoice reconciliation process starts with data extraction and normalisation, moves through automated matching, and ends with exception investigation and resolution. Modern ERPs auto-match the clean invoices — the ones where the PO, receipt, and bill all agree. That part works. What does not work is the tail: the invoices where the price changed after the PO was issued, the shipment arrived short, the credit memo was never applied, or the GL account was miscoded.
These exceptions sit in a queue. With manual processes, someone investigates each one — pulling the PO, checking the receipt, calling the vendor, reading the contract. At scale, this is where AP teams spend the majority of their time, and where month-end close gets delayed.
Our automated invoice reconciliation agents work the exception queue. They investigate each break, pull supporting documentation from both sides, apply your tolerance rules, and either resolve the item or escalate it with a complete audit trail. The result: a clean reconciliation delivered on your schedule.
Three-way match: the foundation
Every invoice is validated against three documents. When all three agree, payment proceeds. When they do not, the exception queue begins.
Purchase order
Quantities ordered, unit prices, delivery terms, payment terms.
Goods receipt note
Quantities received, condition, date, warehouse location.
Vendor invoice
Quantities billed, unit prices, tax, payment due date.
Six exception types we resolve
Each exception type has a different investigation path. Our agents know which documents to pull, which thresholds apply, and when to escalate.
Price variance
PO says $12.40, invoice says $12.80. Below tolerance? Auto-resolve. Above? Escalate with the PO line, receipt, and contract clause attached.
Quantity mismatch
Invoice charges for 500 units; receiving dock logged 480. The agent cross-references the ASN, packing slip, and GRN before flagging.
Duplicate invoice
Same vendor, same amount, same date — different invoice number. The agent checks line-item detail, PO references, and payment history to confirm or clear.
Credit memo mismatch
A credit note was issued but never applied. The agent traces the original invoice, matches the credit, and proposes the offset entry.
Short-pay and substitution
Buyer short-paid due to a quality issue or substitution. The agent maps the deduction to the dispute log and flags unresolved items past aging threshold.
GL coding error
Invoice posted to the wrong account or cost centre. The agent compares against the PO's default coding, vendor master, and prior posting patterns.
Tolerance rules and escalation paths
Not every mismatch is a problem. Tolerances define what auto-resolves and what requires human review. Rules are configurable per vendor, GL account, or globally.
| Field | Example threshold | Action |
|---|---|---|
| Unit price | ±$0.05 or ±0.5%, whichever is greater | Auto-resolve within tolerance; escalate above |
| Line quantity | ±2 units or ±1% | Auto-resolve within tolerance; flag for receiving confirmation above |
| Invoice total | ±$50 absolute | Auto-resolve; log for monthly variance report |
| Tax amount | Zero tolerance (rounding excepted) | Escalate any discrepancy for tax compliance review |
| Payment terms | Net-30 vs. Net-45 mismatch | Flag for AP manager review before scheduling payment |
Systems we connect to
We pull invoice, PO, and receipt data directly from your ERP. No CSV exports, no manual uploads, no middleware.
| System | Integration capability |
|---|---|
| NetSuite | SuiteScript integration, vendor bill matching, GL impact preview |
| Sage Intacct | Dimensions-aware matching, multi-entity consolidation |
| QuickBooks Enterprise | Bill-to-PO matching, class and location tracking |
| Microsoft Dynamics 365 | Three-way match with product receipts, budget validation |
| Bill.com | Inbox ingestion, approval routing, sync back to ERP |
| Acumatica | Subaccount matching, inter-branch invoice allocation |
| SAP Business One | GRN-based matching, landed cost reconciliation |
| R365 (Restaurant365) | Distributor invoice parsing, multi-location GL coding |
Who uses this
Family offices
Managing vendor invoices across multiple entities, properties, and operating companies — each with different GL structures and approval workflows.
Fund administrators
Processing fund expense invoices, management fee calculations, and administrator-to-custodian reconciliation at scale.
Mid-market finance teams
Running high invoice volumes through NetSuite or Dynamics without the headcount to work the exception queue before close.
Related services
Frequently asked questions
What does invoice reconciliation mean?
Invoice reconciliation is the process of matching a vendor invoice against the original purchase order and the goods receipt to confirm that what was ordered, received, and billed all agree. Discrepancies — in price, quantity, tax, or coding — are investigated and resolved before payment is released.
How is this different from accounts payable automation?
AP automation handles the workflow: scanning invoices, routing approvals, scheduling payments. Invoice reconciliation is the control layer underneath — verifying that the amounts are correct before the payment ever runs. We handle the reconciliation; your AP system handles the payment.
What tolerance rules can I set?
Tolerances are fully configurable per vendor, per GL account, per line type, or globally. You can set absolute thresholds (e.g., ±$50), percentage thresholds (e.g., ±0.5%), or combined rules. Breaks within tolerance are auto-resolved and logged. Breaks above tolerance are escalated with full documentation.
How do you handle invoices without a PO?
Non-PO invoices — utilities, subscriptions, one-off services — are matched against recurring patterns, contract terms, or budget allocations instead of a purchase order. The agent learns your approval patterns and flags anomalies against historical baselines.
What systems do you connect to?
We integrate with NetSuite, Sage Intacct, QuickBooks, Microsoft Dynamics, Bill.com, Acumatica, SAP Business One, and Restaurant365. We pull invoice data, PO data, and receipt data directly from your ERP — no manual exports required.
What does the engagement look like?
We start with a scoping call to map your invoice volume, exception rate, and system landscape. Then we configure matching rules, tolerance thresholds, and escalation paths. You receive a daily exception report with proposed resolutions — and a clean reconciliation at month-end.
Stop working the exception queue manually
Tell us your invoice volume, your ERP, and your biggest pain point. We will scope the engagement and show you what the first month looks like.