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:

  1. The purchase order
  2. The goods receipt or service confirmation
  3. 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:

Goods receipt or service confirmation

The receipt records what the business actually received:

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:

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:

Three-way matching adds proof of receipt.

Use it when payment should depend on delivery or completion:

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:

It should not automatically choose which document is correct.

Possible explanations include:

A buyer or operational owner resolves the exception.

Set matching rules

Define which fields must agree:

Then define tolerances.

Examples:

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:

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:

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

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:

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:

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:

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.

Back to journal Get my opportunity map