AIA Billing and Pay Applications: What Construction Software Must Control

Understand G702/G703-style billing, schedule of values, stored materials, prior applications, retainage, change carryover, review, and software controls.

The Syntecton team
6 min

Commercial progress billing is cumulative. Every new payment application depends on the contract value, approved changes, schedule of values, previous applications, stored materials, retainage and current-period production.

That makes billing a control system—not an invoice template.

Short answer: Construction pay-application software should preserve the schedule of values, carry prior billing correctly, separate completed work from stored materials, calculate retainage according to the contract, incorporate approved changes, route review and maintain the complete cumulative history.

What G702 and G703 do

AIA identifies G702 as the Application and Certificate for Payment and G703 as the Continuation Sheet used with it. The G702 summarizes the payment request; the G703 provides schedule-of-values detail.

Using a familiar layout does not itself establish compliance. The governing contract, form license, project requirements and reviewer determine what is required.

The cumulative billing chain

SYNTECTON • OPERATING CONTROL SERIES Aia Billing Pay Applications 1 Original contract 2 Approved changes 3 Current contract sum 4 Schedule of values 5 Work + stored materials 6 Less retainage 7 Less priorcertificates/payments 8 Current amount due Risk-aware construction operations • syntecton.com
The cumulative billing chain: how the current amount due is derived from the contract sum, schedule of values, stored materials, retainage and prior certificates.

Schedule of values

The schedule of values allocates contract value among work components. Software should control:

  • original line items;
  • approved reallocations;
  • approved change additions;
  • scheduled value;
  • prior work;
  • current work;
  • stored materials;
  • total completed and stored;
  • percentage complete;
  • remaining balance;
  • retainage.

Changing the schedule solely to make current billing fit can distort progress and future calculations. Revisions should be controlled and documented.

Core G702-style calculation

The exact form and terms govern, but the conceptual relationship is:

Current payment due = total completed and stored − retainage − previous payments/certificates

The application also reconciles original contract value and approved changes.

Software must retain decimal precision and carry values consistently across periods. Small rounding or carryover errors can repeat through every subsequent application.

Work completed versus stored materials

These categories are not interchangeable.

  • Completed work represents installed or performed work.
  • Stored materials represent qualifying materials not yet incorporated.

Stored-material billing may require:

  • location;
  • invoices;
  • proof of payment;
  • insurance;
  • photographs;
  • title or ownership documentation;
  • owner approval;
  • off-site storage requirements.

Software should collect support without implying that submission automatically makes the material billable.

Retainage

Retainage may apply differently to:

  • completed work;
  • stored materials;
  • particular line items;
  • subcontractors;
  • phases;
  • work after substantial completion.

The platform should:

  • display the applicable rate;
  • preserve prior retainage;
  • support authorized overrides;
  • document releases;
  • prevent unexplained manual changes;
  • reconcile owner and subcontract retainage separately.

Approved changes

Only changes authorized under the governing agreement should revise the contract sum.

The system should distinguish:

  • pending proposal;
  • approved owner change;
  • approved subcontract change;
  • change included in the schedule of values;
  • amount billed;
  • remaining change value.

Pending changes may affect forecast while remaining excluded from contract billing.

Review workflow

SYNTECTON • OPERATING CONTROL SERIES Aia Billing Pay Applications: Control View 2 ReviseApprove/certify 1 Billing period opened 2 Contractor preparesapplication 3 Internal validation 4 Architect/owner review 5 Decision 6 Return with documentedreasons 7 Post receivable and trackcollection Risk-aware construction operations • syntecton.com
The pay-application review workflow, from an opened billing period through internal validation, architect/owner review, and either revision or certification.

Track:

  • submission date;
  • required review date;
  • reviewer;
  • revisions;
  • rejected lines;
  • certified or approved amount;
  • payment date;
  • short payment;
  • outstanding retainage.

Subcontractor pay applications

Subcontractor billing should connect to:

  • executed subcontract;
  • approved commitment changes;
  • subcontract schedule of values;
  • prior billing;
  • stored materials;
  • retainage;
  • compliance documents;
  • project review;
  • accounting payable.

Prevent:

  • billing beyond commitment;
  • unauthorized line-item movement;
  • incorrect prior billing;
  • duplicate applications;
  • overbilling stored materials;
  • approval by unauthorized roles.

Software demonstration checklist

Ask the provider to:

  1. Establish a schedule of values.
  2. Process three billing periods.
  3. Add stored materials in period two and install them in period three.
  4. Carry prior billing correctly.
  5. Apply different retainage treatment where authorized.
  6. Add an approved change.
  7. Reject and resubmit selected lines.
  8. Process a subcontractor pay application.
  9. synchronize the approved transaction to accounting.
  10. Export the full billing record and support.

Common failures

Prior-period values can be edited freely

Cumulative history becomes unreliable.

Change values do not carry to the schedule

Users rebuild the contract manually.

Stored materials remain after installation

The same value can be represented incorrectly across columns or periods.

Retainage is one uncontrolled percentage

Project and line-specific requirements cannot be represented.

The application and accounting invoice diverge

Receivable totals and approval status require reconciliation.

Generating a branded PDF is treated as billing control

The calculation and authorization chain matters more than the layout.

Frequently asked questions

What is the difference between G702 and G703?

G702 is the summary Application and Certificate for Payment. G703 is the continuation sheet providing schedule-of-values detail.

Is AIA billing required on every commercial project?

No. Requirements come from the governing contract and project procedures.

Can software automatically determine billable stored materials?

It can enforce fields and collect evidence, but contract requirements and reviewer judgment still govern eligibility.

How should approved changes enter billing?

Through a controlled, authorized contract revision connected to the schedule of values and billing history.

Can construction software replace architect certification?

No. Software can route and document review; it does not replace contractual authority.

The bottom line

Pay applications are cumulative commercial records. Software should control calculations, authorization and history across the entire billing chain rather than merely generate a recognizable form.

Control every billing period

Syntecton connects prime contracts, commitments, approved changes, schedules of values, retainage, owner billing and subcontractor pay applications.

Related reading

Sources

Signed · Syntecton Source Record© 2026 Syntecton, Inc.