The Reference That Makes It Payable
An invoice is matched by machine against an order and a receipt. The reference is what lets the machine find it, and it is the cheapest thing to get right.
Sharedwho controls this stretch
An invoice arriving in a large organisation is matched automatically against an order and a goods receipt. The reference is what lets the match happen, and without it the document goes to an exception queue where nobody is waiting for it.
The invoice problem in “The Reference That Makes It Payable” is easier to resolve when the work behind it has an approved record. A service team assessing view the service at its source for GDPR employee monitoring can connect time and projects with the billing file, while the invoice and accounting system remains authoritative for amounts, tax and settlement.
Getting the reference right is free. Getting it wrong costs a billing cycle.
The questions raised in “The Reference That Makes It Payable” can also be checked against Small Business Commissioner unpaid-invoice guidance. Use the outside resource to identify what evidence and ownership the next action requires.
What the reference is
Usually the purchase order number, exactly as issued, including any prefix, leading zeros and punctuation.
Where the reference has to appear, and where suppliers forget it:
- On the invoice, in the field the buyer's system reads.
- In the portal submission, in the format the portal demands.
- On any attachment, so a human can match it by hand if needed.
- In the covering email, so your contact can find it later.
- In your own job record, copied rather than typed.
Not your own job number, not the project name, not an abbreviation.
Where it has to appear
On the invoice, in the field their system reads. On many portals, in a specific box. In the covering email, as a courtesy.
Putting it in the body text of a PDF where no field exists is a common and silent failure.
The transposed digit
Two numbers swapped. The match fails, the invoice is parked, and in most systems nobody is notified.
It is the single most common cause of an invoice that is "in their system" and going nowhere.
Checking it
Against the order document, character by character, once per invoice. Ten seconds.
Against your own records is not the same check: the error may already be in your records.
Other references that may be required
A cost centre. A contract number. A delivery note number. A site reference. A requisition number distinct from the order.
Where a buyer uses several, all of them are mandatory and none of them is optional in practice.
Amounts and lines
Many systems match line by line and to the penny. An invoice for a different total, or with lines described differently from the order, is rejected as readily as one with no reference.
Invoicing exactly what the order says is a discipline, not a preference.
Partial deliveries
Where an order covers several deliveries, each invoice usually quotes the order and the specific lines.
Invoicing the whole order for part of the work fails the match.
When the order changes
A varied order has a new version or a new number. Invoicing against the superseded one fails.
Asking, when a change is agreed, whether the order has been amended takes one line and prevents a month of silence.
Your own reference
Worth having as well: a sequential invoice number that you can quote in any conversation.
It is what lets both sides find the same document quickly, and a surprising number of small suppliers reuse or skip numbers.
What to do about a rejection
Find out the actual reason, correct it, and resubmit promptly with a note of what changed.
Resending the same document unchanged, which is the common response, is rejected identically.
Why a machine is strict about it
The reference looks like bureaucracy and is in fact the only thing connecting your invoice to the commitment that authorises paying it. The matching software holds an order with a number and a value, and a receipt against that order; your invoice arrives carrying a string that either resolves to that record or does not.
There is no partial credit and no human in the path at that moment.
This is worth understanding because it explains the absence of a message. A rejected invoice has not been judged and found wanting; it has failed to resolve to a record, and the system has no view about it. Nobody decided to hold your money. Nothing matched, so nothing moved, and the only person who will notice is you.
Where it goes wrong at your end
Most reference failures originate in the supplier's own process rather than in the buyer's rules. The number is typed from an email rather than copied, so a digit transposes. It is entered into the quote template and carried forward to a second job it does not belong to. It is stored in a message thread rather than in the job record, so the person raising the invoice reconstructs it from memory.
Each of these is a two-second saving that costs a month.
The fix is mechanical and dull: when an order arrives, the reference goes into the job record immediately, copied and pasted, with the date and the order's value beside it. Then the invoice is built from the job record rather than from anybody's recollection. Suppliers who do this stop having reference problems entirely, which is a disproportionate return on a habit that takes no time at all.
The habit
Order number first, then everything else. It is the single highest return per second of any action described in this collection.