Rejected Without a Message
Most rejections are silent: the invoice is parked and nobody is told. How to find out, and what the common causes are.
Yourswho controls this stretch
An invoice that fails validation is usually parked rather than returned. No message is sent, no exception is raised with you, and from outside it looks exactly like an invoice that is simply being processed.
The practical point in “Rejected Without a Message” is that getting paid depends on records somebody can explain. A small team considering follow the linked software resource for how to call out of work can organise time and project evidence before invoicing, with transparent settings, proportionate collection and a visible correction route.
Weeks pass. The first time anybody notices is when you ask.
For an independent reference relevant to “Rejected Without a Message”, consult HoneyBook independent-business resources. Compare general information with the contract, jurisdiction, payment route and accounting records involved.
Why nothing is sent
Because the rejection is a system state, not a decision by a person, and nobody owns the exception queue closely enough to notify suppliers.
The commonest causes, in the order they occur:
- A reference that does not resolve to an order.
- An invoice value above the authorised order value.
- No goods receipt entered against the order.
- The wrong legal entity in a group.
- A tax treatment the system will not accept.
In some organisations a weekly report is produced and read by nobody.
The commonest causes
A wrong or missing order number. A value above the order. Lines that do not match. A missing goods receipt. The wrong entity. A closed order. A missing mandatory field.
Seven causes, all clerical, all fixable in minutes once known.
Finding out
Ask. "Has invoice 2214 been received and matched?" to accounts payable, a week after sending.
They can see the state immediately and will tell you, including the reason.
Why a week
Long enough for it to have been processed, short enough that fixing it costs no cycle.
Asking at thirty days finds the same problem a month later.
Acting on the stated reason
Correct exactly what was wrong, resubmit, and note the date. Say in one line what changed.
Resubmitting the same document unchanged — the common response — is rejected identically and wastes another cycle.
The credit-and-reissue
Where the original must be withdrawn, a credit note against it and a fresh invoice is cleaner than amending.
Leaving two live invoices for the same work is the one error that can freeze both.
Rejections that are not clerical
Occasionally the problem is substantive: the buyer disputes the amount or says the work was not delivered.
That is a different situation and belongs with the later notes on disputes, not with resubmission.
Keeping count
Per customer, per quarter: how many invoices were rejected and why.
A short list, and it shows which customer's requirements have changed without anybody telling you.
The pattern worth noticing
The same rejection three times is not bad luck. It is a mismatch between your template and their requirement.
Fixing the template once removes it permanently.
What a rejection costs
A billing cycle, typically. On thirty-day terms that is sixty days rather than thirty, for an error that took ten seconds to make.
The silence is structural, not personal
No message arrives because, in most systems, no message is generated. An invoice that fails validation is held in a queue; the queue is worked by somebody whose task is to resolve exceptions, not to notify suppliers; and the notification would in any case go to whichever address the invoice came from, which may be a template nobody monitors.
A supplier reading this as indifference is usually wrong about the cause and right about the effect.
What follows practically is that discovering a rejection is your job and will not happen by itself. The only reliable mechanism is your own diary: a date, a week or so after sending, on which somebody checks that the invoice is visible in the buyer's system and matched.
What it looks like over a year
Rejections are usually treated as one-off irritations, which is why their real cost is invisible. Counted across a year, a supplier with two rejections a month on thirty-day terms has spent roughly a month of working capital on clerical errors, plus the hours of resolving each one.
Written down, the same errors repeat: one customer's reference format, one entity name, one tax treatment, one address.
That is the useful finding, and it only appears if rejections are recorded. Four columns are enough — date, customer, stated reason, days lost — and a year of them points at three fixes that remove most of the problem permanently.
Suppliers who do not keep the count fix each rejection as it arrives and keep the underlying cause, because nothing in the process ever compares one incident with the last.
The resubmission that goes wrong too
A rejected invoice is usually credited and reissued, and the second document is raised in a hurry by somebody annoyed.
That is how a supplier acquires two live invoices for one job, or a replacement carrying a new date that quietly restarts the payment clock, or a reissue that repeats the original error because the stated reason was never read closely.
Slowing down for five minutes at this point is worth more than it appears: confirm what exactly was wrong, confirm the first document is cancelled at their end, and check the new one against the order before it goes.
The two habits that prevent most of it
Check the eight fields before sending. Ask whether it matched a week after.
Together they catch nearly everything in this note while it is still free to fix.