AI agentIntake-to-pay

AI two-way match agent

An AI two-way match agent pairs each invoice line with the PO line and tests description, quantity, unit price, currency and total against your tolerances.

  • People stay in control
  • Every action is logged
  • Start with a small sample
Invoice
Purchase order and open balance
Matching policy by vendor
Tolerance rule
AI two-way match agentPrepared for review
  • ✓Two-way comparison
  • ✓Open-balance check result
  • ✓Exception list
Handed toAP analyst gets differences with figures
4inputs it reads
6steps in the walkthrough
1point where a person decides
3outputs it prepares
See it run

Watch it work

Agent Record Person
Live walkthrough
  1. 1Read invoiceAgent
  2. 2Fetch the PORecord
  3. 3Compare two waysAgent
  4. 4Analyst decidesPerson
  5. 5Update balanceRecord
  6. 6Warn on exhaustionAgent

The agent reads PO number, lines and amounts.

It pulls the order and its open balance.

It checks price, quantity and totals against the PO.

An AP analyst rules on any difference.

Matched amounts reduce the PO's open balance.

It flags POs nearly fully billed.

The basics

What is an AI two-way match agent?

It decides when two-way match applies by checking the category or value against your policy, for example services or items below a threshold.

Read the full explanation

It reports a pass or lists each difference, such as a price above the PO rate, and sends the exception to the buyer.

Where it breaks

Why this step is hard by hand

Two-way match is lighter than three-way, but its simplicity makes it easy to apply carelessly to spend that really needs a receipt.

Teams disagree about which spend qualifies for two-way match.

A PO raised after the work contains whatever the buyer recalls.

Hours and fees on an invoice can exceed what the PO estimated.

Suppliers rename items, so a human has to confirm the pairing.

A pass says the bill matches the order, not that the work was done.

The path

How the agent does it

  1. 01Decide the match type

    The agent checks your policy to see whether this invoice is eligible for two-way match.

  2. 02Find the PO

    It locates the PO from the reference, or from supplier, amount and date when the reference is missing.

  3. 03Compare lines

    It tests each line for item, quantity, price and currency, and totals for the invoice.

  4. 04Apply tolerances

    It marks differences within tolerance as passes and others as exceptions.

  5. 05Send exceptions on

    It names the issue and routes it to the buyer or AP to resolve.

Want to see this flow on your own items?

Bring a small sample and watch Flo work through it.

Book a demo
Under the hood

Inside the work

AspectBy handWith the agent
SpeedAnalysts compare invoice and PO by eye.Lines are compared automatically with differences highlighted.
Open balanceOverbilling against a PO is found late.Open balance is checked on each invoice.
Service spendReceipts are skipped, so checks are loose.Two-way match is applied where the policy says receipts are not needed.
Policy fitTeams use two-way where three-way is required.The agent applies the matching type set for each vendor or spend type.
ExceptionsMismatches are emailed with no figures.Each exception carries both sets of numbers.
People and control

Who decides, and what to watch

What stays with people

  • ✓
    Define eligibilityFinance decides which categories may use two-way match.
  • ✓
    Resolve differencesBuyers decide whether a variance is acceptable.
  • ✓
    Confirm the workThe requester vouches for delivery where no receipt exists.
  • ✓
    Amend POsOnly authorised staff change an order.

Mistakes to avoid

  • ×
    Using it for physical goodsWithout a receipt, you cannot know delivery happened.
  • ×
    Raising POs after the invoiceA matched invoice proves little if the PO was written to fit it.
  • ×
    Wide tolerances on small itemsMany small variances add up.
  • ×
    No requester confirmationA match to the PO does not prove the service was delivered.

Not sure where two-way match fits in your process?

Talk it through with the team. We will map it to your steps and show where a person stays in control.

  • Works from a sample of your real items
  • Shows what Flo handles and what it hands over
  • No commitment to start
Rollout

Rolling it out

  1. 1Choose eligible spend

    Agree where receipts are not needed.

  2. 2Tag vendors

    Mark vendors with the matching type.

  3. 3Run alongside

    Compare agent results with manual checks.

  4. 4Review policy

    Revisit which spend uses two-way.

Signs you would benefit

PO overrunsBilling passes the order value unnoticed.
Slow low-risk matchingSimple service invoices take too long.
Wrong match typeTeams guess the policy.
Manual comparisonsAnalysts eyeball totals.
The numbers

How to measure it

Set your own baseline first. We do not publish benchmarks without a source you can check.
Metric 1

Two-way match exception rate

Exception rate (%) =
two-way invoices with a differencetwo-way invoices checked× 100

This shows how often bills disagree with orders. A high rate for one supplier suggests the PO terms are unclear or the supplier bills outside agreed scope.

  • Track exceptions by supplier and by category.
  • Check how many POs were created after the invoice date.
Questions

Frequently asked questions

Quick answers to what people ask most about two-way match.

Book a demo
What is two-way matching?

It is a control that compares an invoice to its purchase order only. If supplier, items, quantity and price agree, the invoice passes this check.

When is two-way match appropriate?

It suits services, subscriptions and low-value or low-risk spend where there is no goods receipt. Your policy sets the exact scope.

How is it different from a three-way match?

Three-way match adds the goods receipt as a third document to confirm delivery. Two-way match relies on the PO and invoice alone.

Does a pass mean the invoice can be paid?

No. It means the invoice agrees with the PO. Approval and any confirmation of delivery still follow your process.

Try two-way match on your own data

Bring a small sample of real items. We will show what Flo handles on its own and where it hands over to your team.

  • People approve, sign and pay
  • Every action is logged
  • Start with a small sample