Sound familiar? · Getting paid

Why is my invoicing always weeks behind the work?

The work is done, the customer is happy, and the invoice goes out... eventually. Then it waits. Payroll, meanwhile, has never once waited.

Updated October 14, 2026 Kaizen CRM

The short answer

Invoicing falls behind because it lives in a separate tool from the job, so it depends on someone re-entering the details at a desk after a long day, and anything that depends on end-of-day data entry loses to fatigue. The fix is to build the invoice from the job record itself: the customer, the work, and the price already exist, so the invoice is one tap when the job closes, sent from the driveway. Days-to-invoice typically falls from around fourteen to one.

You know this is you when

Invoicing is a Sunday job, and some Sundays it does not happen.
There is always a backlog of finished work waiting to be billed.
The invoice is built from memory, paper, and a text thread, days later.
Small jobs sit the longest, and small jobs are most of the jobs.
Cash is tight in weeks where the work was plentiful.

14 → 1

days-to-invoice collapses when invoicing happens at job completion

KAIZEN CATEGORY RESEARCH · MORE DATA →

What it is costing you

Every day between finishing and invoicing is a day you are lending the customer money at zero interest. A business doing $60,000 a month with a two-week invoicing lag is permanently funding about $30,000 of its own work. That is a line of credit you are extending without deciding to, and the interest is paid in stress on payroll day.

The lag also compounds the payment lag. An invoice sent two weeks late and paid on 30-day terms is cash forty-five days after the work. The same job invoiced from the driveway with text-to-pay is often cash before the truck leaves the street. The work is identical; the business feels completely different.

Why it keeps happening

The invoice is a second job. The real job ends when the work is done; the invoice begins at a desk, in a different tool, from notes that have to be found and a price that has to be remembered. It is not that anyone forgets; it is that the invoice is a chore separate from the work, and chores separate from the work get batched, and batches slip.

Small jobs suffer most. A $9,000 install gets invoiced promptly because it is memorable and the money matters. The $180 service call waits three weeks because it is one of twenty, and twenty small invoices is an evening nobody wants. Yet the small jobs are the bulk of the ticket count and a larger cash swing than the big ones.

And the data is scattered. Parts used are on a paper slip, hours in a tech's head, the agreed price in a text. Reconstructing that is the slow part, and it is slow because the job and the invoice never shared a record.

How to fix it

01
Make the job record the invoice
Customer, work done, parts tapped, hours logged, price from the quote: all already on the record by the time the job closes. The invoice is that record with a button on it, not a document built from scratch.
02
Invoice from the driveway, as the last step of the job
Close the job, review the invoice, send it by text while the customer is still pleased and the work is still fresh. For most jobs this takes under a minute and it happens before the next job starts.
03
Put payment one tap away
A text-to-pay link in the invoice and card-on-file for repeat customers mean many invoices are paid on the spot. The ones that are not get polite automatic reminders on a schedule, which is awkward for a person to send and effortless for a system.
04
Watch one column
Completed-not-invoiced should be a column on the pipeline, visible every day, ideally empty. Kaizen builds the invoice from the job and keeps that column in view, which is why its customers tend to see the backlog disappear in the first fortnight.

See the fix running, on your business.

A 30-minute walkthrough with Mel, built around slow invoicing & payments. No deck: the product, using scenarios from your trade.

Book a walkthrough

Common questions

Is it unprofessional to invoice on the spot?

Customers expect it. Being handed a clear invoice by text as the technician leaves, with a link to pay, reads as organised. Being invoiced two weeks later for work they had half forgotten reads as the opposite, and it is where disputes start.

What about jobs with parts I have to price later?

Invoice what you know on the day and add the exception later, or send a same-day invoice marked as provisional. The rare job that genuinely needs a desk should not set the process for the twenty that do not.

Does this work with my accounting software?

It should feed it. The invoice originates on the job record and syncs to the ledger, so the accountant sees it without anyone re-keying. The lag you are fixing is between the job and the invoice, not between the invoice and the books.

How does Kaizen handle invoicing?

The invoice is built from the job record and sent from the phone at completion, with text-to-pay, card-on-file for repeat customers, and automatic reminders for anything unpaid. Completed-not-invoiced is a pipeline column, so nothing finished can hide.

In your trade, specifically

The same leak reads differently in every business. These are the versions written for the trades it hits hardest.

Keep reading

Invoicing & Payment Software → How do I get customers to pay invoices on time? Quote to cash, end to end CRM and QuickBooks Customers pay late