A three-way match means checking a supplier's bill against two other documents before you pay it: the purchase order (PO) that said what you wanted, and the goods receipt that shows what actually arrived. If all three agree, you can pay with confidence. Purchase (Beta), Aicountly's purchasing app, runs this check for you when you enter a bill.
What a three-way match checks
Every supplier bill rests on two promises. You promised to buy certain items at certain rates (the PO), and the supplier promised to deliver them (the receipt, often called a GRN, short for goods received note). The bill is the supplier's claim for payment. A three-way match puts the three side by side:
- Purchase order: items, quantities and agreed rates.
- Goods receipt: what was really received, and how much was rejected.
- Supplier bill: what the supplier is now asking you to pay.
A two-way match (PO against bill) cannot catch a short delivery. Only the receipt tells you that you are being billed for goods that never reached your store.
Why it matters for a small business
Most overpayments are not fraud; they are untidy paperwork. A supplier bills for the full order when only part was delivered. A rate quietly differs from the one agreed. The same delivery is billed twice. Once the payment leaves your bank, getting it back means chasing a credit note. Matching before you post is far cheaper.
It also keeps your books clean. A bill that reaches your accounts should reflect goods you actually own and a price you actually agreed. This pairs naturally with the habits in our guide to matching your purchase register with GSTR-2B.
How Purchase (Beta) does the match
In Purchase (Beta), you enter the supplier bill against a purchase order. The bill detail screen then shows a "Three-way match" section with the three documents: the purchase order, the goods receipt and the supplier bill. The receipt is read live from Inventory at the moment of the match, and the bill reaches Smart Books only when you post it. The three documents stay in the three products; the screen compares them rather than keeping copies.
The app compares the bill at the net rate, meaning the rate after the order line's discount, so a discount agreed on the PO does not show up as a false rate difference.
The results you can see
Each match ends in one of four verdicts:
- Matched: the bill agrees with the order and with what arrived.
- Within tolerance: there are small variances, but all are inside your company's agreed limits.
- Review required: something could not be checked, so look at it before posting.
- Blocked: the bill does not agree with the order or the receipt and cannot be posted until this is resolved.
When something is off, the app lists each exception with the ordered, received and billed figures side by side. Typical kinds include a missing receipt (billed, but nothing received), over-billing (billed for more than was received and not yet billed), a rate difference and a value difference.
Setting tolerances
Insisting on exact figures to the paisa can create noise. In the profile settings, Purchase (Beta) lets a company set a tolerance policy with these limits: quantity (in percent), rate (in percent), total value (in amount), freight (in amount), and an "auto-match below" amount under which small bills are matched without line-by-line checks.
If no policy exists, matching stays exact, which is the safe default. You do not need a tolerance policy to use the app. Start exact, and add tolerance only if genuine, harmless differences keep blocking bills.
Deciding on an exception
An open exception is not a dead end. A user with the permission to resolve match exceptions can accept or reject it, and must write a note explaining why. The note is recorded against the bill, because accepting a variance can cost money. A rejected exception means the bill cannot be posted as it stands: revise it (the revision is matched afresh) or cancel it. You can also re-run the match, for instance after the missing goods receipt has been recorded.
A practical routine
- Issue the PO and record each delivery as its own goods receipt as it arrives.
- Enter the supplier bill against the PO when it comes in.
- Read the verdict. Matched or within tolerance bills can go to posting.
- For blocked bills, ask the supplier for a corrected bill or a credit note, or record the missing receipt, then re-run the match.
- Only accept a variance when you can say why in one sentence.
If goods go back, a debit note settles the bill it corrects; see our help article on creating a debit note for a supplier. And remember the tax side: the GST input tax credit on a bill depends on conditions beyond matching, covered in GST input tax credit explained for small businesses.
Key takeaways
- A three-way match compares the PO, the goods receipt and the supplier bill before payment.
- It catches short deliveries, rate changes and duplicate billing that a two-way match misses.
- Purchase (Beta) gives a clear verdict per bill and lists every exception with ordered, received and billed figures.
- Exact matching is the default; tolerances are optional and set per company.
- Accepting a variance needs a written reason, so there is a record of the decision.
Purchase (Beta) is still in Beta, so features and screens may change. If you want to try a stricter bill-checking routine, it is a good place to start. As always, confirm your specific GST and accounting treatment with your CA.