Reconcile Contractor Progress Invoices Before the Next Stage

Before you send the next stage invoice, reconcile four figures in one project ledger: issued to date, paid to date, approved variations, and work completed but not yet invoiced. That is the check that stops a stage being billed twice, shows short payments early, and keeps the invoice aligned with the job record.

For contractors, the usual problem is not one bad line item. It is drift across the contract, variation approvals, prior invoices, site records, and payment receipts. If the next invoice is built from memory instead of the ledger, you can easily rebill a stage, miss a credit, or confuse unpaid work with uninvoiced work.

A contractor invoicing setup can help present staged billing clearly, especially if you manually enter previous billing and track invoice status. See contractor invoicing software for staged billing. The reconciliation itself still depends on your own ledger and actual payment records.

What to reconcile before the next invoice

Use simple categories that answer different questions:

The distinction between issued and paid matters. An invoice is not payment proof; paid to date must come from separate receipt or payment records, consistent with IRS business recordkeeping guidance.

This article is about controlling progress invoices before the next stage goes out. It does not calculate formal payment applications or retainage. If your customer uses those, track them separately in your own records and customer-facing documents as required.

Worked ledger: three stages, variations, and a partial payment

Assumptions for illustration only: fictional residential renovation project, USD, tax excluded, and no retainage calculation.

Planned billing structure before reconciliation:

1. Stage 1: Demolition and site prep: 8,000
2. Stage 2: Rough-in and framing: 12,000
3. Stage 3: Finishes and handover: 10,000
4. Net approved variations: 2,000
5. Revised contract value: 32,000

Now the ledger:

As of June 10, site records show the remaining scheduled work is substantially complete. Before creating the next invoice, reconcile the project:

• Revised contract value: 32,000
• Issued to date: 20,000
• Paid to date: 15,000
• Unpaid issued amount: 5,000
• Remaining value not yet invoiced: 12,000

The next invoice should be based on what has not yet been invoiced, not on what remains unpaid. Those are different numbers.

So if all remaining work is billable now, the amount to invoice is:

32,000 revised contract value - 20,000 issued to date = 12,000

That 12,000 can be invoiced as the remaining project balance only if your schedule clearly allocates the final 10,000 stage plus the net 2,000 of approved variations to that final billing. Otherwise, show Stage 3 as 10,000 and list the approved net variations separately as 2,000.

How duplicate stage billing happens

The common mistake is a carry-forward error.

Using the same example, imagine the June invoice is drafted like this:

• Stage 3: 10,000
• Approved exterior drain variation: 2,400

That creates a new invoice for 12,400. Each line may look reasonable on its own, but the project ledger says only 12,000 remains uninvoiced because the approved variations net to 2,000, not 2,400. The omitted shelving credit of -400 must still be reflected.

A second mistake is rebilling Stage 2 because it is not fully paid. The unpaid 5,000 from Stage 2 is an outstanding receivable. It is not new billable work. If you add any of that original Stage 2 value into the next invoice again, you are mixing collections with current billing.

A quick control question catches both problems:

If I issue this invoice today, will issued-to-date exceed the revised contract value or repeat a prior stage amount?

If yes, stop and reconcile before sending.

Build the invoice from the ledger, not from memory

A practical sequence is:

1. Confirm the latest approved contract value, including adds and credits.
2. Total every invoice already issued for the job.
3. Match payments actually received to get paid to date.
4. Identify completed work not yet invoiced.
5. Draft the new invoice only for that uninvoiced amount.
6. Reference prior billing where your format allows, so the customer can see what is new.

If you use progress invoicing tools for contractors, you can create the invoice with client details, line items, tax and currency settings, payment instructions, and a PDF record, while manually entering previous billing for progress invoices. That helps present the invoice clearly, but your variation register, approval log, and payment records remain separate operational controls.

If the weak point is earlier in the process, billing from the job site can reduce missing details, and improving the office-field billing handoff can reduce omissions before the invoice is prepared.

Two edge cases that need extra care

Approved work completed, but variation not formally cleared

A crew may finish extra work after a verbal instruction, but the variation has not yet been approved in the way your business requires. In that situation, keep it out of approved variations and out of the next invoice if you are treating it as settled work.

Better ledger treatment:

• record the work and completion date
• keep the amount in a pending variation list or separate register
• move it into billing only when it becomes approved, or under a clearly agreed interim arrangement suitable for your contract

That avoids overstating the revised contract value.

Partial payment with unclear allocation

If a client pays 7,000 and the remittance does not say which invoice it relates to, do not guess. Check the payment record, remittance, and correspondence. Your invoice tracking may show what was sent or viewed, but views do not prove payment.

If the allocation is still unclear, record the receipt as unapplied or provisionally applied until you confirm it. That prevents a false paid balance and avoids accidental rebilling.

Keep records that support the invoice trail

Your ledger does not need to be complicated. It does need to be consistent and supported by records that clearly show what was billed and what was paid. The IRS says businesses should keep a recordkeeping system suited to the business that clearly shows income and expenses and retain supporting records: IRS business recordkeeping guidance.

For progress billing, support usually includes:

• signed contract or accepted quote
• approved variation records and credits
• invoice copies and invoice numbers
• payment receipts or confirmed payment records
• site notes or internal completion records
• correspondence explaining disputes or partial payments

Software can centralize invoice creation, saved client details, PDFs, and tracked send or view status, but those features do not replace the reconciliation step. If you want plan details, use InvoiceSonic pricing.

The control to apply before you press send

Reconcile the project total first, then draft the next invoice. When issued to date, paid to date, approved variations, and uninvoiced work all agree, the next stage bill is much easier to defend and much less likely to duplicate a prior stage.

That matters most when the job is moving quickly and an earlier invoice is only partly paid. The unpaid balance should stay visible, but it should not distort what counts as newly billable work. If you keep that distinction clear every time, your progress invoices stay cleaner for your team and clearer for your client.