Invoice reconciliation software

Invoice reconciliation is the check that decides whether a supplier invoice should be paid: every line is reconciled against the purchase order and the goods receipt, on pre-tax unit prices, before the invoice is approved. It happens before money moves — which is what separates it from bank reconciliation, payment reconciliation and account reconciliation.

---

First: which reconciliation do you mean?

"Reconciliation" covers at least four different jobs in finance, and search results mix them freely. They involve different documents, happen at different times and are done by different people. If you buy the wrong one, it will not solve your problem:

This page is about the first row. If your problem is that payments and invoices do not line up in the ledger, or that the bank statement will not tie out, you want one of the other three and a different category of tool.

The distinction has a practical consequence: the other three reconciliations detect problems after the money is gone. Invoice reconciliation is the only one that can still prevent the loss, because it happens while you can still refuse to pay.

What gets reconciled against what

A supplier invoice is a claim. Two documents can support or contradict it:

• The purchase order — the agreement. States the item, quantity and unit price you committed to. Reconciling against it answers "is the supplier billing what we agreed?"
• The goods receipt or delivery note — the evidence of delivery. States what physically arrived. Reconciling against it answers "did we actually get what we are being billed for?"

Reconciling against only the PO is 2-way; adding the receipt makes it 3-way. The receipt is the leg that catches the expensive failure — being billed in full for a short delivery — because the PO and invoice can agree perfectly while the warehouse received less. The full three-way process covers this end to end.

Why it has to be line by line

Reconciling document totals is the most common way this control fails silently. Three reasons, all structural:

• Totals include tax. Tax is computed on the invoice, not the PO, and rates differ by line. Comparing gross totals compares two things that were never meant to be equal.
• Totals cannot express partial anything. A partial delivery or a partial invoice makes the totals legitimately differ, so a total-level check produces either a false alarm or nothing at all.
• Errors cancel. An overcharge on one line and an under-delivery on another can net to a total that looks correct while both lines are wrong. This is not hypothetical — it is the normal shape of a messy invoice.

The arithmetic that makes this concrete is on the invoice matching page, with a five-line invoice where the totals nearly agree and $409 is wrong.

The two variances

Reported separately, because they are different failures with different owners. A price variance is a contract conversation with procurement. A quantity variance is a warehouse or supplier conversation. A tool that reports one blended "difference" makes you re-derive which it was.

What unreconciled invoices actually cost

The cost is rarely a single dramatic error. It accumulates in four ways:

• Silent price creep. A unit price drifts up between the quote and the invoice. Individually small, applied to every unit for the rest of the year.
• Billing for undelivered goods. Caught only by the receipt leg. Nothing else in the process will find it.
• Duplicate payment. The same invoice arriving by email and by portal, entered twice. This one is cash straight out the door — how duplicates get through.
• Unbilled receipts sitting in accrual. Goods received and never invoiced distort your liability until someone reconciles them — GRNI reconciliation.

The reconciliation process, step by step

1. Capture. Get the invoice into a structured form — supplier, number, date, and the lines with quantity and unit price. Whatever the format.
2. Identify the supplier. Match to a supplier record despite name variation. "Acme Ltd" on the invoice, "ACME LIMITED" in your system.
3. Find the order. Link the invoice to the right PO — by reference where the supplier quotes it, otherwise by supplier, amount, date and item pattern.
4. Find the receipt. Link the PO lines to what was received, allowing for several deliveries against one order.
5. Reconcile each line. Compute both variances against tolerance. Mark lines with no PO, no receipt, or not yet invoiced.
6. Route the exceptions. Send each exception type to whoever can actually resolve it, rather than to one shared queue — exception routing.
7. Approve and post. Clean invoices proceed. Only the disputed ones wait.

Steps 2 to 5 are where the work is, and where software earns its cost. Steps 1 and 7 are the parts most tools lead with, which is a decent signal about what they actually do.

Evaluating invoice reconciliation software

The category label is used loosely, so test the substance:

1. Does it reconcile against the goods receipt, or only the PO? Many tools labelled "reconciliation" are 2-way only.
2. Is reconciliation per line or per document total?
3. Can one invoice reconcile across several POs, and one PO across several deliveries?
4. How does it handle a partial delivery followed by a correct partial invoice — does it stay quiet?
5. Are price and quantity variances reported separately?
6. What happens when the invoice wording differs from the PO wording?
7. Is there an audit trail of who accepted a variance, and why?
8. Does it detect duplicates across channels?

How ininvoice reconciles

ininvoice is a reconciliation and validation layer that runs before your accounting system, not a replacement for it. It does not execute payments and it is not a full AP suite.

• Connect Gmail. Invoices and delivery notes that already arrive by email are read as they land.
• Open POs are loaded by CSV or API.
• Every invoice line is reconciled against its PO line and receipt line on pre-tax unit prices, with configurable absolute and percentage tolerances.
• Clean invoices pass through untouched. Exceptions surface with the amount, the cause and the affected line stated plainly.
• Duplicates are caught by supplier, number, amount and timing pattern, including across separate channels.
• Reconciled data exports in formats compatible with Holded, Sage 50/200 and A3 ERP. Native integrations are in development.

Frequently asked questions

Is invoice reconciliation the same as bank reconciliation?

No. Bank reconciliation compares your cash ledger against the bank statement to confirm money moved as recorded. Invoice reconciliation compares a supplier invoice against the purchase order and goods receipt to decide whether it should be paid at all. Bank reconciliation happens after payment; invoice reconciliation happens before it.

How is it different from account reconciliation?

Account reconciliation validates that a general ledger balance is supported by underlying detail, normally at period close. Invoice reconciliation is a transactional control on a single invoice, before approval.

Can we reconcile invoices without purchase orders?

Only partially. With no PO there is nothing stating what was agreed, so price cannot be validated at all. You can still check against a delivery note and detect duplicates. If most of your spend has no PO, that is a purchasing process problem, and no reconciliation tool will fix it.

Is invoice reconciliation the same as invoice matching?

They describe the same operation. "Matching" emphasises the mechanical act of linking lines across documents; "reconciliation" emphasises resolving the differences that linking reveals. In practice a tool that does one does the other.

How long does it take to start?

Connect the inbox and load open POs by CSV or API. No implementation project, no setup fee, and loading historical POs does not block processing.