Use an invoice when you're billing for a complete, self-contained piece of work: a service call, a repair, a delivery, a short job billed once when it's done. Use a pay application when you're billing progressively against a contract — requesting a share of the contract sum each period based on how much of the work is complete, with retainage held back and every application connected to the ones before it.
The fastest tell: read your contract. If it mentions a schedule of values, retainage, applications for payment, or a monthly billing date, the decision has already been made for you — it's a pay application. An invoice sent into that process doesn't get paid; it gets parked.
The 30-second decision
Match your situation to the row. When in doubt on commercial work, the pay application is the safe default — a payer who wanted an invoice can process a pay application, but a payer who requires applications usually cannot process an invoice.
| Your situation | Send | Why |
|---|---|---|
| Service call or repair, billed once when done | Invoice | One request, one payment, no running balance to track. |
| Selling materials or equipment | Invoice | It's a sale, not progress against a contract sum. |
| Short time-and-materials engagement | Invoice | Bill the hours and costs as they accrue; nothing carries forward. |
| Subcontract on a commercial project, billed monthly | Pay application | The payer needs to verify progress against the contract before releasing money. |
| Contract that holds retainage | Pay application | Retainage math only works on a cumulative document. |
| GC or owner with a draw process or architect certification | Pay application | Your request feeds their draw to the lender — it has to be in a form they can certify. |
| Final billing and retainage release at closeout | Pay application | The final application reconciles everything billed before it. |
| Residential remodel paid on milestones | Whichever the contract names | Often a simple invoice per milestone; a pay application also works and looks more professional. |
What each document is
An invoice
An invoice is a request for payment that asserts an amount: here's what was done or delivered, here's what you owe, here are the payment terms. It stands alone — nothing about it depends on any bill that came before or after. That's exactly why every industry uses it, and exactly why construction contracts of any size don't.
A pay application
A pay application is a request for payment that proves an amount. It shows the full contract broken into priced line items (the schedule of values), how much of each line is complete to date, what's already been billed and paid, the retainage withheld, and the arithmetic connecting all of it to the figure due this period. The payer can check every dollar requested against the work actually in place — which is why payers on progress-billed contracts require it.
New to the document itself? Start with these:
The differences that decide it
| Invoice | Pay application | |
|---|---|---|
| Question it answers | “What do I owe you for this?” | “How much of the contract have you earned to date, and what part of that is payable now?” |
| Relationship to other bills | Standalone — each invoice is its own transaction. | Cumulative — every application restates the whole job to date and deducts what came before. |
| Proof | Assertion. Description and amount. | Line-by-line calculation against an agreed schedule of values. |
| Approval | Payable on its terms unless disputed. | Reviewed and certified — the payer can approve less than you applied for. |
| Retainage | Not built in. | Withheld on every application and tracked until release. |
| Supporting documents | Rarely any. | Lien waivers, stored-material documentation, certified payroll — whatever the contract requires. |
| Format | Any layout. | A cover sheet with the summary math plus a continuation sheet — the structure standardized by AIA G702/G703 and matched by equivalent forms. |
| Numbering | Invoice number, unique across your whole business. | Application number, sequential within each project: #1, #2, #3… |
When an invoice is the right document
- The work is complete and self-contained — you'll bill once, get paid once, and be done.
- There's no schedule of values and no retainage in the agreement.
- You're billing for goods, rentals, or time and materials rather than progress against a fixed contract sum.
- The customer is a homeowner or small business that would be confused, not reassured, by a certified application package.
Don't over-engineer small work. A one-page invoice that gets paid in two weeks beats a four-page application package nobody asked for. The mistake that costs money runs in the other direction — invoicing a payer whose process requires applications.
When a pay application is required
You rarely have to guess. Any one of these signals in your subcontract or the general conditions means the payer expects applications, not invoices:
- A schedule of values is attached to the contract or required before first billing.
- The contract states a retainage percentage.
- The payment clause says “application for payment,” “progress payment,” or “payment request,” with a monthly cutoff date.
- An architect, engineer, or construction manager certifies amounts before payment.
- Billing must be “on AIA G702/G703” or “on forms acceptable to Owner.”
- It's public work — government projects pay on progress estimates or applications almost without exception.
The reason is mechanical, not bureaucratic. Your payment request feeds a chain: the GC assembles subcontractor applications into their own application to the owner, the owner may draw on a construction loan, and the lender wants certified progress behind every dollar. An invoice can't ride that chain because it doesn't carry the progress math the next link needs.
The same work, billed both ways
Here's a drywall contractor billing $10,800 of work in a month — first as an invoice, then as month two of a progress-billed subcontract.
- Drywall installation, Building C offices
- $10,800.00
- Terms
- Net 30
- Total due
- $10,800.00
Clean and sufficient — if nothing connects this month's work to a larger contract.
- Contract sum to date
- $48,000.00
- Completed to date (45%)
- $21,600.00
- Less retainage held (10%)
- −$2,160.00
- Earned to date, less retainage
- $19,440.00
- Less previous applications
- −$8,640.00
- Payment due this period
- $10,800.00
Same month, same work. But this version proves the amount, shows the payer 45% complete against the contract, tracks the $2,160 being held, and slots into application #3 automatically next month.
Notice what the application version buys you beyond this month's payment: a running record of retainage you're owed at closeout, agreement on percent complete that protects you in a dispute, and numbers that carry forward so next month's billing takes minutes instead of an afternoon.
How invoices and pay applications work together
For many subcontractors it isn't either/or — it's both, doing different jobs. The pay application is the submission package the payer certifies; a matching invoice is what your accounting system wants, because QuickBooks and its peers track receivables by invoice, not by application. The common workflow: prepare and submit the pay application, then enter an invoice in your books for the same period's amount, referencing the application number.
Some payers even ask for both — the application package for certification, with an invoice number on it so their accounts-payable system can ingest it. That's fine. Keep the application numbers sequential within the project (#1, #2, #3), keep your invoice numbers doing whatever your books need, and record both on each billing so either side can trace any payment.
“Don't send an invoice — send a pay application”
If a GC has just said this to you, here's the translation: your invoice can't enter their payment process, and nothing gets paid until you resubmit in application form. The conversion is straightforward:
- Break your contract price into a short schedule of values — even three or four lines is enough on a small subcontract. Get it accepted before you bill against it.
- Put billing history in its place. Anything already billed and paid on this job goes in the “previous” columns of application #1 — you enter the history once, and it carries forward from then on.
- Bill this period's progress only. The application computes the cumulative total; you report what happened since last time.
- Expect the payment to be smaller than the work: retainage comes off every application and returns at closeout.
- Attach what the contract requires — usually a lien waiver, sometimes stored-material backup or certified payroll.
And three mistakes to avoid — each one shows up constantly in real submissions, and each one gets applications rejected or payments disputed:
- Billing 100% of the contract on every application, invoice-style. Applications are cumulative: bill what's complete to date, and let the previous-payments deduction do its work. Billing the full amount twice reads as double-billing.
- Reissuing application #1 with different numbers instead of moving to #2. Two documents with the same application number and different totals is how payment disputes start. Each new billing period — and each correction after submission the payer has logged — gets the next number.
- Editing the original contract sum when the contract grows. A $200 extra belongs on the change-order lines, not silently added to line 1 — payers check the original contract sum against the signed subcontract, and a mismatch stops payment.
What happens if you use the wrong one
Send an invoice where an application is required, and the usual result isn't a rejection letter — it's silence. The invoice sits in someone's inbox because the payment process has no slot for it, you miss the monthly cutoff, and payment slips a full billing cycle: thirty days or more for a paperwork mismatch. On a $50,000 receivable, that's real financing cost for a free fix.
Send a pay application where a simple invoice would do, and the cost is close to zero — a few extra minutes of setup, and a customer who now has more documentation than they needed. Some large GCs require application format even for small, single-billing subcontracts precisely because their process only speaks that language. That asymmetry is the rule of thumb: on commercial work, when you're not sure, bill with a pay application.
Frequently asked questions
- Is a pay application the same as an invoice?
- No. Both request payment, but an invoice asserts a standalone amount while a pay application proves a cumulative one — showing the schedule of values, percent complete, retainage, and previous payments so the payer can verify the request against the work in place. Payers on progress-billed contracts require the application form and generally can't process a bare invoice.
- Can I just send an invoice instead of a pay application?
- Not if the contract requires applications. An invoice sent into a draw-based payment process typically isn't rejected — it's ignored, because there's no step that can consume it. You'll usually miss the billing cutoff and lose a full payment cycle before finding out.
- Do I need both an invoice and a pay application?
- Often, yes — for different audiences. The pay application is what the payer certifies; an invoice for the same amount is what your accounting software tracks. Enter the invoice in your books referencing the application number, and reconcile payments against either.
- Can an invoice include retainage?
- You can show a deduction on an invoice, but retainage only really works on a cumulative document that tracks what's been withheld across the whole job and computes the release at the end. If your customer holds retainage, that's itself a sign the billing belongs on a pay application.
- What if the contract requires AIA G702 and G703?
- G702 and G703 are the AIA's copyrighted forms — licensed per use from the AIA. Many payers accept an equivalent application format carrying the same information: cover-sheet summary, continuation sheet, retainage, and certification. Ask your GC whether an equivalent form is acceptable before buying licenses; on most private jobs it is.
- Should a small subcontractor bother with pay applications?
- If the contract asks for them, yes — size doesn't exempt you. And even when it doesn't, a progress-billed job with more than one payment is easier to track on applications: a two-line schedule of values takes five minutes and gives you a clean running record of what's billed, paid, and held.
- What's the difference between an application number and an invoice number?
- An application number is sequential within one project — application #1, #2, #3 tell the payer where this billing sits in the job's history. An invoice number is unique across your whole business, for your books. On payer request, carry both on the same submission; never reuse an application number for a different amount.
