Three way matching is the control that keeps you from paying for goods you did not receive at a price you did not agree. Sage recognized its importance and, in 2026 Release 2, added AI driven line level document matching across purchase orders, receivers and vendor invoices.

That handles the clean cases better than a rigid rule ever did. The interesting question is what happens when a line does not match, because that is where money and time are actually spent.

Invoice Capture
Dimension Coding
Three Way Matching
Approval Routing
Duplicate Detection

What native line level matching does

The 2026 Release 2 enhancement matches at the line level rather than only the header, which catches partial receipts and split lines that a header match would miss. It increases accuracy and reduces manual intervention on the straightforward cases.

For most bills that match cleanly, this is enough, and it should be left to run.

The exceptions that remain

A price on the invoice higher than the purchase order.
A quantity billed greater than the quantity received.
A receiver that has not been posted yet.
A tax or freight line that does not appear on the order.
A unit of measure mismatch between systems.

Controls are routine until they are not

Matching is a control that runs quietly all month, which is why its exceptions get postponed.

I remember posting depreciation entries and when I was in big four accounting as an auditor.

Chris Ortega, on the AgentCFO podcast

Set a limit on how long an unresolved match can sit, and report anything older at close.

Rule versus reasoning

A rule can flag that a price is off by more than a tolerance. It cannot tell you the vendor raised the price under a contract clause, or that the receiver is late rather than missing. Reasoning over the purchase order, the receipt history and the contract can propose a resolution rather than just raising a flag.

A matching exception resolved and routed for approval

Tolerances that fit the business

Not every variance deserves a human. A few cents of rounding should pass. ChatFin lets tolerances vary by vendor, amount and category, so small differences clear automatically and only meaningful variances stop for review. This mirrors the governed approach across the full AP flow.

Resolving end to end

When a variance is real, ChatFin gathers the context, proposes a resolution, and routes it to the right person with everything attached. The approver decides in seconds because the work of investigating is already done. Duplicate checks run alongside, covered on duplicate and error detection.

Why this beats a portal

A separate matching portal creates a second source of truth and another screen to check. ChatFin resolves matching inside one governed flow that ends in a bill posted through the Intacct REST API, using native matching where it helps.

The outcome

Clean bills flow, real exceptions get resolved fast, and the AP team stops chasing paperwork. The reconciliation and matching tools guide puts this in the wider context of matching across finance.

Match Every Sage Intacct Bill, Resolve Every Exception

Sage Intacct matches bills with AI at the line level. ChatFin resolves the exceptions end to end and routes only genuine variances to a person.

Book a demo to run your matching exceptions through ChatFin on Sage Intacct.

Book a Demo

What happens to the bills line level matching cannot clear

Native line level matching clears bills that agree with their purchase order and receiver. The remainder is where payables time goes: a price changed after the order, a partial delivery, a unit of measure that differs. Each needs a decision about who is right.

A rule can say that two numbers differ. It cannot say that the supplier always invoices per case when the order is per unit. Reasoning over history can, and it can route the exception to the person who owns that supplier, with the evidence attached.

Teddy Collins, EVP of Finance at SeatGeek, spoke about the accounts payable desk on the AgentCFO podcast.

“Not everything needs an AI solution. If something's deterministic and it's if this then that and it's repeatable, let's use some other tools like RPA, like other middlewares have been around for a while. Let's keep that in the deterministic bucket.”

Teddy Collins, EVP of Finance at SeatGeek. AgentCFO podcast, episode 10

Mismatch cases and who should see them

Examples from a typical three way match queue.

  • Price above the order. Sent to the buyer with the contract price shown, since only they can say whether the increase was agreed.
  • Partial delivery. Held until the receipt arrives, with a reminder to the receiving contact, rather than rejected.
  • Unit of measure difference. Recognised from prior bills for the same supplier and converted, with the conversion noted for the reviewer.
  • Invoice with no order. Routed to the budget owner, who can say whether it was expected spend.

Quick Answers on Two Way and Three Way Matching in Sage Intacct

What is three way matching?

Comparing a bill to its purchase order and to the goods receipt before paying. Two way matching compares only the bill and the order.

Does Sage Intacct do line level matching natively?

This page says Sage Intacct added AI line level matching in 2026. What it leaves is the set of exceptions that need judgment about who is right.

Why use tolerances in matching?

Small differences, such as rounding or freight, are not worth a person's time. Tolerances that fit your business let those clear and keep attention on material gaps.

Why is matching in the ledger better than a supplier portal?

This page's view is that matching inside Sage Intacct sees the actual lines, dimensions and history, so the exception can be resolved end to end rather than bounced between systems.

Related Articles