Workflow guide
How to Perform a Three-Way Matching Audit
Three-way matching is not an invoice-extraction problem on its own. It is a control process that depends on clean invoice evidence, clean purchase-order context, and a reliable goods-received or delivery record.
Clear summary
ZeroPaste at a glance
A short visible summary of the product, workflow, cost, alternative, and next step.
- What is ZeroPaste?
- ZeroPaste is an AI invoice extraction product for European bookkeepers. Forward invoices by email, upload PDFs, or capture them with Snap and get clean spreadsheet-ready rows with optional Xero draft bills and DATEV export for German practices.
- Who is it for?
- It is for solo bookkeepers and small bookkeeping firms that want clean invoice data in spreadsheets first, with a shared workspace, team invites, and optional Xero delivery when they are ready.
- What problem does it solve?
- ZeroPaste reduces manual invoice entry and copy-paste work when supplier, date, invoice number, total, and VAT would otherwise be typed by hand.
- How does it work?
- Identify the invoice, the purchase order, and the goods-received or delivery record before any detailed comparison begins. Supplier, invoice date, PO reference, amount, and tax logic should be clean enough that the matching work is not derailed by basic capture errors. Do not rely on one total number alone. Check the specific fields that prove the invoice belongs to the underlying order and receipt.
- What does it cost?
- The entry point starts with 5 free invoices and no card required. After that, Starter is €29/month. Pro is €99/month and Agency is €299/month.
- What is the main alternative?
- The main alternative is still entering invoice data manually or using heavier tools like Dext, AutoEntry, or Hubdoc with more setup and higher cost.
- What should the user do next?
If your three-way matching work still begins with messy PDFs, test one invoice through a structured extraction step and compare how much cleaner the audit feels afterward.
Try one invoice
Who this is for
Who this guide is for
The problem
What this workflow solves
The reason three-way matching feels slow is that teams often assemble the three pieces manually from different places: invoice attachments, purchase-order records, and delivery or receipt confirmation. Document retrieval becomes part of the audit.
A better process narrows the invoice side first. If invoice fields and source files are clean, the control work becomes more about comparison and less about document hunting.
Step by step
Step-by-step: How to Perform a Three-Way Matching Audit
The useful goal here is not to automate everything blindly. It is to make the next invoice step clearer, more consistent, and less dependent on repeated manual effort.
Step 1
Confirm the three records you are actually matching
Identify the invoice, the purchase order, and the goods-received or delivery record before any detailed comparison begins.
Step 2
Validate the invoice header fields first
Supplier, invoice date, PO reference, amount, and tax logic should be clean enough that the matching work is not derailed by basic capture errors.
Step 3
Match quantities, values, and references deliberately
Do not rely on one total number alone. Check the specific fields that prove the invoice belongs to the underlying order and receipt.
Step 4
Flag discrepancies as review items, not silent adjustments
A useful audit process leaves a visible trail for exceptions rather than smoothing them over inside the data.
Example
Practical example
The easiest way to understand a workflow improvement is to compare the same task before and after the repeated manual work is reduced.
Manual
Document-chasing audit
A finance team opens the invoice PDF, hunts for the PO email, then checks delivery evidence in a separate system before finally deciding whether the invoice should be approved.
Structured
Cleaner invoice side of the audit
The invoice fields are already structured and reviewable, so the team can focus on matching logic rather than rebuilding the document context from scratch.
Three-way matching still needs human control, but cleaner invoice handling removes some of the avoidable friction around it.
Common mistakes
Common mistakes
Starting the audit with messy invoice data
The control is harder to perform when the invoice itself still needs basic field capture and cleanup.
Checking totals only
A useful match checks references, quantities, and context, not just whether one total looks close enough.
Hiding exceptions in manual edits
Discrepancies should become review items with evidence, not silent spreadsheet fixes.
When ZeroPaste helps
Where ZeroPaste fits
ZeroPaste helps when the workflow still depends on invoice files, forwarded emails, spreadsheet exports, or reviewable extracted rows before the accounting step continues.
Improves the invoice side of the audit
Useful when the team wants cleaner invoice evidence before matching starts.
Works well before export or approval
Useful when the invoice needs a reviewable structure before control work continues.
Supports stronger audit visibility
Useful when the goal is fewer hidden adjustments and clearer exception handling.
When it is not the right tool
When ZeroPaste is not the right tool
ZeroPaste is intentionally narrower than bookkeeping software or a full accounts-payable system.
- Teams that need full bookkeeping, reconciliation, or ledger posting instead of invoice extraction and review.
- Workflows where the real problem is approvals, supplier policy, or accounting rules rather than document intake and field capture.
- Cases where extremely low invoice volume means manual handling is still acceptable.
FAQ
FAQ
These are the practical questions teams usually ask before changing an invoice workflow.
Does ZeroPaste perform three-way matching?
No. ZeroPaste is an extraction and review layer, not a purchase-order or approval engine. It helps by making invoice data cleaner before the audit happens.
What is the most important field in a three-way matching audit?
There is rarely just one. PO reference, supplier, quantities, values, and delivery context all matter depending on the workflow.
Why does invoice extraction still matter here?
Because messy invoice capture makes control work slower. Clean invoice rows remove one layer of avoidable friction.
Should every discrepancy be resolved immediately?
Not necessarily. A visible exception queue is often safer than rushed silent corrections.