A general contractor in Phoenix submitted a $1.4 million pay application in March, expected funds in 30 days, and waited 71 days for the wire to land. The cause was not an angry owner or a slow architect. Line 4 on the G702 disagreed with the grand total on the G703 by $312. The architect kicked it back. The bookkeeper resubmitted. The clock restarted. Payroll for that period came out of the owner's personal line of credit.
This is the everyday reality of construction billing. On commercial projects the G702 and G703 pay application package is the single most consequential financial document you produce each month, and yet the gap between filling it out correctly and integrating it into clean GAAP financial statements is wider than most contractors realize. Sureties, banks, and the IRS each read this paperwork differently, and a billing position that looks healthy to your project manager can look alarming to your bonding agent. The good news is that the system is learnable, and the contractors who master it get paid faster, bond bigger projects, and survive downturns that bankrupt their less disciplined competitors.
This guide walks through the AIA pay application workflow, the schedule of values that anchors it, retainage mechanics, the work-in-progress schedule that translates billing into financial reporting, and the over and underbilling reconciliation that ties everything to ASC 606 revenue recognition.
What G702 and G703 Actually Are
The AIA G702 Application and Certificate for Payment and its companion G703 Continuation Sheet are forms first published by the American Institute of Architects in 1992 and updated periodically since. Together they make up the standard pay application package used on roughly three quarters of commercial construction projects in the United States. The G702 is a one-page cover summarizing the request: original contract sum, net change orders, contract sum to date, total completed and stored to date, retainage withheld, previous payments, and the current payment due. The G703 is the line-item backup, listing every category in the schedule of values along with prior period work, current period work, materials stored, and the percentage complete for each row.
The architect uses these forms to certify the amount that the owner should release. Under AIA Document A201, the architect may certify a different amount than the contractor applied for if specific line items are not properly supported or if work appears incomplete. That certification is what unlocks the payment cycle from the owner to the general contractor and ultimately down to subcontractors and suppliers.
The forms exist because construction is structurally different from most commercial transactions. You finish jobs over months or years, you outlay cash for labor and materials before you collect, and the parties involved are seldom willing to trust each other on faith. The AIA package gives everyone a shared format to track progress, valuation, and risk.
The Schedule of Values Is the Document Behind the Document
You cannot fill out a G703 honestly without first preparing a schedule of values, or SOV. The SOV is an itemized list that allocates the entire contract sum to specific portions of work, typically organized by CSI MasterFormat division. It is the single source of truth that drives every monthly billing, every percentage complete calculation, every retainage holdback, and every change order adjustment for the life of the project.
A good SOV breaks the work into line items granular enough to measure progress meaningfully but not so granular that monthly accounting becomes impossible. On a $12 million school renovation, you might see fifty to eighty line items: site work, excavation, concrete foundations, structural steel, roofing, mechanical rough-in, mechanical trim, electrical rough-in, electrical trim, drywall, painting, finish carpentry, casework, flooring, and so on. Each line gets a dollar value. The total of those values must equal the contract sum.
The most common SOV mistake is front-end loading: inflating the dollar value of early work items so the contractor pulls cash forward in the project. A foundation line item that should be $400,000 gets billed at $560,000 by quietly absorbing some general conditions costs that belong later in the project. Architects and owner's representatives look specifically for this, because it shifts the risk of project completion to the owner: if the contractor walks off at fifty percent complete after pulling sixty percent of the contract value, the owner is left holding the bag.
Vague line item descriptions create the second class of problems. A row labeled "Site Prep" that combines clearing, demolition, grading, utility relocations, and temporary fencing into one number makes monthly progress impossible to verify. The architect cannot tell whether you actually completed forty percent of the dollars or just forty percent of one component. Pay applications get rejected, payment slows, and disputes multiply.
The best schedules of values get reviewed by the project manager, the estimator, the accounting team, and a senior superintendent before the first submission. They include a separate line for general conditions, a separate line for bonds and insurance, separate lines for each major trade, and they tie cleanly to the project budget so that earned cost and earned revenue can be tracked together.
How a Pay Application Moves Through the Month
The monthly cycle on a typical AIA project runs like this. Around the twentieth of the month, the project manager and the superintendent walk the site and update the percentage complete for each SOV line item. They compare the dollar value of work in place against the dollar value billed in prior periods. The bookkeeper drafts the G703 with the current period values, recalculates retainage, and rolls totals up to the G702 cover sheet.
The contractor signs and notarizes the G702 and submits the package to the architect, usually with photo documentation, lien waivers from subcontractors covering the prior payment, and any supporting invoices for stored materials. The architect reviews, walks the site if necessary, and either certifies the amount requested or adjusts it down. The certified G702 then goes to the owner, who has a contractual window, usually thirty days under standard AIA terms, to wire the payment to the contractor. The contractor in turn pays subcontractors, typically within seven to ten days of receiving owner funds, after collecting their lien waivers.
The cycle is unforgiving. A pay application submitted on the twenty-fifth with a math error that is caught on the twenty-seventh, returned on the twenty-eighth, and resubmitted on the thirtieth has effectively moved into next month's cycle. The contractor is now financing labor and materials for an extra thirty days. On a $2 million monthly billing, that is real money.
Retainage: The Money You Earn But Cannot Collect Yet
Retainage is the portion of each progress payment that the owner withholds as security for project completion. Five percent and ten percent are the most common rates, though some states cap it lower and some federal projects use a sliding scale that reduces the rate once the project passes fifty percent complete. The G702 has a dedicated line for retainage on completed work and a separate line for retainage on stored materials.
The accounting question that trips up many contractors is when to recognize retainage as revenue. Under GAAP, the answer is that you recognize the full earned amount as revenue in the period the work is performed, including the portion that will be held back as retainage. The retainage is a collection timing difference, not a revenue timing difference. What changes is the balance sheet classification.
When retainage is unconditional, meaning the only thing standing between the contractor and the cash is the passage of time, it is presented as a receivable. When it is conditional, meaning that release depends on the contractor satisfying future performance obligations such as punch list completion, owner sign-off, or warranty milestones, it must be included within the contract asset or contract liability rather than the receivable line. ASC 606 does not prescribe a specific presentation, but the FASB staff has clarified that contractors should evaluate whether release is truly unconditional contract by contract.
This distinction matters because sureties, banks, and analysts read these balance sheet lines differently. A large retainage receivable communicates trapped cash that will arrive on a known schedule. A large contract asset communicates uncertainty about whether the contractor will earn the right to that cash at all. Misclassifying conditional retainage as a receivable overstates the contractor's near-term liquidity and can come back painfully when the surety reviews the next year's financial statements.
Maintaining clean records for each line of retainage, knowing when it converts from conditional to unconditional, and tracking it against contract milestones requires the kind of detailed bookkeeping that pays for itself many times over when it is time to bond the next project or apply for a working capital line.
Percentage of Completion: Translating Billing into Revenue
The percentage of completion method, or PCM, is the foundation of construction revenue recognition under ASC 606. Most contractors use the cost-to-cost variation: divide costs incurred to date by total estimated costs at completion to derive a completion percentage, then multiply that percentage by the total expected contract revenue to find revenue earned to date. Subtract revenue recognized in prior periods and you have current period revenue.
The math is straightforward but the inputs are not. Estimated costs at completion is itself an estimate, and the discipline required to update it honestly each month separates well-run contractors from chronically surprised ones. A project that is showing twenty percent over budget at forty percent complete is not magically going to come back to budget by month-end. Owners and project managers who refuse to revise estimated costs upward in the WIP schedule end up recognizing revenue that the project will never deliver, which becomes a painful catch-up in the final months of the job.
The key insight is that revenue earned, as measured by percentage of completion, is almost never equal to the amount billed in the same period. That gap is what creates over and underbillings, and the WIP schedule is the document that exposes it.
The WIP Schedule: Where Billing Meets Reality
A work-in-progress schedule is a one-page financial summary of every open contract on the books. Each row represents a single project. The columns typically include the original contract value, approved change orders, current contract value, costs incurred to date, estimated cost at completion, percentage complete, revenue earned to date, billings to date, and the resulting overbilling or underbilling. Most schedules also show gross profit estimated, gross profit earned to date, and the change in gross profit since the last period.
The WIP schedule sits at the intersection of three different views of a project. The project management view tracks work in place. The billing view tracks invoices sent. The accounting view tracks revenue earned under GAAP. When these three views diverge, the WIP schedule is where the divergence becomes visible.
Sureties care more about this document than almost anything else in your financial package. A bonding agent will sometimes accept a tax return as supporting documentation, but the WIP schedule is required, and it is the first item the underwriter will ask for. Underwriters know that aggressive billing can disguise a fundamentally unprofitable contractor, and the WIP schedule is the spotlight that shows them whether the company is earning cash or merely collecting it.
Overbilling and Underbilling, Plainly Explained
Every open project on a contractor's books sits in one of two billing positions. Either the project has been billed for more than the revenue earned under percentage of completion, in which case it is overbilled, or it has been billed for less, in which case it is underbilled.
Overbilling means the contractor has invoiced the owner for work that has not yet been performed in proportion. The excess billing appears on the balance sheet as a liability, traditionally called billings in excess of costs and estimated earnings, and now generally classified as a contract liability under ASC 606. It represents an obligation to deliver future work that the contractor has already been paid for. A modest level of overbilling is normal and even healthy because it provides working capital to fund the next phase of the work. A large or persistent level of overbilling is dangerous because it consumes the cash that the contractor will need to complete the project. Sureties typically grow concerned when total overbillings exceed ten to fifteen percent of remaining contract backlog.
Underbilling means the contractor has performed more work than the cumulative billings reflect. The shortfall appears on the balance sheet as an asset, traditionally called costs and estimated earnings in excess of billings, now generally a contract asset under ASC 606. It represents work the contractor has done but for which it has not yet collected, beyond the timing of the next invoice. Underbilling is also normal in small amounts, particularly after a large month of work that has not yet been formally billed. Large or persistent underbilling is a working capital crisis in slow motion. It often signals that change orders are being worked on without approval, that scope creep is going unbilled, or that pay applications are being prepared sloppily and missing real progress.
The sum of all overbillings minus all underbillings reconciles to the net contract liability or contract asset on the balance sheet, which is one of the cleanest sanity checks a controller can run each month. If the WIP schedule disagrees with the trial balance, one of them is wrong, and it is almost always worth finding out which before the financial statements go out.
Tying It Back to ASC 606
ASC 606 supplanted ASC 605-35, the legacy construction-specific revenue standard, in 2018 for public companies and 2019 for most private companies. The core mechanics of percentage of completion did not disappear under the new standard, but the language changed and certain presentation rules tightened. Contracts are now evaluated for performance obligations, transaction price, allocation, and timing of revenue recognition. Most fixed-price construction contracts continue to be treated as a single performance obligation satisfied over time, with revenue recognized as the contractor's progress toward complete satisfaction is measured.
The presentation changes are where the practical impact lands. Under legacy GAAP, contractors freely used line items called billings in excess of costs and costs in excess of billings on their balance sheets. Under ASC 606, the netting required for contract assets and contract liabilities is contract by contract, and retainage may need to be carved out and presented separately depending on whether the right to payment is unconditional.
The disclosure requirements also expanded. Contractors are expected to disclose disaggregated revenue, remaining performance obligations, and significant judgments about variable consideration. Sureties have generally welcomed the additional disclosure even when it complicates the financial statements, because it gives them more visibility into the underlying contract economics.
For most private contractors, the practical implication is that the bookkeeping needs to be tighter than it used to be. The data underlying revenue recognition, the WIP schedule, the retainage classifications, and the contract asset and liability roll-forwards has to be traceable, auditable, and consistent across periods.
Common Errors That Slow Down Payment
Several patterns appear repeatedly in pay application rejections and surety pushback. The first is the math mismatch between G702 and G703. The grand total on the G703 must equal the total completed and stored to date on the G702. If they do not, the architect should and usually does send the package back. Most accounting software handles this automatically, but spreadsheet-based submissions and last-minute change order edits routinely introduce arithmetic errors.
The second pattern is misallocated change orders. When an owner approves a change order, it must be added to a specific SOV line or assigned to a new line, and the contract sum on both the G702 and G703 must reflect the addition. Contractors who casually fold change orders into the next month's billing without updating the SOV create confusion that cascades through every subsequent application.
The third pattern is improper retainage. Some owner agreements require retainage to step down at substantial completion or to be released entirely on certain line items, such as bonds and insurance, that are not subject to performance risk. Contractors who apply a flat retainage percentage to every line on every application leave money sitting in retainage that they could have collected months earlier.
The fourth pattern is missing lien waivers. Most owners and lenders require that conditional and unconditional lien waivers from the subcontractors paid in the prior cycle accompany the next pay application. Missing waivers will hold up the architect's certification regardless of how clean the math is.
The fifth pattern is overstating stored materials. Materials stored on site or in a bonded warehouse can be billed under most contracts, but they must be properly documented with invoices, a certificate of insurance, and sometimes photographs. Generous estimates of stored material values that are not backed by paper trail get rejected.
Building the Habit of Reconciliation
The contractors who do this well share a few habits. They close the books monthly, not quarterly. They reconcile the WIP schedule to the general ledger and to the trial balance every month. They review every overbilled and underbilled project with the project manager, not just the bookkeeper, so the operations team understands the financial picture they are creating. They update estimated costs at completion based on actual job site data, not optimism. They keep retainage in a separately tracked account, classified by conditional and unconditional status, and they roll forward contract asset and contract liability balances explicitly each month.
These habits compound. A contractor who knows their billing position on every project within a few days of month-end can have hard conversations with owners before disputes calcify. A contractor who understands their working capital needs three months out can negotiate better terms with subcontractors and suppliers. A contractor who can hand a bonding agent a clean WIP schedule and reconciled financial statements without scrambling can bond bigger jobs at better rates.
Keep Your Construction Books Clean from Day One
As you scale a construction business, the gap between the projects you can run and the projects you can finance grows largely because of how well your books and pay application discipline hold up. Accurate WIP schedules, traceable retainage tracking, and clean reconciliations between billings, earned revenue, and the general ledger are what give bonding agents and lenders the confidence to back larger contracts. Beancount.io provides plain-text accounting that is transparent, version-controlled, and AI-ready, so every entry in your contract asset and contract liability accounts has a clear audit trail you can hand to a surety, a lender, or a CPA without apology. Get started for free and see why developers and finance professionals are switching to plain-text accounting that grows with their business.