A technician is already on-site. They discover a hidden leak, non-compliant material, or a repair that no one could have seen during the initial quote. The team fixes the issue to avoid a costly return trip. Two weeks later, the office receives an incomplete timesheet, three photos on a phone, and an awkward question: can we still add this amount to the invoice?
Knowing when to invoice for additional work is not just about choosing a date. It is a matter of proof, authorization, and the flow of information between the field, the project manager, and the administration. When this flow is unclear, unplanned work quickly becomes time absorbed by the company rather than revenue billed to the client.
The right time: before executing, not after
In most cases, the best time to invoice for an extra is prepared before the work is even done. As soon as a team notices a discrepancy between the planned scope and the reality on-site, they must be able to identify it as such in their work order or project.
The profitable reflex is simple: stop, document, price, and get authorization. This is not about unnecessarily slowing down an intervention. It is about clearly distinguishing what is included from what is not, while the context is still visible to everyone.
Written approval—via email, on-site signature, acceptance of a revised quote, or validation in the work document—protects both the client relationship and your margin. The client knows what they are buying. Your team knows what to do. The office knows what to invoice.
However, there are exceptions. An emergency related to safety, the prevention of major damage, or service continuity may require immediate intervention. In such cases, the team must record why they acted without waiting for formal authorization, notify the client as soon as possible, and have the work performed confirmed. Urgency does not eliminate the need for traceability: it makes it even more necessary.
What turns an extra into a defensible amount
Additional work is billed effectively when it is linked to specific facts, not memories or verbal conversations. The file must tell the same story from start to finish: what was planned, what was observed, what was authorized, and what was actually executed.
To achieve this, keep at a minimum the description of the problem, before-and-after photos, time worked, materials used, and the identity of the person who approved it. If the price could not be set in advance, also document the calculation method: hourly rate, cost of parts, equipment rental, travel, or subcontracting fees.
Let’s take a common example in property management. A work order calls for replacing a faucet. On-site, the plumber notices that the shut-off valve is seized and the piping behind the wall is corroded. Replacing only the faucet would not properly fix the problem. The technician takes photos, adds a clear note, estimates the hours and parts, then obtains the manager's agreement. The extra will not be a surprise on the invoice: it is already a validated element of the file.
This discipline also applies to small discrepancies. Ten minutes here, a fitting there, an additional trip: taken separately, they seem trivial. Repeated over dozens of interventions, they can erase a significant portion of your monthly profitability.
When to invoice for additional work based on the type of mandate
The timing for generating the invoice depends on your agreement, but validation of the extra should not wait until the end of the project. For maintenance services or service calls, the extra can generally be added as soon as the work order is closed, once hours, parts, and approvals are confirmed.
In a longer project, it is often better to create an amendment or an additional quote as soon as the scope changes. You can then invoice it according to the same milestones as the main mandate, or invoice it separately if the client wants to distinguish costs. This separation is useful when a project owner needs to have extras approved by another department or charged to a separate budget.
For fixed-price work, do not let the extra blend into the initial mandate. The fixed price covers a specific scope, not all unforeseen conditions. Conversely, in a time-and-materials mandate, hours and materials can be invoiced as you go, provided the client knows the applicable rates and receives frequent enough updates so they do not discover an unexpected balance.
The operational rule is as follows: invoice as soon as the work is completed and validated, according to the agreed terms. Waiting for the final invoice creates two risks. Evidence becomes harder to find, and the client associates the extra with a past decision they no longer remember making.
Create a workflow that lets nothing fall through the cracks
A reliable process does not need to be cumbersome. Above all, it must prevent information from getting stuck in a text message, a timesheet, or an employee's memory. Your work document should allow the field team to flag an extra with a visible status, for example, "to be priced," "pending authorization," "approved," or "ready to invoice."
The workflow can look like this: an accepted quote becomes a work order; the team adds an extra with photos and time; the manager sends the price or calculation method to the client; the approval is added to the file; hours, expenses, and inventory items then feed into the invoice. Each step remains attached to the same mandate.
This is precisely the value of a work-document-centered approach. Instead of copying field notes into a spreadsheet and then re-entering them into accounting software, the office retrieves data already entered where the work took place. With Sequentia, a configurable work order can gather validations, photos, time, and materials, then convert what is approved into billing items without double entry.
The level of authorization must match your reality. A company might allow a technician to get an extra approved up to a certain amount, then require a project manager's agreement beyond that. Another will need to have any modification validated by the owner or the client's representative. The important thing is that the rules are clear and the system makes them easy to follow in the field.
Avoid the three most costly mistakes
The first mistake is performing the work assuming the client will understand. Even if the need seems obvious, the client may dispute the price, the delay, or the fact that the option was presented to them. A quick, documented conversation is better than a long negotiation after the fact.
The second is sending an invoice with a vague line like "additional work." Such a description invites questions. Instead, indicate the date, the nature of the intervention, hours, parts, and the reference to the approval. A clear invoice is easier to pay because it answers questions before they are asked.
The third is handling extras only at the end of the month. At that point, the coordinator has to chase down employees, suppliers, and clients to reconstruct the story. Instead, conduct a weekly review of open documents and statuses like "pending authorization" or "ready to invoice." You will quickly see blocked amounts and files that require follow-up.
Make the extra a management indicator
Additional work is not just a billing issue. It often reveals what is actually happening in your operations. If the same type of extra comes up often, your quotes may be too general, your initial inspection lacks information, or your teams regularly encounter the same unforeseen conditions.
Track the value of approved, rejected, and unbilled extras by type of service, client, team, or project. A high rejection rate may indicate a communication or pricing problem. A high amount of unbilled extras signals a direct leak in your process. This data helps you adjust your quote templates, field checklists, and authorization thresholds.
The right reflex is therefore not to ask at the end of the month if you can invoice more. It is to give everyone the means to signal, prove, and get an discrepancy approved the moment it occurs. When the field and the office work in the same file, invoicing for work actually performed becomes a logical consequence of a job well done.
