Invoice matching agent

Invoices matched. Only exceptions reach finance.

Each invoice is checked against its purchase order and receipt, and each exception arrives with the reason it did not match.

About 5 weeks
to live on real traffic
Founder-led
no handoff to juniors
Fixed price
agreed before work starts
INV-14884 Three way match Matching 1 line for review
InvoiceINV-14884$1,625.00Supplier, 4 Nov
Purchase orderPO-7731$1,495.00Ops buyer, 21 Oct
Goods receiptGR-55202,600 items inWarehouse, 2 Nov
LineInvoicedOrderedReceivedResult
Steel brackets, 40mm500500500 Waiting Checking Matched
Hex bolts, M82,0002,0002,000 Waiting Checking Matched
Mounting plates120100100 Waiting Checking Over the PO
Freight111 Waiting Checking Matched
Today matched for payment
InvoiceTotalStatus
INV-14884$1,625.00In review
INV-14883$812.40Ready to pay
INV-14882$4,960.00Ready to pay
INV-14881$1,240.00Ready to pay
INV-14880$318.75Ready to pay
INV-14879$2,050.00No receipt yet
The problem

Finance keys invoices by hand and chases every mismatch by email

Month end means overtime, and when an auditor asks why an invoice was paid, the answer is in someone’s inbox.

8.2 days

is the average time to process one invoice.

Sourcepayablesplace.ardentpartners.com

18.4%

of invoices hit an exception, on average.

Sourcepayablesplace.ardentpartners.com

How we fix it

Code matches the invoices, and people look only at the exceptions.

What changesWithout itWith it
Data entryKeyed by hand.Read, with a confidence per field.
MatchingChecked line by line.Two- and three-way match in code.
ExceptionsFound late, explained by email.Flagged with the reason and logged.
How it works

What we build

What changes for your teams. We pick the tools to fit the systems you already run.

InvoiceINV-14884$1,625.00Supplier, 4 Nov
Purchase orderPO-7731$1,495.00Ops buyer, 21 Oct
Goods receiptGR-55202,600 items inWarehouse, 2 Nov
LineInvoicedOrderedReceivedResult
Steel brackets, 40mm500500500 Waiting Checking Matched
Hex bolts, M82,0002,0002,000 Waiting Checking Matched
Mounting plates120100100 Waiting Checking Over the PO
Freight111 Waiting Checking Matched
What changes

Measured against where you started

Example: Acme Inc

What changes at a company like Acme Inc

Illustrative figures, not a client result. Your own baseline is taken in the first week.

MeasureBeforeAfter
Invoices keyed by handAll 4,000 a monthOnly the fields the model is unsure of
Time to process an invoice8 days1 day
Exceptions with a written reasonFewEvery one
Month-end overtimeEvery monthRare

How others built it

Another company built the same kind of system and wrote publicly about how it went.

What you keep

Everything runs in your cloud, and stays yours

You own the config, the tests and the runbooks, so you can swap any part later.

The agent running in your cloud, connected to your ERP.

Today matched for payment
InvoiceTotalStatus
INV-14884$1,625.00In review
INV-14883$812.40Ready to pay
INV-14882$4,960.00Ready to pay
INV-14881$1,240.00Ready to pay
INV-14880$318.75Ready to pay
INV-14879$2,050.00No receipt yet

Your matching rules and tolerances as code, with tests.

InvoiceINV-14884$1,625.00Supplier, 4 Nov
Purchase orderPO-7731$1,495.00Ops buyer, 21 Oct
Goods receiptGR-55202,600 items inWarehouse, 2 Nov
LineInvoicedOrderedReceivedResult
Steel brackets, 40mm500500500 Waiting Checking Matched
Hex bolts, M82,0002,0002,000 Waiting Checking Matched
Mounting plates120100100 Waiting Checking Over the PO
Freight111 Waiting Checking Matched
  • An audit log of every match, exception and approval.

  • A runbook your finance team owns.

Typical building blocks: Docling or Azure Content Understanding with per-field confidence; Pydantic total checks; a deterministic two- or three-way match in code; the ERP through official MCP servers (NetSuite, QuickBooks, Xero) or SAP APIs; a model only for fuzzy matches; an audit log.

Alternatives: Rossum; Unstract (AGPL).

How the weeks run

Live in about 5 weeks

The work happens in your cloud, with the people who will own it.

  1. Week 1Sample your invoices, map your matching rules and build the test set.
  2. Weeks 2 to 4Build reading and matching, and run it beside your team on live invoices.
  3. Week 5Switch on posting for the first suppliers and hand over the runbook.
  4. After thatRunning on real traffic

    Invoices matched, every exception explained.

Before we start

  • At least 200 past invoices with their outcomes.
  • API access to your ERP, or a sandbox copy of it.
  • A named finance owner for the matching rules, about 3 hours a week.
Fit

Is this the right first build?

It fits when

  • Finance keys invoices by hand.
  • A mismatch is found late.
  • A team on your side will own it after we leave.

It does not fit when

  • You want a hosted tool picked and resold to you.
  • You want a strategy deck in place of working software.
  • Nobody on your side can own it after we leave.

What’s included and what isn’t

Included

  • One document family, such as supplier invoices.
  • Up to 5 layouts and 25 fields.
  • One ERP integration.
  • Matching against orders and receipts, with your tolerances.

Not included

  • Paper scanning and mail handling.
  • A second document family or a second ERP.
  • Payment runs, which stay in your ERP.
Fixed quoteOne price, agreed before work starts

About 5 weeks. You get a price range before the call and one fixed number after it. That number is the invoice.

  • If the work takes longer than we planned, we absorb the cost.
  • You pay 50% at the start and 50% at acceptance. Builds of 6 weeks or more pay 40% at the start, 30% at the midpoint and 30% at acceptance.
  • If a build starts within 60 days of your Audit results, the full Audit fee comes off its price.
  • We start three new projects a quarter, so your start date depends on when you book.
Book a demoSee starting prices
FAQ

Questions teams ask before they book

Which tools do you use?

We pick the one that fits the systems you already run. You own the config, the tests and the runbooks, so you can swap any part later. Most often Docling or Azure Content Understanding for reading, matching in code, and your ERP through its official MCP server (NetSuite, QuickBooks, Xero) or SAP APIs; Rossum or Unstract when they fit better.

Does a model decide what gets paid?

No. Matching runs as rules in code. A model helps only with fuzzy cases, such as a supplier name spelled two ways, and a person approves.

What happens when a field is unclear?

Each field has a confidence score. When a score is below the limit you set, a person checks that field before matching.

Can our auditors follow it?

Yes. Every match, exception and approval is logged with who did what and why.

Where do our invoices go?

They stay in your cloud. Reading, matching and the log run in your account.

Invoice matching agent, running in your cloud in about 5 weeks.

Invoices matched, every exception explained. You own the config, the tests and the runbooks.