Fintra Feature
Catch overbilling before you pay it, not after
3-Way Match Queue
Example figures- MATCHED CLEAN
- 28
- this month
- DISCREPANCIES
- 3
- $2,140 total
- AVG MATCH TIME
- < 1 min
- per bill
- PO #4021: bill matches receipt exactly
- $6,200
- PO #4033: billed qty exceeds receipt
- $840 over
- PO #4040: unit price above PO rate
- $310 over
- PO #4055: matched, released for payment
- $4,975
What 3-way match in Fintra does
Overbilling rarely looks dramatic: a slightly higher unit price, a quantity rounded up, a line added that was never ordered. Three-way match catches exactly this: Fintra automatically compares the vendor bill against the original purchase order and the goods receipt confirming what actually arrived, before the bill is eligible for payment approval.
- Automatic comparison of bill quantity and price against the PO
- Cross-check against goods receipt to confirm what was actually received
- Tolerance thresholds you set for acceptable variance before flagging
- Discrepancies routed for review instead of blocking the whole bill silently
Core capabilities
| Capability | What it does | What it replaces |
|---|---|---|
| PO comparison | Checks billed price and quantity against the purchase order | Trusting the invoice at face value |
| Receipt comparison | Confirms billed quantity against what was actually received | Paying for goods that never arrived |
| Tolerance thresholds | Allows small, defined variances without flagging every bill | Flagging every rounding difference as an error |
| Discrepancy routing | Sends mismatches to a reviewer with the exact variance shown | Discovering overbilling during a later audit |
| Match history | Keeps a record of every match result per bill and vendor | No record of how often a vendor overbills |
How it works
From bill arrival to a clean or flagged match
Bill arrives
A vendor bill referencing a PO number is captured in the AP inbox.
System pulls the PO and receipt
Fintra retrieves the original purchase order and any goods receipt recorded against it.
Compare automatically
Quantity and price are compared across all three documents within your defined tolerance.
Route the result
A clean match proceeds to normal approval; a discrepancy routes to a reviewer with the exact variance.
Resolve or approve
The reviewer approves a justified variance or sends the bill back to the vendor before payment.
A worked example
Questions people ask
What exactly does 3-way match compare?
It compares the purchase order (what you agreed to pay), the goods receipt (what actually arrived), and the vendor bill (what you’re being asked to pay): checking that quantity and unit price agree across all three within a tolerance you define, before the bill is eligible for payment approval.
What happens when there’s a discrepancy?
The bill is held from normal approval and routed to a reviewer with the specific variance shown, for example, billed quantity 12 units above the goods receipt. The reviewer can approve a justified variance or send the bill back to the vendor rather than paying an unexplained difference.
Can I set tolerance levels for acceptable variance?
Yes. Small variances, a rounding difference or a minor price adjustment within an agreed range, can be set to pass automatically, so 3-way match flags genuine discrepancies rather than every immaterial difference between documents.
Does 3-way match require a purchase order for every bill?
No. It applies to bills that reference a purchase order and goods receipt. Bills without a PO (a recurring software subscription, for example) go through the standard AP approval process without a three-way match step.
Keep reading
Guides
Calculators
One finance briefing a week
New guides, checklists and benchmarks, by email. Unsubscribe from any issue.
Stop paying for what you didn’t order
Talk to us: we will map it to your stack. Match your next PO-backed bill automatically before it’s approved.