Accounts Payable & Invoicing · Checklist
Accounts Payable Month-End Close
Use this template to run the AP close as a tracked checklist rather than a shared spreadsheet and a long evening without…
Explore templateThree-Way Match Exception Template
Give the match exception process one front door, one owner and one visible status. Built for finance teams in manufacturing.
- Stages
- 6
- Fields
- 8
- Automations
- 4
- Setup
- 10 minutes
Three-Way Match Exception Exception Workflow · Accounts Payable & Invoicing
- 1Issue raised
- 2Triage
- 3Investigation
- 4Counterparty follow-up
- 5Resolution agreed
- 6Closed and analyzed
Quick answer
The Three-Way Match Exception template is a pre-built AP automation workflow used to resolve mismatches between purchase order, goods receipt and invoice before payment. It runs across 6 stages, from issue raised to closed and analyzed, captures 8 standard fields including invoice reference and po value, and applies 4 automations so routing, checks and record-keeping happen without manual chasing.
What you get with the Three-Way Match Exception template
The template gives the match exception process a defined shape. Submission captures 8 fields up front, which removes the back-and-forth that normally follows an incomplete request. From there the record moves through 6 stages, each with its own owner and exit condition, and 4 built-in automations apply checks and routing consistently rather than depending on who is available. It suits finance teams in manufacturing that need control and an audit trail without adding administrative work, and it syncs with SAP and Oracle NetSuite.
The problem it solves. Mismatches are discovered at payment run, which is far too late and usually means a delayed supplier payment. With the workflow running in Zapro, the status is the same wherever you look at it from.
From request to closure in 6 stages
Every match exception follows the same 6 stages, so anyone can see where a record is without asking. Stages, owners and exit conditions are configurable if your policy differs.
-
Issue raised
Anyone can log the match exception with the reference document, the amount in question and supporting evidence.
-
Triage
Zapro categorizes the issue, assigns severity and routes it to the team that can actually resolve it.
-
Investigation
The owner gathers the related documents and transaction history from the linked records in one place.
-
Counterparty follow-up
Supplier or internal follow-up happens in a shared thread that stays attached to the case.
-
Resolution agreed
The corrective action, credit or adjustment is agreed and approved by the AP manager.
-
Closed and analyzed
The case closes with a root-cause code so recurring issues become visible instead of invisible.
The data this template collects up front
These 8 fields are pre-configured on the intake form. Mandatory rules, picklists and validation are already applied, so a match exception cannot progress with gaps in it.
- Invoice reference
- PO reference
- Goods receipt reference
- Mismatch type
- PO value
- Received quantity
- Invoiced value
- Resolution
The manual steps this template removes
Automatic three-way match on receipt
This runs as a built-in rule, which removes the follow-up chasing that usually surrounds it.
Tolerance rules by supplier and category
Zapro applies this to every match exception as it enters the workflow, so nobody has to remember to do it.
Exception routing to buyer or receiver
Configured once during setup, then enforced consistently on every record without further effort.
Resolution recorded against the invoice
It triggers the moment the condition is met, so nothing waits on someone noticing it first.
What teams get out of this template
- Invoice exceptions surface early instead of at close
- Approval status is visible to the business and the supplier
- Duplicate and mismatched invoices are caught before payment
- Month-end stops being a reconciliation scramble
- The team can resolve mismatches between purchase order, goods receipt and invoice before payment from a single record
Manual process versus the Three-Way Match Exception template
| Aspect | Manual process | With the Zapro template |
|---|---|---|
| Match exception handling | Mismatches are discovered at payment run, which is far too late and usually means a delayed supplier payment | One workflow that helps you resolve mismatches between purchase order, goods receipt and invoice before payment |
| Data quality | Re-keyed between spreadsheets and the ERP | Captured once, validated at entry, synced to the ERP |
| Audit readiness | Evidence reassembled from mailboxes at audit time | Complete trail generated as the work happens |
| Cycle time | Depends on who is chasing this week | Predictable, with reminders and escalation built in |
| Status visibility | Chase people on email or Slack to find out where it is | Live status on every record, visible to requester and approver |
Systems this template connects to
Zapro connects to your existing systems so this template becomes part of the process rather than another place to check.
- SAP
- Oracle NetSuite
- Microsoft Dynamics 365
- Slack
- Microsoft Teams
- Zapro Supplier Portal
Guides that go with this template
- AP Automation
The Zapro product page behind this template and everything it connects to.
- Purchase Order Process
Why the PO is the anchor for invoice matching.
- Accounts Payable Automation Guide
The definitive guide to automating accounts payable.
Three-Way Match Exception template FAQs
What is the Three-Way Match Exception template?
It is a pre-built AP automation workflow in Zapro that lets finance teams resolve mismatches between purchase order, goods receipt and invoice before payment. Each match exception is captured on an 8-field form, moves through 6 stages with a named owner at each step, and is supported by 4 automations covering routing, validation and record updates.
How long does the Three-Way Match Exception template take to set up?
Most teams have it running in about 10 minutes. The stages, fields and automations are already configured, so setup is mainly adjusting approval thresholds, field labels and owner assignments to match your own policy.
Who uses the Three-Way Match Exception template?
Primarily AP managers, working with AP clerks and finance controllers. It is most commonly used by finance teams in manufacturing, though the workflow itself is not sector-specific.
Does this handle non-PO invoices?
Yes. Non-PO invoices follow a coding and approval path instead of a match path, and both types sit in the same queue with the same visibility.
What matching tolerances are supported?
Quantity, price and total tolerances are configurable by supplier and category, and anything outside tolerance is routed as an exception rather than blocked silently.
Get the Three-Way Match Exception workflow live
Zapro ships with this template plus the rest of the procurement and vendor management suite. Start with the match exception process and expand into sourcing, contracts, invoices and spend when you are ready.