AIA billing in QuickBooks: how to map G702/G703 and schedule of values to your books
QuickBooks Online has no native AIA G702/G703 billing template, but controllers and finance managers can configure its invoice structure to mirror a schedule of values line by line. When this mapping is done ad hoc, the consequences compound quickly: rejected pay apps, retainage parked in the wrong account, and a WIP schedule that never reconciles to what's been billed — rework that follows every application period.
Key takeaways
Here is what matters most before you compare options.
QuickBooks native support: QuickBooks Online has no native AIA G702/G703 template, but its progress invoicing and item-level structure can be configured to mirror a schedule of values line by line.
Correct posting matters: How a pay app posts in QBO determines whether your WIP, overbilling, and retainage receivable accounts are accurate — getting this wrong creates reconciliation problems that compound every application period.
Retainage requires its own receivable account: Retainage withheld by the GC must be tracked as a separate current asset in QBO, not left embedded in the invoice balance, or your AR aging and cash forecast will misstate the job's true position.
When QBO becomes the bottleneck: Multi-entity GCs and specialty contractors managing 10 or more jobs simultaneously hit structural limits in QBO that a purpose-built construction ERP like Flow ERP is designed to remove.
What do the AIA G702 and G703 forms mean for your books?
The AIA G702 is the Application and Certificate for Payment — the cover sheet that states the total amount due — and the G703 is the Continuation Sheet that itemizes each line of the schedule of values with amounts billed to date, stored materials, and retainage withheld. Together, they define the billing structure for most commercial construction contracts.
From an accounting standpoint, each G703 line maps to a specific GL entry. The scheduled value on each line represents the contract value for that cost division. Work completed to date drives revenue recognized under the percentage-of-completion method. Retainage withheld is a contra-receivable or deferred asset, not collectible until project closeout. The balance to finish represents the remaining contract obligation still to be earned.
The G703's line-item structure is what creates difficulty in QBO. AIA billing requires item-level invoice tracking that matches each SOV cost code — QBO's default invoice template doesn't produce that granularity without deliberate configuration. For construction accounting software built for how contractors actually bill, this mapping has to be built into the system's architecture — not bolted onto a general-purpose invoice screen.
According to AICPA-CIMA guidance on long-term contract revenue recognition, the percentage-of-completion method requires that billed amounts track closely to the measure of progress — which is exactly why your G703 line-item structure must mirror your QBO invoice structure without exception.
How should AIA progress billing post in QuickBooks Online?
In QuickBooks Online, each G703 line item from the schedule of values should map to a separate invoice line using a service item tied to the corresponding income account and job or class tracking. Here is the setup and posting workflow, step by step.
Configure the Customer:Job hierarchy. In QBO, go to Sales > Customers. Create the general contractor or owner as the top-level customer. Then add the specific contract as a sub-customer, checking the box "Bill this customer" so QBO treats it as its own job. This Customer:Job relationship is what enables job-level AR and cost reporting.
Build service items that match each SOV cost code. Go to Sales > Products & Services > New > Service. Create one service item per G703 line — for example, "Site Work," "Concrete," "Framing." Map each item to the corresponding income account in your chart of accounts. These items must match the G703 exactly; naming mismatches create reconciliation gaps later.
Enable progress invoicing in QBO settings. Go to Settings (gear icon) > Account and Settings > Sales > Progress Invoicing. Toggle "Create multiple partial invoices from a single estimate" to on. This setting is required before QBO will let you bill incrementally against an estimate loaded with your SOV lines.
Load the schedule of values as a QBO estimate. Go to Sales > Estimates > New Estimate. Select the Customer:Job created in step 1. Add each SOV line as a row, using the service items built in step 2, with the scheduled value as the quantity or rate. Save the estimate — this becomes the master contract record that all progress applications pull from.
Create the pay application invoice from the estimate. Open the estimate and select "Create Invoice." QBO will ask whether to invoice a percentage of the estimate, a custom amount per line, or the full amount. Select "Custom amount for each line" — this lets you enter the cumulative billed-to-date amount on each SOV line for the current application period, not just the current-period increment.
Tag each line to the correct class or location. If you're tracking by project or entity, assign the class or location on each invoice line before saving. This drives the job costing reporting in QuickBooks Online that your CFO or operations team will need to review by job.
Correct posting produces a job-level AR balance that matches the G702 net amount due — with retainage excluded, which is covered separately below.
QBO progress invoicing vs. standard invoicing — which one to use
QBO's progress invoicing feature bills a percentage of a pre-built estimate, which approximates the SOV structure when the estimate is loaded with the same line items as the G703. If your contract is loaded into QBO as an estimate before the first application, use progress invoicing — it carries forward the cumulative structure automatically.
If no estimate exists in QBO, the fallback is a manually structured standard invoice using the service items built to match each SOV line. The risk with standard invoicing is that you lose QBO's automatic tracking of what's been billed vs. the original contract value, which means your billing-to-contract reconciliation has to be managed entirely outside QBO.
Class and location tracking for multi-entity or multi-job reporting
QBO's class and location tracking lets you tag each invoice line to the correct project or entity for cross-job reporting. For controllers managing multiple jobs in the same QBO file, this is the only way to get a job-level P&L without exporting and sorting manually.
QBO's structural limit here is real: standard QuickBooks Online supports one tracking dimension at a time — either class or location, not both simultaneously. QuickBooks Online Advanced unlocks both dimensions at once. For multi-entity operators managing several projects across separate QBO files, this single-dimension limit is where the system starts to show structural strain.
How do you set up retainage lines from a pay app in QuickBooks Online?
Retainage withheld on a pay application must be recorded in QuickBooks Online as a separate receivable line item — not left as an unpaid portion of the invoice balance — so that your AR aging accurately reflects cash collectible now versus cash collectible at project completion.
The setup requires three specific actions. First, create a Retainage Receivable account in QBO under Chart of Accounts as a current asset — not as part of the standard accounts receivable account. Go to Accounting > Chart of Accounts > New, select "Other Current Assets" as the account type, and name it "Retainage Receivable." Second, create a service item for retainage: go to Sales > Products & Services > New > Service, name it "Retainage Withheld," and map it to the Retainage Receivable account you just created. Third, add a negative retainage line to each progress invoice equal to the withheld percentage multiplied by the gross amount billed on that application.
When retainage isn't separated, three specific problems follow. Your AR aging overstates collectible cash — the retainage balance shows as open AR, but it won't be collected until project closeout. Your job-level cash forecast is wrong because it counts retainage as near-term cash. And at project close, when the owner releases retainage, there's no clean account to pull from, creating a scramble to reclass entries in the period the payment arrives. To understand how retainage interacts with your overbilling risk, see our guide on overbilling and underbilling in construction.
How does a completed pay app connect to WIP and cash forecasting in QuickBooks?
Once a pay application is posted correctly in QuickBooks Online, the billed-to-date amounts on each job become the billing side of your WIP schedule — which you then compare to cost-to-date to determine whether the job is overbilled or underbilled.
The WIP calculation works as follows: divide costs incurred to date by total estimated cost to get percent complete (cost method). Multiply percent complete by the contract value to get revenue earned. Compare revenue earned to billed-to-date from your QBO invoices. If billed-to-date exceeds revenue earned, the job is overbilled — a liability. If revenue earned exceeds billed-to-date, the job is underbilled — an asset. Your QBO invoice structure, when built correctly per the steps above, feeds the billed-to-date column directly. For a full walkthrough of this calculation, see how to build a WIP schedule in QuickBooks Online.
The approved pay app also drives your short-term cash forecast. The net amount due on the G702 — gross billed minus retainage withheld — is the cash you expect to collect, typically within 30–45 days depending on contract payment terms. Retainage release dates, which are often tied to substantial completion or final lien waivers, require a separate cash forecast line. QBO has no native WIP report, so this connection between pay app, WIP, and cash forecast is managed in a spreadsheet layer that sits on top of your QBO data.
What breaks your AIA billing workflow in QuickBooks Online?
Three workflow failures cause the most reconciliation problems in AIA billing with QuickBooks Online: unapproved SOV changes that weren't reflected in the QBO invoice structure, stored materials billed on the G703 but not tracked in QBO, and prior application amounts that weren't carried forward correctly to the current period.
Unapproved SOV changes
When a GC or owner modifies the schedule of values mid-project without a formal change order posted in QBO, the invoice item structure no longer matches the G703. Line-item billing-to-date becomes misaligned, and the pay application gets rejected because the numbers the owner sees on the G703 don't tie to what's in your billing history. The corrective action is to create a change order as a new QBO estimate line or invoice line item before the next application period closes — not after the rejection arrives.
Stored materials on the G703
Stored materials — materials delivered to the job site but not yet installed — are billed on the G703 as a separate column from work completed in place. In QBO, if stored materials are folded into a work-completed service item, the G703 percentage complete will be distorted because you've billed for materials that haven't been installed. The fix is a dedicated service item per SOV line for stored materials that can be reversed when those materials are installed and billed as work completed in the next application period.
Prior application amounts not carried forward
AIA billing is cumulative — each G703 shows work completed to date, not just the current period increment. In QBO, if a controller invoices only the current-period amount rather than the cumulative billed-to-date amount, the billed-to-date figure understates total billing and the WIP schedule shows a false underbilling. The fix is to always invoice the cumulative billed-to-date amount on each line and apply prior payments against the invoice, rather than issuing a new invoice for only the current-period increment.
When these breaks occur frequently across multiple jobs, the manual overhead of correcting them signals that QBO's structure is no longer the right fit for the operation's billing volume and complexity. Forvis Mazars notes that construction companies with multiple active contracts and complex billing structures typically need dedicated construction accounting systems to maintain audit-quality records across project billing cycles.
How do you get live reporting in QuickBooks when Procore, Buildertrend, or JobTread owns your pay app?
When a construction management platform like Procore, Buildertrend, or JobTread generates the AIA pay application, the accounting team's job is to ensure that what the field submits matches what posts to the QuickBooks general ledger — and that the sync doesn't create duplicate or misaligned entries.
Each platform generates pay apps and syncs to QBO, but none of them fully replicate the line-item SOV structure inside QBO. The sync typically moves the invoice total — not each G703 line as a separate QBO item. Retainage, stored materials, and cost code alignment require manual steps after every sync. Understanding what the Procore–QuickBooks sync connector does and doesn't move, the process of closing the WIP gap in a Buildertrend–QuickBooks stack, and what the JobTread–QuickBooks integration syncs will help you identify exactly where your manual reconciliation workload sits.
The table below shows the gap profile for each platform across the attributes that matter most to your month-end close. Verify current behavior against each vendor's documentation before relying on these descriptions for your specific version.
AIA billing sync capabilities: Procore, Buildertrend, and JobTread to QuickBooks Online | |||
Attribute | Procore | Buildertrend | JobTread |
|---|---|---|---|
Pay app generation (G702/G703) | Yes — native AIA G702/G703 generation within Procore | Yes — pay app generation within Buildertrend owner invoicing | Yes — invoice and draw schedule generation within JobTread |
QBO sync type | Invoice-level sync; line-item SOV detail does not carry into QBO line items by default | Invoice-level sync; individual SOV line items typically require manual QBO setup | Invoice-level sync; line-item detail in QBO depends on item mapping configuration |
Retainage sync | Not automatically synced to a separate retainage receivable account in QBO; manual journal entry required | Retainage tracked in Buildertrend; manual QBO entry required to separate from AR | Retainage tracked in JobTread; manual QBO setup required for separate receivable account |
Stored materials sync | Stored materials tracked in Procore; does not create a distinct QBO line item automatically | Not separately synced to QBO; manual service item entry required | Not separately synced; finance team must create dedicated QBO item |
Cost code to QBO item mapping | Procore cost codes map to QBO items via sync setup; initial mapping requires manual configuration | Buildertrend cost codes map to QBO items; mapping configured during integration setup | JobTread categories map to QBO items; requires initial manual mapping |
Manual steps required after sync | Retainage journal entry, stored materials item, SOV line-item verification against G703 | Retainage journal entry, stored materials item, cumulative billing verification | Retainage journal entry, line-item detail verification, stored materials entry |
WIP impact in QBO | Invoice total posts to QBO; WIP schedule must be built externally against QBO job cost data | Invoice total posts to QBO; WIP schedule requires external spreadsheet layer | Invoice total posts to QBO; WIP schedule requires manual construction outside QBO |
For teams managing three or more entities with separate QBO files and multiple integrations, the reconciliation work between the project management platform and QBO grows faster than headcount can absorb. Deloitte's construction industry research consistently identifies data fragmentation across field and finance systems as one of the primary drivers of reporting delays in mid-market contractors. That fragmentation is structural when a project management tool and a separate GL each hold part of the billing record.
What Flow ERP removes from this workflow
Flow ERP is built with native multi-entity architecture and combines an accounting ledger with FP&A in one platform — which means the sync layer between a project management tool and a separate GL is replaced by a unified system where job costing, billing, and reporting share one data source. For a multi-entity GC or specialty contractor, that eliminates the reconciliation gap described in the table above.
For controllers evaluating a move off QBO, the migration path is straightforward: migrate from QuickBooks Online to Flow ERP in under 2 minutes with all dimensions and attachments, with books live in 11 days or less after migration is complete. Once you're live, the AI Month-End Close Agent runs a dynamic checklist tied to actual job data, turning close into a review rather than a reconstruction. Bank reconciliation runs continuously via Plaid rather than as a month-end batch, so close starts mostly reconciled. For construction-specific context, see the Flow ERP construction page and the full Flow ERP product overview.
When LiveFlow FP&A fills the gap without switching the GL
For finance teams staying on QBO and needing live consolidated reporting across multiple QBO entities or across QBO and a spreadsheet WIP model, LiveFlow FP&A connects directly to QBO and Google Sheets or Microsoft Excel, keeps models updated with live data, and consolidates multiple entities in minutes rather than through manual exports. This is the right path for the team that knows QBO is a constraint but can't change the GL mid-year.
LiveFlow FP&A is the reporting and consolidation layer — not a GL replacement. If your WIP schedule lives in a spreadsheet that you rebuild every month from QBO exports, LiveFlow FP&A keeps that model live without requiring a manual export after each pay application posts. Book a demo to see how the connection works across your specific entity and job structure.
According to LiveFlow's Finance in the AI Era report (March 2026), 78% of finance teams still move data primarily via manual spreadsheet exports — and 78% say waiting on data from other systems is the number one cause of close delays. For construction finance teams bridging a project management platform and QBO, both of those statistics describe the same problem: the integration gap is costing you close time every period.
Ready to stop reconciling pay apps by hand?
AIA billing in QuickBooks Online is workable with the right setup — a properly structured Customer:Job hierarchy, service items that mirror the G703, a dedicated Retainage Receivable account, and cumulative invoicing that carries forward each application period. But the manual reconciliation between the pay app, the GL, and the WIP schedule compounds with every additional job and entity you add.
Two paths forward exist depending on where you are in your stack evaluation. LiveFlow FP&A is built for finance teams staying on QBO who need live consolidated reporting across multiple entities or a live connection to their WIP spreadsheet model — without rebuilding anything. Flow ERP is built for multi-entity GCs and specialty contractors ready to replace QBO with a system where multi-entity accounting, job costing, and FP&A share one ledger and close doesn't require a separate reconciliation cycle.
Book a demo to see how Flow ERP handles AIA job costing, WIP, and close without the manual sync work.
Frequently asked questions
Quick answers to the questions contractors ask most about this topic.
Does QuickBooks Online do AIA billing natively?
QuickBooks Online does not support native AIA G702/G703 billing. There is no built-in AIA template — finance teams must configure QBO's progress invoicing feature, service items, and Customer:Job hierarchy to approximate the schedule of values structure, with retainage and stored materials handled through manual account setup. For multi-entity GCs with high billing volume, Flow ERP replaces this workaround with a native construction accounting structure.
Can I create an AIA pay app in QuickBooks Online?
You can create an AIA-style pay application in QuickBooks Online using its progress invoicing feature, but the output is a standard QBO invoice — not an AIA-formatted G702/G703 document. The G702 and G703 forms themselves must be generated separately in Excel, a construction management platform like Procore or Buildertrend, or a dedicated AIA billing tool. QBO stores the underlying billing data; the form generation happens outside QBO.
Why can't I find an AIA billing template in QuickBooks?
QuickBooks Online doesn't include an AIA billing template because QuickBooks is a general-purpose accounting platform, not a construction-specific system. The AIA G702 and G703 are standardized forms published by the American Institute of Architects and are specific to commercial construction contracts — a billing format QBO was not designed to produce natively. Contractors using QBO generate the AIA forms in a project management platform or spreadsheet and post the resulting amounts into QBO as standard invoices.
What is the best AIA billing software for QuickBooks users?
For QuickBooks users who need AIA pay app generation with a QBO sync, Procore, Buildertrend, and JobTread all generate G702/G703 forms and connect to QBO — but each requires manual steps to handle retainage, stored materials, and SOV line-item detail in QBO after the sync. For multi-entity contractors ready to consolidate billing, accounting, and FP&A into one system, Flow ERP removes the sync gap entirely by handling job costing and pay app accounting in a single ledger.
What is the best AIA billing software?
The best AIA billing software depends on where the form generation needs to happen. For field-driven pay app generation, Procore is the most widely adopted platform in commercial construction and produces AIA-compliant G702/G703 output. For multi-entity GCs and specialty contractors who need the accounting side — WIP, retainage receivable, and job-level P&L — handled natively alongside billing, Flow ERP unites accounting, AP/AR, and FP&A in one AI-native platform built for physical businesses with complex project structures. See our guide to construction accounting software by growth stage for a full breakdown by company size and billing complexity.
