Retainage in QuickBooks Online
Yes—kind of. QuickBooks Online can track retainage concepts depending on your setup, but it doesn’t produce an AIA-style pay application package. If your billing is driven by a Schedule of Values and you need clean period-to-period rollforward, you typically need a dedicated pay app workflow alongside QBO.
Retainage is simple in theory: hold back a percentage until the job is complete. In practice, it’s the part that most often causes billing drift between QuickBooks Online, your pay app package, and what the GC/owner actually approves.
This page is a retainage deep-dive. If your real question is whether QuickBooks can do AIA billing at all, start with: Does QuickBooks Do AIA Billing (G702/G703)?. If you’re trying to map month-to-month billing, read: Progress Billing in QuickBooks Online and the plain-English overview: Construction Progress Billing (Explained). For the “connect the dots” workflow, see: QuickBooks Online AIA billing integration options.
What “retainage in QuickBooks” usually means
When contractors ask about retainage in QuickBooks Online, they’re usually trying to do two things:
- Track withheld amounts (retainage) for accounting and reporting, and
- Show retainage correctly in a reviewer-friendly pay app package.
QBO is built for accounting. AIA-style pay apps are built for pay app review. Those are overlapping worlds, but not identical—especially when retainage is applied line-by-line and must roll forward cleanly. If you’re also wrestling with how percent-complete billing rolls forward each month, see Construction Progress Billing (Explained).
Most retainage confusion starts when billing is driven by a Schedule of Values and prior periods.
Where retainage gets tricky in QuickBooks Online
In QuickBooks Online, retainage problems rarely start on day one. They start around month 3—when you have prior billing, change orders, and a reviewer who expects the pay app to roll forward exactly.
- Summary vs line-item retainage: QBO can be made to “show retainage,” but reviewers usually expect it at the SOV line level.
- Rollforward math: what was “earned prior,” “this period,” and “stored materials” must reconcile across applications.
- Approval vs invoicing timing: “approved amount” and “invoiced amount” are not always the same moment in your process.
- Change orders: contract sums shift—if they’re not reflected consistently, retainage totals drift.
Common retainage approaches in QuickBooks Online
Different teams do this differently. The “best” method is the one that reconciles cleanly with how you submit pay apps. (If you’re building pay apps monthly, the rollforward context in progress billing helps this section click.)
Approach A: Accounting-first retainage (QBO controls)
Retainage is tracked primarily on the accounting side. The pay app package is produced separately and then reconciled back.
- Pros: clean AR reporting in QBO
- Risk: pay app line-item retainage often doesn’t match summary retainage
- Most common failure: totals drift across periods
Approach B: Pay app-first retainage (SOV controls)
Retainage is applied at the Schedule of Values line-item level (the way reviewers typically expect), then mirrored into QBO.
- Pros: G702/G703-style totals roll up cleanly
- Risk: requires a consistent workflow for syncing/mirroring
- Most common win: fewer “revise and resubmit” cycles
QuickBooks retainage vs AIA-style retainage: what’s the difference?
In accounting, retainage is “money withheld.” In AIA-style billing, retainage is also a presentation and rollforward problem: it must reconcile across prior applications, SOV lines, and contract changes.
Why retainage creates “totals drift”
Retainage problems usually aren’t about one invoice. They show up across periods when you have: a Schedule of Values, prior applications, change orders, stored materials, and multiple retainage rules.
- Different retainage math between QBO and the pay app package
- Line-item vs summary mismatch (reviewers expect line-item clarity)
- Prior-period rollforward errors that compound over time
- Change orders not reflected consistently in contract sums
If you’re trying to map retainage + progress billing + pay apps to accounting, start here:
Retainage checklist (so you don’t fight the same battle every month)
- Confirm your retainage rate (and whether it changes at milestones).
- Decide line-item vs summary retainage and be consistent.
- Define how COs affect the contract sum (approved only vs pending).
- Confirm stored materials handling (retainage on stored or not).
- Decide your “truth” system: accounting in QBO, pay app rollforward in pay app workflow.
- Align invoice timing with pay app approval (avoid “approved ≠ invoiced”).
- Reconcile once per period using the same rollforward logic every time.
- Document the rule so PM + accounting execute consistently.
The simplest workflow that keeps retainage aligned
Keep accounting in QuickBooks Online. Keep pay app presentation and rollforward in a pay app workflow.
1) Build your SOV once
Your Schedule of Values drives line-item billing and retainage math across periods.
2) Apply retainage consistently
Line-item retainage rolls up cleanly so your totals match what reviewers expect.
3) Mirror approved totals into QBO
Create or update invoices so your AR reflects the approved pay app amount.
Stop re-checking retainage math every billing cycle
Build AIA-style pay apps with clean retainage rollforward, then keep QuickBooks Online aligned without spreadsheets.