AIA Billing Invoice Processing: G702 & G703 Guide

AIA pay application processing is the workflow of receiving, verifying, and extracting data from G702 (Application and Certificate for Payment) and G703 (Continuation Sheet) forms submitted by subcontractors. The G703 continuation sheet contains a schedule of values breaking down each line item's description, scheduled value, work completed in previous and current periods, materials presently stored, total completed and stored to date, percentage complete, retainage, and the balance to finish. Each of these data points must be accurately extracted and entered into project accounting systems before payment can be approved.

Both forms are standardized documents created by the American Institute of Architects and serve as the default payment application format across U.S. construction contracts. The G702 acts as the summary cover sheet, capturing the total application amount, change order status, and certification signatures. The G703 is the detailed backup, listing every cost code or trade division with its corresponding financial breakdown. Together, they create a structured but data-dense payment request that flows from subcontractor to general contractor to owner.

Here is what nearly every guide, template, and software tool gets wrong: they focus exclusively on helping contractors fill out these forms. The other side of the transaction, where AP departments and project accountants must receive, cross-reference, and process those same forms, gets almost no attention. Yet this is precisely where payment delays originate. A subcontractor submits a pay application; the receiving team must verify that billed amounts match contract values, confirm retainage percentages are applied correctly, reconcile change orders against approved amounts, and then key all of that data into their accounting or ERP system. Errors or bottlenecks at this stage hold up the entire payment chain.

The scale of this challenge compounds on larger projects. A general contractor managing a commercial build may receive monthly pay applications from 30, 50, or even 80 subcontractors, each submitting multi-page G703 continuation sheets alongside their G702 summaries. Every one of those submissions requires the same verification and data extraction process. When AIA billing invoice processing is handled manually, the monthly close becomes a recurring crunch where AP staff race to validate dozens of pay applications against contracts, prior billings, and stored materials documentation before payment deadlines hit.

Data Points Inside G702 and G703 Forms

Every AIA pay application landing on your desk consists of two interconnected documents. The G702 provides the summary view. The G703 supplies the line-item detail behind those summary numbers. Processing either form in isolation is impossible because the two must reconcile mathematically, and understanding exactly which data fields matter will clarify why AIA billing invoice processing demands more rigor than standard AP workflows.

G702: Application and Certificate for Payment

The G702 is a single-page summary that captures the financial snapshot of a contract at a specific point in time. The critical data fields you need to extract and validate include:

Contractor and project identification — contractor name, project name, project number, application number, and the billing period covered. These fields tie the pay application to a specific contract in your system.
Original contract sum — the base contract amount before any modifications.
Net change by change orders — the cumulative total of all approved change orders to date, which adjusts the original contract sum up or down.
Contract sum to date — the adjusted contract total (original sum plus net change orders). This is the number every downstream calculation builds from.
Total completed and stored to date — the combined value of all work performed and materials stored, pulled directly from the G703 totals.
Retainage — typically shown as a percentage and a calculated dollar amount, sometimes split between retainage on completed work and retainage on stored materials. This field varies more than any other across submissions because some contracts apply different retainage rates at different project phases.
Total earned less retainage — the amount the contractor has earned after withholding retainage.
Less previous certificates for payment — what has already been paid on prior applications.
Current payment due — the net amount owed this billing period.
Architect/engineer certification fields — the signature block and approved amount, which may differ from the amount requested if the architect has adjusted the application.

Each of these fields feeds directly into your accounts payable records, project cost tracking, and cash flow projections.

G703: Continuation Sheet Line-Item Detail

The G703 is where the complexity lives. This continuation sheet breaks down the contract into individual line items from the contractor's schedule of values, with each row tracking cumulative progress across billing periods. For every line item, you are extracting:

Item number — the reference identifier tied to the schedule of values.
Description of work — the scope element (e.g., "structural steel," "electrical rough-in," "site grading").
Scheduled value — the budgeted dollar amount for that line item, established when the schedule of values was approved.
Work completed from previous applications — the cumulative dollar value of work billed and approved in all prior periods.
Work completed this period — the new dollar value of work being billed in the current application.
Materials presently stored — the value of materials delivered to the site (or stored off-site with approval) but not yet incorporated into the work.
Total completed and stored to date — the sum of previous work, current work, and stored materials. This cumulative figure drives percentage-complete calculations.
Percentage complete (%) — total completed and stored divided by the scheduled value.
Balance to finish — the scheduled value minus total completed and stored, representing remaining contract value on that line item.
Retainage — the dollar amount withheld on that specific line item, calculated by applying the retainage percentage to the total completed and stored.

Why G703 Is the Data Extraction Bottleneck

Standard invoices have a fixed, predictable structure. A G703 continuation sheet does not. A single subcontractor's pay application might contain 15 line items or 150, depending on how granularly the schedule of values was broken down. This variable-length table format is the first challenge: you cannot build a fixed template that maps to every submission.

The second challenge is cumulative math. Every G703 carries forward figures from all prior billing periods. The "work completed from previous applications" column must match exactly what was approved last month. If a subcontractor's previous-period numbers do not align with your records, every calculated field on the current application is suspect.

The third challenge involves nested relationships. Change orders add new line items or modify existing scheduled values, which ripples through the cumulative totals. Retainage may apply at different rates to different line items or shift when the project hits substantial completion. These interdependencies mean that each line item is not truly independent; errors in one row can cascade across the entire form.

Cross-Form Reconciliation

The G702 summary totals must tie back to the G703 line-item details. The "total completed and stored to date" on the G702 should equal the sum of that same column across all G703 line items. The retainage amount on the G702 should equal the sum of all line-item retainage on the G703. When these figures do not reconcile, the pay application cannot be approved, and identifying exactly where the discrepancy originates requires tracing through every line item.

How Construction Progress Billing Differs from Standard Invoicing

A standard vendor invoice states a fixed amount for goods delivered or services rendered. Construction progress billing is fundamentally different in three ways. First, billed amounts change every period based on the percentage of work completed, which means every application is a moving target tied to physical progress on the job site. Second, materials presently stored must be tracked as a separate category because they represent value on-site that has not yet been installed, creating a distinct accounting treatment. Third, retainage creates a running liability that compounds across every billing period and every line item, affecting the current payment due, the contractor's earned-but-unpaid balance, and your organization's cash position on the project.

This layered structure is why AIA G702 G703 data extraction requires more than a simple line-item read. Each pay application is a cumulative financial record of the entire project's billing history, compressed into a two-form package that must be decomposed, validated, and reconciled before a single dollar moves.

The Receiver's Pay Application Processing Workflow

Most AIA billing guides end at the subcontractor's submit button. The workflow below covers what happens after the pay application lands on your desk.

Without a structured process, pay application processing becomes reactive — documents sit in inboxes, verifications happen inconsistently, and payment deadlines creep up without warning. According to Rabbet's 2025 Construction Payments Report, general contractors spend an average of 65 hours per month managing payments to subcontractors and vendors. Both general contractors and subcontractors identify lack of organized process as the top reason for slow payments in U.S. construction.

A repeatable construction progress billing workflow eliminates that ambiguity. Here is a seven-stage process you can adopt directly or use as a benchmark against your current approach.

1. Receipt and Logging

Every pay application should be logged the moment it arrives — whether by mail, email, or a project management portal. Capture four data points immediately:

Date received (this starts the clock on prompt-payment obligations)
Subcontractor name and contract number
Billing period covered
Application number (sequential, matching the subcontractor's numbering)

A centralized tracking log, even a simple spreadsheet, gives your team visibility into which applications are in-house and where each one sits in the review cycle. The received date matters more than any other field here: many construction contracts and state prompt-payment statutes mandate payment within specific timeframes — often 30 days from receipt of a compliant application. Miss that window, and you face statutory interest penalties that compound quickly across multiple subcontractors.

2. Initial Review and Completeness Check

Before verifying a single dollar, confirm the submission package is complete. An incomplete application is not a compliant application, and returning it resets the payment clock.

Check for:

Required signatures on both the G702 cover sheet and the G703 continuation sheet
Notarization, if your contract requires it
Supporting documentation such as material delivery receipts, daily logs, or inspection reports referenced in the contract
Conditional or unconditional lien waivers for prior-period payments, as stipulated by the subcontract terms
Schedule of values alignment — the line items on the G703 should match the originally approved schedule of values without unauthorized additions or modifications

Flag deficiencies immediately and return the package to the subcontractor with a written list of what is missing. Document the return date — this protects you if payment timing becomes disputed.

3. Mathematical Verification

This is where subcontractor payment application verification demands the most attention. Three calculations must check out before you move forward:

G702/G703 reconciliation. The total completed and stored-to-date on the G702 cover sheet must equal the sum of all line items in Column G of the G703 continuation sheet. Any discrepancy, even a rounding difference, needs resolution.

Cumulative carry-forward accuracy. Each line item's "work completed from previous application" (Column D on the G703) must match the corresponding "total completed and stored to date" from the prior billing period. Pull the previous application and compare line by line. Errors here are common and often unintentional — subcontractors working from their own internal tracking may drift from the figures on their last submitted G703.

Retainage calculations. Verify that retainage is calculated correctly per your contract terms. Some contracts apply a flat percentage across all work; others reduce retainage after substantial completion or exempt stored materials. The retainage withheld on each line item should reflect the contractual rate precisely, and the G702 summary retainage figures should match the G703 detail.

4. Cross-Reference Against Contract and Previous Applications

Mathematical accuracy does not guarantee billing accuracy. Cross-reference the current application against:

The original contract value and any approved change orders. The G702's "original contract sum" and "net change by change orders" fields should reflect your records exactly. Unapproved change orders billed as approved are a frequent source of disputes.
The prior application's cumulative totals. Beyond the line-item carry-forward check, confirm that the G702's summary figures (total completed, total retainage, total earned less retainage) progress logically from the previous period.
Field observations or project manager assessments. Does the percentage of completion claimed on individual line items align with what your project team observes on-site? A subcontractor billing 90% complete on structural steel when your PM estimates 60% needs resolution before payment certification proceeds.

5. Data Extraction into Accounting Systems

Once verification is complete, the approved figures need to move into your project accounting or construction management system. This is typically the most time-consuming step in the entire workflow.

A single G703 continuation sheet can contain dozens of line items, each with six or more data columns. For every pay application, someone on your team is manually re-keying each line item — description, scheduled value, work completed this period, materials stored, cumulative totals — from a PDF or paper form into your system. Multiply that by the number of active subcontractors billing monthly, and the data entry burden becomes substantial.

The re-keying step also introduces transcription risk. A misplaced decimal or transposed digit at this stage can propagate through your cost reports, job costing, and owner billing — potentially undermining the verification work you just completed.

6. Approval Routing

With verified data entered into your system, route the application through your internal approval chain. Depending on your organization, this may involve:

Project manager sign-off confirming work-in-place percentages
Project accountant review confirming mathematical and contractual accuracy
Senior management or owner approval for applications above a dollar threshold

Define approval authority levels and turnaround expectations in advance. A pay application that passes every verification step but stalls in an approval queue for two weeks still results in a late payment.

7. Payment Scheduling

After final approval, schedule the payment according to contract terms. Record the approved amount, retainage withheld, net payment amount, and scheduled payment date in your tracking log. This closes the loop on that billing period and establishes the baseline for the next application's cross-reference checks.

Keep prompt-payment deadlines visible throughout this process. If your contract specifies payment within 30 days of a compliant application and your internal workflow consumes 25 of those days, you have almost no buffer for exceptions or disputes. Building payment certification timelines backward from the contractual deadline — rather than forward from receipt — keeps subcontractor payments on schedule and your organization out of penalty territory.

Common AIA Billing Errors That Delay Subcontractor Payments

Even experienced subcontractors submit pay applications with errors. When your AP team processes 20 or more G702/G703 packages each month, these mistakes compound quickly — a single undetected error can trigger payment disputes, lien threats, or overpayments that are difficult to claw back. These errors are not unique to AIA billing; they reflect broader construction invoice processing challenges that affect any AP team managing high volumes of subcontractor payments. Building systematic checks around the most frequent error categories is the difference between a controlled process and a reactive one.

Scheduled Value Mismatches

The G703 schedule of values should reflect the original contract amount, adjusted only by formally approved change orders. One of the most common errors occurs when a subcontractor revises their line-item breakdown — splitting or reallocating scheduled values — without a corresponding change order to authorize the change. The total contract sum on G702 might still appear correct, but the underlying distribution across line items no longer matches your records.

If you approve a revised schedule of values that was never formally authorized, you lose your baseline for tracking completion percentages. Catching this after several billing cycles means reconciling months of prior applications against an incorrect foundation.

Cumulative Calculation Errors

Each pay application builds on the previous one. The "Work Completed from Previous Application" column on G703 must exactly match the cumulative approved totals from the prior period. When subcontractors prepare applications manually or use spreadsheets with broken cell references, prior-period figures get re-entered incorrectly.

A subcontractor might show $45,000 completed from previous applications on a line item when your records show $42,000 was approved. That $3,000 discrepancy flows through to the current amount due, inflating the payment request. These errors are particularly insidious because they can persist undetected across multiple billing periods, with each subsequent application compounding the original mistake.

Retainage Arithmetic Mistakes

Retainage errors take two forms. The first is straightforward miscalculation — applying 10% retainage to a $50,000 line item and arriving at $4,800 instead of $5,000. The second is more subtle: applying the wrong retainage rate entirely. Many construction contracts specify different retainage rates by project phase. A subcontractor might continue applying 10% retainage after substantial completion when the contract calls for a reduction to 5%, or vice versa. When different line items carry different retainage rates — common on projects with phased completion milestones — the arithmetic becomes error-prone on both sides.

The consequence: Retainage miscalculations directly affect the amount you are holding. Undercollecting retainage exposes the owner and GC to risk if the subcontractor fails to complete punch list work. Overcollecting creates cash flow disputes that can damage subcontractor relationships and trigger formal disputes.

Overbilling Beyond Actual Progress

Billed completion percentages that exceed actual field progress represent the highest-risk error category. A subcontractor billing 75% complete on rough-in electrical when the field inspector's report shows 60% completion is requesting payment for work not yet performed.

Catching overbilling requires coordination between your AP team and field personnel. The pay application alone will not reveal this — the numbers can be internally consistent while still overstating progress. Systematic overbilling, whether intentional or the result of optimistic self-reporting, creates a front-loaded payment curve that leaves insufficient contract value to fund remaining work. On larger projects, this is a leading indicator of subcontractor financial distress.

Missing or Incomplete Change Order Documentation

Paying for unapproved change order work puts you in a difficult position — if the change order is later negotiated to a lower amount or rejected entirely, you have overpaid. Yet subcontractors sometimes bill for change order work before the change order is formally executed. You will see the contract sum on G702 adjusted to reflect pending change orders, or new line items appearing on G703 for work that has no approved change order number. In some cases, the G702 net change by change orders reflects an amount, but the G703 schedule of values has not been updated to incorporate the new scope as discrete line items. Your review process should flag any change order amounts on G702 that cannot be matched to fully executed change order documentation in your project files.

G702 Summary Reconciliation Failures

The G702 acts as a summary of the G703 detail, and the two forms must reconcile exactly. The original contract sum plus net change by change orders must equal the current contract sum. Total completed and stored to date on G702 must equal the sum of the corresponding G703 column. The math seems straightforward, but rounding differences, transposition errors, and incorrect cell references in spreadsheet-based applications create discrepancies that require the subcontractor to revise and resubmit.

Every resubmission cycle adds days to the payment timeline. For subcontractors operating on tight cash flow, even a one-week delay can strain their ability to pay suppliers and labor — which ultimately affects your project schedule. The goal is not to eliminate errors entirely, but to catch them systematically before they enter your approval workflow and cascade into payment delays, disputes, or overpayment exposure.

Verifying Retainage Calculations and Change Order Adjustments

Retainage and change order verification are where the highest-dollar errors hide in AIA pay application processing. A missed decimal on retainage across dozens of line items or an unapproved change order slipping into a billing can cost tens of thousands of dollars per pay period. These two verification tasks demand methodical, line-by-line review rather than spot checks.

Retainage Verification Across G702 and G703

Retainage appears in both forms, and the figures must reconcile. The G702 reports total retainage withheld as a single summary figure. The G703 breaks retainage down at the individual line-item level. Your verification starts at the G703 detail and works up to the G702 summary.

For every line item on the G703, the retainage calculation follows a straightforward formula:

(Total Completed and Stored to Date) × (Retainage Percentage) = Retainage Amount

Check this for each line item without exception. Errors frequently appear when subcontractors calculate retainage against the wrong base amount — using work completed this period instead of the cumulative total, for instance. Once you have verified every line item, sum the individual retainage amounts. That total must match the retainage figure reported on the G702. Any discrepancy means at least one line-item calculation is wrong, or the G702 summary was not updated after G703 changes.

Retainage Release Tracking

Retainage is not static across the life of a project. As milestones are reached — substantial completion, punch list completion, final acceptance — retainage rates may decrease or partial retainage may be released. A project might start at 10% retainage and drop to 5% after the work is 50% complete, or release retainage entirely on specific line items that are fully accepted.

The G703 must reflect current retainage terms, not the original contract terms if those have been modified. When reviewing a pay application mid-project, confirm that the retainage percentage applied to each line item matches the most recent contractual agreement. If a subcontractor is still billing at original retainage rates after a contractual reduction, they are overbilling retainage — and if they are applying reduced rates before those reductions were formally approved, they are underbilling it.

State law adds another layer. Many U.S. states cap retainage percentages, commonly at 5% or 10%, and mandate specific release timelines after substantial completion. Some states prohibit retainage entirely on certain project types or above certain completion thresholds. Your verification process must account for the applicable state statute. If a subcontractor is working in a state that caps retainage at 5% and the pay application withholds 10%, you have a compliance problem regardless of what the contract says — state law typically overrides contractual retainage terms.

Change Order Reconciliation

Approved change orders modify the G703 schedule of values in one of two ways: they add entirely new line items for additional scope, or they adjust the scheduled value of existing line items. Either way, the G702's "Net Change by Change Orders" field must equal the sum of all change order adjustments reflected in the G703. This is a hard reconciliation — the numbers either match or they do not.

The verification process requires you to trace each change order referenced in the pay application back to approved documentation. Every change order line item or adjustment on the G703 should correspond to a signed, approved change order with a matching dollar amount. Flag any G703 line item that references a change order number you cannot locate in your approved change order log. Similarly, flag any approved change order that should appear on the G703 but does not.

A common timing issue complicates this reconciliation: change orders approved partway through a billing period may be reflected in the G702 summary totals but not yet broken out in the G703 line-item detail. This creates a temporary gap where the two forms do not reconcile cleanly. When you encounter this, document the discrepancy and confirm with the subcontractor whether the G703 detail will be updated in the next pay application. Do not approve payment on change order amounts that lack G703 line-item support, even if the G702 summary includes them.

Connecting Verification to Payment Matching

Retainage and change order verification do not happen in isolation. The verified pay application must ultimately match against three reference points: the original contract amount, the cumulative approved change orders, and the complete prior payment history. This multi-document reconciliation is the construction-specific version of invoice matching workflows including three-way matching, adapted for the progressive billing structure of AIA documents. If your retainage and change order figures are verified at the line-item level but the pay application still does not reconcile against these reference documents, the discrepancy likely traces back to an error carried forward from a prior billing period — which means reviewing previous pay applications, not just the current one.

From Manual Entry to Automated AIA Billing Data Extraction

While existing tools and guides focus on helping subcontractors generate G702/G703 forms, the data extraction challenge on the receiving end has fewer purpose-built solutions. Most construction AP departments still process AIA pay applications by hand. A staff member opens the G702 cover sheet, types the contract sum, retainage percentage, and payment amounts into a spreadsheet or accounting system, then moves to the G703 continuation sheet and begins entering line items one row at a time. For a single G703 with 50 line items, that means keying 10 or more data fields per row — item number, description, scheduled value, work completed from previous applications, work completed this period, materials presently stored, total completed and stored, percentage complete, balance to finish, and retainage. Then the staff member cross-checks every column total against the G702 summary figures. The entire process for one pay application can take 30 to 45 minutes, and the error rate climbs with every row because transcription mistakes compound in cumulative billing documents where a single miskeyed figure cascades through calculated fields.

Some firms reduce the math burden by using pre-formatted Excel templates that mirror the G703 column structure. Staff still enter every value manually, but the template calculates retainage amounts, completion percentages, and column totals automatically. This eliminates arithmetic errors — if someone enters the raw numbers correctly, the derived figures will be right. But the transcription bottleneck remains identical. The person entering data still reads each cell from the paper or PDF form and types it into the corresponding spreadsheet cell, which is where most errors originate in the first place.

Traditional optical character recognition offers a partial solution by digitizing the printed or scanned content of pay applications. However, standard OCR struggles with the tabular density of G703 continuation sheets. The tightly spaced columns, variable row counts across multi-page continuations, and nested sub-line items create parsing challenges that generic OCR engines are not designed for. More critically, traditional OCR treats each cell as an isolated text fragment. It does not understand that "work completed this period" plus "from previous application" should equal "total completed and stored," or that the retainage column follows a specific percentage of the total completed value. The result is raw text output that still requires substantial manual cleanup and restructuring before it can feed into an accounting system.

AI-powered document extraction approaches AIA pay applications differently from character-level OCR. Rather than scanning characters in isolation, AI-based extraction recognizes the G703 as a structured table with defined column relationships and cumulative calculation logic. It identifies table boundaries across multi-page continuation sheets, maps each column to its semantic meaning, and extracts line-item data with awareness of how values relate to each other. The output is a structured Excel, CSV, or JSON file where every row represents a line item and every column maps to a specific G703 field — ready for direct import into accounting or project management software.

With a tool like Invoice Data Extraction, the workflow for processing AIA pay applications shifts from manual transcription to guided automation. You upload the G702/G703 PDF — whether it is a native digital file or a scan — and prompt the AI on exactly what to extract:

"Extract line items from this G703: item number, description of work, scheduled value, work completed from previous application, work completed this period, materials presently stored, total completed and stored, retainage"

The AI parses the document structure, handles continuation sheets that span multiple pages, and returns a clean spreadsheet with properly typed numeric values. Because the extraction prompt is reusable, you can save it to a prompt library and apply the same instructions to every subcontractor's pay application across monthly billing cycles. The consistency this creates is particularly valuable for AIA billing, where the same form structure repeats every payment period but the values change incrementally.

Choosing the right approach depends on volume and complexity. If your firm manages a small project with three or four subcontractors submitting straightforward pay applications, manual entry with a template may be adequate — the time investment is manageable and the error surface is limited. But when you are processing dozens of pay applications monthly, each with multi-page G703 continuation sheets carrying 40 to 100 line items, manual methods become unsustainable. The hours spent on data entry, the errors caught during reconciliation, and the payment delays caused by rework all point toward a threshold where AIA billing automation is no longer optional. For firms at or beyond that threshold, AI-powered extraction tools that automate AIA pay application data extraction eliminate the transcription bottleneck entirely, letting your AP team focus on the verification and approval decisions that actually require human judgment.