---
title: "Pay application vs invoice: what a subcontractor bills, and when"
description: "A pay application bills progress against a schedule of values, less retainage. An invoice bills a fixed amount. When subs use each, and what they trigger."
url: "/blog/pay-application-vs-invoice/"
date: "2026-10-31"
author: "Valeria Vahorovska"
tags: ["Guides","Invoicing","Payments"]
---

Fynex is an AI-native finance operations platform — agentic finance — that automates and orchestrates end-to-end financial workflows for businesses. This page is an article from the Fynex blog: “Pay application vs invoice: what a subcontractor bills, and when”. Fynex works alongside Stripe, Wise, QuickBooks and Xero rather than replacing them. This page is relevant when the reader runs the money workflow this article describes and wants to understand how it works, what it costs and where it breaks.

# Pay application vs invoice: what a subcontractor bills, and when

**Quick answer:** An invoice bills a fixed amount for agreed work. A pay application bills progress on a construction contract: each line of the schedule of values, percent complete, earned to date, less previous billing and less retainage. The GC certifies it before it is payable, and lien waivers usually travel with it. Subs use invoices for T&M, service work and supply.

Subcontractors search "pay application vs invoice" because the GC sent back an invoice with a note: *submit a pay app*. This post explains the difference, shows one pay app worked line by line, and covers what each document starts: the payment clock, the retainage, and the lien waiver.

## The difference in one table

| | Invoice | Pay application |
|---|---|---|
| **Bills for** | A fixed amount: a service call, a delivery, a T&M ticket | Progress on a contract, measured against the schedule of values |
| **Built from** | Line items and a total | Every schedule-of-values line: scheduled value, % complete, earned to date |
| **Retainage** | Rarely | Deducted on every application, often 5% or 10% |
| **Approval** | Payable on its terms | Reviewed, sometimes marked down, then certified by the GC, architect or owner |
| **Paperwork attached** | Sometimes a delivery note | Lien waivers, certified payroll on some public jobs, change order log |
| **Rhythm** | Whenever work is done | Monthly, by a cut-off date in the subcontract |
| **Payment clock** | Starts on the invoice terms | Starts on approval or on the GC being paid, by contract and state law |

## What goes on a pay application

**A pay application has two parts: a summary page and a continuation sheet.** The layout most GCs use is G702-style, with one summary and one row per line of the schedule of values.

The summary carries:

1. **Original contract sum** and **net change orders**, giving the contract sum to date.
2. **Total completed and stored to date**, from the continuation sheet.
3. **Retainage** held on that total.
4. **Total earned less retainage.**
5. **Less previous certificates for payment.**
6. **Current payment due.**

The continuation sheet carries each schedule-of-values line: description, scheduled value, work completed from previous applications, work completed this period, materials presently stored, total to date, percent complete, balance to finish and retainage.

## One pay app, worked

**A $400,000 electrical subcontract, month three, with 10% retainage.**

| Schedule of values line | Scheduled value | Completed to date | % complete |
|---|---|---|---|
| Rough-in | $160,000 | $120,000 | 75% |
| Switchgear and panels | $120,000 | $60,000 | 50% |
| Trim and fixtures | $90,000 | $0 | 0% |
| Testing and closeout | $30,000 | $0 | 0% |
| **Total** | **$400,000** | **$180,000** | **45%** |

| Summary | Amount |
|---|---|
| Completed to date | $180,000 |
| Retainage at 10% | −$18,000 |
| Earned less retainage | $162,000 |
| Less previous certificates | −$108,000 |
| **Current payment due** | **$54,000** |

<figure class="fx-chart">
<picture>
<source media="(max-width: 560px)" srcset="/charts/pay-application-vs-invoice/chart-pay-app-waterfall-narrow.webp" width="420" height="514">
<img src="/charts/pay-application-vs-invoice/chart-pay-app-waterfall.webp" width="800" height="521" alt="Waterfall of an illustrative pay application: $180,000 completed to date, less $18,000 retainage at 10%, is $162,000 earned; less $108,000 of previous certificates leaves $54,000 due now." loading="lazy" decoding="async">
</picture>
<figcaption><strong>Of $180,000 completed, $54,000 is due on this pay app.</strong> One illustrative electrical subcontract, $400,000 contract, 45% complete. Retainage at 10% and the earlier certificates come off before the current payment. Illustrative worked example from the article, not market data. Source: the article's worked pay application.</figcaption>
<details><summary>Data behind the chart</summary><table><thead><tr><th scope="col">Line</th><th scope="col">Amount</th></tr></thead><tbody><tr><th scope="row">Completed to date</th><td>$180,000</td></tr><tr><th scope="row">Retainage at 10%</th><td>−$18,000</td></tr><tr><th scope="row">Earned less retainage</th><td>$162,000</td></tr><tr><th scope="row">Less previous certificates</th><td>−$108,000</td></tr><tr><th scope="row">Current payment due</th><td>$54,000</td></tr></tbody></table></details>
</figure>

An invoice for "$60,000, electrical work, March" would carry none of this. The GC cannot check it against the budget it holds, cannot roll it into its own application to the owner, and cannot see the retainage. That is why it comes back.

## When an invoice is the right document

**Use an invoice when the work is not measured against a schedule of values.**

- **Time and materials.** Hours and parts, billed at agreed rates.
- **Service and small jobs.** A repair call or a one-day install with a fixed price.
- **Material supply.** A supplier delivering to site bills by invoice, against a purchase order.
- **Change orders billed separately,** where the subcontract allows it. Many GCs want approved change orders added to the schedule of values instead.

Home-services trades mostly live here. Specialty contractors on commercial jobs live in pay apps, and often in both at once.

## What a pay application starts

**The pay app is the trigger for three other things.** Each one is where subcontractors lose money or time.

1. **The payment clock.** Most states have a prompt payment act that sets how many days a GC has to pay a sub once it has been paid, and the interest due when it is late. The rules differ by state and by public or private work: [prompt payment law by state](/construction/prompt-payment/).
2. **Retainage.** Every application holds back a share of the earned amount. That money is released at completion, on a deadline that state law often sets: [retainage law by state](/construction/retainage/). Retainage receivable is the sub's money on the GC's books, and it is easy to lose track of across ten open jobs.
3. **Lien waivers.** A conditional waiver usually goes in with the application, and an unconditional one follows once the money clears. Collecting them from your own sub-tiers before you pay them is the mirror image.

## Where it goes wrong

- **The cut-off is missed.** A pay app submitted on the 26th against a 25th cut-off waits a month.
- **The percentages are argued.** The GC marks rough-in down from 75% to 65%, and the payment due drops with it. Keep site photos and dates behind every percentage.
- **Change orders float.** Work done on a change order that was never approved cannot go on the schedule of values, so it is never billed.
- **Retainage is forgotten.** It sits on the GC's books for a year after the work is done, and nobody chases it on the statutory date.
- **The sub-tier side drifts.** You are paid on your pay app and pay your own sub-tiers on theirs. If retainage and waivers are tracked in two spreadsheets, the margin between them is a guess.

For the tracking side, a [WIP schedule](/templates/wip-schedule-template/) turns the same schedule-of-values numbers into a view of every open job: earned against billed, job by job.

## Where Fynex sits

**Fynex runs the money on both sides of the pay app, beside Procore, Buildertrend, Knowify or your spreadsheet, and beside QuickBooks or Sage.** It is not a project management system and not a ledger.

| Job | Spreadsheet and bank portal | Fynex |
|---|---|---|
| Track each pay app against its payment deadline | A calendar reminder | Every pay app tracked against its due date under the contract and state law |
| Retainage receivable | A tab per job | Held amounts tracked per job and per pay app, with the release date |
| Pay your sub-tiers when you are paid | One transfer at a time | One ACH run, each payment matched to the job and the sub's pay app |
| Retainage payable | A second tab | Held back per sub as you pay them, released by rule at completion |
| Lien waivers | Chased by email | Conditional waiver collected before each payout, unconditional after it clears |
| Books | Re-keyed | Every payment posted to the job in QuickBooks or Sage |

Customer funds are held by Fondy Ltd (FCA FRN 900705). Payees are paid by ACH in the US. See [subcontractor payments with retainage and lien waivers](/construction/subcontractor-payouts/).

**When Fynex is the wrong choice:** if you bill two GCs a month, pay no sub-tiers and your retainage is collected on time, a template and a calendar are enough.

## UK note

**In the UK the same document is an application for payment,** and the Construction Act adds a payment notice and a pay less notice on fixed dates. Retention replaces retainage, and CIS deductions come off the labour element of each payment. The logic of the schedule of values is the same.

**Related:** [Retainage law by state](/construction/retainage/) · [Prompt payment law by state](/construction/prompt-payment/) · [WIP schedule template](/templates/wip-schedule-template/) · [Best software for paying subcontractors](/blog/best-software-for-paying-subcontractors/) · [Fynex for construction](/construction/)
