The AIA G702 and G703 forms are the backbone of construction payment processing. The G702 is the application and certificate for payment. The G703 is the continuation sheet that breaks down the schedule of values by line item. Together, they control how money flows from owner to GC to subcontractor.

Most GCs treat these forms as paperwork to process, not financial controls to enforce. That approach costs the average mid-size GC $84,000 to $210,000 annually in overpayments, duplicate billing, and retainage errors.

Here are seven best practices that turn the G702/G703 from an administrative burden into a financial safeguard.

1. Standardize the Schedule of Values Before the First Draw

The SOV on the G703 determines how every dollar gets billed for the entire project. A poorly structured SOV creates billing disputes that compound month after month.

Set SOV standards before the subcontractor submits their first G703. Require line items that match the scope breakdown in the subcontract, not the sub's internal cost codes. A mechanical sub billing $1.2M should have 25-40 line items, not 6 lump sums.

Reject any SOV that front-loads mobilization or general conditions above 5% of contract value. A $600K electrical sub billing $90K for mobilization in month one is pulling profit forward, not covering real costs.

Mandate that the SOV includes labor and material splits on every line item exceeding $50,000. This gives you the data to verify percentage completion against actual deliverables.

2. Establish a Percentage Completion Verification Process

The percentage complete column on the G703 is the most manipulated field on the form. Subs estimate their own completion. Without verification, those estimates drift upward by 8-15% on average.

Create a verification protocol before the first billing cycle. Assign a project engineer or superintendent to walk each major scope area and record independent percentage estimates 3-5 days before pay apps are due.

Compare the sub's claimed percentage against your field estimate. Flag any line item where the gap exceeds 10%. A drywall sub claiming 70% complete on Level 3 framing when your field walk shows 55% is overbilling by $22,500 on a $150K line item.

Document your field verification with photos and notes tied to specific G703 line items. This documentation becomes critical if a dispute escalates.

3. Implement Front-Loading Detection on Every Pay App

Front-loading is the practice of billing disproportionately high amounts in early billing periods. It shifts financial risk from the sub to the GC. If the sub defaults after collecting 60% of the contract value while completing only 35% of the work, the GC funds the gap.

Build a front-loading check into your G702/G703 review. Calculate the billing curve for each sub and compare it against the project schedule.

Warning Sign	What It Looks Like	Financial Risk
Mobilization above 5% of contract	$80K mobilization on a $800K sub	$40K+ overpayment if sub defaults early
Material-heavy early billing	90% materials billed by month 3 of 8	Stored material disputes, double billing
General conditions front-loaded	50% of GC billed in first 2 months	Inflated early draws, reduced leverage
Overhead loaded into early items	Shop drawing/submittal lines at 3x industry rate	Profit pulled forward, reduced completion incentive
Unbalanced unit prices	Early-phase items priced above market	Overpayment on completed items

A sub billing on a straight-line curve through month 4, then claiming 85% complete at month 5 on an 8-month scope, is front-loading. Catch it before you certify the G702.

4. Require Supporting Documentation for Every Line Item Over $25,000

The G703 shows numbers. Supporting documentation proves those numbers are real.

For every line item billing above $25,000 in a single period, require at minimum: delivery tickets for materials claimed, labor reports or timesheets for self-performed work, subcontractor invoices for lower-tier work, and inspection reports for completed milestones.

Stored materials require particular scrutiny. The G703 includes a column for materials presently stored. Require photos with date stamps, warehouse addresses, and insurance certificates covering stored materials. A sub claiming $175,000 in stored ductwork should produce a warehouse receipt, delivery schedule, and proof of insurance on those materials.

Without documentation, you are certifying payment based on the sub's word alone. That word is worth exactly nothing in a surety claim or an owner audit.

5. Coordinate Lien Waivers With Every G702 Submission

Lien waivers and pay applications are two sides of the same transaction, but many GCs process them separately. This creates a window where payment is released before lien rights are waived.

Require conditional lien waivers with every G702 submission. The conditional waiver covers the current draw amount and becomes unconditional upon payment. Require unconditional waivers for all prior draws before processing the current one.

Track lien waiver status on a matrix that mirrors the G703 line items. Every sub and every billing period should have a corresponding waiver. Missing waivers from two periods ago are a bigger problem than a missing waiver from last month, because they represent unresolved lien exposure on already-paid work.

States handle lien waivers differently. California requires statutory waiver forms. Texas allows custom forms. Know your state requirements and build them into your G702 workflow.

6. Automate Math Verification Across G702 and G703

The G702 and G703 contain interdependent calculations that must reconcile perfectly. The total completed and stored on the G703 must match Line 4 on the G702. Retainage on the G703 must match Line 5 on the G702. The net payment due on the G702 should equal total earned minus retainage minus previous payments.

Manual verification catches most errors. But when you process 30-60 pay apps per month across multiple projects, math errors slip through. Industry data shows that 12% of manually reviewed G702/G703 submissions contain at least one arithmetic error. The average error value is $4,200.

Automate the math check. Whether you use a spreadsheet formula, a construction management platform, or a dedicated pay app tool, the math verification should happen before any human reviews the content. This frees your project accountant to focus on the judgment calls, like whether that 72% completion claim is accurate, instead of recalculating column totals.

7. Establish Clear Change Order Integration Procedures

Change orders are where the G703 gets messy. New line items appear mid-project. Contract values shift. Previous billing history becomes harder to reconcile.

Create a standard procedure for how change orders appear on the G703:

Add approved change orders as new line items at the bottom of the G703, with clear CO numbering that matches the change order log.
Never allow a sub to modify an existing line item to absorb change order value. That hides the cost impact and makes auditing impossible.
Require that the G702 contract value (Line 1 plus Line 2) matches the original contract plus all approved change orders, and nothing more.
Pending change orders should not appear on the G703 until formally approved. Track them separately.

A sub adding $45,000 in approved change order work should show exactly $45,000 in new G703 line items. If the G702 contract value increased by $52,000 instead, you have a $7,000 discrepancy that needs explanation before certification.

Putting It All Together

These seven practices form a complete G702/G703 management system. Implemented individually, each one catches specific errors. Implemented together, they create overlapping controls that make overbilling, front-loading, and billing fraud extremely difficult to execute.

The investment is 2-4 hours of additional review time per billing cycle. The return is $8,000 to $35,000 in prevented overpayments per cycle, depending on project size and subcontractor count.

Frequently Asked Questions

How many line items should a G703 have per $1M of contract value? Industry standard is 20-40 line items per $1M. Below 20, the line items are too broad to verify meaningful progress. Above 40, you are tracking at a level of detail that slows review without improving accuracy. Adjust based on trade complexity. Mechanical and electrical scopes need more granularity than concrete or steel.

Should I reject a G702 for a $500 math error? Yes. Return it for correction every time, regardless of the dollar amount. A $500 error today becomes a $5,000 error next month if the sub learns that small discrepancies pass through. Consistent enforcement establishes your standard.

How do I handle a sub who refuses to provide supporting documentation? Your subcontract should require supporting documentation as a condition of payment. If the sub refuses, withhold payment on the undocumented line items and process the remainder. Document the withholding reason in writing. Most subs comply after the first withheld payment.

Can I use non-AIA forms that mirror the G702/G703 format? Yes, but verify that your prime contract and subcontracts allow substitute forms. Many owner-GC agreements require AIA documents specifically. Non-AIA forms work if they capture the same data fields and your contract permits them.

What retainage percentage should I apply on the G702? Standard retainage is 10% through 50% completion, reducing to 5% thereafter. Some states cap retainage at 5% throughout the project. Your subcontract retainage should match or align with the owner-held retainage on your prime contract. Never hold more retainage from subs than the owner holds from you.

How far back should I audit G702/G703 submissions if I suspect overbilling? Go back to draw one. Front-loading and overbilling are cumulative. A sub who overbilled by 8% in month two compounds that error through every subsequent billing. Reviewing only recent draws misses the root cause and understates the total overpayment.

Stop reviewing G702/G703 submissions manually. SubcontractorAudit automates math verification, flags front-loading patterns, and tracks every line item across billing periods. See how pay app audit works.