A construction payment application, or "pay app," is a formal, packaged request for a progress payment that documents work completed, materials stored, and all supporting proof. It is not a simple invoice. On most US commercial projects, a pay app is the only mechanism that triggers payment under the contract, which means a sloppy submission doesn't just delay your check — it can void your right to collect on time under state prompt-payment law.
Every pay app that clears review without a hold contains the same core documents:
- Schedule of Values (SOV): The line-item breakdown of the contract, showing each scope item and its value
- Pay application form: AIA G702/G703, ConsensusDocs 710, or a contract-specified equivalent
- Continuation sheet: The line-by-line progress update tied to the SOV
- Approved change orders: Any additions or deductions formally authorized since the last billing
- Backup documents: Vendor invoices, delivery tickets, certified payroll (if required), and photos
- Lien waivers: Conditional waivers for the current payment; unconditional waivers for prior payments
- Retainage calculation: The withheld percentage shown clearly on the face of the application
Pro Tip: The single most common reason a pay app gets held is not a math error — it's a missing or misdated signature. Before you hit send, confirm that every signature block is filled, every date matches the billing period, and the SOV totals reconcile exactly to the continuation sheet.
Key Takeaways
A complete, correctly submitted payment application is the single most reliable lever for protecting cash flow and lien rights on a US construction project.
| Point | Details |
|---|---|
| Use the contract-specified form | Check whether the contract mandates AIA G702/G703, ConsensusDocs 710, or a custom form before the first billing. |
| Keep the SOV current and reconciled | Update the SOV for every approved change order and confirm it matches the continuation sheet before each submission. |
| Collect waivers before you submit | Gather lower-tier conditional waivers during the billing period, not the morning the application is due. |
| Submit on the cut-off date | Late submission can forfeit prompt-payment protections; confirm the contractual billing date at project start. |
| Mbqs provides end-to-end pay-app support | From SOV setup to disputed-payment resolution, Mbqs's claims and contract administration service covers the full billing cycle. |
Table of Contents
- What is a payment application in construction, and when do you need one?
- Which pay application forms do US contractors actually use?
- What every complete pay application must include
- How to build a pay application step by step
- How the submission and approval workflow actually runs
- Common mistakes that get pay applications rejected
- Where to get pay app forms and how to use templates effectively
- Software and digital tools that reduce pay-app errors
- Legal and contract considerations that affect every pay app
- How Mbqs approaches pay-app preparation and quality assurance
- Why disciplined pay-app practice is a commercial decision, not just an admin task
- Mbqs can handle your pay-app process from SOV setup to dispute support
- Sources
What is a payment application in construction, and when do you need one?
A pay app is fundamentally different from a standard invoice. An invoice says "here is what I am owed." A payment application says "here is what I am owed, here is the proof, and here is how it was calculated against the contract we both signed." That distinction matters in practice because most construction contracts — particularly those using AIA, ConsensusDocs, or any lender-backed form — require the packaged format as a condition of payment, not just a courtesy.
Pay apps are required in most of these situations:
- Monthly progress billing on projects with a draw schedule (the most common scenario)
- Milestone billing when the contract ties payment to defined completion events
- Stored materials claims when materials are on-site or off-site but not yet installed
- Final application for payment at project closeout, which typically requires additional closeout documentation
On a typical US project, the routing goes: subcontractor submits to the general contractor, the GC consolidates and submits to the owner, and the owner's architect or engineer reviews and issues a Certificate for Payment. On lender-financed projects, the lender's inspector adds another layer before funds are released.
Short-term glossary worth keeping handy:
- Schedule of Values (SOV): The line-item budget breakdown agreed at contract start; every pay app draws against it
- Continuation sheet: The running ledger (AIA G703 is the standard form) that shows percent complete and dollar amounts for each SOV line
- Retainage: The percentage withheld from each progress payment (typically 5–10%) until substantial completion
- Conditional lien waiver: Waives lien rights only if and when payment is actually received
- Unconditional lien waiver: Waives lien rights regardless of whether payment arrives — never sign one before the check clears
Construction cash flow is one of the tightest constraints in the industry. Delayed pay apps compound quickly: a single billing cycle missed or rejected can push a subcontractor's receivables out 60–90 days past the work completion date.
Which pay application forms do US contractors actually use?
The form you use is usually dictated by the contract. When the contract attaches a specific form, use it exactly — procedural rejection for using the wrong template is a real and avoidable problem. When the contract is silent, a styled template that contains all required fields is generally acceptable.
AIA G702/G703
The AIA G702 (Application and Certificate for Payment) paired with the G703 (Continuation Sheet) is the most widely recognized standard in US commercial construction. Architects, lenders, and owners are familiar with its layout, which reduces review friction. The G702 is the face sheet showing the summary figures; the G703 is the line-by-line SOV progress record. AIA sells these forms directly, though Levelset notes that when a contract doesn't mandate the official AIA document, a styled template modeled on the same fields is usually acceptable.
ConsensusDocs 710
ConsensusDocs 710 is the payment application form published under the ConsensusDocs suite, which is developed collaboratively by owner, contractor, and subcontractor associations. It covers similar ground to the AIA set but uses different field structures and terminology. Projects using ConsensusDocs prime contracts will typically require the matching payment application form — mixing form families mid-project creates reconciliation headaches.
Excel and custom templates
Many GCs and specialty contractors use their own Excel-based or PDF templates, particularly on smaller projects or when the owner has a proprietary format. These work fine as long as every required field is present. The risk is version drift: an Excel template that hasn't been updated since a contract amendment can produce SOV totals that no longer match the current contract value.
| Form type | SOV / continuation sheet | Typical use case | Practical note |
|---|---|---|---|
| AIA G702/G703 | G703 continuation sheet included | Commercial, architect-led, lender-financed | Most familiar to architects and lenders; purchase from AIA |
| ConsensusDocs 710 | Integrated payment application | ConsensusDocs prime contracts | Required when contract references ConsensusDocs suite |
| Excel / custom | Custom continuation sheet | Smaller projects, owner-specific formats | Confirm all required fields match contract; control versions carefully |
What every complete pay application must include
A complete pay app is a document package, not a single form. Fieldwire's guide to pay apps identifies the core inclusions: original contract amount, approved change orders, total value of work completed and materials stored, retainage, and amounts earned to date. Here is how each piece fits together in practice.
Schedule of values and continuation sheet
The SOV is the backbone. Every line item carries a contract value, and the continuation sheet records what percentage of each line is complete this period and cumulatively. Quantity-based lines (concrete poured, linear feet of conduit installed) are easier to defend than judgment-based percentages.
Backup documents
Reviewers spot-check backup against the SOV claims. Standard backup includes:
- Vendor invoices and receipts tied to specific SOV lines
- Delivery tickets for materials received on-site
- Certified payroll records (required on Davis-Bacon and prevailing-wage projects)
- Daily reports and site photos showing progress
- Stored-materials documentation: photos, insurance certificates, and storage location confirmation when claiming off-site materials
Change orders
Include only approved change orders — those with a signed change order number or a written authorization from the owner or GC. Pending change orders (PCOs) do not belong in the pay app amount unless the contract explicitly allows billing for unapproved extras. List each approved change order separately on the continuation sheet so reviewers can trace the authorization.
Lien waivers
Conditional waivers for the current payment period go out with the pay app. Unconditional waivers for the prior payment period are typically submitted at the same time, confirming that the previous payment was received. If you have lower-tier subs or suppliers, collect their conditional waivers before submitting your own — most GC contracts require them.
Retainage
Show retainage as a line on the face of the application: total earned to date, minus retainage withheld, equals the net amount due.
Pro Tip: Keep a separate retainage tracker updated each billing period. When substantial completion arrives, you'll need to submit a final application that reconciles every retainage dollar withheld across all prior pay apps — and a tracker makes that calculation a five-minute job instead of an afternoon.
How to build a pay application step by step
The calculation is straightforward once the SOV is set up correctly. Here is the sequence most project administrators follow each billing period.
- Review the contract and SOV. Confirm the current contract value including all approved change orders. If the SOV hasn't been updated to reflect approved changes, update it before calculating anything.
- Pull the last approved pay app. Your "previously billed" figures come from the last approved application, not the one you submitted — if the prior app was partially approved, use the approved amount.
- Assess percent complete for each SOV line. Walk the job or get confirmation from the site superintendent. For quantity-based lines, count what's installed.
- Compile backup documents. Match invoices, delivery tickets, and photos to the SOV lines they support. Flag any stored-materials claims that need additional documentation.
- Calculate the current amount due. The formula is: Total Earned to Date minus Prior Payments minus Retainage Withheld equals Amount Due This Period.
- Prepare lien waivers. Conditional waiver for the current request; unconditional waiver for the prior payment if funds were received.
- Assemble and review the package. Check every signature block, confirm dates match the billing period, and verify that SOV totals on the face sheet match the continuation sheet exactly.
Worked calculation example
Pro Tip: Build your Excel SOV so that the "Amount Due This Period" cell is a formula, not a typed number. A typed number that doesn't match the formula result is one of the most common math errors reviewers catch — and it flags the whole application for a closer look.
How the submission and approval workflow actually runs
Most construction contracts set a monthly billing cycle with a specific cut-off date — often the 25th of the month, with payment due 30 days later. Procore's payment application guide notes that project teams typically agree on billing periods in the contract, and submitting outside that window can delay payment by a full cycle or, on some contracts, forfeit your prompt-payment protections for that period.
Confirm your cut-off date from the contract before the first billing. If it isn't stated explicitly, ask the GC or owner in writing and document the response.
Typical routing after submission:
- Day 1: Subcontractor submits to GC with full backup package
- Days 1–7: GC reviews, reconciles against their own SOV, and may request clarifications
- Days 7–14: GC submits consolidated application to architect or engineer
- Days 14–21: Architect reviews, may conduct a site visit, and issues Certificate for Payment
- Days 21–30: Owner processes payment; on lender-financed projects, the lender's inspector may add 3–7 days
After submission, follow up at each handoff point. A brief email confirming receipt and asking for an estimated review completion date is standard practice and keeps the application visible. If you haven't received a Certificate for Payment within the contractual review period, send a written notice — most state prompt-payment laws start the clock from submission, and a documented follow-up protects your position.
Common mistakes that get pay applications rejected
Most pay-app rejections trace back to a short list of recurring errors. Knowing them in advance is the cheapest form of quality control.
Top causes of holds and rejections:
- Math mismatches: The face sheet total doesn't match the continuation sheet sum — a formula error or a manually typed override is usually the culprit
- SOV discrepancies: The SOV on the current application doesn't match the SOV approved at contract start, or hasn't been updated to reflect approved change orders
- Missing or misdated lien waivers: A waiver dated before the billing period ends, or a lower-tier waiver missing entirely, will stop the application at the GC level
- Unapproved change orders billed: Including PCO amounts that haven't been formally authorized is one of the fastest ways to get an application rejected and a relationship strained
- Late submission: Missing the contractual cut-off date can push payment out a full cycle and, in some states, affect your prompt-payment rights
- Missing signatures: An unsigned application or an unsigned waiver is not a valid document — it will be returned
What reviewers look for in the first 60 seconds:
- Do the face-sheet totals match the continuation sheet?
- Is the retainage calculation consistent with the contract rate?
- Are all required waivers present and correctly dated?
- Does the SOV match the contract and prior approved applications?
Centralized digital document libraries address most of these issues before they reach the reviewer. When invoices, delivery tickets, and waivers are stored in a shared folder organized by pay-app number and billing period, assembling the backup package becomes a retrieval task rather than a search.
Pro Tip: Stamp every SOV with the pay-app number and the billing period date in the file name — for example, "SOV_PayApp04_Oct2025." When a reviewer asks "which version of the SOV is this?" you have an immediate, unambiguous answer.
Where to get pay app forms and how to use templates effectively
The authoritative sources for standard forms are the organizations that publish them. For AIA G702/G703, purchase directly from the AIA. For ConsensusDocs 710, access through ConsensusDocs. Both organizations sell individual form licenses as well as subscription access.
When the contract doesn't mandate a specific published form, a styled template that replicates the required fields is generally acceptable — Levelset confirms this is standard practice. The practical test is whether every field the contract requires is present and clearly labeled.
Template options and when each fits:
- AIA-style Excel template: Useful when the project uses AIA contract documents but the owner hasn't purchased official AIA forms; replicate the G702 face sheet and G703 continuation sheet exactly
- ConsensusDocs-style template: Appropriate for ConsensusDocs prime contracts when the official form isn't provided; confirm field names match the contract's defined terms
- Custom Excel continuation sheet: Works well for smaller projects or when the GC has a proprietary format; build in formula checks so totals auto-calculate
Keep at least one sample completed pay application on file as an internal QA reference. Before submitting a new application, compare its structure against the sample: same fields, same calculation logic, same waiver format. This takes five minutes and catches structural errors that a math check alone won't find.
For stored-materials claims, the documentation bar is higher. Reviewers typically require photos of the materials in storage, confirmation of the storage location (on-site or a bonded warehouse), and proof of insurance covering the stored items. Prepare this package before the billing period closes, not the morning of submission.
Software and digital tools that reduce pay-app errors
The pay-app process has a well-documented automation gap. Many contractors still assemble applications in Excel, email PDFs, and chase waivers by phone — a workflow that works until it doesn't. Autodesk Construction Cloud's analysis of progress claims finds that switching to digital templates and tracking tools reduces errors and speeds approvals by standardizing SOVs, automating calculations, and tracking waiver status in real time.
Feature categories worth prioritizing when evaluating tools:
- SOV management: The tool should lock the SOV at contract execution and flag any deviation in subsequent applications
- Auto-calculation: Percent-complete inputs should drive all downstream figures automatically — no manually typed totals
- Waiver generation and exchange: The tool should generate conditional and unconditional waivers from payment data and track which lower-tier waivers have been returned
- Audit trail: Every change to a pay-app figure should be logged with a timestamp and user ID
- Accounting integration: The tool should push approved pay-app data directly to your accounting system to eliminate double-entry
Procore's construction financial management module handles pay-app creation, routing, and approval tracking within a broader project management environment. Levelset specializes in lien rights and waiver management, with pay-app forms and a waiver exchange network built around the US lien system. Both integrate with common accounting platforms.
The practical adoption path: start with one project, map your SOV line items to your accounting cost codes before the first billing, and run one full billing cycle manually in parallel with the digital tool. The parallel run catches mapping errors before they affect a live payment.
Legal and contract considerations that affect every pay app
Pay apps don't exist in a legal vacuum. Several US legal frameworks directly affect when you submit, what you include, and what happens if payment is late or disputed.
Prompt payment laws
Every US state has some form of prompt-payment statute that sets deadlines for owners to pay GCs and for GCs to pay subcontractors after receiving payment. Deadlines vary by state and contract type — some states set 7-day pay-down requirements from GC to sub after the GC receives payment; others allow 30 days. Submitting your pay app on time is a prerequisite for triggering these protections. A late submission can reset the clock or, in some states, waive your right to interest on delayed payments. Check your state's prompt-payment statute directly or through a construction attorney.
Notice requirements
Many contracts require written notice before you can bill for extras, claim additional time, or assert a change order. If you miss the notice window, the change order may be denied even if the work was clearly directed by the owner. The pay app is not a substitute for a timely notice — it is the billing step that follows a properly noticed claim.
Lien waiver strategy
The practical rule: always provide conditional waivers with the pay app, and convert to unconditional only after the payment has cleared your account. Collect lower-tier conditional waivers before submitting your own — most GC contracts require them as a condition of processing your application.
Retainage
Retainage is typically withheld on US commercial projects, with some states capping the percentage after a project reaches a certain completion stage. Show retainage clearly on the face of every application: total earned, retainage withheld, net amount due. Track cumulative retainage separately so the final application reconciles cleanly.
Warning: "Pay when paid" clauses in subcontracts can delay your payment indefinitely if the GC hasn't been paid by the owner. These clauses are enforceable in most US states, though some states limit their scope. Never rely on a "pay when paid" clause as a cash-flow plan — get legal review of any subcontract that contains one before you sign.
How Mbqs approaches pay-app preparation and quality assurance
Mbqs works with contractors and subcontractors across commercial construction projects, and the pay-app process is one of the highest-friction points in the billing cycle. The internal QA checklist Mbqs uses before any application goes out covers four areas: SOV reconciliation, backup completeness, waiver status, and signature verification.
Mbqs's recommended file structure for each pay-app package:
- Folder named by pay-app number and billing period (e.g., "PA-05_November")
- Sub-folder: face sheet and continuation sheet (current version, stamped with pay-app number)
- Sub-folder: backup (vendor invoices, delivery tickets, photos, certified payroll if applicable)
- Sub-folder: lien waivers (conditional for current period; unconditional for prior period)
- Sub-folder: change orders (signed authorizations only)
Mbqs maps SOV line items to commercial cost reports and accounting codes at the start of each project, so that percent-complete assessments in the field feed directly into the billing calculation without manual re-entry. This mapping step eliminates the most common source of SOV drift — a field team updating progress in one system while the billing team works from a different version.
Third-party pay-application reviews are especially valuable on projects with lenders or multiple tiers of subcontracting, where SOV misallocations can compound across billing cycles before anyone catches them. Mbqs's contract administration service includes periodic pay-app audits that check for exactly these systemic issues.
Pro Tip: Run a "pre-submission review" 48 hours before the billing cut-off — not the morning of. That buffer gives you time to chase a missing lower-tier waiver or correct a calculation without missing the contractual deadline.
Why disciplined pay-app practice is a commercial decision, not just an admin task
The pay app is where the commercial management of a project either holds together or starts to unravel. Mbqs has seen contractors with strong site performance lose weeks of cash flow because the billing package was assembled in a rush, a waiver was missing, or the SOV hadn't been updated to reflect a change order approved two months earlier. The reviewer isn't being difficult — they're doing exactly what the contract requires, and a package that doesn't meet the standard goes back.
The contractors who get paid on time, consistently, treat the pay app as a commercial document with the same discipline they'd apply to a contract negotiation. They keep the SOV current, they collect waivers as work progresses rather than scrambling at billing time, and they submit on the cut-off date rather than a few days after. That discipline doesn't just improve cash flow — it reduces the probability of a lien dispute, because a well-documented pay app is also the best evidence you have if a payment is wrongfully withheld.
Mbqs can handle your pay-app process from SOV setup to dispute support
Contractors who need more than a template — who are dealing with a disputed application, a GC pushing back on change orders, or a project where the SOV was never properly set up — have a direct route to hands-on support.
Mbqs's claims support service covers the full pay-app lifecycle: SOV setup and mapping, monthly application preparation, backup assembly, lien waiver coordination, and dispute resolution when a payment is withheld without valid grounds. The service is structured for contractors and subcontractors on commercial projects who need a quantity surveying professional in their corner, not a generic bookkeeping solution.
If you're starting a new project and want the SOV and billing process set up correctly from day one, or if you're mid-project with a disputed application that needs a professional review, contact Mbqs directly. The starting point is a short conversation about the contract and the current billing position — from there, the scope of support is matched to what the project actually needs.
Sources
The following authoritative references were used throughout this guide. Each is worth bookmarking for ongoing reference.
- Construction Payment Applications: A Guide for Contractors | Procore
- Pay Applications in Construction | FAQs, Guide, & Forms | Levelset
- ConsensusDocs 710 — Payment Application | ConsensusDocs
- A Guide to Pay Applications in Construction | Fieldwire
- Construction Progress Claims Explained: A Guide for Smooth Payments | Autodesk Construction Cloud
- Payment application reviews for construction project success | Baker Tilly