We Never Received It
The most common answer to a first chase, usually true, and answerable only with a record you made at the time.
Theirswho controls this stretch
"We never received it" is the commonest answer to a first chase. It is usually true, it is rarely anybody's fault, and it is answerable only with a record made when you sent the invoice.
The practical point in “We Never Received It” is that getting paid depends on records somebody can explain. A small team considering review the linked implementation resource for getting teams to meet deadlines can organise time and project evidence before invoicing, with transparent settings, proportionate collection and a visible correction route.
Without that record the exchange ends in a resend and a lost month.
For an independent reference relevant to “We Never Received It”, consult US Chamber finance resources. Compare general information with the contract, jurisdiction, payment route and accounting records involved.
Why it is usually true
Because the invoice went to an individual rather than a route, or to an address that has changed, or into a portal where submission failed silently, or to the wrong entity in a group.
- Sent to an individual rather than to the invoice address.
- Sent to a shared inbox nobody monitors.
- Caught by a filter because of the attachment.
- Arrived and failed validation so completely that nothing was recorded.
All four are honest, and all four are indistinguishable from a lie if you have no record of what you sent and where.
All four produce a genuine absence at their end.
What the record has to show
The date, the route, the address or portal reference, and any confirmation of receipt.
Four facts. With them, the conversation moves from "did you send it" to "let us find where it went".
The confirmation that is free
Many portals issue a submission reference. Many email systems can confirm delivery. A one-line reply from a human is best of all.
Asking for an acknowledgement when you send is normal and nearly always given.
When it is not true
Occasionally it means "I cannot see it", because the person asked is looking in the wrong place, or it is parked where they do not look.
Asking specifically whether it is in the exception queue often produces a different answer.
The resend
Do it immediately, to the correct route, referencing the original date and number, and say plainly that it is a copy of an invoice first sent on a stated date.
Not a new invoice, and not a new number.
Why the date matters
Because the terms may run from receipt, and a resent invoice can reset the clock. Where your original was properly sent, say so and ask for the original date to stand.
Often granted where it is asked for politely and evidenced.
Two live invoices
The risk of resending carelessly: the original surfaces later and both are in the system.
Marking the resend as a copy of the same number prevents it.
After it happens once
Change the route. The failure has told you exactly what is wrong with your process for that customer, and it will recur until it is fixed.
The entity problem
In a group, an invoice to the wrong company is received by nobody who is looking for it, and may sit in a shared mailbox indefinitely.
Checking the entity on the order against the invoice prevents this entirely.
What this costs when it goes wrong
A full cycle, typically, plus the standing impression that your paperwork is unreliable.
What usually happened
The claim is nearly always honest, and the explanation is nearly always one of four things: the invoice went to an individual rather than to the invoice address, it went to a shared inbox that nobody monitors, it was caught by a filter because of its attachment, or it arrived and failed validation so thoroughly that it was never recorded.
None of these involve anybody lying, and all of them are indistinguishable from a lie if you have no record.
Which is the point of the record. A supplier who can state the date, the address and the reference is having a factual conversation about where a document went. A supplier who can only say that it was definitely sent is having a different and much worse conversation.
What the resend has to avoid
The instinct is to forward the original immediately, and that is where a recoverable situation becomes a tangled one.
A resent invoice must be the same invoice: the same number, the same date, the same figures, clearly marked as a copy of a document already submitted rather than as something new. A fresh invoice with today's date creates a second live document for the same work, and in many systems restarts the payment period from the new date — which is precisely the outcome the buyer's position implies and you are trying to avoid.
It is also the moment to fix the route rather than repeat it. If the original went somewhere that evidently does not work, sending the copy to the same place will produce the same result, and in a month's time the conversation will be identical.
Confirming the correct address, resending the original document to it, and asking for acknowledgement of receipt costs one email and ends the matter. The acknowledgement is the part suppliers skip, and it is the only part that prevents a repeat.
What prevents nearly all of it
Sending to the stated route, keeping the submission reference, and asking in week one whether it arrived.
Three habits, all free, and between them they make this conversation almost impossible to have.