Explain the gap between the invoice and the installed work.

Begin with the measures, not the accusation

A project can show more billed value than installed value without the comparison alone proving an error. The contract payment basis may recognize stored material, design work, mobilization, or other items differently from a field quantity count. Conversely, an explainable difference still needs supporting evidence. Neither a reassuring percentage nor a large gap settles the question.

The first task is to define what each number measures. Requested billing is not necessarily an assessed amount. An assessed amount is not necessarily cash paid. Incurred cost is not the contract selling price. Installed quantity is not automatically earned value, and a package quantity percentage is not whole-project completion.

This method builds a short reconciliation for one scope and cutoff. It extends the metric distinctions in the owner-reporting guide with a traceable reconciliation from requested billing to assessed value and payment. It does not approve an application or determine a party’s payment entitlement.

Put the records on a comparable basis

Fix the scope and cutoff

Locate the current specification and drawings defining the work, the contract’s payment provisions, and the relevant contractor submittals and review dispositions. The owner’s representative uses the retained design and payment reviewers for their assigned assessments. A reporting template should carry those requirements forward, not set new acceptance or payment rules.

Identify the package, reporting date, contract-value basis, and quantity definition. State whether figures are cumulative or current-period. If an application closes earlier than the field report, show both dates or reconcile to a common cutoff. Comparing a cumulative invoice with one week’s production creates a difference that has no useful meaning.

Reconcile the application components

Separate installed work, material stored onsite, material stored offsite, and items in transit or ordered but not delivered. Stored-material progress billing is a common way to fund procurement before installation, including before site receipt where the contract permits. After the required design-submittal approval and other release conditions, the subcontractor should order in time to protect the supplier-confirmed lead time and prepare the supporting monthly application.

Check the actual payment clause and required approval first. For an offsite claim, retain any advance owner approval of payment and storage location, identified inventory tied to the project, invoices and location evidence, title or other agreed protection of the owner’s interest, applicable insurance, delivery arrangements, and required lien waivers or releases. Use forms appropriate to the jurisdiction and payment status. An approved submittal, purchase order, deposit, or shipment forecast alone does not prove eligibility. Record in-transit and not-yet-delivered claims separately and apply their actual contract terms; do not label them stored merely to obtain payment.

When material is incorporated, move its value from stored material to completed work and reconcile prior applications so it is counted once. The monthly payment assessment remains separate from physical completion and from cash actually paid.

Bridge assessed value to cash

List the documented deductions, withholding, prior payments, or other relevant adjustments in the project’s actual payment record. Keep the date of payment distinct from the assessment date. An unpaid amount may reflect timing or a dispute; the difference itself does not identify which. Use the assigned payment review rather than inventing a reason.

Describe physical progress independently

State how installed quantity was measured and which evidence supports it. Counting equal units works only for a defined unit set. Mixed quantities require an agreed method; averaging unrelated percentages can hide the work that matters. If earned value is reported, identify its authorized budget basis and earning rules separately.

Trace a delivery or completion commitment to the entity controlling it, including a subcontractor’s or vendor’s own supplier where relevant. Record that party’s dated confirmation, scope, conditions, evidence, and current document revision separately from the general contractor’s estimate. The contractor coordinates the combined forecast. Neither a vendor promise nor an estimated date proves material is stored, work is installed, or payment is due; those states still require their own evidence and assigned review.

Worked example: one package, five different measures

Use the comparison record

The blank CSV contains one empty row. The worked file records the single fictional package and common cutoff. All amounts are cumulative and use U.S. dollars. The quantity fields identify one set of equal units. The file stores inputs and evidence references; it contains no formulas, accounting integration, or automatic payment assessment.

Complete the requirement-document and revision fields, design and owner review roles, required review reference, actual disposition and evidence reference, and contractor currentness check. Use the unresolved-requirement field to identify a gap and its next action. These entries carry the existing project basis into the record; filling them does not grant review approval or authorize a change.

Record the entity controlling the milestone, its scope, confirmation status and date, evidence and conditions, and the contractor’s separate forecast and coordination action. Check that the confirmation still covers the current revision. Unconfirmed values remain planning estimates.

Enter zero only for a known zero. Leave an unavailable cost budget, assessed amount, or unit count blank, and explain the gap in the unresolved-question field. Calculate a ratio only when its denominator is positive and its basis is understood. A zero or missing denominator does not mean zero-percent progress.

Check that the requested components sum to the billed total and that the assessed-to-cash bridge explains the recorded payment. The worked file uses a deliberately simple bridge. Where several transactions, taxes, offsets, or earlier payments apply, retain that detail in the actual payment schedule and reference it instead of forcing it into an unsuitable single-row model.

Keep revisions under the same scope identifier, with new revision labels and cutoffs. Do not sum repeated cumulative observations. Preserve earlier reports so a later assessment does not rewrite what was known when the application was first reviewed.

Retain specification and drawing revisions, applicable submittal dispositions, and payment-review authority with the linked evidence. If a required document is missing, record the available basis and obtain clarification from the responsible reviewer; an empty reference is not permission to assume compliance.

Close the explanation before changing the headline

Ask whether the field measure and billing record cover the same work, whether their dates match, and whether every amount can be traced. Confirm that stored items have not also been counted as installed in the same payment component. Identify differences that remain unsupported and assign their review to the appropriate person.

A useful report can state both the present numbers and their limits. It should never turn a cash ratio into physical progress or a quantity ratio into permission to pay. Contract interpretation, accounting treatment, and payment approval remain with the responsible reviewers.

Release edition · 2026-10-21 · Companion file version 1.1-review. All amounts, quantities, and payment assumptions are fictional.

Sources, method & limitations

The explanation, field structure, and fictional scenario are original teaching material. The cited primary guidance provides context; it does not endorse this resource or make its records an official approval process.

1. Caltrans Construction Manual, section 3-9: Payment (March 2024)
   An agency-specific example of distinguishing measured work, payment records, materials on hand, and withholds. Its rules are not asserted to govern other contracts; the reconciliation below uses expressly fictional payment assumptions.
2. GAO Cost Estimating and Assessment Guide, GAO-20-195G (2020)
   Background on defining estimate scope, documenting assumptions, and updating estimates with actual information. The examples do not reproduce a government cost model.
3. Caltrans Construction Manual, section 5-1: Project Records and Reports (November 2024)
   Background on retaining organized project records. These CSV fields and examples are independently authored, not copied Caltrans forms or a mandated filing structure.
4. AIA Contract Documents: what is a submittal in construction?
   Background on required submittals and their review against project requirements. The project’s own contract determines the responsible roles and procedures; a submittal disposition does not itself replace a required contract modification.
5. AIA Contract Documents: payment for materials stored offsite
   Explains A201–2017 section 9.3.2 as one contractual approach: advance owner approval for offsite storage and payment, an agreed location, protection of the owner’s interest, and applicable insurance and transport arrangements. The executed project contract governs eligibility.
6. AIA Contract Documents: payment applications and stored-material reconciliation
   Describes required payment support and moving stored value to completed work as incorporation occurs without charging for the same material twice. Use the project’s actual payment rules and applicable waiver requirements.
7. AIA G901–2022: conditional progress-payment waiver instructions
   Explains a conditional progress waiver tied to payment and a stated application. Applicable law and the project’s required forms govern; this guide does not prescribe a universal waiver or treat a submitted waiver as proof of payment.

Apply the actual project requirements and obtain the relevant professional review. This guide does not establish contractual entitlement, certify technical performance, or replace authorized acceptance. No actual client record or project outcome is represented by the fictional examples.

Release edition · October 21, 2026. Source notes identify the references used in preparation. Report an error or review our correction policy.