AIA G702 and G703 Pay Applications: Setting Up Schedule of Values Billing Without Spreadsheet Errors

An AIA G702 G703 pay application works only when every number has a traceable path from the contract to the schedule of values, through prior billing, current work, stored materials, retainage, and finally the amount requested for the current period.

That is where many construction draws go wrong. The problem is often not that the contractor performed insufficient work. It is that the billing package does not reconcile. Last month’s cumulative numbers changed. 

A change order increased one sheet but not another. Stored materials were billed twice. Retainage was calculated against the wrong base. Or the mathematical package was correct but required supporting documents were missing.

A successful AIA-style payment application therefore starts with a well-designed schedule of values and depends on cumulative math that does not drift from one billing period to the next. 

The G703 Continuation Sheet supplies the detailed schedule-of-values support, while the G702 Application and Certificate for Payment summarizes the payment request and, in the standard owner-contractor workflow, provides the certification layer. 

AIA currently identifies the standard documents as G702–1992, Application and Certificate for Payment and G703–1992, Continuation Sheet. It also publishes other variations for subcontractor, cost-plus, GMP, construction-manager-as-adviser, and design-build arrangements.

The contract documents and project billing instructions still control. Not every project requires AIA forms, the same retainage treatment, notarization, lien waivers, stored-material proof, or architect review.

This guide focuses on the operational question that matters each billing cycle: How do you make the G702/G703 package mathematically consistent and complete enough that the GC, owner, architect, construction manager, or lender can review it without discovering avoidable discrepancies?

What Are AIA G702 and G703 Pay Applications?

AIA G702 Pay Applications and G703 Pay Applications are coordinated construction payment documents designed to show the financial status of a contract as work progresses.

The current standard G702 is G702–1992, Application and Certificate for Payment. AIA describes it as the document used when a contractor formally applies for progress payment and an architect certifies the amount due in the traditional owner-contractor-architect structure. 

It summarizes such items as the current contract amount, completed and stored work, retainage, previous payments, change-order adjustments, and the amount currently requested.

The current standard G703 is G703–1992, Continuation Sheet. It provides the detailed breakdown underneath that summary. AIA explains that G703 divides the contract sum into portions of work according to a contractor-prepared schedule of values and tracks progress against those portions.

The distinction matters:

Document	Purpose	Main Data	Common Error
G702	Summarizes the payment application and certification process	Contract sum, changes, completed/stored work, retainage, prior payments, current request	Summary numbers do not agree with G703
G703	Provides detailed schedule-of-values support	SOV lines, prior billing, current work, stored materials, cumulative progress, remaining value, retainage	Prior-period or formula values drift
Supporting package	Provides evidence required by the contract or payer	Waivers, invoices, delivery records, CO backup, signatures and other required documents	Mathematically correct pay app is incomplete

AIA says G702 and G703 are designed to work together, although project structure matters. AIA also provides G702S/G703S subcontractor variations and other specialized payment forms.

Because AIA Contract Documents are copyrighted and licensed works, contractors should obtain legitimate forms or authorized access rather than copying a recreated form from an unofficial spreadsheet. 

AIA’s instructions state that its copyrighted documents may not be reproduced or excerpted without permission. This article therefore discusses the calculations and workflow without reproducing form text or layout.

When Construction Projects Require G702 and G703

G702/G703 packages are common on commercial and institutional work, particularly where the construction contract establishes formal monthly applications for payment.

A general contractor may submit an AIA pay application to an owner. A subcontractor may be told to submit an AIA-style package to the general contractor, although AIA publishes specific contractor-subcontractor variations for that relationship. A lender-funded project may also incorporate the approved pay application into a broader draw package.

Architect-reviewed projects often use the G702/G703 structure because the detailed continuation sheet gives the reviewer a way to evaluate individual portions of the work before the payment summary is certified. 

AIA identifies the standard G702/G703 documents as designed for projects where the contractor has a direct agreement with the owner and separately identifies variations for other project arrangements.

That does not mean every construction project must use them.

Projects may instead use:

• proprietary owner forms;
• a construction-manager payment portal;
• lender-specific draw forms;
• subcontractor billing templates;
• modified AIA documents;
• cost-plus/GMP payment forms;
• design-build payment forms; or
• software-generated applications that follow a similar SOV structure.

The correct starting point is therefore the executed contract, general and supplementary conditions, subcontract, billing instructions, owner requirements, and any project-specific procedures.

A project may also specify a billing cutoff, submission date, waiver package, invoice format, stored-material documentation, certification path, or electronic portal requirements beyond anything visible on the payment forms themselves.

How to Build a Schedule of Values That Will Not Cause Problems Later

The strongest schedule of values billing setup happens before the first payment application.

A schedule of values, or SOV, allocates the contract amount among defined portions of the work. AIA describes it as a financial roadmap that itemizes project components and assigns dollar values to them. Under the standard AIA payment structure, the SOV becomes the basis for subsequent payment applications.

A poor SOV creates problems that compound every billing period. If it is too broad, reviewers cannot judge progress. If it is excessively fragmented, every monthly update becomes administratively heavy. 

If it is front-loaded, reviewers may challenge the relationship between value and actual progress. If change-order space was never considered, staff may eventually overwrite original contract lines merely to make revised totals work.

The schedule should normally reflect meaningful pieces of the contracted scope, considering factors such as trade, phase, physical location, major equipment packages, labor/material components, and the review expectations established by the project.

A mechanical subcontractor, for example, might separate major equipment procurement from rough-in, distribution, controls, startup, testing, and closeout instead of billing the entire subcontract through one line named “HVAC.”

A general contractor’s SOV may contain major divisions plus project-specific cost categories. Whatever structure is selected, its total must reconcile to the applicable contract value before billing begins.

A schedule of values is easier to maintain when its line items also connect logically to the project’s underlying cost structure. A consistent job costing system for contractors can help accounting teams compare billed progress with actual labor, material, subcontractor, and equipment costs without turning the pay application itself into a full job-cost report. 

Choosing the Right Line-Item Granularity

There is no universal correct number of SOV lines.

One $1 million “Electrical” line provides little visibility if the project includes underground work, switchgear, feeders, branch wiring, lighting, controls, testing, and closeout. The reviewer may struggle to determine whether a request for 58% completion accurately reflects the work in place.

At the other extreme, turning every box, fitting, room, and minor activity into its own SOV line can create hundreds of rows that accounting and field staff must maintain every month.

A useful line generally represents a portion of work that can be:

1. valued credibly;
2. observed or documented;
3. progressed independently;
4. tied to the contract scope; and
5. reviewed consistently throughout the job.

An illustrative building-project structure might include mobilization, demolition, structural framing, major equipment, rough-in, finishes, testing, punch-list work, and closeout. Larger or more complex projects may require substantially more detail.

Contractors designing their first detailed SOV may also find AIA’s discussion of how a construction schedule of values is structured useful when deciding how to divide the contract into meaningful billing components. 

Line-Item Approach	Benefit	Risk
One broad line per trade	Easy administration	Poor visibility; difficult progress review
Phase-based lines	Tracks construction sequence	May hide major material packages
Location-based lines	Useful for floor/area turnover	Can become repetitive on large jobs
Labor/material split	Useful for stored materials and separate retainage rules	Adds administrative detail
Highly granular cost-code structure	Strong traceability	Can make monthly billing cumbersome
Balanced hybrid	Supports review while remaining manageable	Requires thoughtful setup before billing

Avoiding Front-Loading

Front-loading means assigning disproportionately high value to early portions of the work relative to their reasonable value, often to accelerate recovery of cash early in a project.

Front-loading is not automatically unlawful merely because an SOV recovers certain costs early. Mobilization, bonds, permits, procurement, engineering, or legitimate early activities may carry significant value. The issue is whether the values are supportable under the contract and acceptable to the reviewing parties.

AIA’s schedule-of-values guidance emphasizes that an SOV should provide a meaningful financial roadmap. Project-specific supplementary conditions can also expressly address unbalanced or front-loaded schedules.

Operationally, aggressive front-loading creates a second problem even if initially approved: too little value may remain in later activities to cover the actual work needed to complete them.

Suppose finish carpentry requires $120,000 of real future production but the SOV leaves only $45,000 against that work because value was shifted into early mobilization. The contractor may eventually reach a point where field progress and billable SOV value no longer align.

Front-loading can also make later WIP reporting harder to interpret because billing position may move ahead of the actual cost-to-complete pattern. Keeping retainage and WIP schedules aligned with the underlying job-cost records makes it easier to distinguish legitimate early billing from a schedule that leaves too little value for later work. 

Separate Labor and Materials Where It Helps

Labor and material lines do not need to be separated on every project, but separation can materially improve billing control when the contract treats them differently.

A separate material component may make it easier to show that a major equipment package has been purchased and stored but not installed. It can also support contracts that apply different retainage treatment to completed work and stored materials.

For example:

• Air-handling equipment – materials
• Air-handling equipment – installation
• Electrical switchgear – materials
• Electrical switchgear – installation

This structure can make the movement from stored to installed value easier to audit. It can also help prevent the classic mistake of leaving material dollars in the stored-material column after those same materials are included in installed work.

Do not add the split solely because it looks more sophisticated. Use it when it creates meaningful progress visibility or aligns with the payer’s billing requirements.

Planning for Change Orders

Build the SOV expecting that approved changes may occur.

That does not mean inflating the original contract or entering speculative change value. It means leaving your spreadsheet, accounting structure, or billing system capable of adding uniquely identifiable change-order lines without rewriting the original scope.

A useful design might contain:

• base contract section;
• approved change-order section;
• unique CO identifier;
• approval date;
• approved amount; and
• billing status.

Pending changes should remain separately tracked until the applicable contract procedure permits them to affect the payment application.

How G703 Pay Application Math Works

The G703 is where most of the detailed payment arithmetic lives. The exact form should be completed using the licensed document and applicable instructions, but conceptually the continuation sheet tracks each SOV line from its scheduled value through prior and current activity.

AIA describes G703 as tracking scheduled portions of the work, work completed, stored materials, cumulative progress, and retainage. Its instructions also contemplate separately listing change orders.

The basic progression is:

Scheduled value → prior billing → current work → stored materials → cumulative completed/stored → percentage progress → remaining value → retainage

Each line then contributes to totals that flow into the G702 summary.

Previous Applications

Previous applications are not a fresh estimate every month.

If last month’s approved or otherwise contractually established cumulative billing for an SOV line was $40,000, that historical value should become the appropriate prior-period amount in the next application. It should not be manually re-created from memory.

The same principle applies at the total level. Period 6 must start from Period 5’s accepted billing history, subject to a documented revision or adjustment process when corrections are necessary.

This is one of the most common G703 continuation sheet errors in spreadsheets. Someone opens the prior workbook, adjusts a formula, inserts a new row, copies the wrong range, or “fixes” an old number to make the current total look right. Now the prior column in the current application no longer matches the last submitted package.

Reviewers frequently compare applications from period to period precisely because the documents are cumulative.

The safest control is to derive prior values directly from the locked previous application rather than re-entering them.

This-Period Work

Current-period work is the incremental amount earned during the current billing period.

It is not the cumulative value.

Consider this illustrative example:

• Scheduled value: $100,000
• Previously billed work: $40,000
• Work completed this period: $20,000
• Cumulative work before any stored materials: $60,000

The current-work entry is $20,000—not $60,000.

Scheduled Value	Prior Work	Current Work	Stored Materials	Total Completed/Stored	Balance Before Separate Retainage Treatment
$100,000	$40,000	$20,000	$0	$60,000	$40,000

This seems elementary until the project has 150 SOV lines, three revised submissions, separate stored-material activity, and 12 months of history.

Current-period input should therefore be limited to the new production since the previous accepted billing cutoff.

Stored Materials Billing

Stored materials billing G702 workflows require particular care because physical material can move between billing classifications without increasing cumulative earned value.

Projects may permit billing for materials stored at the site. Some contracts may also permit off-site stored materials when specified conditions are satisfied. AIA guidance notes that off-site stored-material arrangements should be addressed specifically and that transportation and insurance considerations may be relevant.

Do not assume an off-site purchase is automatically billable because the supplier issued an invoice.

Depending on the contract and payer, supporting evidence may include:

• supplier invoices;
• delivery tickets;
• photographs;
• serial numbers or equipment identification;
• evidence of ownership or title;
• insurance documentation;
• warehouse or storage-location confirmation;
• proof the materials are segregated for the project; or
• other contractually required support.

Suppose $20,000 of equipment was approved as stored in Period 3. In Period 4, $15,000 of that equipment is installed.

The contractor should not add $15,000 of installed value while leaving the full $20,000 classified as stored. Instead, the value moves from stored status into installed-work status. The cumulative total should increase only for genuinely new earned value.

Conceptually:

Period 3: Installed $40,000 + stored $20,000 = cumulative $60,000.

Period 4: $15,000 of previously stored equipment gets installed. If no additional work or new stored material occurs, cumulative earned value remains $60,000; only its classification changes.

That reclassification is one of the most important controls in stored-material billing.

Percent Complete and Balance to Finish

For a normal SOV line, percentage complete should be derived from dollars instead of being independently typed whenever the billing system allows.

Conceptually:

Percent complete = total completed and stored to date ÷ scheduled value

If the scheduled value is $100,000 and cumulative completed-and-stored value is $60,000:

$60,000 ÷ $100,000 = 60%

Typing both the dollar amount and the percentage independently creates two opportunities for the same information to disagree.

Likewise, the remaining scheduled value before considering how the specific form presents retainage can be understood conceptually as:

Scheduled value − cumulative completed and stored value

In the example:

$100,000 − $60,000 = $40,000 remaining

When working in the actual licensed G703, follow its structure and project instructions rather than replacing its prescribed calculations with a homemade interpretation.

How Pay Application Retainage Is Calculated

Retainage is an amount withheld from otherwise earned progress under the terms of the applicable contract and law.

There is no universal retainage percentage that belongs in every pay application retainage calculation. AIA’s construction-payment guidance states that the agreement should specify the retainage arrangement and release conditions, and applicable state law may impose additional restrictions.

That means the billing administrator needs to answer four questions before creating formulas:

1. What amount is subject to retainage?
2. What rate applies?
3. Does the same rate apply to completed work and stored materials?
4. Has any reduction or release been authorized?

Do not hard-code “10%” into a template simply because a previous project used that percentage.

Retainage on Labor, Work, and Stored Materials

Some contracts apply the same rate to all applicable earned values. Others distinguish between completed work and stored materials. Some may exclude particular components or use line-specific treatment.

AIA’s payment-application guidance expressly distinguishes fixed retainage and variable retainage concepts, and its instructions recognize that completed work and stored materials may need separate handling.

Consider this hypothetical example only:

Billing Component	Amount	Hypothetical Retainage Rate	Retainage
Completed work	$80,000	10%	$8,000
Stored materials	$20,000	5%	$1,000
Total	$100,000	—	$9,000

The spreadsheet must calculate those components separately. Applying one 10% formula to the entire $100,000 would produce $10,000 of retainage and overstate the hypothetical withholding by $1,000.

The point is not that 10% and 5% are standard. They are not. The example shows why the formula must mirror the contract.

Retainage Reduction and Release

Retainage can also change during a project.

Depending on the contract and applicable law, reductions or releases may be associated with substantial completion, completion of a phase, final completion, punch-list status, or another defined milestone. Partial release may also be specifically authorized before final payment. 

AIA publishes documentation intended for circumstances involving partial retainage release where a surety is involved, further demonstrating that retainage treatment can change during a project rather than remaining mechanically fixed.

When a reduction is authorized, the change must be reflected consistently.

Do not reduce retainage on the G702 while leaving detailed G703 retainage unchanged. Do not alter prior-period earned work to create the release. Instead, maintain the historical billing and process the authorized retainage change through the project’s established method.

How Change Orders Enter the Schedule of Values

Approved changes need to affect the contract value without destroying the historical SOV.

AIA’s current G703 instructions state that change orders are commonly listed separately, such as at the end of the basic schedule or on a separate continuation sheet, and that the adjusted contract amount is reflected in the corresponding payment application.

The operational rule is simple: add history; do not rewrite history.

Suppose the original contract is $500,000 and an approved $25,000 change adds new electrical work.

A traceable SOV might look like this:

ID	Description	Status	Approved Amount	Historical Treatment
Base-01	Original electrical scope	Original contract	$500,000	Preserve original value
CO-003	Added panel and feeders	Approved	$25,000	Add separate SOV line
Revised contract	—	—	$525,000	Original plus approved change

The project record should preserve the change-order number, approval date, approved value, and supporting authorization.

Pending or disputed changes require more care. Do not automatically increase the contract sum merely because field work occurred. Follow the specific contract’s change procedure. AIA’s own instructions distinguish formal change-order treatment from other properly authorized change mechanisms under its contract families.

Construction accounting may still need to track costs associated with pending changes internally. That is different from treating an unapproved amount as an approved contract increase on the pay application.

That distinction should also exist in the contractor’s project-management system. When evaluating construction management software, look for separate statuses for potential changes, submitted changes, approved change orders, and rejected changes so only properly authorized amounts flow into billing.

Deductive Change Orders

A deductive change reduces contract value.

That does not mean the correct solution is to create impossible negative percentages or erase previously earned work.

The system needs to identify:

• what scope was removed;
• the approved deduction;
• whether any portion of that scope was previously completed or billed;
• how the approved change modifies the remaining SOV; and
• how the revised contract amount reconciles.

If a deduction affects work that has already been billed, obtain direction under the project’s billing procedure rather than improvising a retroactive edit.

Historical applications need to remain traceable even when the contract changes later.

G703 Continuation Sheet Errors That Get Draws Rejected

Most G703 continuation sheet errors are not sophisticated accounting failures. They are continuity failures.

A spreadsheet’s greatest weakness is that a user can often modify anything.

A formula can be replaced with a typed dollar amount. A new SOV line can be inserted outside the total range. A row copied from another section may still point to the wrong cells. A prior-period column can be manually “corrected.” One worksheet can round at the line level while another rounds only at the total level.

The result may look reasonable while being internally inconsistent.

Error	What It Breaks	Prevention
G703 total differs from G702	Summary no longer agrees with supporting detail	Automated tie-out control
Prior-period values changed	Period-to-period audit trail	Lock imported historical values
SOV total differs from current contract	Billing base is wrong	Contract-value validation
Approved CO missing	Revised contract and SOV disagree	Approved-CO reconciliation
Pending CO treated as approved	Contract value may be overstated	Approval-status control
Stored material unsupported	Reviewer cannot validate eligibility	Required backup checklist
Stored material billed twice	Cumulative earned value overstated	Stored-to-installed reclassification
Retainage rate applied to wrong base	Net payment request is wrong	Contract-driven formula
Percentage exceeds 100%	Line appears overbilled	Maximum-value validation
Balance becomes negative	Scheduled value has been exceeded	Overbilling warning
Formula row omitted from total	Pay-app totals drift	Protected structured ranges
Signature/notary requirement missed	Package may be administratively incomplete	Project-specific checklist
Required waiver or backup missing	Payment conditions incomplete	Attachment gate before submission

Rounding Drift

Rounding can produce apparently mysterious differences between G703 detail and the G702 summary.

Suppose dozens of individual line calculations produce fractional cents or percentages. If the spreadsheet rounds each intermediate calculation differently from the summary formula, the total may be off by several cents or dollars.

A disciplined approach is to:

• calculate using sufficient internal precision;
• display monetary values consistently;
• avoid manually typing rounded percentages that independently drive dollars; and
• perform a final reconciliation against the summary.

Do not hide a mismatch by randomly adding a dollar to an unrelated line.

Percent Complete Above 100%

A line above 100% generally requires investigation.

Common causes include:

• duplicate stored-material billing;
• current work added on top of a cumulative value;
• scheduled value entered incorrectly;
• an approved change not yet added to the SOV;
• a copied formula pointing to the wrong row; or
• manual edits to historical columns.

The proper fix is to find the source, not cap the displayed percentage at 100% while leaving excess dollars in place.

Negative Balance to Finish

Likewise, a negative remaining value is typically an exception worth investigating.

Possible causes include:

• overbilling;
• duplicate billing;
• missing approved change value;
• incorrect scheduled value;
• a deductive change handled incorrectly; or
• formula/reference failure.

An automated validation rule should flag the condition before submission.

Missing Signatures, Notarization, Lien Waivers, and Backup

A mathematically perfect pay application can still be returned if the required package is incomplete.

The contract and project instructions determine what must accompany the payment request.

AIA’s construction-administration guidance notes that applications may need supporting information requested by the owner or architect, including documentation such as requisitions and releases or waivers. It also recognizes that notarization may be required depending on the applicable project documents rather than presenting it as universal.

Therefore, do not assume every G702 requires notarization.

Likewise, do not assume every progress payment requires the same lien-waiver package. Depending on the project and jurisdiction, requirements may involve conditional waivers, previous-payment waivers, lower-tier waivers, affidavits, or other evidence.

When waivers are part of the payment package, a documented lien waiver collection workflow can help accounting confirm that the correct current- or prior-period waivers have been collected before the pay application is released.

Possible supporting documents, when required, can include:

• supplier invoices;
• stored-material schedules;
• delivery tickets;
• photographs;
• warehouse confirmation;
• approved change-order documentation;
• lien waivers;
• lower-tier waivers;
• certified payroll records on applicable projects;
• insurance documents;
• project-specific affidavits; and
• other supporting records specified by the payer.

The key control is not to attach every conceivable construction document. It is to maintain a project-specific package list.

Pay Application Submission Package

Document	Required If Applicable?	Who Verifies It
G702 or required summary form	Per project requirements	Project accounting
G703/SOV support	Per project requirements	PM + accounting
Approved change-order backup	When changes are billed	PM
Stored-material support	When stored materials are billed and support is required	PM/accounting
Lien waivers	When contract/project/law requires	Accounting/compliance
Certified payroll	On projects requiring it	Payroll/compliance
Insurance documentation	When required with draw	Risk/admin
Signature	Per form/project procedure	Authorized signer
Notarization	When required	Authorized signer/admin
Portal/email confirmation	After submission	Billing administrator

How the G703 Must Tie to the G702

The G703 is not an independent spreadsheet that happens to accompany the G702.

Its totals support the summary application.

Contractors who want to see the two documents handled as a coordinated workflow can also review AIA’s guidance on completing G702 and G703 payment applications.

AIA describes the coordinated documents as showing the status of the contract amount through completed and stored work, retainage, previous payments, change-order adjustments, and the current amount requested.

Before submission, run a deliberate tie-out:

1. Original contract amount: matches executed contract.
2. Approved change adjustments: match the current approved change-order log.
3. Current contract amount: original amount plus/minus applicable approved changes.
4. SOV total: equals the appropriate current contract amount.
5. Completed-and-stored detail: G703 aggregate agrees with the corresponding G702 summary amount.
6. Retainage: detailed or calculated retainage agrees with the summary.
7. Prior payments/applications: agree with established prior history.
8. Current amount due/requested: mathematically follows from the cumulative position.
9. Application number and period: agree across the package.
10. Project identifiers: agree across forms and backup.

Do not perform this by looking at the documents and thinking they “seem close.”

Create explicit control cells such as:

SOV total − current contract sum = $0

G703 completed/stored total − G702 completed/stored summary = $0

G703 retainage − G702 retainage = $0

A nonzero result should prevent submission.

Progress Payment Application Construction Workflow

A disciplined progress payment application construction process reduces both mathematical errors and last-minute document chasing.

The monthly workflow should begin before the deadline.

1. Lock the current contract value

Start with the last approved contract amount and current approved change-order log. Resolve discrepancies before updating production.

2. Import approved changes

Add only changes eligible for billing under the project’s contract procedure. Preserve unique identifiers and approval dates.

3. Carry forward the prior application

Import prior-period values from the exact accepted or controlled prior version. Do not retype them.

4. Establish the billing cutoff

Project management and accounting should agree on the cutoff date. Field teams need to know what production is included and what belongs in the next period.

5. Verify field progress

The PM, superintendent, or responsible field personnel should confirm the quantity or percentage of work actually in place as of the cutoff.

6. Enter current-period work

Enter incremental activity only.

7. Update stored materials

Add eligible new stored materials, move installed material out of stored classification, and attach required support.

8. Calculate cumulative progress

Let the system derive cumulative completed-and-stored value.

9. Calculate retainage

Apply the contractually applicable rate or rates and any authorized reductions.

10. Verify remaining value

Investigate any negative balance or line exceeding its scheduled value.

11. Tie G703 to G702

Run explicit zero-difference controls.

12. Assemble supporting documents

Collect CO backup, waivers, material records, payroll or insurance documents, and other required evidence.

13. Execute the package

Obtain required internal approval, signatures, certifications, or notarization as applicable.

14. Submit through the required channel

Use the designated portal, email, document system, or other project process.

15. Archive the exact submission

Save the actual PDF, attachments, transmittal, submission timestamp, and spreadsheet/system version.

16. Lock the period

Once established as the historical basis for the next application, prior-period values should become read-only except through a controlled correction workflow.

Billing Cutoff, Review Adjustments, and Revisions

One source of pay-app confusion is allowing field progress to change continuously while accounting is trying to close the billing package.

Establish a billing cutoff.

For example, if the formal application is due late in the month, the project may establish an earlier internal field-verification deadline. The exact dates depend on the project. The important point is that PMs, superintendents, subcontractors, and accounting work from the same cutoff.

A reviewer may later reduce an amount.

An architect may determine that a line’s reported progress is unsupported, a payer may disallow stored materials, or the parties may agree that the current request needs revision.

Do not respond by silently modifying historical data.

Use a revision workflow:

• Pay App 08 – Original;
• Pay App 08 – Revision 1;
• revision date;
• reason for change;
• reviewer comments;
• changed current-period amounts;
• approval/rejection status; and
• final submitted version.

If a prior application itself needs formal correction, preserve both the original and the corrected record and follow the project’s agreed procedure.

Never overwrite the only copy of a submitted workbook.

How Construction Billing Software Carries Prior Periods Forward

The strongest reason to move from ad hoc spreadsheets to dedicated construction billing software is not that software “does math.”

Excel also does math.

The advantage is controlled continuity.

A properly configured construction billing system can retain SOV line identities and carry a prior application’s cumulative values into the next billing period automatically. AIA’s own current Catina workflow, for example, allows users creating a subsequent payment application to start from a previous pay app, illustrating the value of structured carryforward.

A well-designed system should be able to:

• lock established prior-period billing;
• preserve SOV line IDs;
• carry forward cumulative amounts;
• incorporate approved change orders;
• update the contract amount;
• calculate current and cumulative billing;
• calculate retainage under configured rules;
• track stored-material movement;
• identify required attachments;
• maintain revision history; and
• validate summary/detail reconciliation.

This does not eliminate reviewer judgment. Software cannot decide whether work actually exists in the field or whether a particular stored-material request complies with the contract.

It can, however, eliminate many ways a spreadsheet creates unnecessary inconsistency.

Billing controls should also be considered when choosing construction management software. A system that handles field reporting well but cannot preserve SOV history, approved change orders, stored-material detail, or billing revisions may still leave accounting dependent on manual spreadsheets. 

Automated Retainage and Change Orders

Retainage automation should reflect the project’s actual rules.

Depending on the platform, useful capabilities may include:

• global retainage rate;
• line-specific rate;
• separate work/material treatment;
• variable retainage;
• authorized reduction;
• partial release; and
• historical retainage reporting.

Do not assume every billing platform supports every configuration.

Change-order integration should similarly preserve:

• CO number;
• description;
• approval status;
• approval date;
• approved amount;
• associated SOV line;
• amount billed to date; and
• remaining change value.

An approved CO should update contract value through a traceable event—not by changing the original contract number in an unlabeled spreadsheet cell.

Stored Materials Tracking

Software can substantially improve stored-material control when it tracks both the asset and its movement.

Useful fields include:

• material package;
• SOV line;
• supplier;
• invoice amount;
• storage location;
• documentation;
• amount previously stored;
• new amount stored;
• amount installed this period;
• remaining stored balance; and
• cumulative earned value.

This creates a ledger-like trail from purchase to storage to installation.

A simple spreadsheet often contains only one “stored materials” column, making it difficult to determine whether this month’s number is new material, total stored material, or remaining stored material.

Validation and Historical Locks

Useful automated validation rules include:

• SOV total equals current contract amount;
• cumulative line billing does not exceed scheduled value;
• percentage complete does not exceed 100% under normal line structures;
• negative remaining values are flagged;
• G703 supporting totals agree with the G702 summary;
• retainage calculations reconcile;
• approved changes agree with contract adjustment totals;
• pending changes are not treated as approved;
• required attachments are present; and
• prior-period locked values have not changed.

Historical locking may be the single most valuable control.

After a pay application becomes the established basis for the next period, the system should restrict ordinary users from editing those historical amounts. If a correction is necessary, authorized personnel should use a controlled revision or adjustment that leaves an audit trail.

Spreadsheet vs. Construction Billing Software

Software is not automatically better in every situation.

A small contractor running one or two straightforward projects may maintain accurate pay applications in a controlled spreadsheet. A poorly configured billing platform can create different problems.

The relevant comparison is control.

Task	Spreadsheet Risk	Construction Billing Software Control
Prior-period carryforward	Manual or formula-dependent	Automated or structured
Change orders	Rows and totals manually updated	Approval-linked CO structure
Retainage	Formula-dependent	Configured rules where supported
Stored materials	Easy to double-count	Structured movement tracking
Historical values	Can be overwritten	Read-only/permission controls
Audit trail	Weak unless intentionally maintained	Typically stronger
G702/G703 reconciliation	Manual check	Automated validation
Revision management	File-name dependent	Version/revision workflow
Attachments	Separate folders/email	Can be connected to pay app
Approval workflow	Email/manual	Role-based routing where supported

The goal is not to eliminate human review. It is to remove unnecessary opportunities for arithmetic and version-control mistakes.

The same principle applies beyond the pay application itself. Construction workflow automation can connect PM review, accounting approval, supporting-document collection, executive certification, and final submission without relying on disconnected email threads and duplicate files.

Spreadsheet Controls for Contractors Who Still Use Excel

Excel can still work if the workbook is treated like a controlled billing application rather than an open scratchpad.

Start by separating inputs from formulas.

Users should be allowed to update current work, applicable stored-material inputs, authorized retainage settings, and approved changes without being able to overwrite cumulative formulas or prior-period history.

Recommended controls include:

• protect formula cells;
• visually distinguish input cells;
• lock prior-period columns;
• restrict SOV-value changes after approval;
• maintain a separate approved-CO table;
• use structured references or controlled table ranges;
• add data validation to status fields;
• build zero-difference reconciliation cells;
• flag percentage above 100%;
• flag negative remaining amounts;
• flag SOV/contract mismatch;
• reconcile stored material from prior to current period;
• save each submission as a new monthly version;
• export an immutable PDF of the actual submission; and
• never overwrite the final prior-period workbook.

Use descriptive filenames, such as:

Project-123_PayApp-07_Submitted_2026-08-25.xlsx

If a revision is required:

Project-123_PayApp-07_Rev1_2026-08-28.xlsx

Avoid filenames such as:

Final.xlsx

Final2.xlsx

FinalLatest_USETHIS.xlsx

Those names eventually produce exactly the historical confusion a cumulative payment process cannot tolerate.

Common AIA Pay Application Mistakes

Several mistakes recur because they cross multiple parts of the package.

Common Schedule-of-Values Mistakes

Watch for:

• lines too broad to verify progress;
• lines so granular that monthly updating becomes impractical;
• unsupported front-loading;
• no meaningful closeout allocation;
• no structure for change orders;
• inconsistent labor/material separation; and
• an SOV that no longer equals the current contract amount.

Common Retainage Mistakes

Typical problems include:

• applying retainage to the wrong base;
• assuming a default percentage instead of checking the contract;
• using one rate when separate rates apply;
• omitting required retainage on a component;
• continuing old retainage after an authorized reduction;
• releasing retainage before authorization; and
• changing detailed retainage without making the corresponding summary adjustment.

Common Change-Order Mistakes

Watch for:

• billing a pending CO as though approved;
• changing original SOV values instead of creating traceable CO entries;
• failing to add an approved deductive change;
• deleting an old CO line;
• using a revised contract value that does not equal the documented change log; and
• updating G702 while leaving G703 unchanged.

Common Stored-Material Mistakes

Frequent errors include:

• billing unsupported off-site materials;
• lacking required evidence of ownership or storage;
• billing the same material as both stored and installed;
• leaving previously installed materials classified as stored;
• failing to reduce the remaining stored balance; and
• billing material before the contract’s eligibility conditions have been satisfied.

Common Documentation Mistakes

Administrative errors include:

• wrong billing period;
• incorrect application number;
• wrong project number;
• unsigned package where signature is required;
• missing notarization where required;
• stale or mismatched waiver;
• missing stored-material backup;
• missing CO authorization;
• incomplete supporting invoice package; and
• a portal submission that differs from the internally approved PDF.

AIA G702/G703 Pay Application Checklist

Use this checklist against the contract and project billing instructions before every submission.

1. Review the project’s billing requirements.
2. Confirm the original contract amount.
3. Confirm approved additions and deductions.
4. Import only changes eligible for the current application.
5. Verify the revised contract amount.
6. Verify the schedule-of-values total.
7. Carry forward the previous application’s established values exactly.
8. Lock prior-period amounts.
9. Enter only current-period work.
10. Enter eligible stored materials separately.
11. Reclassify previously stored materials when installed.
12. Check for duplicate stored-material billing.
13. Verify cumulative completed-and-stored amounts.
14. Calculate percentage complete from dollars where practical.
15. Confirm no ordinary SOV line exceeds its scheduled value.
16. Investigate any negative balance.
17. Apply the contract’s retainage rules.
18. Apply separate work/material rates where required.
19. Record authorized retainage reductions or releases consistently.
20. Tie G703 totals to G702.
21. Verify the approved change-order summary.
22. Check application number and billing period.
23. Check project identifiers.
24. Attach stored-material documentation where required.
25. Attach approved change-order backup.
26. Attach lien waivers where required.
27. Attach payroll, insurance, or other project-required documentation where applicable.
28. Obtain required signatures.
29. Confirm whether notarization is required.
30. Submit through the required portal, email, or other channel.
31. Save evidence of submission.
32. Archive the exact submitted package.
33. Preserve revisions separately.
34. Lock the completed period before starting the next application.

Frequently Asked Questions

Conclusion

A reliable AIA G702 G703 pay application is built on continuity.

The schedule of values establishes the structure that every later application must follow. Prior-period values should carry forward without unexplained changes. Current work must represent incremental production. Stored materials need separate tracking so value moves from stored to installed rather than being billed twice.

Retainage must follow the applicable contract and law rather than a default percentage. Approved change orders should increase or decrease the contract through traceable entries without rewriting historical billing. 

Before submission, the G703 detail must reconcile to the G702 summary, and the package must include whatever signatures, waivers, stored-material evidence, change documentation, or other support the project requires.

Spreadsheets can handle this process when their formulas, history, and versions are tightly controlled. Construction billing software can strengthen that control by automatically carrying periods forward, locking historical values, incorporating approved changes, tracking stored materials, applying configured retainage rules, and running validation checks.

The goal is not merely to produce a pay app that looks complete. It is to create a billing record whose numbers can be traced from contract value to SOV, current progress, cumulative billing, retainage, and the amount requested—month after month.