Billing Versus Installed Work: A Line-by-Line Review for Owners and Builders
A contractor's monthly bill and a count of the work in place measure different things, so a gap between them does not by itself prove an error. They can also agree while something is still unexplained. Ryan Lippmann, a senior construction project manager in California and the principal of Pacific Project Controls, works in the project controls discipline this review belongs to. This note follows one monthly application, the contractor's request to be paid for work through a stated date, from the page to the field record, for owners and builders. Nothing here is legal, accounting or contract advice, and where an answer depends on the contract, the contract controls. The bill is fictional; its numbers come from the teaching example in the Pacific Project Controls billing guide and describe no real project or client.
Set the scope, the date and the total first
First write down what the bill covers, the date it runs through and where each figure came from. In this fictional example the bill covers one package of work, meaning one defined piece of the job, with a current contract value of $200,000. Check that the current contract value is the original value plus approved changes only. Proposed changes that are still pending do not belong in it. The package is 100 planned units, all alike, so they can be counted.
Settle whether the figures are cumulative, meaning the running total to that date, or cover the current period only. The fictional example is set at October 31, 2026: the billed amounts and the field count share that one cutoff, the date through which figures are counted, and both are cumulative. Keep the date of payment separate from the date of the assessment. If the bill and the field count run through different dates, show both dates or bring both to one cutoff.
Read the application one component at a time; this fictional bill splits the request into three. The contractor requests $72,000: $50,000 for installed work, $14,000 for stored material and $8,000 for a component whose support has not been identified. Check that the components add up to the total. Each question below goes to the reviewer the project has assigned to the payment.
Count the installed units and record the method
The first component claims $50,000 for installed work, meaning work physically in place. In the fictional example, 40 of the 100 planned units are in place as of the cutoff. Write down what counts as a unit in place, when and how the count was made, and what evidence supports it. Counting suits this fictional package; mixed work needs an agreed measuring method instead.
The 40 units are evidence of what is in place; they do not set what the component is worth. In this fictional example the contract value also covers priced components that the units do not stand for, and the reviewer assigned to the payment assesses the value. Forty percent of one package is not forty percent of the project.
Check the stored-material component against its records
The second component claims $14,000 for stored material, which is material held for the job and not yet installed. In the fictional example it is $6,000 at the site and $8,000 at a warehouse off site. Whether material can be billed before it is installed is a contract question, and the contract controls. For the material on site, look for invoices tied to this project, a list that matches what is billed, and evidence that it is stored and protected as the contract requires.
For the off-site material, look for these records on paper: any advance owner approval of the payment and the storage place; an identified inventory tied to this project, with invoices and evidence of where it sits; title or another agreed protection of the owner's interest; the applicable insurance; the delivery arrangements; and any required lien waivers or releases, the signed payment papers that the contract and applicable law call for, on forms that fit the jurisdiction and the payment status. The fictional example assumes these were in place and reviewed; a real application has to supply its own.
In the fictional example neither stored amount is part of the 40 units counted, and the warehouse material has not reached the project. Check that no stored amount is also counted as installed work, and when stored material is installed, move its value to installed work so it is counted once. A purchase order, a deposit or a shipment forecast does not by itself make material eligible for payment.
Keep the unsupported component open and in view
The third component on this fictional bill is $8,000. The warehouse material is a different $8,000, inside the stored-material component. The specification is the written requirement for the work. A submittal is the contractor's submission showing how it will meet that requirement. Ask in writing which part of the current specification, which reviewed submittal, which field measurement and which payment clause support the $8,000. A reviewed submittal does not by itself make an amount payable or change the scope. Also ask whether the amount bills work under a change that has not been approved, which belongs in the change record and not in the current contract value.
Send the question to the assigned reviewer and ask for the missing evidence. If the gap is about scope, meaning what work the contract covers, it goes to the project's process for clarifying the documents or, where the scope itself changes, its formal process for changing scope, price or time. Whether anything changes is for the people the contract names.
Record the fictional $8,000 component as unresolved and leave it in view. Leave its assessed amount blank rather than entering a zero, because a zero is for an amount known to be zero, and do not count it in the assessed amount just so the page adds up. Give it one entry in the weekly review record: the issue, the evidence, the effect, the person responsible for the next response and the date that response is needed.
Set the bill beside the count and ask four questions
Against the $200,000 contract value of this fictional package, the request of $72,000 is 36 percent. The count is 40 of 100 units, or 40 percent. That figure is measured in units, not dollars, so neither share can stand in for the other. A gap between the two shares, in either direction, does not by itself decide what the contractor is owed.
Ask four questions before anyone uses the word overbilling. First, scope: do the count and the bill cover the same work? In the fictional example they do not, because the stored material sits outside the 40 units and nothing yet ties the third component to any measurement. Second, timing: were the bill and the count taken at the same cutoff, and are both running totals? In the fictional example they were, because both run through October 31 and both are cumulative.
Third, contract payment terms: does the payment clause recognize things a field count does not, such as stored material or design work? In the fictional example it does for the stored material, because the example assumes the contract allows both kinds of storage. Fourth, unsupported information: what is left that nothing explains? In the fictional example that is the $8,000 component. An explanation that sounds right still needs evidence behind it.
Trace the request down to the payment
In the fictional example the requested amount, what the contractor asked for, is $72,000. The assessed amount, the running total the reviewer assigned to the payment found supported before any deductions, is $64,000, or 32 percent of the contract value: for the example only, the first two components at their requested amounts, with the $8,000 component left unresolved. An assessed amount is not necessarily the cash paid. The cash paid is $60,800, or 30.4 percent.
The only step from assessed to paid in this fictional example is withholding, which is money held back from the assessed amount. The example assumes five percent of $64,000, or $3,200, with no other adjustment and no earlier payment, so $64,000 minus $3,200 leaves $60,800. That rate is an assumption, not a recommended term, and the contract and the project's actual payment record set what is withheld. Any other amount held back, such as for a disputed item, is listed separately with its own reason and record.
Check that the documented deductions, withholding and earlier payments carry the assessed amount down to the payment recorded. Check that any lien waivers or releases the contract requires for this payment are in hand, on forms that fit the jurisdiction and the payment status, and that each names the application it covers. A submitted waiver is not proof that payment was made.
Write down the numbers together with their limits
Each amount in the written note gets a definition, a date and a source, and the note says how the installed quantity was measured. Keep the cash-paid share and the unit count apart in the note: one measures money paid, the other measures work in place.
This comparison does not approve the application or decide what anyone is owed. File each month's note as issued, as with the October note in this fictional example, and record later answers as new entries. From the second month on, reconcile each application with the earlier ones so nothing is counted twice, and do not add one month's running total to the next.
In this fictional example, two components are supported by the example's own assumed facts, and one has no support yet. That component stays open in the weekly project controls review until someone supplies the evidence and the decision is recorded with its source.