Progress Billing vs Pay Application
Progress billing is the overall billing method: getting paid in stages as work is completed. A pay application is the formal request for payment used for one of those billing periods.
In plain English: progress billing is the process, and the pay app is the package. On many projects, the pay application is how progress billing actually gets reviewed and approved.
These terms get mixed together all the time. That makes sense, because they overlap a lot. But if you treat them like the exact same thing, you can end up with accounting that does not match what the reviewer approved.
Why people confuse these two terms
In construction, the same monthly billing event often gets described three different ways:
- “We’re doing progress billing on this job.”
- “We need to submit the pay application by Friday.”
- “Accounting needs the invoice after approval.”
All three may be talking about the same billing cycle, but each one points to a different part of the workflow.
Progress Billing vs Pay Application at a Glance
Same job, same month, different meaning.
| Topic | Progress Billing | Pay Application |
|---|---|---|
| What it is | A billing method based on work completed over time | A formal request for payment for one billing period |
| Main purpose | Bill gradually instead of all at once | Show what was earned, what is due, and why |
| Typical format | Can be simple or complex | Usually includes summary + detail + backup |
| Who uses the term most | Accounting, PMs, contractors, software vendors | GCs, owners, architects, lenders, accounting reviewers |
| Needs prior-period rollforward | Usually yes | Almost always yes |
| Includes backup docs | Not necessarily | Often yes — waivers, stored materials, CO support |
| Example on many projects | Monthly billing by percent complete | AIA-style G702/G703 pay app package |
What progress billing means
Progress billing means you do not wait until the entire job is complete to bill. Instead, you bill as work is completed over time.
On a small job, that might be as simple as billing by milestone. On a larger commercial project, it often means billing against a Schedule of Values (SOV) with previous, current, and to-date values.
For the broader plain-English overview, see Construction Progress Billing.
- Billing by month, milestone, or percent complete
- Tracking previous, current, and to-date amounts
- Handling retainage consistently
- Updating for approved change orders
- Reconciling what was billed vs what was approved
What a pay application means
A pay application is the actual package submitted for review and payment. It is not just a number. It is the documentation behind the number.
On many projects, the package includes:
- A summary page showing the amount due
- Line-item detail tied to the SOV
- Retainage treatment
- Stored materials support
- Change order support
- Lien waivers or other required attachments
For the broader overview, see Construction Payment Application Guide.
- More formal than a standard invoice
- Built for reviewer approval, not just AR
- Dependent on prior-period consistency
- More likely to get kicked back if the math drifts
Where the invoice fits in
This is where many teams get tripped up. A standard invoice is not always the same thing as the pay application package.
In many real-world workflows:
- The team prepares the pay application package
- The GC, owner, architect, or lender reviews it
- The approved amount becomes the accounting amount
- Then the invoice is created or updated in accounting
Where AIA-style billing fits into this
AIA-style G702/G703 workflows are one common way to execute progress billing through a pay application package. They are not the only way, but they are widely recognized because they separate the process into:
- A summary page for the amount due
- A continuation sheet for the line-item detail
If your project uses that structure, start with: AIA G702/G703 Billing Guide, G702 hub, and G703 hub.
How QuickBooks Online fits into this comparison
QuickBooks Online is usually the accounting system, not the reviewer-facing pay app package. That distinction matters because progress billing and pay applications often split into two workflows:
- Reviewer workflow: pay app package gets submitted and approved
- Accounting workflow: approved totals get recorded in QBO
When people say “QuickBooks does progress billing,” they may really mean “QuickBooks handles the accounting side.” That is different from generating a reviewer-ready pay application package.
Common mistake: treating them like the same thing
When teams blur progress billing and pay applications together, they usually run into one of these problems:
- The invoice is created before the pay app is reviewed, so accounting does not match approval
- The pay app package does not have the backup the reviewer expects
- The summary total makes sense, but the line-item detail does not
- Retainage is handled one way in accounting and another way in the pay app
- Change orders appear in one place and disappear in another
How PayAppPro fits
PayAppPro helps with the pay application side of progress billing — the part reviewers actually have to approve.
SOV-driven billing
Build your Schedule of Values once and carry it forward across billing periods.
Reviewer-ready package
Keep summary, detail, retainage, and backup aligned so the package is easier to approve.
Cleaner accounting handoff
Mirror approved totals into accounting after review instead of fighting spreadsheet drift.
FAQ: Progress Billing vs Pay Application
Short answers to the terms people mix together most often.