Is a pay application legally required?

No law requires the format — your contract does. Most commercial construction contracts specify progress payments against a schedule of values, which in practice means a pay application. Follow whatever form and deadlines your contract names.

Is a pay application the same as an invoice?

They serve the same purpose — requesting payment — but a pay application adds the running project math: schedule of values, percent complete, retainage, and previous payments. Some accounting systems still want an invoice number attached to each application, which is fine; the application is the backup.

Who signs a pay application?

Someone authorized by the contractor submitting it — typically an owner, officer, or project manager. The certification language states the work covered has been completed per the contract documents. Some contracts additionally require notarization; check yours.

What happens after I submit one?

The customer (GC, construction manager, or architect) reviews and certifies it, possibly adjusting quantities they disagree with. The certified amount — not necessarily the requested amount — is what gets paid, and next month's application must account for what was actually certified.

What Is a Pay Application? The Complete Guide for Subcontractors

A pay application — short for application for payment, and often just called a pay app — is the document package a contractor or subcontractor submits to request payment for work completed during a billing period. On most commercial construction projects, you don't send an invoice the way a plumber bills a homeowner. You submit a pay application that shows, line by line, how much of the job is done, what you've already been paid, and exactly what you're owed right now.

If you're new to progress billing, that distinction is the single most important thing to understand: an invoice asserts an amount; a pay application proves one. Every dollar you request is backed by a calculation the customer can check against the contract.

Why construction doesn't just use invoices

Construction projects are long, expensive, and paid for in installments while the work is still unfinished. That creates two problems a regular invoice can't solve. First, the customer needs a way to verify that the amount requested matches the progress on site — nobody wants to pay 60% of the contract for 40% of the work. Second, everyone needs a running record that connects this month's request to everything billed before it, so double-billing is impossible and the remaining balance is always known.

The pay application solves both. It breaks the contract into line items (the schedule of values), reports progress against each line, and carries forward the running totals from every previous application. The math has to reconcile — this month's request plus everything previously billed can never exceed the value of work actually in place.

What's in a pay application

A standard pay application package has two parts, which mirror the structure made familiar by the AIA's G702 and G703 forms (most non-AIA formats, including the one this site generates, follow the same logic):

The application (cover page) — identifies the parties, project, application number, and billing period, then summarizes the money: original contract sum, change orders, total completed and stored to date, retainage withheld, previous payments, and the amount due for this period. It usually carries a signed certification, and on some projects a notarization.
The continuation sheet — the line-by-line detail. Each schedule-of-values line shows its scheduled value, work completed in previous periods, work completed this period, materials presently stored, percent complete, balance to finish, and retainage.

The two parts must agree to the penny: the continuation sheet's totals are the source of the cover page's numbers. Most rejected pay apps fail exactly here — a cover page edited by hand that no longer matches its own detail.

The key numbers, in plain English

Original contract sum — what your contract says the whole job is worth.
Net change by change orders — everything added or deducted by approved change orders. Together with the original sum, this gives the contract sum to date.
Total completed and stored to date — the value of all work done since the project started (not just this month), plus materials delivered but not yet installed, where your contract allows billing them.
Retainage — the percentage (commonly 5–10%) your customer withholds from earned value until completion, as security that the job gets finished.
Less previous certificates — everything already approved for payment on earlier applications.
Current payment due — what's left after subtracting retainage and previous payments from the total earned. This is the number the check should match.

A worked example — application #3 on a $250,000 contract

Original contract sum: $250,000.00
Approved change orders: +$8,000.00
Contract sum to date: $258,000.00
Total completed & stored to date (55%): $141,900.00
Retainage (10%): −$14,190.00
Total earned less retainage: $127,710.00
Less previous certificates (apps #1–2): −$92,500.00
Current payment due: $35,210.00

Every number is checkable: the $141,900 comes from the continuation sheet's line items, and the $92,500 is the sum of the two prior applications' approved amounts.

The monthly cycle

Pay applications run on a rhythm set by your contract, usually monthly. A typical cycle: work is performed through a cutoff date (the period-to date); the sub submits the application by the contract's deadline — often the 25th, or 5 days before month end; the GC or architect reviews and certifies it (sometimes adjusting quantities); and payment arrives within the contract's payment window after certification. Miss the submission deadline and you often wait a full extra month — which is why experienced subs treat the pay app date like a hard deadline.

Each new application starts where the last one ended: this month's 'work completed — previous applications' column is last month's total. Keeping that roll-forward accurate by hand, month after month, is where spreadsheet-based billing quietly breaks down.

Common mistakes that get pay apps rejected

Cover page and continuation sheet that don't reconcile (usually a hand-edited total).
Billing ahead of actual progress — percent complete that the site walk doesn't support.
Forgetting approved change orders, so the contract sum is wrong and every downstream number with it.
Retainage math drift — applying the rate to the wrong base, or losing track when rates differ for completed work vs stored materials.
Skipping required attachments — lien waivers, stored-material documentation, or certified payroll where applicable.

Frequently asked questions

Is a pay application legally required?: No law requires the format — your contract does. Most commercial construction contracts specify progress payments against a schedule of values, which in practice means a pay application. Follow whatever form and deadlines your contract names.
Is a pay application the same as an invoice?: They serve the same purpose — requesting payment — but a pay application adds the running project math: schedule of values, percent complete, retainage, and previous payments. Some accounting systems still want an invoice number attached to each application, which is fine; the application is the backup.
Who signs a pay application?: Someone authorized by the contractor submitting it — typically an owner, officer, or project manager. The certification language states the work covered has been completed per the contract documents. Some contracts additionally require notarization; check yours.
What happens after I submit one?: The customer (GC, construction manager, or architect) reviews and certifies it, possibly adjusting quantities they disagree with. The certified amount — not necessarily the requested amount — is what gets paid, and next month's application must account for what was actually certified.