How to Invoice Approved Change Orders: A Contractor Example

Invoice an approved change order by tying the invoice to the original contract, the written approval, and the extra work actually authorized. In practice, the document should make five things easy to see: the original scope reference, the change-order approval reference, separate lines for the added work, the amount due for that change, and the revised total project value.

If the extra work is approved, you usually have two clean billing options: send a standalone invoice just for the change, or add the change as separate lines on the next base invoice that has not yet been issued. The right choice depends on where you are in the billing cycle, but in both cases the goal is the same: the customer should be able to match the invoice back to the approval without guessing.

A practical starting point is a contractor invoice template that lets you show business and client details, line items, tax and currency settings, payment instructions, and a PDF version for review before sending.

Approval comes before the invoice

A change order records that the agreed scope, price, timing, or some combination of them has changed. The invoice is only the request for payment. It does not create approval by itself, and it is not proof that payment was made.

Before you invoice, gather the supporting records in one place:

original quote, proposal, or contract reference
job or site reference
written change approval from the authorized person
approved scope description
approved price or pricing method
any purchase order amendment the client's accounts team requires

Clear records matter because vague lines such as “extras” with no approval trail can create avoidable payment questions after the work is done. The IRS also expects businesses to keep a recordkeeping system suited to the business and to retain supporting records; see IRS business recordkeeping guidance.

What an approved change-order invoice should show

For a contractor, the invoice does not need to be complicated. It needs to be specific enough that someone outside the project team can still understand it.

A strong approved-change invoice usually shows:

Invoice element	Why it matters
Invoice number and date	Basic billing reference
Your business details and client billing details	Identifies the parties
Original project or contract reference	Links the bill to the base job
Change-order reference, such as CO-01	Links the bill to approval
Approval date or signed approval note reference	Helps accounts verify authorization
Separate line items for added labor, materials, or lump-sum work	Shows exactly what changed
Change-order subtotal	Isolates the value of the variation
Tax treatment if applicable	Keeps the billing presentation clear
Amount due now	States what is currently being requested
Revised project value	Shows how the total job value changed
Payment instructions	Tells the client how to pay

If you use software, the value is presentation and tracking, not entitlement. For example, a contractor invoice template can help you lay out itemized change work consistently, and InvoiceSonic supports client details, line items, tax and currency settings, payment instructions, PDFs, saved client details, and invoice status tracking.

Worked example: original contract $10,000, approved extra $600

Here is a fictional USD example. Tax is excluded for illustration so the arithmetic stays focused. Actual tax treatment varies by situation.

Assumptions:

Original contract value: $10,000
Change order approved in writing: CO-01
Approved additional work value: $600
No previous invoice has included this $600

Example invoice detail for the approved change

Invoice field	Example entry
Original project reference	Quote Q-201
Job reference	Kitchen remodel, 18 Oak Street
Change approval reference	CO-01
Approval date	8 Sept 2026
Currency	USD
Tax	Excluded for illustration

Line item	Amount
CO-01: additional labor for approved cabinet filler adjustment	$400
CO-01: additional materials and trim to complete approved adjustment	$200
Change-order subtotal	$600
Amount due now	$600

Revised project value summary

Project summary	Amount
Original contract value	$10,000
Approved extra CO-01	$600
Revised project value	$10,600

That revised project value gives context without rebilling the original work. It tells the client that the total job value is now $10,600, while this invoice concerns only the approved $600 change.

Option 1: send a standalone invoice for the change

A standalone invoice is often the cleanest choice when the variation is approved after earlier invoices have already been issued, or when the customer's approval path for extras is separate from ordinary stage billing.

Using the same project, assume you have already issued $8,000 of base invoices under the original $10,000 contract. Then CO-01 is approved for $600.

Billing position after issuing the change invoice	Amount
Original contract value	$10,000
Approved extra CO-01	$600
Revised project value	$10,600
Base invoices already issued	$8,000
Standalone change invoice issued now	$600
Remaining base work still to invoice	$2,000
Total invoiced to date	$8,600

This approach works well because it leaves the original stage billing untouched and makes the extra easy to reconcile against its approval. It is especially useful when the client wants variation invoices routed to a different approver or cost code.

A concise description might read:

Approved change CO-01 to Contract Q-201, authorized on 8 Sept 2026. Additional trim adjustment and materials beyond original scope. Amount due for approved variation: $600. Revised project value: $10,600.

Option 2: add the change to an unissued stage invoice

Sometimes the approved extra is known before the next stage invoice has been sent. In that case, one invoice can work well, as long as the base stage and the approved variation are shown separately.

Using the same numbers:

original contract: $10,000
approved change: $600
final unissued base stage: $2,000

Combined invoice lines on the unissued final stage	Amount
Final base stage under original scope	$2,000
CO-01 approved extra work	$600
Invoice total	$2,600

That is acceptable only if the $600 has not already been invoiced elsewhere. If you already sent a standalone invoice for CO-01, do not add it again to the final stage invoice. In that case, the final base invoice remains $2,000 and your project summary should note that CO-01 was billed earlier.

If you are deciding how this fits into the rest of the job, see Progress Billing for Contractors: A Worked Invoice Example. For the wider timing of deposits, milestones, and final billing, see Contractor Payment Schedule: Deposits, Milestones and Final Payment.

Two edge cases that deserve care

1. The change is approved, but the amount is later revised

Suppose CO-01 was first approved at $600, but you later agree a $200 reduction because one material item is no longer needed. The net approved addition becomes $400.

Do not quietly erase the earlier history. Keep both references in your records and invoice only the current agreed amount under your normal correction process. Your revised project value would then be:

original contract: $10,000
net approved addition: $400
revised project value: $10,400

The practical point is traceability. The client should be able to see why the number changed and which approval record now controls.

2. The work was done, but approval wording is vague or disputed

On fast-moving jobs, someone on site may say “go ahead,” but the customer later disputes scope or price. In that situation, keep the undisputed original-scope billing separate from the disputed variation in your records. Do not bury the extra inside general labor lines.

Maintain your own supporting file showing the original scope reference, the change request or site instruction, who approved it if anyone, what extra work was done, and the amount claimed. Then decide whether the item should be invoiced now or held pending resolution. The invoice format cannot fix a missing approval trail.

Review the invoice before sending

Before you send the PDF, check a few points that prevent most confusion:

Final check	What to confirm
Original reference	Contract, quote, or job reference is visible
Approval reference	Change order is named or numbered clearly
Itemization	Added work lines are specific enough to understand
Amount due now	The invoice isolates the approved change amount
Revised value	The new total project value is stated correctly
No double billing	The $600 has not already appeared on another invoice
Combined invoices	Base stage and variation are shown separately
Payment status	Outstanding amounts are checked against actual payment records

That last point matters. An invoice is not payment proof, so if you are assessing what remains unpaid, check your payment records separately rather than assuming an earlier invoice was paid.

Keep the billing summary aligned

Once the invoice is prepared, update your project billing summary so the contract value, approved extras, invoiced amounts, and remaining unbilled work still reconcile. If the variation changes billing timing, your wider payment schedule may need updating too.

The practical goal is simple: make every approved extra easy to trace from scope change, to approval, to invoice, to payment record, without rebilling the base work or losing the revised project value along the way.