Three-way matching sounds like something only big companies with an accounts-payable department bother with. It isn’t. It’s three questions asked before you pay any bill: what did I order, what did I receive, and what is the vendor charging? When all three agree, pay. When they don’t, you’ve just found money.
The name comes from matching three documents against each other. For a business your size the practice is a ninety-second check done at the counter with a phone in your hand. No software requirement, no approval workflow, no finance team. Just the habit of not paying a bill you haven’t checked.
Most small businesses already do a version of this, badly, from memory. Somebody looks at a bill, thinks “that seems about right”, and pays it. That’s a feeling rather than a match, and feelings tend to agree with whoever prepared the invoice. What the upgrade takes isn’t effort so much as timing and evidence.
Worth saying plainly, because people get squeamish about this: none of it assumes your vendors are cheating you. Almost every mismatch you’ll find is an honest mistake, a picking error, an invoice raised from the order rather than from what actually went on the vehicle, a rate that changed in their system and not in your agreement. Vendors generally fix these without argument the moment you point them out. The problem is that nobody points them out, because nobody checks.
The three documents
Each of the three answers a different question, and each gets created by a different person at a different moment. That’s the whole reason the match works. Three independent records are hard to get wrong in the same direction.
| Record | Answers | Made by |
|---|---|---|
| Purchase order | What did I ask for, at what price? | You, when you placed the order |
| Goods receipt note | What actually arrived? | Whoever received the delivery |
| Invoice | What is the vendor charging? | The vendor |
None of these has to be a formal document. Your purchase order can be the WhatsApp message you sent. Your goods receipt note can be a photo of the delivery challan with the counted quantities written on it in biro. The invoice is whatever the vendor sends. What matters is that all three exist, that you can find them, and that they’re attached to the same order. Here’s the fuller explanation of how the three fit together.
If you can only manage two of the three, keep the order record and the receipt record. Those are the two you create yourself, and they’re the two that go missing.
How the match works
Take a realistic shape of order. A café orders 30kg of coffee beans at ₹900/kg, delivery Tuesday. The message goes out on Saturday evening and the vendor replies “ok, Tuesday 👍”.
Tuesday morning the delivery arrives. The assistant manager counts it: 25kg. The driver says the rest is coming Thursday. She writes “25kg received, 5kg short, balance Thursday” on the delivery note, photographs it, and records the received quantity against the order.
Friday the invoice arrives by WhatsApp. It bills 30kg at ₹900, so ₹27,000.
Now the three-way match, one line at a time:
| Ordered | Received | Invoiced | |
|---|---|---|---|
| Coffee beans | 30kg | 25kg | 30kg |
| Rate | ₹900/kg | — | ₹900/kg |
| Value | ₹27,000 | ₹22,500 | ₹27,000 |
The price matches. The quantity doesn’t. You’re being billed ₹4,500 for coffee sitting in somebody else’s warehouse, and if the Thursday balance never turns up, which happens more than anyone likes, that’s ₹4,500 gone.
The resolution conversation
This is the part people dread, and it’s genuinely not dramatic. The message is short, factual and accuses nobody of anything:
Hi, invoice #4412 bills 30kg but we received 25kg on Tuesday (5kg short, balance was promised Thursday and hasn’t come). Can you send the balance, or a revised invoice for 25kg?
Three things make that message work. It cites the invoice number, it states the received quantity and the date, and it offers the vendor two acceptable outcomes instead of demanding one. Nine times out of ten you get a revised invoice or the balance stock within a day, because the vendor’s own delivery record agrees with yours.
Compare it with what you send when you have no receipt record: “I think we got less than 30, can you check?” That’s an opening bid rather than a claim, and you’ll lose it.
A lightweight process for small teams
The biggest improvement most businesses can make has nothing to do with matching better. Do it earlier.
Match when the invoice arrives, not at month end
Month-end matching fails for one simple reason: the person doing it wasn’t present at any of the three events. By the 30th nobody remembers the truck on the 8th, so the invoice gets paid, because arguing needs evidence nobody has.
When the invoice arrives you’re within days of the delivery. The person who received it is still in the building, still remembers, and the delivery note is still on the clipboard. The check takes ninety seconds and it either closes cleanly or catches something while it’s still catchable.
The ninety-second version
- Open the order. Read what you asked for and the agreed rate.
- Read the received quantities recorded on delivery.
- Read the invoice line by line against both.
- If everything agrees, mark it approved for payment and move on. If it doesn’t, send the message above before it goes in the payment pile.
Step four is the one with teeth. A queried invoice must not be able to get paid by accident. Whether that means a separate pile, a flag or a status on an order board, keep disputed bills physically or logically apart from approved ones.
Who should do it
Ideally not the same person for all three steps, though in a small business that’s a luxury you may not have. What you can always arrange is that the person who receives goods isn’t the person who approves the payment. That says nothing about anyone’s honesty; it’s just why two independent records beat one careful one. If it really has to be one person, the compensating control is that the received quantity gets written down at the door, before the invoice is ever seen, so the count can’t be quietly shaped by what the bill says.
The owner doesn’t need to run every match. The owner needs to see the exceptions. A five-second daily question, “anything queried today?”, is enough supervision for most small businesses, provided queried invoices can’t sneak through to payment while nobody’s looking.
Tolerance: don’t chase ₹40 on a ₹40,000 order
Rounding, a rate that moved by a rupee, a weight that differs by 200 grams. Chasing every one of these costs more in time and vendor goodwill than it recovers. Set a tolerance you’re comfortable ignoring on a single invoice. Many small businesses land somewhere around one percent, or a fixed rupee amount, whichever is smaller. Pick the number once and stop rethinking it per invoice.
But tolerance applies to single invoices, never to patterns, and that half is the one people forget. Forty rupees on one order is noise. Forty rupees on every order from the same vendor for six months is a pricing decision they made and didn’t mention. Your tolerance is there to stop you being petty. It should never stop you noticing.
So run two checks at two different speeds: the per-invoice match, which is fast and forgiving, and a monthly glance at whether the same vendor keeps landing just inside the line.
Common mismatches and what they mean
Price creep
The invoice rate is higher than the rate you agreed. Usually genuine: input costs moved, the vendor updated his system, nobody told the person who takes your orders. Occasionally not. Either way the fix is identical. Ask, and get the new rate in writing before the next order rather than discovering it again on the next invoice.
Price creep is the mismatch most likely to stay invisible without a purchase order record, because the invoice on its own looks perfectly reasonable. You only catch it by comparing against what you were quoted.
Quantity gaps
Billed more than arrived, which is the short-delivery case above. Almost always a timing problem rather than dishonesty: the vendor invoices from the picking list, not from what went on the vehicle. It resolves easily if you have a received-quantity record. Without one it’s your word against a document. Recording deliveries properly is the single control that makes this category winnable.
Double invoicing
The same delivery billed twice, usually weeks apart, usually because a manual invoice went out and then the system raised another. This is the one most often paid twice, because each invoice looks correct in isolation. The defence is matching every invoice to a specific order: an invoice you can’t tie to an unbilled delivery is either a duplicate or something you never received.
Unordered items
Goods on the invoice that you never asked for. Sometimes a substitution the driver made without telling anyone, sometimes another customer’s line ending up on your bill. You are not obliged to pay for goods you didn’t order and didn’t accept. If you did accept a substitution at the door, fine, but whoever accepted it should have written it on the delivery record, which turns a dispute into a note.
Right goods, wrong bill
Easy to miss, so worth naming: everything matches except the invoice is addressed to the wrong business, or carries the wrong tax details. It doesn’t change what you owe, but it can change what you’re able to claim. Query it the same day. Vendors reissue these without argument.
When a mismatch keeps repeating with one vendor
One mismatch is an error. The same mismatch every month is a process, theirs, not yours.
This is where matching stops being an accounting chore and starts being management information. If one vendor short-delivers on a third of orders, that’s a supply reliability problem more than an invoicing one, and it’ll be showing up as late deliveries and slow confirmations too. The invoice is simply where it becomes measurable.
The conversation to have isn’t about the individual invoice. Try: “Four of the last ten deliveries were short, and each time we had to chase a revised bill. What changed?” You can only say that if you kept count, which is the entire argument for scoring vendors on the record rather than on gut feel. You already generate the data every time you match an invoice. The only question is whether anyone adds it up.
And notice which direction the errors run. Occasional mistakes in both directions, sometimes over and sometimes under, are ordinary human error. Errors that consistently favour the vendor are a different kind of finding, and worth a very direct conversation.
Keep reading
- Purchase order vs invoice vs GRN explains the three documents in the match properly.
- What a goods receipt note (GRN) is covers how to record what actually arrived, short deliveries included.
- How to measure vendor reliability is for when the same vendor keeps producing mismatches.