The job is finished. Why hasn’t the invoice gone out?

The useful check is simple: take the work your operations team marked complete and find the invoice, or the documented reason it is not due yet. Start with 1 service line and the last 30 days. Every unmatched job gets an owner and a next action.

A completed-job list and an unpaid-invoice list answer different questions. The second tells you who owes money on invoices already issued. It cannot tell you about work that never became an invoice.

That gap matters when a contractor, agency, or service business keeps delivery in 1 system and billing in another. A technician closes a job. A project manager marks a milestone complete. Finance waits for a signed worksheet, an approved timesheet, or an email that nobody realizes they were supposed to send.

The work is finished. The billing handoff is still open.

Before calling that lost revenue, check the agreement. Some work belongs to a retainer. Some requires customer acceptance. Some is billed at month-end. The question is whether each completed job has reached its agreed billing point and, if it has, what is holding it there.

Walk 1 completed job before exporting everything

Pick an ordinary job your team finished last week. Follow it from completion to billing.

What tells finance the work is ready? Is that event a status change, an approved time entry, a delivery confirmation, or a person sending a message? Where does the agreed price live? Who supplies the evidence the customer requires?

Then find the invoice. If there is none, ask the person responsible for billing what they are waiting for. Ask the delivery owner whether they knew that was still outstanding.

If both people give the same answer and there is a due date, the process may be working. If each thought the other had finished their part, you have found the handoff to examine.

This is especially useful where jobs are completed separately and billed separately. If every job is prepaid, or a fixed subscription covers the work without a separate billing event, this particular check may add little.

Build the comparison from 2 lists

Export completed jobs, deliveries, or milestones from the system operations actually uses. Include work finished in the last 30 days and older items already waiting for billing.

Export invoices for the same customers and a sufficiently wide date range to catch advance billing and consolidated invoices. Include invoice lines where several jobs can appear on 1 invoice.

Match using a job, order, project, or milestone reference. Customer name alone is insufficient: the same customer may have 6 jobs open. If there is no shared reference, manually check a small sample before trusting a bulk comparison.

Keep the result on 1 page:

Field	What it answers
Job or milestone reference	Which piece of work are we tracing?
Completion date	When did operations finish it?
Billing condition and due date	What must happen before billing is permitted?
Invoice reference and amount	Has it already been billed, wholly or partly?
Exception and evidence	What explains the gap?
Owner and next action date	Who will resolve it, and when?

An unmatched row is a question to investigate. It is not permission to send an invoice.

Separate 4 outcomes

Already billed. The job was included in a consolidated invoice, billed in advance, or recorded under another reference. Correct the match. Do not count it as an opportunity.

Not due yet. The work is under a retainer, awaiting a contractual milestone, or included in a scheduled billing run. Record the reason and date. Completion alone does not establish a right to invoice.

Blocked. Billing is due, but a timesheet, purchase-order reference, acceptance record, or price approval is missing. Give the missing item an owner. A dispute about scope or quality also belongs here until the responsible person resolves it.

Omitted. The agreement and completion evidence support billing, but the job never reached the billing queue. Finance checks the amount and authorization, then issues the invoice through its normal process.

These distinctions protect the usefulness of the exercise. A report that calls every unmatched job “money found” will produce an impressive total and an unreliable decision.

An illustrative check

Suppose a service company compares 40 completed jobs with its invoice records. After matching consolidated invoices, 6 jobs remain unmatched.

Outcome	Jobs	Value excluding tax	Decision
Included in a retainer	2	$3,000 equivalent	No additional bill
Milestone not yet due	1	$4,000	Review at the agreed date
Missing completion evidence	2	$5,000	Resolve the billing block
Omitted from the billing queue	1	$1,200	Confirm and issue the invoice
Total unmatched	6	$13,200	Investigate by outcome

The $13,200 is not additional revenue. Only $1,200 is confirmed omitted billing in this example. The $5,000 is work to resolve. The $4,000 follows its existing schedule. And the retainer creates no extra invoice.

Even issuing the $1,200 invoice does not prove collection or establish when revenue should be recognized. Those decisions depend on the contract and the company’s accounting treatment. Finance makes them.

All figures are illustrative. Do not multiply this month’s exception total by 12 and call it annual savings. Check whether the cause repeats, whether previous jobs were eventually billed, and what the business can reasonably collect.

Fix the handoff that created the exception

For the next month, hold a short weekly review of completed work without a resolved billing outcome. Finance and the delivery owner should be able to work from the same list.

Choose a billing-ready condition that fits the agreement. A job may be operationally complete but still require acceptance or approved time before invoicing. Keep those states distinct.

Then make 3 things explicit:

• The completion record carries the reference finance uses to match the job.
• A named person supplies the remaining billing evidence.
• An overdue exception reaches an owner instead of staying on an unmonitored list.

Use an existing report or saved view first. At modest volumes, a shared exceptions sheet may be enough. If someone must rebuild the same comparison every week, evaluate whether the existing systems can share the reference and produce the list automatically.

Automatic invoice creation needs a separate decision. Confirm pricing, partial billing, credits, and approval rules before enabling it. An alert that brings a job into the billing queue can solve the immediate problem without taking the final billing decision away from finance.

Measure what changed

After 30 days, compare the number and age of overdue billing exceptions. Track confirmed omitted invoices separately from invoices issued sooner.

Faster invoicing can improve cash timing when customers pay from the invoice date. It does not create another year’s worth of revenue. Fewer hours spent chasing job evidence are a separate benefit, measured from actual time saved. Freed staff capacity is not automatically a payroll saving.

If the review finds no overdue jobs and the handoff is traceable, keep the process you have. If exceptions recur, fix the common cause before expanding the exercise across the company.

Where FoundMargin can help

FoundMargin examines how work moves between the systems a business already uses. For a completion-to-billing gap, that means tracing a sample of jobs with operations and finance, comparing the records you provide, and identifying the step where information stops moving.

We can put evidenced exceptions and avoidable administrative effort into a findings ledger, with a proposed fix, owner, and cost to implement. Your finance team validates billing eligibility and the amounts. A saved report may be enough. A system configuration or integration may require separately scoped implementation.

The first useful result is a list the business can act on: work already billed, work legitimately waiting, and work that needs someone’s attention. Start with last month’s completed jobs. Find the invoice or the reason it is not due. The unresolved rows tell you where to look next.