Two-way matching with your exceptions encoded.

Two-way matching checks the invoice against the purchase order — what was ordered versus what was billed. Three-way matching adds the receiving report, confirming what actually arrived before payment. We encode whichever your controls require, including the tolerance levels your team applies today. Three-way match automation is the same encoded rule set with one more input — and where nothing physical arrives, as with services and pass-through work, the rules say so instead of stalling the bill.

Automated invoice matching compares invoice data with purchase orders and, where required, receiving records. We define tolerances, no-PO handling, and contract checks with your team, then test which steps can be automated and which need approval.

No-PO bills follow your no-PO logic, not a generic one. We encode how your team handles them today — which vendors are allowed to bill without a PO, which approver each one routes to, and what back-up is required — so the exception queue holds only the bills that genuinely need a decision.

AP tools vary in their support for exceptions. We assess your current system and define any additional rules needed for contract rates, pass-through terms, and vendor-specific handling, including when a person must review the result.

Available contract price sheets can become part of the matching rules. We test comparisons against invoice data and flag potential rate changes for review; coverage depends on the quality and currency of those sources.

Capture is getting the bill out of the inbox and into data — reading the emailed PDF, the scan, the photo. Processing is everything after: matching it to the purchase order, checking it against your rules, and posting it. Capture quality matters, but the exceptions in processing are where the manual work lives.

Goods received not invoiced is where matching failures surface: the delivery arrived, the invoice has not, and the accrual gets guessed at month-end. Where your flow carries receiving data, the match flags receipt-without-invoice lines as they happen, and the exception queue carries the accrual evidence — so GRNI stops being a month-end surprise.