A Three-Way Match for Work You Cannot Count
Three-way matching compares what you ordered, what arrived and what you were billed. For a service, "what arrived" has no count. It still needs an answer before money moves, and the answer is a confirmation.
For the meeting
A delivery confirmation on a service line counts as received in the three-way match, exactly as a check-in does for goods. An order is not ready to pay while a service on it is unconfirmed, a payment past a failed match needs its own permission and a written reason, and a services-only order is paid through the normal supplier payment ledger and booked once.
The point of a three-way match is that nobody pays for something on the strength of the bill alone. The order says what was agreed, the receipt says what turned up, and the bill has to agree with both. When they disagree, payment waits.
Goods give you the middle document for free: the storekeeper counts the delivery. Services do not, which is why many organizations quietly exempt them from matching altogether. That exemption is where invoiced-but-not-delivered work gets paid. What three-way matching is has the full background.
The confirmation is the receipt
When someone confirms a service line was delivered, as described in buying a service you cannot count, the match reads that confirmation as the received quantity for that line. Ordered one month of cleaning, confirmed one month: the line matches. Nothing confirmed: the line has not been received.
| Order | Goods | Service | Payment |
|---|---|---|---|
| Goods and a service | Checked in | Not confirmed | Blocked: discrepancy |
| Goods and a service | Checked in | Confirmed | Ready, if the bill agrees |
| Service only | None | Confirmed | Ready, if the bill agrees |
| Goods and a service | Check-in awaiting approval | Confirmed | Blocked until the check-in is approved |
The first row is the one that matters most. An order where the goods have arrived and the installation has not been confirmed looks, to the match, exactly like a short delivery. It is held for the same reason.
Exempting services from the match is how invoiced work that never happened gets paid.
Overrides are a separate decision
Sometimes paying past a failed match is right: a deposit, a disputed line being paid in part, a supplier you cannot afford to lose. The match can be overridden, but only by someone holding a permission set aside for that, separate from approving orders, and only with a written reason. Who overrode it and when is stamped on the order.
Payment before anything has been received is a separate setting. By default it warns rather than refuses, because prepayments are ordinary; an organization that wants it refused can switch that on. Every tolerance ships at zero explains the tolerance settings behind the match.
Paying a services-only order
An order with no goods on it is paid the same way as any other: through supplier payments, by any of the methods your workspace uses. The payment is booked once against the supplier's payable that the confirmation raised, so the cost is not recognised twice.
Four questions for your payables team
Are service orders matched before they are paid?
Likely answer
Usually not.
What to do
That is the exemption this closes. Confirm service lines before the bill is approved.
Who confirms a service was delivered?
Likely answer
Whoever raised the order.
What to do
Better: whoever would have signed for goods. Keep the person who ordered and the person who confirms separate where you can.
Who can pay past a failed match?
Likely answer
Anyone who can pay.
What to do
Give the override permission to as few people as possible and read the reasons monthly.
Do we pay before receipt?
Likely answer
Sometimes, for deposits.
What to do
Decide whether that should warn or refuse, and set it.
Tighter controls for service-heavy spend
The match now covers services. These go further for organizations whose spend is mostly services.
Confirmer separate from orderer
Refuse a confirmation from the person who raised the order.
Evidence on a confirmation
Attach a timesheet, a job card or a signed completion note to each confirmation.
Withholding on direct order payments
Calculate withholding when a services order is paid without a supplier bill.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your workspace and maintained with the product.
Talk to us about payablesWhat AWRA OpsHub does today
- Service confirmations counted as received in the three-way match.
- Payment held on an order whose service lines are unconfirmed, or whose check-ins await approval.
- Overrides behind their own permission, with a written reason and a stamp of who and when.
- A setting to refuse payment before receipt, warning by default.
- Services-only orders paid through supplier payments, booked once against the payable.
More we can add to your workspace
- Separation of orderer and confirmer, refusing a confirmation from the person who raised the order.
- Attachments on a confirmation, such as a timesheet or completion note.
- Withholding calculated on a direct order payment for services, alongside the withholding already applied on supplier bills.
Where we point you to a specialist
- We do not decide when your organization may pay before receipt. The setting is there and it is yours to turn on.
Each item in the middle column can be scoped for your workspace.
Match your next service order
Confirm the service line, then open the match. The feature page has the full purchase flow.
See how service items workFrequently asked questions
Does three-way matching work for services?
Yes. A delivery confirmation on a service line counts as the received quantity, just as a check-in does for goods.
Can I pay an order whose service has not been confirmed?
Not without an override. An unconfirmed service line is a discrepancy in the match, and paying past it needs a separate permission and a written reason.
How is a services-only order paid?
Through supplier payments, like any other order. The payment is booked once against the payable raised by the confirmation.
Can we refuse payment before anything is received?
Yes. By default it warns; your organization can switch it to refuse.
