Industry
Part of Invoices and receipts: the fields that survive contact with reality
Why do invoices and receipts keep getting rejected or delayed?
Invoice mistakes sorted by how long they take to hurt, from same-week rejections to year-end questions about numbering, with the fix for every one of them.
Invoice mistakes sort by how long they take to hurt, and some bounce back within a day.
Others sit quietly until year-end, when an accountant asks why invoice numbers skip from 214 to 217 and nobody remembers.
The slow ones are expensive. By the time they surface, the person who made them has moved on and the customer has closed their books.
Four horizons. For each mistake: how you find out, and what to do instead.
What to take away
- A mistake that surfaces on day one costs an apology. One that surfaces at year-end costs a reconstruction.
- Never edit an issued document. Every correction is a new document that points at the old one.
- Most late payments were caused before the invoice was sent, at the point the order was taken.
Day one: the invoice is rejected
These come back from the customer's accounts team, often with no explanation beyond "cannot process."
Day-one invoice rejection checks
- Billing entity matches customer's legal entity
- Purchase order or reference included
- Sent to accounts payer, not orderer
- File format accepted by customer system
- Invoice terms match contract exactly
Wrong legal entity. You invoiced the trading name, the parent company, or the person who ordered. How you find out: the invoice is returned, or silently parked. Instead: ask for the exact billing entity when the order is taken, and store it against the customer.
No purchase order or reference. Their system cannot match it to an approved spend. How you find out: it never enters their queue. Instead: make the reference a required field on your side, and when a customer has no PO process, put the name of the person who approved the order.
Sent to the orderer, not the payer. The person who wanted the work forwards it eventually, or does not. Instead: collect the accounts contact at the start, and copy the orderer.
A file their system cannot read. A spreadsheet, an image, a document that reflows. Instead: a fixed-format file, and for customers who use a portal, whatever the portal accepts.
Terms that contradict the contract. "Due in 14 days" on the invoice, 30 in the agreement. The contract wins and the invoice looks careless. Instead: the invoice repeats the agreed terms exactly.
Week four: the payment is wrong
The money arrives, but not the right amount.
Week-four payment error checks
- Deposit shown as line, not sentence
- Tax line named and inclusive/exclusive stated
- Payment reference requested on document
- Quantity and unit price on every line
- ISO currency code in header and total
Deposit mentioned in a sentence, not shown as a line. The customer pays the headline total and overpays, or nets it off and appears to underpay. Instead: total for the job, less deposit paid with its invoice number, total due, as three figures.
Tax presentation ambiguous. Whether the figure is inclusive or exclusive is not stated, and the customer pays the other one. Instead: a named tax line shown separately, and a check with your tax authority's invoicing rules on how it must appear. The UK's guidance on invoicing and taking payment is one example of an authority setting that out in public.
No payment reference requested. Money arrives with the customer's own internal number, which matches nothing. Instead: "Please quote [invoice number] on your payment" on the document.
Unit price and quantity omitted. The customer received part of the order and cannot work out what to pay, so pays nothing. Instead: quantity, unit price, and amount on every line, even when the quantity is one.
Currency assumed. A symbol shared by several currencies, and the customer's bank picks one. Instead: the ISO code in the header and beside the total.
Month three: the records disagree
Discovered at reconciliation, when your ledger and the customer's statement do not match.
Month-three reconciliation checks
- Receipts show what they settle
- Issued invoices never edited in place
- One numbering source, no duplicates
- Unallocated money held on account
- Every reminder logged with date and channel
A receipt that does not say what it settles. One payment against three invoices, allocated differently on each side. Instead: an "applied to" block on every receipt that covers more or less than one invoice.
An issued invoice edited in place. You fixed a line and resent the same number. The customer holds the first version. Two documents, one number, two totals. Instead: a credit note against the original, then a new invoice if needed.
Duplicate numbers. Two people raised invoices from two copies of the template. Instead: one numbering source, whatever it is, and a rule that nobody raises an invoice outside it.
Unallocated money treated as revenue. A customer overpays, you bank it, and it disappears into income. Instead: hold it on account, show it on the receipt, and settle it deliberately.
Chasing without logging. Three reminders, none recorded, and the customer says they never had one. Instead: date and channel of every reminder against the invoice.
Year-end: the file will not reconstruct
The accountant's questions, and the ones an inspection would ask.
Year-end file reconstruction checks
- Void canceled invoices, keep numbers
- Store document as sent, every time
- Date receipts on cleared funds only
- Credit notes state how settled
- Keep records for required period and form
Gaps in the sequence with no voids. Canceled invoices were deleted rather than voided, and now the gaps look like missing income. Instead: void, keep the number, record the reason.
No copy of what was sent. The tool regenerates invoices from current data, and your address or prices have changed since. Instead: store the document as sent, every time.
Receipts issued before funds cleared. A receipt dated when the customer said they paid, for a payment that bounced. Instead: date receipts on cleared funds only.
Credit notes without a settlement line. Credits exist, but nobody recorded whether they were refunded or applied, so the customer's balance is wrong in both directions. Instead: every credit note says how it is settled.
Records kept for the wrong period, in the wrong form. How long you must keep invoices, and whether an electronic copy is enough, is set where you operate. Instead: ask your tax authority and your accountant, and keep at least that long. The US tax authority's page on how long to keep records shows why the honest answer is a range rather than a single number: it moves with what the record is.
Symptom to cause
| What you notice | Usual mistake | Horizon |
|---|---|---|
| Invoice silently parked | Wrong entity or no reference | Day one |
| Paid, but short by a round figure | Deposit shown as text, not a line | Week four |
| Paid, short by a small amount | Tax or bank charges ambiguous | Week four |
| Customer statement never matches yours | Receipts not allocated, or edited invoices | Month three |
| Two invoices with one number | Two copies of the template | Month three |
| Accountant asks about number gaps | Deleted rather than voided | Year-end |
The one habit behind most of it
Almost every day-one mistake was made at the point the order was taken, not when the invoice was written. The entity, the reference, the billing contact, the terms, and the currency are all known then and rarely asked.
The fields the invoices and receipts overview lists are easiest to fill from the accepted quote, which names the customer and scope. Turn the questions into a short intake step in your order procedure, and the invoice writes itself later.
The pre-send pass from the letter checklist reads every number aloud, catching the transposed figure no template prevents.
