Construction Progress Billing: How AIA Forms Actually Work
Construction projects don't bill the way most businesses bill. A typical service business sends an invoice when work is complete, the client pays the invoice, and the transaction closes. Construction operates on a different model entirely: contractors perform work over months or years, bill periodically based on percentage of completion, hold back retention until project completion, and produce specific forms required by owner and lender contracts. The most widely used forms for this billing pattern are AIA G702 (Application and Certificate for Payment) and G703 (Continuation Sheet), which together produce the standard pay application format used across most commercial construction.
Understanding how these forms work matters operationally for several reasons. Contractors who don't understand them produce pay applications that get rejected, delayed, or paid incorrectly. Contractors who understand them but use generic accounting tools that don't support the format end up recreating the forms manually for every pay application, with predictable consequences for time and accuracy. Contractors who use construction accounting software that produces compliant forms automatically eliminate this friction entirely.
The standard reference is AIA Document G702, Application and Certificate for Payment, which provides the framework for progress billing across most commercial construction projects. Most commercial contracts incorporate AIA documents by reference, which means the G702 format is contractually required for pay applications on those projects. Contractors who don't comply with the format produce pay applications that may be rejected outright, regardless of whether the underlying work was performed correctly.
This article covers how AIA progress billing works, what each form does, how schedule of values structures the billing, how retention is handled, and how software automates the whole workflow. The deeper coverage of retention specifically lives here: Construction Retention Tracking Software. Coverage of construction accounting more broadly can be found here: What is Construction Accounting Software?
How Progress Billing Differs From Standard Invoicing
The structural differences between construction progress billing and standard invoicing matter because they determine what software needs to handle.
Periodic Billing Against Total Contract Value
Standard invoicing produces an invoice for a specific amount when work or product is delivered. Progress billing produces a series of invoices over the project's duration, each for a portion of the total contract value, based on the work completed to date.
A $1.2M project might bill 8 progress payments of approximately $150K each over the project's duration, with the cumulative billed amount approaching $1.2M as the project completes. Each progress payment represents what was earned during a specific period, not a transaction-by-transaction billing.
Schedule of Values as the Structure
The schedule of values (SOV) breaks the total contract into line items that can be billed against. A commercial project might have an SOV with 30-50 line items: site preparation, demolition, framing, mechanical, electrical, finishes, etc. Each line item has a contract value, and pay applications bill against completion percentages of each line item.
The SOV serves multiple purposes:
Provides the structure for periodic billing
Allows different work to bill at different completion percentages
Supports detailed cost analysis at the line-item level
Becomes the framework for change order tracking
Strong SOV structure makes progress billing manageable. Weak SOV structure (too few line items, mismatched to actual work flow, lumping disparate work together) makes billing more difficult and creates dispute opportunities.
Percent-Complete Billing
For each pay period, the contractor reports the percentage of completion for each SOV line item. The billing for the period is the difference between what's earned to date (line item value × percentage complete) and what's been billed previously.
This is fundamentally different from billing for specific transactions. The contractor isn't billing for "this material delivered" or "that work performed." The contractor is billing for "this much progress earned against this line item to this point."
Retention Held Back
Most commercial contracts include retention (typically 5-10%) held back from each pay application until project completion. The retention serves as the owner's protection: if the project has issues at completion, the owner has retention available to address them.
Tracking retention across many projects produces visibility about working capital tied up in retention. The deeper coverage can be found here.
Change Orders Modify Total Contract Value
Change orders modify the total contract value, which modifies the SOV that pay applications bill against. Pay applications need to reflect:
Original contract value
Approved change orders to date
Revised contract value (original plus change orders)
Work completed against revised contract value
Retention calculated against revised contract value
Net amount due for current period
The interplay between change orders and pay applications is one of the more complex parts of the workflow. Operations that handle this badly produce billing errors that cause disputes. Read this article for deeper coverage of change order management.
Required Forms and Documentation
Standard invoicing typically uses whatever invoice format the business prefers. Progress billing for commercial work typically requires specific forms (AIA G702/G703 most commonly) plus supporting documentation: schedule of values, supporting cost detail, lien waivers, certified payroll where applicable, change order documentation.
The forms aren't optional preferences; they're contractual requirements. Pay applications that don't comply with the required format may be rejected.
Pro Tip: When evaluating construction accounting software, ask the vendor to demonstrate generating an AIA G702/G703 pay application from start to finish, including a change order modification mid-project. The end-to-end demonstration reveals whether the platform actually handles AIA billing or whether it's generic accounting with construction features bolted on. Strong platforms produce compliant forms in minutes from properly-coded job data, with change orders modifying the SOV automatically. Weaker platforms require workarounds, manual calculations, or external tools to produce compliant forms. The demo difference is usually obvious if you push the vendor through the actual workflow including change orders.
What G702 and G703 Actually Contain
The two forms work together to produce the standard pay application package.
G702: Application and Certificate for Payment
G702 is the summary form that owners and architects sign to certify and authorize payment.
It contains:
Header Information:
Project name and location
Owner, contractor, and architect identification
Application number and period
Project number and contract date
Summary Section:
Original contract sum
Net change by approved change orders
Contract sum to date (original plus change orders)
Total completed and stored to date (from G703)
Retention amounts (separate for completed work and stored materials)
Total earned less retention
Less previous certificates for payment
Current payment due
Balance to finish, including retention
Certification Section:
Contractor's certification that the work has been performed
Architect's certification that work qualifies for payment
Owner's authorization for payment
Change Order Summary:
Total approved change orders to date
Net amount of change orders approved during current period
The form summarizes the financial position of the contract at the current moment, with the math flowing from G703 details into G702 summary.
G703: Continuation Sheet
G703 is the detail form that supports G702. It contains the schedule of values with completion percentages and amounts:
Line-Item Structure:
Item number
Description of work
Scheduled value (contract value for the line item)
Work completed from previous applications
Work completed this period
Materials presently stored (not yet incorporated)
Total completed and stored to date
Percentage of completion
Balance to finish
Retention
For each SOV line item, the contractor reports completion to date with separate columns for previous billings and current period work. The cumulative completed amounts feed into G702.
How the Two Forms Integrate
The flow is straightforward in concept:
1. SOV defines the line items and contract values
2. For each pay period, contractor reports completion percentages on each line item
3. G703 calculates earned amounts based on completion
4. G703 totals flow into G702 summary
5. G702 calculates retention, previous billings, and current payment due
6. G702 gets signed by contractor, architect, and owner
7. Approved G702 authorizes payment
When change orders happen, the SOV gets modified (new line items added or existing line items adjusted), and subsequent pay applications reflect the modified SOV.
Required Supporting Documentation
Beyond G702/G703, complete pay application packages typically include:
Conditional waiver and release for the current pay application amount
Unconditional waiver and release for previous pay applications received
Sworn statement in some jurisdictions, listing all subs and suppliers
Lien waivers from subcontractors where required
Certified payroll reports for prevailing wage projects
Stored materials documentation if billing for stored but not installed materials
Insurance certificates confirmed current
Photos or other progress documentation in some cases
The supporting documentation makes the pay application complete and supports the certifications on G702. Operations that submit incomplete pay applications face delays and resubmission cycles.
State and Project Variations
While AIA G702/G703 dominates commercial construction, variations exist:
ConsensusDocs forms (Form 700 series) provide an alternative to AIA documents
State-specific forms may be required for state public works projects
Federal forms (SF-1442, SF-1443) for federal projects
Owner-specific forms for certain large institutional or commercial owners
Lender-required formats for projects with construction financing
Strong construction accounting platforms support the major formats. Operations working across project types may need platforms that handle multiple formats appropriately.
Case Study: A 35-person commercial GC ran AIA pay applications through Excel templates manually through 2022. Each pay application took approximately 4-6 hours to produce: extracting job costing data from QuickBooks, manually transcribing into Excel templates, calculating completion percentages, applying retention math, generating the supporting waivers, assembling the package. With approximately 18 active projects each generating monthly pay applications, the workload consumed roughly 100-130 hours per month of admin time. Pay application errors triggered occasional rejections and resubmission cycles that added additional time. They migrated to Foundation Software with native AIA billing in early 2023. The migration took 4 months and approximately $18,000 in implementation costs. Post-migration, pay application generation took approximately 30-45 minutes each, including supporting documentation. The same workload that had consumed 100-130 hours per month dropped to approximately 12-15 hours per month. The annual time savings exceeded $80,000 in admin labor cost (at fully-burdened rates), making the platform investment immediately ROI-positive. The lesson was that AIA billing through generic tools is one of the highest-cost workarounds in contractor operations, and dedicated construction accounting typically pays back quickly through this single capability alone.
How Software Automates the Progress Billing Workflow
The capabilities below distinguish strong AIA billing software from weaker alternatives.
Native AIA Form Generation
Strong platforms produce G702 and G703 forms in compliant format directly from job costing data. The forms generate with proper formatting, all required fields populated, and math calculated automatically.
Weaker platforms produce something resembling AIA forms but with formatting issues, missing fields, or calculation errors that require manual correction.
Schedule of Values Management
The SOV gets entered once at project setup, with the platform managing it through the project's duration. Change orders modify the SOV automatically. Pay application reporting uses the SOV structure consistently across all periods.
Real-Time Completion Tracking
Project managers can update completion percentages from the field, with the data flowing into pay application preparation. Real-time tracking eliminates the end-of-month scramble to gather completion data from multiple sources.
Automatic Retention Calculation
Retention rates defined at project setup apply automatically to pay applications. Strong platforms support different retention rates on different line items if the contract specifies (different rates for different work categories).
Change Order Integration
When change orders execute, they automatically modify the SOV and flow into subsequent pay applications. The contract value updates, retention recalculates against the revised value, and the pay application reflects the modified position automatically.
Supporting Documentation Workflow
Strong platforms generate the supporting documentation alongside the pay application: lien waivers in proper format for the project's state, certified payroll if applicable, stored materials documentation, sworn statements where required.
Multi-Project Pay Application Cycle
For operations running many projects simultaneously, strong platforms support batch pay application processing: generate pay applications for all active projects in one workflow, with appropriate review and approval steps.
Owner and Architect Distribution
Some platforms support electronic distribution of pay applications directly to architects and owners, with signature capture and tracking. The workflow eliminates print-sign-scan cycles that wet signature workflow requires.
Audit Trail and Documentation
Pay applications generate with comprehensive audit trails: who entered completion percentages when, what supporting documentation was attached, who signed what at each step. The audit trail supports dispute defense if pay applications get challenged.
Integration With Receivables
Approved pay applications flow into receivables, with payment tracking, aging reports, and follow-up on outstanding amounts. Operations that don't track pay application aging often have meaningful working capital tied up in approved-but-unpaid pay applications without active management.
Pro Tip: Establish a standard pay application submission cadence and stick to it ruthlessly. Most commercial contracts allow monthly pay applications with specific cutoff dates and submission deadlines. Operations that submit at irregular intervals or miss cutoffs produce cash flow drag from delayed payments. Operations that establish "pay application Friday" or similar rhythm with batch processing across all active projects produce consistent cash flow and reduce the per-application administrative burden through workflow consistency. The cadence discipline matters more than the specific schedule choice.
AIA Billing Is Operational Infrastructure for Commercial Work
AIA progress billing is one of the operational realities that distinguishes commercial construction from typical service businesses. Operations doing commercial work need to produce compliant pay applications efficiently, manage the SOV and change order interplay accurately, handle retention tracking consistently, and produce the supporting documentation that makes pay applications complete.
The capability is essentially required for operations doing commercial work at any meaningful scale. The question isn't whether to handle AIA billing; the question is whether to handle it through purpose-built construction accounting software (efficient, accurate, scalable) or through generic accounting with extensive workarounds (time-consuming, error-prone, unsustainable). For most commercial operations, the math favors purpose-built software meaningfully.
Frequently Asked Questions
What's the difference between AIA G702 and G703?
G702 is the summary form (Application and Certificate for Payment) that owners and architects sign to certify and authorize payment. It contains the contract summary, retention calculations, previous billings, and current payment due. G703 is the continuation sheet that contains the detailed schedule of values with completion percentages for each line item. The detail in G703 flows into the summary on G702. Both forms together constitute a complete pay application package, plus supporting documentation (lien waivers, certified payroll, etc.).
Do I have to use AIA forms for progress billing?
Depends on your contracts. Most commercial contracts using AIA documents (A101, A102, A201, etc.) incorporate G702/G703 as the required pay application format. Contracts using ConsensusDocs may use ConsensusDocs forms instead. Public works projects (federal, state, municipal) often have specific forms required by the public agency. Owner-specific contracts may have proprietary formats. The right answer is whatever your contract requires, not necessarily AIA. But AIA G702/G703 dominates commercial construction, so most commercial operations use it most of the time.
What's the typical retention rate on commercial construction?
Retention typically runs 5-10% on commercial construction, with 10% being more common on smaller projects and 5% being more common on larger projects. Some contracts reduce retention at substantial completion (e.g., 10% retention dropping to 5% once 50% complete). Public works projects often have specific retention requirements set by the public agency. Federal projects typically use a 10% retention rate. The contract specifies the applicable rate, which the SOV and pay applications then track against.
Can I bill for stored materials before they're installed?
Sometimes, with specific requirements. AIA G703 includes a column for "materials presently stored" separate from "work completed," allowing billing for materials delivered but not yet incorporated into the work. The requirements typically include: materials stored on-site or in approved off-site location, materials properly insured, materials properly identified as belonging to the project, and approval from owner or architect. Contracts may have specific requirements about what materials qualify and what documentation is needed. Stored materials billing supports cash flow when contractors purchase materials in advance of installation, but the requirements need to be followed precisely to avoid rejection.