The Job That Was Already Invoiced
Hours arriving after a job is closed and billed. Where they go, what the practice of refusing them does, and the honest alternative.
Hours arrive after a job has been invoiced: a defect, a question, a small favour, a piece of handover nobody scheduled. The job is closed, the invoice is out, and the hours have nowhere to go. In most operations they go to a standing code, to the next job, or nowhere at all.
The commercial issue in “The Job That Was Already Invoiced” becomes easier to audit when estimated work, recorded hours and approved changes remain distinct. Teams considering tools for project time recording for project time recording can strengthen the project-time evidence without treating a software report as a substitute for the quote, contract or accepted invoice.
Each of those destinations makes a different number wrong, and the third makes the labour hours disappear entirely.
For a separate reference relevant to “The Job That Was Already Invoiced”, consult Association for Project Management resources. Compare the general material with the organisation’s actual contracts, accounting policy and jurisdiction.
Why the job is closed
Because closing is tied to invoicing, which is tied to a financial period. The accounting is correct and it creates a container that can no longer accept the work that is still arriving.
The three destinations
- A standing code. The cost is visible in total and attached to no job, so no job's true cost is known.
- The next job. That job is overstated and this one is understated, and the error compounds if it is the same customer.
- Nowhere. The hours vanish from the job system and appear only in the payroll reconciliation as unattributed.
What the practice costs
The operation loses the ability to say what any job actually cost, which means every estimate built from history is built from a truncated figure.
Jobs with long tails — installations, software, anything with a warranty — are understated systematically.
The honest alternative
Keep the job open for cost after it is closed for invoicing. Two states, not one: billable closed, cost open.
Most systems support this and most policies conflate the two because one date is simpler than two.
The tail
Measure it once: hours arriving against jobs after their invoice date, as a share of the job's total, by job type.
In installation and software work the tail is frequently ten to twenty per cent, and nobody has it in their estimates.
What to do with the figure
Put it in the estimate. A job type with a known fifteen per cent tail should be quoted on the full expected cost, not on the cost to handover.
This is the single most direct use of job costing data and it requires the tail to have been measured, which requires the job to have stayed open.
Warranty as a named container
Where the tail is contractual — a defects liability period — it deserves its own container linked to the job, with its own code.
Then the warranty cost by job type is visible and can be priced rather than absorbed.
Goodwill
The other half of the tail: work done because the relationship matters, with no obligation. Legitimate and worth measuring, because goodwill that nobody counts tends to grow.
A named code makes it a decision rather than a habit.
The reopening question
Some operations refuse to reopen a closed job on principle. The principle is about financial control and it is sound; applying it to cost recording rather than to billing is the error.
Separating the two states resolves it without touching the financial control.
When the hours are a dispute
Where the customer disputes that the work is covered, the hours still happened and still cost money. Recording them against the job is a costing act, not a commercial one.
Keeping the cost record honest is what makes the commercial conversation possible.
The tail by job type
Worth computing separately rather than as an average, because the variation between types is large. A straightforward supply job may have no tail; a complex installation may have a fifth of its hours arriving after handover.
A single blended tail percentage applied to everything understates the complex work and overstates the simple, which is the familiar shape of every averaging problem in this collection.
Closing for cost eventually
The second state cannot stay open forever. A sensible convention closes for cost at the end of the defects period, or a fixed interval after the invoice where there is none.
What matters is that the date is a convention rather than an accident, and that hours arriving afterwards go somewhere named rather than into the catch-all.
What the finance system thinks
Most accounting systems want a job to be either open or closed because the revenue recognition depends on it. A second state can usually be held outside the financial ledger, in the job costing layer, without touching anything the auditors look at.
Where it genuinely cannot, a linked follow-on job with the original's reference is the workaround, and it preserves the analysis.
The tail table
For each job type: cost at handover, cost including tail, and the difference as a percentage. Three columns.
That table is what turns a vague sense that certain work "always comes back" into a number that can be quoted for.