Job invoicing: finished work, never invoiced

There's one finding about job invoicing from my operations work that I keep coming back to.

We found around $200,000 of work that was finished and never invoiced. (A real example from a past operations role. Details kept private.)

The work had been delivered. The project management system wasn't talking to the accounting system. The timesheets weren't talking to the project management system. Everything was done, but the invoices had never been sent.

What stays with me is the gap between “job done” and “invoice sent”. That is the handover I want to talk about: the handover between finishing a job and sending the invoice. A job can be complete in one system without being ready for accounts to bill in another. I would start by making that handover visible.

Start your job invoicing check with one question

When I talk to business owners, this is one of the first things I ask: can you see, today, every finished job that has not been invoiced yet?

If answering that question means asking around, start by following one job. Pick a completed job and check where its record sits. Then find the invoice record. I want to be able to connect the two without relying on someone to explain what happened.

The point of this check is to understand the handover. I would trace the signal that tells accounts the work is complete, where it goes and who checks it. Then I would check how missing information is flagged before billing.

Write down the steps you actually find. Include the spreadsheet, the email and the conversation if they are part of the process. A process written on a page is only useful here if it matches how the job reaches accounts.

One job record both teams can use

I would start with one job record that operations and accounts can both use. It needs a clear reference so that completed work can be matched to the right invoice. The question is whether both teams can identify the same job and see what needs to happen next.

That does not mean buying new software before you understand the problem. First, check what your existing systems can show. I would check whether the project reference links to the accounting record, accounts can see the completion status and operations can see whether the invoice has been sent.

Keep the first pass small. Follow a job from completion to invoice and note each point where someone has to copy information or ask for an update. Those are the places to check before deciding what to connect or change.

Make work complete a clear step

Agree what “work complete” means for the handover. A status called complete needs to tell the next person something they can act on. If it only tells the project team that delivery has finished, accounts may need another step before billing can start.

On the shared record, make that next step visible. Work complete should trigger an invoice check. The check asks whether the job has been invoiced and, if it has not, what is needed before an invoice can be sent.

Keep completion and invoicing as separate checks. Marking a job complete does not prove an invoice exists. Creating an invoice does not prove it has been sent. Your record needs to show where the job is in that sequence, rather than treating those steps as the same thing.

Give the invoice handover a named owner

One named person should own the invoice until it is sent. That person needs a way to see which completed jobs are waiting and what is holding each one up. If a detail is missing, record the detail and who needs to provide it.

Ownership needs to cover the handover, too. Name the person who picks up the completed job, follows up missing information and confirms that the invoice has gone out. Make those answers clear enough that the next job follows the same steps.

Connecting the systems can help move the information. It does not answer every question about who acts on it. Agree the owner and the next action before treating the connection as the whole fix.

Check finished jobs waiting for invoices

Create a list of completed jobs that have not been invoiced. Check it every week. For each job, show the job reference, its completion status, the invoice status, the owner and the next action. Keep the list focused on the handover you are trying to see.

If something is waiting, record why. I would check for missing information from operations, a job reference missing from the accounting record, or an invoice prepared but not sent. Record what you find against the job so the next action is clear.

Use that weekly check to test whether the process is working. Take a job that has moved off the list and trace it through to the sent invoice. Then take one that is waiting and check whether its owner knows what is needed next.

Connect the steps you can explain

Once the handover is clear, look at which parts your systems can carry. A completion update could create an invoice check. The shared job reference could help match the records. The list could show which jobs need attention. Confirm what your software supports before choosing the setup.

Test the handover with a completed job before expanding it. Check the signal, the record, the owner and the sent invoice. If a step does not work, you have a specific gap to fix and a way to check it again.

I would start with that visibility. Follow your finished work through to the invoice being sent, with one record, a clear completion step and someone responsible for the handover.

Is this happening in your business? Send me a message and tell me where things are getting stuck.