Contractor Billing Handoff: From Site Notes to Invoice

A reliable way to move from site notes to an invoice is to treat billing as a handoff with three checks: the foreperson confirms what was completed, the billing clerk verifies the records support billing, and the customer approver signs off on changed work before it reaches the invoice.

That matters because the office often receives scattered notes, photos, texts, and verbal updates, then has to bill under time pressure. When the handoff is loose, quantities get rounded, unsigned variations slip in, and the customer receives an invoice that does not match their view of the work.

Using contractor invoicing software can make invoice creation easier, but the app does not replace the records behind the bill. Site notes, delivery dockets, variation forms, and approval logs are still your separate operational records. The IRS says businesses may use a recordkeeping system suited to the business as long as it clearly shows income and expenses and supporting records are retained: IRS business recordkeeping guidance.

Assign each person one job

A handoff works best when each person owns a narrow responsibility.

The foreperson confirms field facts for the billing period: what was finished, what remains open, what materials were installed, and what customer-requested changes occurred. The foreperson is not guessing how the office should bill; the job is to pass on reliable field information.

The billing clerk turns approved, documented work into invoice lines. The clerk should not infer quantities from partial notes or include unsigned extras because "everyone knows it happened." If the support is incomplete, the item belongs in an exception queue, not on the invoice.

The customer approver handles signoff on changed work, stage acceptance, or customer-side references the customer wants included. A purchase order number or cost code may help routing, but it does not replace a signed variation or any separate approval requirement.

This split prevents two common failures: the foreperson trying to bill from memory, and the office acting as if the invoice can repair missing project records.

What the foreperson should hand over

The field package does not need to be polished. It needs to let someone in the office understand what can be billed now and what cannot.

The key question is not, "What can we probably charge?" It is, "What can another person support from the records?" If a quantity is still estimated, label it clearly and hold it from billing unless your contract allows that treatment and the record is clear.

The billing clerk's pre-invoice review

Before drafting the invoice, the billing clerk should run a short review against the field package:

1. Match each proposed line to completed original scope or an approved variation.
2. Confirm the dates fall inside the billing period.
3. Check quantities, units, rates, and arithmetic.
4. Separate completed work from partly completed work.
5. Confirm support exists for materials or outside costs.
6. Remove anything that depends on an unsigned variation.
7. Add customer-required references without treating them as approvals.
8. Put blocked items on an exception list.

At this stage, software for contractor invoicing helps with the document itself: business and client details, line items, tax and currency settings, payment instructions, a PDF copy, saved client details, status tracking, and reminders subject to settings and plan limits. Those features help with sending and follow-up, but they do not solve missing approvals or missing field support.

If your process problem starts with invoices drafted from the truck or site gate, see Invoice App for Contractors: Bill Clients From the Job Site. If the job uses staged claims and you need to compare prior billing before the next stage, see Reconcile Contractor Progress Invoices Before the Next Stage.

Worked example: what gets billed now

Assume a fictional U.S. contractor is billing in USD. Tax is excluded for illustration, and actual tax treatment varies by situation.

The invoice subtotal prepared now is:

• Wall framing: 120 x 18.00 = 2,160.00
• Door hardware: 6 x 85.00 = 510.00
• After-hours callout: 3 x 95.00 = 285.00
• Total to invoice now: 2,955.00 USD

The unsigned variation and the internal rework stay off the invoice. Sending 3,735.00 USD and then arguing about 780.00 USD of unsupported items usually creates more friction than waiting one cycle for proper signoff.

Keep an exception queue for unsigned changes

The exception queue prevents a false choice between delaying the whole invoice and slipping disputed items into it.

A simple exception list can include five fields:

Unsigned changes are not the same as forgotten work. They may become billable later, but they should not be blended into clearly earned amounts now. Keeping them visible also reduces the chance that the variation disappears when memories fade.

Two edge cases worth a clear rule

Partly completed scope at period end

A frequent handoff problem is work that is started but not truly finished. The field team may say it is basically done, while the customer expects testing, cleanup, or final fixings before calling it complete.

Set a rule: if the contract or job record defines a measurable unit, bill the measured completed portion only. If it requires a completed deliverable, hold the line until the deliverable is actually complete. Do not turn vague phrases like "90 percent done" into invoice math unless the billing method expressly allows it and the record explains it.

Customer approver unavailable

Sometimes the usual customer approver is on leave or slow to respond. That does not mean all billing stops. The office can still invoice fully documented original-scope items that do not require fresh approval, while moving approval-dependent items to the exception queue.

A related mistake is assuming a customer reference field makes the invoice valid for every internal customer workflow. It does not. A purchase order number, site contact, or cost code may help routing, but it is not a substitute for signed approval on changed work.

Ask for missing approval without padding the invoice

When a variation is the blocker, a short request is usually better than a long argument. Try this, replacing the bracketed placeholder before sending:

Please confirm approval of the attached variation for the additional corridor backing completed on [insert date]. We have included the site notes and photos for reference. Once approved, we will include it on the next invoice. The current invoice will cover only completed, documented items from the original scope and signed extras.

That wording identifies the missing step, attaches evidence, and reassures the customer that the current invoice is limited to supportable items.

Turn verified records into the invoice

Once the checks are complete, draft the invoice so the line items match the approved wording and quantities from the handoff pack. Include business and client details, billing date, line items, currency, relevant tax setting, and payment instructions. If useful, save the client details, generate the PDF, and monitor status after sending.

If there has been a deposit, short payment, or prior part-payment, confirm the balance against actual payment records before carrying amounts forward. An invoice is not proof of payment, and a viewed invoice is not proof that funds were received.

For teams standardizing this last step, review how contractor invoicing software handles invoice fields, saved client details, status tracking, and reminders. If you also need plan details, see pricing.

A defensible contractor invoice starts earlier than the billing screen. If the foreperson hands over complete field records, the billing clerk verifies support before drafting, and the customer approver signs off on changed work, the next invoice becomes easier to explain line by line. Bill what is completed, documented, and approved now; queue what is real but not yet supported; and leave rework or unresolved changes off the invoice until the record catches up.