Skip to main content
GullySystem
A practical guide

Why three way invoice matching keeps failing on small orders

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 5 min read

In this guide 6 sections
The short answer

Three way matching fails on small orders because the three documents are raised by different people at different times, and small orders get the least care. Quantity, rate and tax drift apart. Rules can clear rounding and tolerance gaps. A missing receipt or a changed rate needs a named person.

Three documents, three authors

The purchase order comes from a buyer or a department head. The goods receipt note comes from a storekeeper at the gate. The invoice comes from the supplier’s billing desk. The buyer may be at a desk in another town, the storekeeper on a loading dock and the supplier in a different time zone.

None of them sees the others’ work. The buyer types a rate from last quarter’s quote. The storekeeper counts what is on the pallet. The supplier bills what the dispatch clerk reported.

Large orders get reviewed because the money is large. A box of fasteners does not, so its three documents drift. So the cheap items quietly cause the most rework per unit of purchase value, simply because nobody looks until the match fails.

How quantity mismatches arise

A supplier ships forty of fifty and promises the balance next week. The storekeeper receives forty. The supplier invoices fifty. The matcher sees ten units billed but never received. The matcher is right to flag it, but a clerk then spends twenty minutes on a ten-unit gap worth less than the time.

Pack sizes cause quieter errors. The order says 100 pieces, the supplier sends two cartons of 48 and invoices by the carton. Units of measure differ on each document.

Receipts also go in late. If the gate entry is made three days after the delivery, the invoice arrives first and fails for want of a receipt. A supplier’s invoice date can also precede the delivery date, which breaks any rule that expects the receipt to come first.

  • Part shipments invoiced as complete
  • Carton, box and piece used interchangeably
  • Receipt keyed after the invoice arrives
  • Returns not netted against the invoice

Rate and tax mismatches

Rate differences come from stale price lists. The supplier bills the new rate, the order carries the old one, and the buyer never saw the revision letter. A small supplier rarely sends one, and the buyer keeps the old rate on the order for months.

Freight and packing are added as extra lines that no order mentions. Tax lines fail when the supplier’s tax registration, the place of supply or the rate class differs from what the buyer set up in the master. Each of these lines is legitimate in the supplier’s mind and invisible in yours.

A rounding difference of one minor currency unit on a long line list can fail a strict matcher as firmly as a wrong rate.

  • Revised price not recorded on the order
  • Freight or packing line absent from the order
  • Tax code differs from the supplier master
  • Rounding on multi-line invoices

Which exceptions a rule can clear

Rules work well on predictable gaps. A tolerance for rounding, a per-line variance limit and a unit conversion table settle most of the harmless ones without a human. A good setup writes each decision to the invoice record, so the reason for every auto-clear can be read later.

Anything touching money direction needs a person: a higher rate, a quantity billed but not received, a new tax line. Route each to the role that can judge it, the buyer for rates, the storekeeper for quantity. Route each to the role that can judge it, the buyer for rates, the storekeeper for quantity, and accounts for anything touching tax codes or registration numbers.

Attach the three documents side by side so the reviewer decides in a minute, and set a time limit so a held invoice does not age silently.

  • Auto-clear within a stated tolerance
  • Rate variance to the buyer
  • Missing receipt to the storekeeper
  • Tax difference to accounts

Fix the documents before the matcher

Most failures start upstream. Read the last twenty rejected invoices and tag each one by cause. You will likely find three or four causes repeated. Often two causes, a late receipt and a stale rate, account for most of the pile.

Fix the biggest cause first, perhaps a same-day receipt rule at the gate, then set the tolerance. Review the tolerance each month using the cause log, and tighten it where clerks keep overriding the same harmless gap.

Mismatch cause log

A one-page log for rejected invoices. Columns hold invoice number, supplier, order number and receipt date. Further columns name the failed field (quantity, rate, tax or missing receipt), the size of the gap, who resolved it and days to clear. A summary box counts causes.

Open a blank worksheet to print

Questions owners ask

Should small orders skip matching?

Many firms use two way matching, order against invoice, below a set value. The cutoff is a policy choice for your finance head to document.

What tolerance should we set?

Start tight and widen it from the log. The data on rejected invoices shows which small gaps were always harmless.

Who should own an unmatched invoice?

The person who can judge the cause: buyer for rate, store for quantity, accounts for tax. One name per exception type.

Does this work with our existing accounts software?

Usually, if it can export orders, receipts and invoices. A matching layer reads those files and posts approved results back.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Share Your Requirements