Pay Application vs Invoice: What Is the Difference in Construction?
What is the difference between a pay application and an invoice in construction? An invoice says "you owe me this much for this work." A pay application says the same thing, then backs it up: it proves what got built, reconciles every dollar against the contract, holds back retainage, accounts for change orders, and gets certified before anyone cuts a check. If you are a sub on a commercial job and the GC tells you to "get your pay app in by the 25th," they are not asking for an invoice. They are asking for the whole package.
The pay app exists because construction pays for progress. On a job that runs six months, nobody can invoice the whole contract up front, and nobody wants to argue about percent complete every month from scratch. The pay application standardizes the argument. It carries the billing period and application number, the original contract sum, the net change from approved change orders, the contract sum to date, the total completed and stored to date, the retainage deduction, the total earned less retainage, the previous payments, and the current payment due. Nine fields on the AIA G702, each one checkable against the last month's application.
What the G702 and G703 actually do
The AIA forms are the industry's version of this, published by the American Institute of Architects. The G702 is the Application and Certificate for Payment: the summary page. It shows the contract value, the approved change orders, the completed work, the retainage, the previous payments, and the current amount due. It also carries the contractor's certification and the architect's signature, which is what turns a request into an entitlement.
The G703 is the Continuation Sheet, and it is where the real work happens. It breaks the project into schedule-of-values line items, concrete, electrical, roofing, HVAC, and shows how much of each is complete and billed. The G703 totals feed directly into the G702's completed-work line. Reviewers use the G702 to confirm the overall request and the G703 to verify progress item by item. The two forms are mathematically linked, which means one wrong line on the G703 invalidates the whole summary. Ask anyone who has had a pay app kicked back over a broken spreadsheet formula.
That kickback moment is the emotional core of pay-app life. You submit on the 25th, the architect redlines your percent complete on three line items, and your payment slides a month. The pencil-copy review exists precisely for this: a draft round where the numbers get negotiated before anything is certified. The contractors who get paid on time treat the pencil copy as the real deadline.
When you need a pay app and when an invoice is enough
You need a pay application when the contract uses progress billing, when the project runs over several months, when payment happens on a fixed cycle, or when the contract names AIA forms. That covers most commercial and public work. The monthly rhythm is standard, though some contracts bill by milestone instead.
A plain invoice is enough for smaller, simpler jobs: a residential remodel billed at completion, time-and-materials work, a supplier delivering materials. No retainage, no schedule of values, no certification chain. Just the work, the amount, and the terms.
And sometimes you need both. Several firms create a separate invoice in their accounting system after the G702 is reviewed and certified, because their ERP wants an invoice-shaped object and the owner wanted a pay app. Neither document is wrong. They serve different audiences: the pay app convinces the project team, the invoice feeds the books.
The one thing to keep
Invoice means request. Pay application means request plus proof, reconciliation, and certification. If your contract mentions AIA G702/G703, retainage, or a schedule of values, you are in pay-app territory. Build the G703 first, let it feed the G702, and treat the pencil-copy review as the real deadline.
The move that saves the most pain is embarrassingly simple: reconcile your G703 line items against your schedule's percent complete before you submit, not after the architect redlines it. A pay app that matches the field story sails through certification. One that contradicts the schedule gets questioned on every line, and questioned pay apps get paid late.
Frequently asked questions
Is a pay application the same as an invoice?
No. An invoice requests payment with line items and terms. A pay application is a formal construction billing package that proves completed work, reconciles it against the contract sum, deducts retainage, accounts for change orders, and gets certified by the architect or owner before payment.
What is the difference between AIA G702 and G703?
The G702 is the Application and Certificate for Payment, a summary showing contract sum, change orders, completed work, retainage, previous payments, and current amount due. The G703 is the Continuation Sheet with the line-by-line schedule of values breakdown. The G703 totals feed into the G702.
How often are pay applications submitted?
Typically monthly. The construction contract defines the billing cycle and the due date, for example the 25th of each month. Some contracts use milestone-based schedules instead.
Do I still need an invoice if I submit a pay application?
Sometimes. Some companies create a separate invoice in their accounting system after the G702 pay application is reviewed and certified. Whether you need both depends on the contract and your accounting process.
What is retainage on a pay application?
Retainage is a percentage of completed work, typically 5 to 10 percent, that the owner holds back until the project reaches substantial completion or final acceptance. It appears as a deduction on the pay app and is released later.
Related reading: What Is a Contractor Progress Invoice? Billing as the Work Gets Done · What Is a Schedule of Values in Construction? · What Is Retainage on a Contractor Invoice? · How to Invoice for Change Orders Without Starting a Fight