Purchase order and invoice matching: which variance blocks payment and which one a person clears

An invoice arrives for goods that were ordered and, mostly, delivered. The supplier wants $5,501.50; the order authorised $5,440.00; the delivery note records 38 of one item against 40 ordered. Somewhere in those three documents there is a number that should be paid, and the whole of the matching discipline is knowing which parts of the difference are arithmetic — settled by a stated rule, without anybody’s opinion — and which parts are decisions that belong to a person with the authority to take them.

Most organisations collapse that distinction, and they collapse it in one of two directions. The lenient version pays the invoice and clears the difference at month end, which converts every supplier error into the buyer’s cost. The strict version holds the entire invoice over a $30 freight line, which costs a supplier relationship and a week of somebody’s attention to recover a sum smaller than the time spent on it. Both are failures of the same kind: nobody wrote down which variances are tolerated, so each one is settled by whoever is nearest.

This piece sets the three documents out, separates the mismatches that block payment from the variances that a person may clear, works an invoice line by line to a figure that adds up, costs the cycle, and states the one limit that no tolerance closes.

The three documents

The match is called three-way because it tests three documents against each other, and dropping the middle one is the most common shortcut in the work. The order authorises; the receipt evidences; the invoice charges. Two-way matching — invoice against order, with no receipt — is a test of whether the supplier’s paperwork agrees with the buyer’s paperwork, and it pays for a supplier’s mistake out of the buyer’s margin, because goods that never arrived are reconciled as though they had.

The order as issued. Quantities, unit prices, currency, delivery date and point, payment terms, and the quotation it accepts. The critical property is that it is the version that left, not the version that was later amended. An order amended after issue must be a new document with its own date and its own authorisation, because the match tests the invoice against an authority, and an authority that has been edited to agree with the result is not an authority.

The receipt. What arrived, when, how many, in what condition, signed by somebody. It is the only one of the three documents the buyer generates from an event rather than from an intention, and it is therefore the only one that can contradict the other two with evidence. It is also the document most often missing, and its absence is not a reason to match on two documents; it is the reason payment is held.

The invoice. What the supplier says it is owed, line by line, with its own reference, date, tax treatment and payment terms. It is a claim, not a fact, and it is the easiest of the three to check because it is the only one written by a party with an interest in the outcome.

The match tests each invoice line against the order line and the receipt line that correspond to it. Where there is no corresponding line on either of the other documents, the line has nothing to match and cannot be cleared by any tolerance, however generous.

Blocks and tolerances

The distinction that matters is not size. A $4,000 error on a line the buyer ordered is a smaller problem than a $40 charge for something nobody ordered, because the first is arithmetic inside an authority and the second is an absence of authority. Blocks are about absence: no order, no receipt, no reference. Tolerances are about arithmetic inside a band that somebody stated in advance.

Table 1. The mismatches a three-way match produces, what each one is, and who may clear it. Source: the studio’s purchase manager specification, whose match reports line by line and does not adjust.

The table has one property that is worth stating because it is what makes it usable: every row on it can be decided by a rule or routed to a named authority, and no row requires the person running the match to exercise commercial judgement. That is the design. The match reports; the report is complete; the decisions happen where the authority is, on the record, with a date.

The tolerance itself is a policy figure and should be described as one. An organisation that states a three per cent price tolerance or a twenty-dollar limit, whichever is lower, has made a decision about how much arithmetic it is willing to examine. A tolerance set generously to keep suppliers happy is a standing authorisation for the supplier to invoice to the top of the band, and the arithmetic below shows what that costs over a year.

Worked example: one order, one invoice

The organisation in this example is illustrative and its tolerances are stated rather than assumed: three per cent of the ordered line value or twenty dollars, whichever is lower, on goods; a twenty-five dollar absolute limit on freight; rounding under one dollar cleared; invoiced quantity above receipt held at any amount, regardless of tolerance. The documents are constructed for this piece. Table 2 lays the three of them side by side, line by line.

Table 2. The three documents, line by line. Constructed for this piece; not a real transaction.

The five comparisons come out of the documents set out in Table 2, and each one lands in a different row of Table 1.

L1 is clean. Ordered 120, received 120, invoiced 120 at the ordered price. It is the line that proves the match is running: a document set in which nothing ever matches exactly is a document set where the comparison is not happening.

L2 is a hard block on part of the line. The invoice charges 40 units; the delivery note evidences 38. Thirty-eight at $64.00 is $2,432.00, and that portion matches both order and receipt. The remaining two units are $128.00 invoiced against no receipt, and the tolerance does not reach them because a tolerance compares prices and this is an absence of goods. The block is $128.00, not $2,560.00: the invoice is not rejected, it is paid to the evidence and held at the difference.

L3 is a price variance inside tolerance. Invoiced at $32.90 against an ordered $32.00 is $0.90 a unit, $13.50 on the line, which is 2.81 per cent of the ordered $480.00. The stated band is three per cent or twenty dollars, whichever is lower — 2.81 per cent is inside three per cent, and $13.50 is inside twenty, and the lower of the two thresholds is $14.40, which $13.50 does not exceed. It clears by rule, and it is recorded rather than ignored, because the record is how a supplier’s price drift becomes visible across twelve months.

L4 is a tolerance decision. Freight invoiced at $210.00 against $180.00 ordered is $30.00, or 16.7 per cent above the ordered figure. The freight tolerance is $25.00 absolute, so the variance exceeds it by $5.00 and the whole $30.00 becomes a query rather than an adjustment. The agent cannot clear it: accepting an increase in carriage is a commercial decision and it belongs to the person who set the tolerance. The $180.00 that was ordered is paid; the $30.00 waits, with an owner and a date.

L5 is a hard block with nothing behind it. A fuel surcharge of $18.00 appears on the invoice and on nothing else. There is no order line, so there is no authority, and there is no tolerance that converts an unorderable charge into a payable one. It is queried with the supplier and, where the supplier confirms it is a legitimate charge that will recur, it is ordered — which is to say the correction is a new order line, not a note in the match.

The invoice splits into three figures rather than one, and Table 3 collects the outcomes line by line.

Table 3. The outcome of the match, line by line, to a figure that reconciles.

The invoice is $5,501.50. One hundred and seventy-six dollars of that does not clear today: $146.00 because the documents do not support it and $30.00 because a person has to decide it. The distinction is the whole point of the table — the $146.00 will not become payable by waiting, and the $30.00 will become payable the moment somebody with the authority says so. A match that reported “variance $176.00” and stopped would have one number where the buyer needs two, and the supplier would receive the same answer to two different questions.

What the tolerance costs over a year

The $30.00 above is small, which is exactly why it is dangerous. Suppose every invoice in a month carried a freight excess at the tolerance limit rather than above it: $25.00 on sixty invoices is $1,500.00 a month, or $18,000.00 a year, cleared by rule and examined by nobody. That is not a hypothetical about dishonest suppliers. It is what a tolerance is: an advance authorisation to charge up to a stated figure without being asked, granted to every supplier on the list, renewed on every invoice.

The response is not a tighter tolerance, which produces the opposite failure — a mass of queries over sums smaller than the cost of raising them. It is two habits. State the freight figure on the order rather than accepting whatever arrives, since a supplier who has been given a number to invoice against has far less room than one who has been given a category. And review the cleared variances in aggregate once a month, because sixty entries of $13.50 that were each too small to examine are a $810.00 price drift, and the drift is visible in the record that the rule said nobody needed to read.

The cost of the cycle

Three documents are extracted — the order, the delivery note, the invoice — the match is built in one call, and the queries are drafted in one. Five calls at the measured Base rate of $0.00700 is $0.03500 for the cycle. At the metered ceiling of $0.00955 a call it is $0.04775. Sixty cycles a month is the 300 calls and $2.10000 stated on the purchase manager’s own page, which is five calls a cycle, reconciled from the other end.

Set that against the figure the match produced. The $128.00 held on two bearings is more than three and a half thousand times the $0.03500 the match cost to run, and it is the largest of the three amounts held. The economics of running the match are not in question; the economics of what a generous tolerance does over twelve months are, and those are decided in the policy document rather than in the workspace.

Where the match stops

The match tests agreement between three documents, and three documents can agree and all be wrong. The delivery note is a person’s signature on a count somebody made in a yard at the end of a shift; the order is the version that was issued, which is why the as-issued copy has to be filed; the invoice is the supplier’s arithmetic, which is only as good as the extraction that read it. A perfectly matched invoice is evidence of consistency. It is not evidence that the goods are the ones specified, that the price is fair, or that the delivery happened when the note says.

Four limits follow, and each is structural rather than technical.

The match cannot certify a delivery. Evidence of receipt is a document from a warehouse, a carrier or a person at the door, and no reading of an invoice creates one. Where the receipt is a signature and the goods were never counted, the match will clear the invoice, and it will be right about the documents and wrong about the world.

The match cannot value a substitution. A delivered item that differs from the ordered item is a specification question, and the arithmetic has nothing to say about it: the price may match, the quantity may match, and the wrong part may be in the stores. That decision belongs to the person who accepted the requirement, and it is the row in Table 1 that neither a rule nor a tolerance can reach.

The tolerance is not the agent’s to set or to move. It is stated by the client, it appears in the order, and the workspace reports against it. An agent that could clear a variance above the tolerance would be taking a commercial decision, and a match that adjusts a discrepancy into agreement destroys the only thing it produces: a record of what did not agree.

And the match is only as good as the order it tests against. Where the order was drafted loosely — a freight figure of “as quoted”, a unit price with no currency, a delivery point unstated — every invoice will match it and none will be checked. The quality of the match is decided upstream, in the order, and no amount of care in the comparison stage repairs an order that authorises nothing in particular.

The decision

Put the tolerance in the order and in the supplier’s terms, in figures, before the first invoice arrives. An order that states the price, the freight and the band it may vary inside has given the match something to test; an order that says “per quotation” has given it a document to agree with.

Block on absence before doing arithmetic. No order line, no receipt, no reference: these are absence and they are held regardless of amount. Then run the arithmetic, clear what is inside the band by rule, and route what is outside it to a named authority with a date. The order of those two operations matters, because running the arithmetic first produces a number that looks like a decision.

And treat every variance above tolerance as a query, never as an adjustment. A discrepancy that is reported can be chased; one that has been smoothed into agreement cannot, and the file that recorded the smoothing will show a match with no variance at all — which is the clearest sign, to anybody reading it a year later, that nobody was looking.

Where this goes

• The pillar: x402.review/2026/10/31/commercial-operations/ — the record, the six ways the work fails and the approvals between them
• The role that runs the match: studio.x402.press/roles/purchase_manager — the order, the approval record and the three-way match
• The side that receives the order: studio.x402.press/roles/sales — the proposal and the terms the buyer’s order accepts
• The service it buys: x402.press/services/deepseek/ — the canonical price, seven chains
• The review: x402.review/2026/10/31/deepseek-review/ — the measured handshake and what it does not promise

Method note

The price was read from the live 402 challenge on Base on 31 October 2026, outside DeepSeek’s weekday peak windows of 01:00–04:00 and 06:00–10:00 UTC: 7000 atomic units under exact, which is $0.00700, and 9550 under upto at the max_tokens tested. Call counts are planning assumptions, stated in the cost section: five a cycle, three hundred a month, reconciling with the purchase manager page’s own figure.

The order, the delivery note and the invoice are constructed for this piece and labelled as such; no supplier, purchase or payment is described, and the supplier’s name is deliberately absent because none was involved. The tolerances — three per cent or twenty dollars on goods, twenty-five dollars on freight — are the illustrative organisation’s stated policy and not a norm: another organisation’s figures would produce the same structure and a different outcome on L3.

x402.review is written and edited by N.P. Vincent. The publication is connected to x402.press, which sells the services reviewed here; that interest is disclosed on every piece that touches a service, and it is stated here rather than left to inference.

Filed under Jobs · Tags: purchase-order, invoicing, three-way-match, controls