When finished jobs sit waiting for paperwork before they can be invoiced

The short version#

• ‘Done’ means different things on site, in the office and in accounts. Name the stages between finished and paid, and use them.
• Write down what each job type needs before it can be billed, from your scope, your customer’s process and your terms, not from memory.
• For every waiting job, name what’s missing, who’s getting it and by when. Review the queue weekly, oldest first.
• This shortens the gap between finishing and invoicing. It doesn’t guarantee payment, and it doesn’t create revenue.

First step: list every job where the work is finished but there’s no invoice yet. Download the billing readiness tracker (.xlsx)

What it looks like#

A job is finished on a Tuesday. Three weeks later, it still hasn’t been invoiced.

Nobody has been idle. The office was waiting for the signed job sheet, which was in the ute. Then the purchase order number turned out to be missing. Then someone noticed the extra work hadn’t been approved in writing, so nobody wanted to bill for it, or to bill without it. Each delay was small. Together they took three weeks.

Signs it’s happening:

• Your list of finished but uninvoiced jobs exists only in someone’s head.
• Invoices go out in batches, whenever someone has time to chase paperwork.
• Customers query invoices because something is missing.
• Extra work gets written off because nobody can show it was approved.

Why finished jobs stall#

• ‘Done’ is doing too much work. The site team means the work is finished. The office hears ‘ready to invoice’. Many job lists use one word for both.
• Requirements live in people’s heads. One customer needs a purchase order number on every invoice, another a portal upload with photos, a third signed delivery dockets. That knowledge often sits with one person.
• Missing items aren’t named. ‘Waiting on paperwork’ can’t be acted on. ‘Waiting on PO number from the strata manager, office admin chasing, follow up Friday’ can.
• Finished jobs drop out of sight. They leave the list people check every day, but they aren’t invoices yet, so accounts isn’t looking either.

Five stages between finished and paid#

Give each stage a name, a test and a person who moves the job on. Rename them to suit your business.

1. Work complete
2. Documentation complete
3. Ready for billing review
4. Invoice issued
5. Paid

Stage	The test	Who moves it on
1. Work complete	The work in the agreed scope is physically finished.	Whoever did the work, by recording it.
2. Documentation complete	Everything this job type needs is in the record.	The job’s owner, chasing anything missing.
3. Ready for billing review	Queued for a check against the scope, approvals and the customer’s terms.	Whoever reviews billing.
4. Invoice issued	Sent in the format and through the channel the customer requires.	Accounts.
5. Paid	Payment received and matched to the invoice.	Accounts.

Add ‘On hold’ for jobs waiting on a decision or a dispute, with a reason and an owner, so they don’t make the whole queue look older. This guide is mostly about stages 1 to 3, marked in red. That’s where finished work waits.

How to set it up#

1. Name the stages and use them

   Add them wherever your job status lives: job management software, the job record from guide 01, or a spreadsheet. Agree as a team what each one means. The point is that ‘done’ stops being ambiguous.

2. Write down what each job type needs

   List what has to be in the record before a job can be billed. Take it from three places:

   • The agreed scope: what you agreed to deliver, and what shows you delivered it.
   • The customer’s process: purchase order numbers, portals, required attachments, who approves invoices.
   • Your terms: what you’ve agreed about extra work, call-out fees, waiting time or progress claims.

   Don’t add requirements just to be safe. Every item is something to chase.

3. Name what’s missing, who’s getting it and when

   Every job between ‘work complete’ and ‘ready for billing review’ shows the missing items, one person responsible, and a follow-up date. If you can’t name what’s missing, either the job is ready for review or nobody has checked.

4. Review the queue weekly, oldest first

   List every finished job with no invoice, oldest first. For each: what’s missing, who’s getting it and when, and is it stuck on a decision, like a dispute or unapproved extra work? Escalate anything past the limit you set.

   Before a job moves on to invoicing, check it against the scope: everything done and evidenced, extra work approved in a form you can file, and the invoice in the customer’s format. A few minutes here can save a rejected invoice.

5. Fix repeat gaps at the source

   If signed job sheets are missing on most call-outs, the fix isn’t better chasing. It’s getting the signature on site, before the job can be marked complete. If purchase order numbers always arrive late, ask for them at booking.

Worked example: a week’s billing queue#

Start this week#

1. List every finished job with no invoice yet. Check the job list, the group chat and the calendar.
2. Next to each one, write what’s missing, who’s getting it and by when.
3. Sort by date finished, oldest first, and start at the top.
4. Write the requirements for your three most common job types.
5. Put a twenty-minute queue review in the calendar, same time each week.

That first list is the most useful thing in this guide. Everything else is about keeping it short.

Template: Billing readiness tracker#

When the tracker stops being enough#

1. The same items go missing on siteA completion form that asks for signatures, photos and notes before a job can be marked complete, with a ‘couldn’t get it’ option that becomes a named missing item.
2. Requirements change by customerRequirements kept as data, by job type and customer, so a job’s missing items are worked out rather than remembered.
3. Job and accounting systems disagreeA connection that keeps the job reference and invoice number in both, and drafts the invoice when a job reaches ‘ready for billing review’. Sending stays a person’s decision.
4. Follow-ups depend on someone rememberingReminders driven by the follow-up date, and a weekly queue that builds itself.

For whoever builds it

Setup notes#

Stages and data

• Store the stage as one field with fixed values. If you can, record the date each stage was reached: ‘days in this stage’ tells you more than the stage alone.
• Keep ‘On hold’ separate, with a reason, so held jobs don’t distort the age of the queue.

Job and accounting systems

• Decide which system owns the job reference and which owns the invoice number, and store both in each.
• Watch for invoices raised outside the process, such as a quick invoice made directly in the accounting software. Unless they’re matched back to the job, the job will look unbilled.

Checking it’s working

• Jobs between work complete and invoice issued, counted weekly, and the age of the oldest.
• The most common missing item. If it never changes, the source hasn’t been fixed.

What this won’t do#

• It won’t get you paid on its own, or create revenue. It helps you invoice work you’ve already done, sooner and with fewer queries. When and whether customers pay is a separate matter.
• It isn’t legal or accounting advice. What you can bill, and when, depends on your contracts and terms.

Want it built into your business?#

Where I help: turning your scopes, customer processes and terms into requirements your team can check, connecting job and accounting records so finished work doesn’t fall between them, and setting up the weekly review so it keeps happening without you.

Book a free 30-minute call How working together works