Three-Way Matching for Small Businesses
Three-way matching checks that what was ordered, what was received, and what was invoiced agree before payment. Small businesses can use it without building an enterprise procurement bureaucracy.
Three-way matching compares three records before a supplier invoice is approved:
- The purchase order
- The goods receipt or service confirmation
- The supplier invoice
The question is simple:
Did we order it, receive it, and get billed according to the agreement?
Large companies often embed this check in procurement software. Small businesses tend to perform it through email, memory, and a quick message to whoever bought the item.
That informal process works until invoice volume grows, the buyer is away, deliveries are partial, or a supplier bills a different quantity or price.
Three-way matching provides a controlled answer without requiring every purchase to pass through a maze of approvals.
What each document proves
Purchase order
The purchase order records what the business authorised:
- Supplier
- Item or service
- Quantity
- Unit price
- Currency
- Tax treatment
- Delivery terms
- Project or department
- Approver
Goods receipt or service confirmation
The receipt records what the business actually received:
- Item or service
- Quantity
- Date
- Condition or completion status
- Receiving location
- Employee confirming receipt
For services, this may be an approved timesheet, milestone certificate, job completion, or named confirmation.
Supplier invoice
The invoice records what the supplier requests payment for:
- Supplier and legal entity
- Invoice number
- Purchase-order reference
- Quantity and price
- Tax
- Total
- Payment terms
- Bank details
A match confirms consistency. It does not prove every document is genuine, so supplier and payment controls still apply.
Two-way versus three-way matching
Two-way matching compares the purchase order with the invoice.
It may be enough for:
- Fixed subscriptions
- Rent
- Approved professional retainers
- Purchases where receipt is not a meaningful separate event
Three-way matching adds proof of receipt.
Use it when payment should depend on delivery or completion:
- Inventory
- Equipment
- Materials
- Project services
- Quantity-based purchases
- Milestone work
Do not require a fictional receipt simply to satisfy the system. Choose the control that reflects the transaction.
A worked example
The purchase order states:
100 units × SGD 20 = SGD 2,000
The receiving record shows:
90 units received
The supplier invoice states:
100 units × SGD 22 = SGD 2,200
The workflow should flag:
- Ten units not received
- SGD 2 unit-price variance
- SGD 400 difference from the received quantity at the approved price
It should not automatically choose which document is correct.
Possible explanations include:
- Partial delivery
- Approved price change not reflected in the purchase order
- Incorrect invoice
- Missing receipt
- Wrong purchase order
A buyer or operational owner resolves the exception.
Set matching rules
Define which fields must agree:
- Legal entity
- Supplier
- Purchase-order number
- Item or service
- Quantity
- Unit price
- Currency
- Tax
- Total
Then define tolerances.
Examples:
- Rounding difference below an approved amount
- Quantity difference only where over-delivery is permitted
- Price variance within a contractually approved tolerance
- Freight handled as a separate authorised line
Tolerances should reflect commercial policy, not a desire to increase the automatic-match percentage.
Never use a percentage tolerance that allows a material variance on a large invoice without review. Consider both percentage and absolute value.
Handle partial deliveries
Partial delivery is normal in many businesses.
The matching system needs to track:
- Ordered quantity
- Quantity received to date
- Quantity already invoiced
- Remaining quantity
- Open purchase-order value
For example:
Ordered: 100
Received: 60
Previously invoiced: 40
Current invoice: 20
Remaining received but uninvoiced: 0
Open order quantity: 40
Do not close the purchase order after the first invoice unless the remaining commitment is genuinely cancelled.
Match services properly
Services do not arrive at a loading bay.
Use appropriate evidence:
- Approved milestone
- Signed completion record
- Accepted deliverable
- Approved timesheet
- Monthly service confirmation
The employee confirming receipt should understand what was agreed. “Invoice received” is not proof that the service was delivered.
A small-business workflow
1. Create the purchase order
Record the authorised supplier, scope, value, and approver before commitment where practical. If the business does not raise purchase orders yet, start with the purchase order process guide.
2. Record receipt
The employee receiving goods or confirming services records quantity, date, and exceptions.
3. Capture the invoice
Extract supplier, invoice number, purchase-order reference, quantities, price, tax, and total.
4. Run the match
Compare documents using explicit rules.
5. Pass or route
- Exact or approved-tolerance match: proceed
- Missing document or variance: route to owner
- Duplicate or suspicious change: stop
6. Approve and prepare payment
Matching supports invoice approval. It does not replace authorised payment release.
7. Reconcile and retain evidence
Link the payment and preserve the order, receipt, invoice, decisions, and audit history.
Exception ownership
Route each problem to the person who can resolve it:
| Exception | Likely owner |
|---|---|
| Purchase order missing | Buyer or requester |
| Receipt missing | Operational receiver |
| Quantity variance | Buyer and receiver |
| Price variance | Buyer or commercial owner |
| Tax or coding issue | Finance |
| Duplicate invoice | Accounts payable |
| Bank-detail change | Supplier-master owner |
An exception queue should show amount, age, owner, evidence, and required action.
Fraud and control boundaries
Three-way matching does not prevent every payment fraud.
Keep separate controls for:
- Supplier onboarding
- Bank-detail changes
- Approval authority
- Split purchases below thresholds
- Related parties
- Urgent out-of-cycle payment
- Payment-file preparation and release
An attacker may submit a convincing invoice referencing a real order. Payment destination still needs independent control — see supplier-payment approval workflows.
When automation is worthwhile
Automation helps when:
- Purchase orders already exist
- Invoice volume is material
- Partial deliveries are common
- Finance spends time chasing receipt confirmation
- Price and quantity variances recur
- Duplicate bills appear
- Approval delays payment
It is premature when the business has no clear purchasing authority or receipt process. Software cannot match documents that nobody creates.
Start with high-value or repeat suppliers rather than forcing every petty purchase through the same workflow.
What to measure
Track:
- Invoices matched automatically
- Exceptions by type
- Missing purchase orders
- Missing receipts
- Price and quantity variance
- Time from invoice receipt to approval
- Duplicate invoices blocked
- Purchase orders remaining open incorrectly
- Manual overrides
Review repeated exceptions. Ten missing receipts from one team indicate a process problem, not ten unrelated invoice problems.
The bottom line
Three-way matching is a simple control:
Ordered
= received
= invoiced
For a small business, the best version is risk-based. Use it where delivery, quantity, price, or completion matters; define sensible tolerances; and route uncertainty to a named owner.
Automation should compare documents and surface exceptions. Authorised people should resolve variances and release payment. Matching is one stage of the wider payables workflow described in what is accounts payable automation.
Use the Calcudesk automation ROI calculator to estimate the time spent checking invoices and chasing approvals. If matching lives across email, spreadsheets, and accounting software, book a 30-minute discovery call and we will map the workflow before recommending automation.