Work finished on the third, invoiced on the thirtieth, paid sixty days later. Half that delay is self-inflicted and it repeats every month. Here is how to remove it.
The delay nobody counts
Most small businesses invoice in a batch at month end because that is how it has always been done. The cost is invisible because it never appears as a late payment; the invoice was simply issued late.
Work finished on the third of the month, invoiced on the thirtieth, on net 30 terms, gets paid roughly sixty days after the work was done. Half of that delay is yours.
Every day between delivery and invoice is a day you financed the client for free, and it is the only part of the payment cycle entirely within your control.
How to build it
1. Decide what triggers an invoice
Work moving to a delivered status, a milestone being reached, or a date arriving for a retainer. Write the rule down per client type. This is the step that turns invoicing from a memory task into a scheduled one.
2. Pull the lines from the work, not from a spreadsheet
If you bill by hours, pull logged time for the period. If by milestone, pull the deliverable name. Re-typing invoice lines is where errors enter, and an invoice with a wrong line gets queried, which costs far more than the typing.
3. Generate a draft, never a sent invoice
This is the one rule I would not bend. Generation is the tedious part and approval is cheap. An invoice is a legal document going out under your name, and the failure modes are expensive.
4. Attach the supporting detail automatically
A timesheet breakdown or deliverable list attached to every invoice removes most queries before they happen. Queries are the quietest cause of late payment, because the clock keeps running while somebody asks a question.
5. Set the due date from the terms, not by hand
Terms live per client. Calculate the date rather than typing it, because a wrong due date is an argument you will lose.
6. Notify a human when generation fails
Silent failure means an invoice that was never raised, which you discover during a cash review weeks later.
Tools and what they cost
| Option | What it costs | Honest trade-off |
|---|---|---|
| Accounting software native (Xero, QuickBooks) | Included in your existing subscription. | Recurring invoices and templates handled well. Pulling lines from your project tool usually needs an integration. |
| Practice or agency management tools (Harvest, Productive) | Per user per month, typically single to low double digits. | Time tracking and invoicing in one place, which removes the join entirely. Another subscription and a migration. |
| Apps Script joining your tracker to your accounting API | Free with Google Workspace. | Full control over the trigger and the line logic. You build and maintain the API calls. |
| Connector platform | Per task. One invoice is a handful of tasks, so volume matters less here than elsewhere. | Reasonable fit, because invoice volume is usually low. Watch the cost if you invoice hundreds of clients. |
What it is actually worth
This one has arithmetic you can do exactly, which is rare.
Count the average days between work being delivered and the invoice being raised. Multiply by your monthly invoiced value, divided by thirty. That is roughly the cash permanently sitting outside your account because of invoicing lag, and it is recoverable once rather than repeatedly.
For context on why it matters: the JPMorgan Chase Institute, analysing transaction data from over 600,000 US small business accounts, found the median small business holds about 27 days of cash buffer. Against a buffer that size, a two-week invoicing lag is not an administrative detail.
How it breaks
It invoices work that was not actually delivered. If your delivered status is used loosely, you will invoice early and damage trust. Tighten the status definition before automating against it.
Duplicate invoices. Same discipline as any generator: check whether an invoice already exists for that work before creating one.
Approval becomes a bottleneck. If one person approves everything and they are away, nothing goes out. Name a deputy.
How to tell whether it worked
Median days from delivery to invoice, which should fall to under two. Then days sales outstanding, which will follow. And the number of invoices queried, which the attached detail should reduce.