How to capture extra work before the final invoice
Invoicing workflows
The short answer
Capture extra work when it is requested, link it to the job and record the proposed scope, pricing basis, decision and completion separately. Keep pending requests out of approved billing lines. Before preparing the final invoice, review the accepted quote alongside approved changes and earlier billing. A small change register in your existing tool can be enough, provided someone owns unresolved items and each approved charge can be traced to its source.
A note that says 'did a little extra' is difficult to use at billing time. The office needs to know what changed, what the customer agreed and whether that work has already been invoiced.
Record the request before it becomes a billing puzzle
Create an extra-work entry when a request arrives, whether it comes by phone, message or an on-site conversation. Link it to the job and accepted quote. Describe the requested change in plain language, including what is different from the original scope. A general job note can point to the entry, but should not be the only record.
Do not turn an observation into a charge automatically. A staff member may record a possible improvement, corrective work or something already included in the quote. The entry first establishes a question to resolve. Your business decides how requests are assessed and agreed before the workflow treats them as approved billing information.
Separate requested, agreed, completed and billed
Use statuses that answer one question at a time. A request can be approved but not completed; work can be completed while a billing decision is still unresolved. 'Done' should not stand in for both facts.
- Requested
- Someone has asked for a change or reported a possible extra.
- Needs assessment
- Scope, quantity, price or responsibility is not settled.
- Approved or declined
- The decision and supporting record are stored.
- Completed
- The agreed additional work has been carried out.
- Included in billing
- The relevant invoice reference and billed portion are recorded.
These are operational labels, not a legal approval template. Agree what evidence your business requires, and seek appropriate advice about contractual requirements.
Keep a small, useful change register
- A unique change reference and linked job.
- The request date, source and description.
- The proposed quantity, price or agreed calculation basis.
- The decision, decision date and evidence location.
- The person responsible for resolving open questions.
- Completion details and any remaining work.
- The invoice reference and amount or portion already included.
Keep internal working notes distinct from the wording intended for the customer. Preserve the original request rather than rewriting it to imply agreement. If details change, record a revision. The next reviewer should be able to see what was proposed and what was ultimately approved without reconstructing an entire message thread.
Illustrative example: three extras, three different outcomes
The following illustrative register shows why a list of completed tasks is not automatically a list of charges.
| Entry | Recorded decision | Billing review |
|---|---|---|
| E-01: additional adjustment | $80 approved and work completed. | Check whether it appears on an earlier invoice. |
| E-02: second visit | Request recorded; price not agreed. | Hold for a decision, not an automatic charge. |
| E-03: minor correction | Manager records no-charge treatment. | Retain the reason; do not add a paid line. |
If E-01 was already billed at an earlier stage, its reference prevents it appearing again. E-02 remains visible even though it is excluded from approved lines. E-03 explains why recorded work and chargeable work differ.
Review the whole job, not only the latest message
Before final billing, compare the accepted quote version, approved changes, completed work and earlier invoices. Resolve pending changes with a named person. If the business decides to proceed while an item remains open, record that decision and what happens to the unresolved item next.
For work billed by agreed time or quantity, compare the records against the applicable pricing basis. More recorded time does not necessarily mean a new approved extra. Similarly, a fixed-price change should not be billed again as separate time entries. Your accounting reviewer determines how approved information becomes financial transactions; the operational register helps make that review complete.
Use an existing tracking feature when it fits
Check whether your current tool can save unbilled work, associate it with a customer and mark it as included once invoiced. Conta's work-tracking documentation provides one example of recording work before creating an invoice. A work tracker still needs your approval rules; recording an entry is not proof the customer agreed a charge.
If a shared register plus links solves the problem, keep it simple. A connection becomes useful when approved records repeatedly have to be copied into billing. Define which statuses qualify, how partial billing is recognized and how an entry is prevented from appearing in two drafts.
Make capturing extras workable during the job
Ask the delivery team to capture what they can know: job reference, request and relevant evidence. Let the appropriate reviewer supply pricing and approval decisions. A long form that requires on-site staff to make financial judgments can encourage skipped records or guesses.
Review unresolved entries during the job rather than discovering them only at the end. We scope customer invoicing workflows that carry accepted work and reviewed changes into billing preparation. This is process and tool implementation, not dispute resolution, bookkeeping or a legal change-order service. The useful starting point is a blank current template and an anonymized example of where an extra gets lost.
A few follow-up questions
Does a photo prove an extra charge was approved?
A photo may show work or site conditions, but it does not by itself establish an agreed price or scope change. Store the decision evidence required by your business process separately.
Should we delete declined extras from the job?
Keep an appropriate record of the outcome so the same request is not reopened or billed by mistake. Retention and access should follow your business's policies and any applicable requirements.
What if work was completed before approval was recorded?
Flag it for the responsible person to resolve. Do not fabricate an earlier approval or let invoice generation make the decision. Record the actual sequence and the eventual billing instruction.
Sources and further reading
Keep approved extras connected to billing
Tell us how requests reach your team, where decisions are recorded and which tool prepares invoices. We can scope a practical change register and handoff.
Discuss extra-work tracking See what our invoicing workflows service includes