Invoice matching software checks a supplier invoice against the purchase order and, in a three-way match, the goods receipt, then posts what agrees and queues what does not. In our opinion buyers pick the wrong one because they compare match types, when the deciding factor is how the exception queue gets cleared.
Almost every AP team we meet already matches invoices. They do it in the ERP, by hand, and the part that hurts is not the matching. It is the 30 or 40 invoices a week that fail the match for entirely ordinary reasons: a partial delivery, a price change nobody told finance about, a supplier who invoices two purchase orders on one document. Those land in a queue, and the queue is where the days go.
At Lleverage we build accounts payable agents that read the invoice, do the match and route the exceptions with the context attached, which is the pay-and-collect side of the back office. Every product claim below comes from the vendor's own documentation. If you would rather see it than read it, book a demo with one of your own failed matches.
What is invoice matching software, and what does it actually do?
Invoice matching software automates the comparison between what you ordered, what arrived and what you were billed. It captures the invoice, finds the related purchase order and receipt, compares quantities, prices and totals line by line, applies your tolerance rules, and posts the invoices that agree straight into the ERP without a person touching them.
The word "software" hides how differently these products behave, because matching is only half the job. Every one of them will match a clean invoice. What separates them is the other half: what happens to the ones that fail, how much context the system assembles before a human sees it, and whether a match that failed once teaches the system anything about the next one.
For the mechanics of the match itself, including tolerance settings and the four-way variant, we wrote a separate piece on how three-way matching automation works. This one is about choosing what to buy.
What is the difference between 2-way, 3-way and AI matching?
| 2-way match | 3-way match | AI matching | |
|---|---|---|---|
| Compares | Invoice against purchase order | Invoice against purchase order and goods receipt | Whatever documents exist, including ones with no clean reference |
| Controls for | Billing above the agreed price or quantity | The above, plus paying for goods never received | The above, plus documents that would not match at all under rules |
| Needs | A PO on the system | A PO and a posted receipt | Neither, though both improve the result |
| Typical use | Services, subscriptions, freight | Physical goods against a PO | Mixed AP flows with many exceptions |
| Fails when | The invoice references no PO number | Receipts are posted late or in the wrong unit | Genuinely ambiguous documents, which it escalates |
| Who clears exceptions | A person, from a queue | A person, from a longer queue | The agent resolves the routine ones and routes the rest with context |
The row that matters is the last one. Two-way and three-way are control choices and you may well need both for different spend categories. AI matching is not a fourth control level competing with them, and any vendor presenting it that way is selling you a category error. It is a different way of arriving at the same match, one that reads the document rather than requiring the document to arrive pre-structured.
What does your ERP already match for free?
More than most buyers assume, which is why this question belongs before any vendor conversation. Microsoft's own documentation for Dynamics 365 Business Central describes native matching in detail: the Get Receipt Lines and Get Order Lines actions on the Purchase Invoices page let you match an invoice line to any number of purchase order lines, with or without a posted receipt, and a Matched Order Lines page where you review quantities and inspect discrepancies such as price or amount differences before posting.
So the honest starting position is that a Business Central shop is not buying the ability to match. It is buying everything around it.
Microsoft also documents where the native path stops, and the limits are worth reading before you scope a project. The Get Order Lines action does not work with orders that carry prepayments or Item Charges lines, and it cannot be used with orders linked to projects, subcontracting, blanket orders or intercompany transactions. Autoreceive will not work on partially received lines, or at locations using directed put-away and pick.
Read that list against a project-based manufacturer and you will see the problem immediately. Blanket orders, subcontracting and project-linked purchasing are not edge cases in engineered-to-order businesses, they are the normal way of buying, which is precisely why those companies feel matching pain that a straightforward distributor does not.
Why do invoice matching projects stall at the exception queue?
Because the business case was written on the clean invoices and the work lives in the dirty ones. A vendor demo matches a tidy PO to a tidy invoice and reports a 90% touchless rate. Your AP clerk then spends the same four hours a day she spent before, on the 10% that failed, and the saving never shows up in the department.
The mechanics of the stall are mundane and always the same. An invoice fails on a quantity variance, so it enters a queue. Nobody in AP can resolve it, because the answer is in the head of the buyer who agreed a partial shipment three weeks ago. It waits. The supplier chases. Someone approves it to make the chasing stop, which is how invoice matching quietly stops being a control.
Royal Kaak is a useful example of the shape of this problem, if not a metric. As a project-based manufacturer of industrial bakery lines, every custom installation sits behind dozens of purchase orders across many vendors, and each of those returns as an invoice to be checked, matched and booked. The volume is not the difficulty. The variety is.
What does AI matching add that rules-based matching cannot?
Three things, and only the third is difficult to copy. It reads documents that carry no usable structure, so a supplier's PDF with the PO number buried in a free-text line still finds its order. It handles the many-to-many cases that break line-level rules, such as one invoice spanning three purchase orders or a delivery split across two receipts. And it holds the customer-specific rules that used to live in someone's head.
That third one is where the difference compounds. At Xpol, 25 customer-specific rulesets covering unit conversions and multi-depot splits were encoded into the agent instead of remaining the private knowledge of a retiring specialist, which is also how roughly 20 minutes of manual handling per large order was removed across about 150 orders a week. Topa Bathroom Products reached over 90% straight-through processing into Business Central on the order side, with confirmations back to the customer inside 30 seconds and four FTEs redeployed onto after-sales.
Our reading is that this is the actual buying decision. Rules-based matching plateaus at whatever your rules cover, and every new supplier quirk needs a person to write a new rule. An agent that captures the resolution the first time a human clears an exception keeps improving without that project.
"It's a matter of building trust in the organisation with these kinds of initiatives. You can't just throw something like this over the fence."— Cees Maaskant, General Manager, Xpol
Which invoice matching software fits which company?
The market splits into four groups, and telling them apart matters more than any feature grid, because they are bought for genuinely different reasons.
- ERP-native matching. Free, already installed, and adequate when your purchasing is straightforward. Business Central and SAP both do the core match. Start here and find out what actually fails before you buy anything.
- AP automation suites. Basware, Medius, Coupa and, in North America, AvidXchange, which TPG acquired in partnership with Corpay for 2.2 billion dollars in a deal announced in May 2025 and completed that October. These bundle capture, matching, approval workflow and supplier portals. Strong fit when you want the whole AP department in one system and have the change budget to move it there.
- Capture-led products. OCR and template-driven extraction feeding your ERP. Cheaper, narrower, and they behave well until a supplier changes a layout.
- AI agents. Read the document, apply your rules, post the result and route exceptions with context. This is what we build, and it fits companies whose difficulty is variety rather than volume.
None of the vendors in group two publish rate cards, so budgeting means a sales conversation in every case. Lleverage publishes its pricing: one monthly price per agent, from €2.000 per month, with integration and AI usage included rather than metered.
How should you evaluate invoice matching software?
Take your last month of failed matches, not a sample of clean ones, and put that stack in front of every vendor. It is the only test that distinguishes the four groups above, and it takes an afternoon to assemble.
Then ask five questions, in this order:
- What percentage of these invoices, the ones that already failed, would post without a human? Never accept a touchless rate measured on clean documents.
- When a match fails, what does the person who has to fix it see? Assembled context, or a line item and a link to the ERP?
- Who resolves a price variance, and does the system remember the resolution for next time?
- Does it handle our awkward purchasing, meaning blanket orders, subcontracting, project-linked POs and intercompany, or does that stay manual?
- What is the total annual cost including implementation, and is any of it metered by volume?
Question one usually ends the process on its own. The company brain that stores your rules and exceptions is what turns a resolved exception into a permanently solved one, and any product that cannot answer question three is asking you to keep a person on the queue indefinitely.
Frequently asked questions
What is the difference between 2-way and 3-way invoice matching?
A two-way match compares the supplier invoice against the purchase order only, checking price and quantity billed. A three-way match adds the goods receipt, so you also confirm the goods physically arrived before paying. Two-way suits services and freight; three-way is the standard control for physical goods.
Does Business Central need separate invoice matching software?
Not for basic matching. Business Central natively matches invoice lines to purchase order and receipt lines through the Get Order Lines and Get Receipt Lines actions, with a Matched Order Lines page for reviewing discrepancies. Microsoft documents limits around prepayments, blanket orders, subcontracting, project-linked and intercompany purchasing, which is where most buyers add something.
How much does invoice matching software cost?
Most AP automation vendors do not publish pricing, so expect a quoted figure driven by invoice volume, supplier count and connected systems. Lleverage publishes its own: one monthly price per agent, starting from €2.000 per month, with integration and AI usage included rather than billed by volume.
Can invoice matching be fully automated?
The routine matching can be. The judgement cannot, and should not be. A well-configured agent posts clean matches without a person and resolves common exceptions from learned rules, while genuinely ambiguous cases, such as a disputed price change, still go to a human with the full context attached.
What causes most invoice matching exceptions?
Quantity variances from partial deliveries, price differences between the PO and the invoice, missing or late-posted goods receipts, invoices spanning several purchase orders, and invoices arriving with no usable PO reference. Very few are supplier errors; most are timing and structure problems inside your own process.
Bring us the invoices that already failed
Any product will match a clean invoice. Send us the exceptions from last month, the partial deliveries, the price variances and the invoices that span three purchase orders, and we will run an accounts payable agent against them so you can see what posts and what does not.
Book a demo with Lleverage with your own failed matches. If your ERP already handles them, we will tell you that instead.