From the seller’s side an invoice looks like two events: you send it, and eventually money arrives. The gap between them is where the frustration lives, and it is not empty — it is a sequence of steps happening mostly inside someone else’s organisation, each with its own failure mode.
Understanding the whole arc changes what you do about slow payment. Most "chasing" is aimed at the wrong stage: a polite reminder does nothing for an invoice stuck in a matching exception, and neither does a late fee. Knowing where an invoice actually is tells you which lever moves it.
The eight stages
A complete lifecycle runs from before the invoice exists to long after it is paid. Roughly half of it happens on the buyer’s side, invisible to you unless you ask.
- **Trigger** — the work completes or the goods ship, creating the right to bill
- **Draft** — the invoice is prepared but not yet issued; still freely editable
- **Issued** — the invoice is finalised, numbered and dated; from here it is a record, not a document you edit
- **Delivered** — it reaches the buyer and enters their system, which is a distinct event from you sending it
- **Validated** — the buyer checks it against the order and the delivery evidence
- **Approved** — someone with authority agrees it should be paid, and it joins a payment run
- **Paid** — funds are released and the payment reaches you
- **Reconciled and archived** — the payment is matched to the invoice in your books, and both are filed for the retention period
Where the time actually goes
Sellers reliably overestimate how much of the delay is the buyer being slow to pay, and underestimate how much is the invoice failing to arrive properly or failing validation.
The delivery stage is the most underrated. An invoice emailed to an individual who is on leave, or to a person who left the company, has not reached the buyer’s system at all — and nobody is going to tell you. Many organisations have a dedicated intake address or portal specifically to avoid this, and using it is the single highest-return change most suppliers can make.
Validation is where mismatches surface. If the invoice disagrees with the purchase order or the delivery record, it goes to an exceptions queue rather than generating a rejection. Silence is the symptom, which is why an unexplained delay is worth a specific question — "has this passed matching?" — rather than a generic reminder.
Approval is a queue problem: the invoice needs a person with the right authority to act, and that person has other work. Payment itself is usually the least variable stage, because most organisations run payments on a fixed cycle. An invoice approved the day after a payment run waits for the next one regardless of its due date.
The branches that are not "paid"
Not every invoice completes the happy path, and the alternative endings need handling deliberately rather than by neglect.
A disputed invoice has stopped for a stated reason. It is genuinely better news than silence, because you know what to fix. Resolve the substance, then correct the record properly — a credit note plus a corrected invoice where the original was wrong, rather than editing the original.
A partially paid invoice continues to live with a reduced balance. The invoice does not change; the payments are recorded against it. Editing the amount to match what arrived is the classic mistake and it breaks the trail.
An invoice that will never be collected ends as a write-off — recorded as bad debt, not deleted. Deleting it erases the fact that you were owed money and did not receive it, which is information you want when deciding whether to work with that client again.
Shortening the cycle
The interventions that work are mostly upstream of the payment stage, which is where most effort is misdirected.
Invoice promptly. The clock starts at issue, so an invoice raised a fortnight after the work is a fortnight of delay you created. Send it to the right destination — the intake address or portal, not a personal inbox — and include the references the buyer needs to match it, above all the purchase order number.
Make it easy to act on: correct amounts, a clear description tied to what was ordered, a due date stated as a date, and a payment method that does not require retyping bank details. Then follow up on a schedule rather than on irritation, and ask stage-specific questions. "Can you confirm this was received and passed matching?" gets a useful answer; "just checking in on this invoice" gets a polite nothing.
Finally, close the loop. Reconciling promptly means you know which invoices are genuinely outstanding, which is what makes an ageing report worth looking at. Chasing an invoice that was paid last week costs you more credibility than the reminder was worth.
Common Mistakes
Assuming sent means received
An email to a personal inbox is not delivery into a system. Ask where invoices should be sent, use that channel, and treat confirmation of receipt as a distinct milestone.
Chasing without knowing the stage
A generic reminder does nothing for an invoice stuck in matching. Ask whether it was received, whether it passed validation, and whether it has been approved — each answer points at a different fix.
Editing issued invoices
Once issued, an invoice is a record. Corrections go through credit notes and replacements so the history stays intelligible to both sides and to an auditor.
Leaving reconciliation until month end
Unreconciled payments make your outstanding list wrong, which means chasing clients who have already paid. That costs more goodwill than the time saved.
Frequently Asked Questions
How long should the whole cycle take?
It varies enormously by client size. A small business paying by transfer may settle within days; a large organisation with formal approval and a monthly payment run can take six weeks on 30-day terms without anything being wrong. Track your own average and investigate the outliers rather than the mean.
At what point does an invoice become a receivable?
On accrual books, at issue — that is the point revenue is recognised and the amount enters accounts receivable. On a cash basis nothing is recorded until payment arrives.
What is the most common place invoices stall?
Delivery and validation, not payment. An invoice that never reached the right inbox, or that failed a match against the purchase order, sits silently. Both are cheap to prevent and expensive to discover late.
Should I send a statement as well as invoices?
A periodic statement listing open invoices is useful for clients with several outstanding, and it catches invoices that went missing in delivery. It is a summary, not a demand, and it should never carry its own invoice number.
Sources & Further Reading
Ready to put this into practice?
Create a professional invoice in your browser — free, no sign-up, no watermark.
Open the Invoice Generator