SubAscentVisit Website →
← Back to blog

4 Ways to Close the Gap Between QuickBooks and AIA for Trade Subs

August 31, 2026
4 Ways to Close the Gap Between QuickBooks and AIA for Trade Subs

QuickBooks Online does not natively generate AIA G702/G703 pay-application packages. It has no built-in template that spits out a reviewer-ready form. Your move: keep QuickBooks as your accounting system of record, and layer either QuickBooks' newer construction billing features or a dedicated pay-app workflow on top. Which one depends on how many draws you bill a month, and that's covered below.

TL;DR:

  • QuickBooks Online does not provide native support for AIA G702/G703 pay-application forms, requiring external templates or workflows for review-ready output.
  • Accurate progress billing in QuickBooks depends on detailed Schedule of Values setup, consistent line-item naming, and attaching official pay-app PDFs to invoices.
  • Most contractors use a combination of QuickBooks with spreadsheets or dedicated integration tools to handle retainage separate from job costs and streamline line-item rollforwards.
  • Common rejection errors include inconsistent line labels, incorrect retainage application, missing change orders, and invoice number mismatches, which must be checked before submission.
  • Implementing a locked SOV template and using dedicated tools like SubAscent can significantly reduce manual effort and improve pay app approval success rates.

Table of Contents

What AIA billing actually requires beyond a regular invoice

A standard invoice says "here's what we did, pay us." A pay application says "here's what we've billed cumulatively, here's what's left on the contract, and here's how the math ties back to last month." That distinction is the whole game.

The AIA's G702 (Application and Certificate for Payment) and G703 (Continuation Sheet) work as a pair. G702 is the cover summary: contract sum, total completed to date, retainage, and balance to finish. G703 is the Schedule of Values (SOV) broken into line items, each one showing prior billing, current billing, materials stored on site, and percent complete.

Reviewers check specific things, not just your bottom line:

  • Does this period's billed amount plus prior periods equal the new cumulative total, line by line?
  • Is retainage calculated consistently against the correct base (contract value or completed value)?
  • Are stored materials tracked separately so they don't get double counted once installed?

QuickBooks needs to hold the financial truth (job costs, AR, retainage liability). The G702/G703 formatting, line-item rollforward, and signature blocks are presentation. You can build that presentation layer outside QuickBooks as long as the numbers underneath match exactly.

Where QuickBooks stands today, and where it stops

QuickBooks Online handles the accounting backbone of progress billing well: it invoices customers, tracks AR by job, and runs job cost reports if you're using classes or projects correctly. For a lot of small commercial jobs, that's most of what you need.

Where it gets more interesting is the newer construction-focused rollout. QuickBooks has added an AIA-style progress invoicing beta that introduces structured SOVs, period-based billing, and running percent-complete tracking for some account tiers. It's a real step forward, but availability varies, and formatted, reviewer-ready G702/G703 output still isn't guaranteed across all plans.

Reality check: Even where the beta is live, most contractors still hit the same three walls:

  • No native way to apply retainage differently by SOV line (some lines get 5%, some 10%, some none)
  • Stored materials tracking that satisfies a reviewer, not just an internal note
  • Formatted, printable G702/G703 output matching AIA's actual layout

If your GC or owner requires the official AIA forms, plan on a supplemental workflow no matter which QuickBooks tier you're on.

Four ways to close the gap between QuickBooks and AIA forms

Contractors generally land on one of four workflows. Most fall into QuickBooks-only, QuickBooks plus a spreadsheet, or QuickBooks plus dedicated pay-app software, with outsourcing as a fourth path for firms that would rather not own the process at all.

  1. QuickBooks-only, summary invoices. Fine for small jobs with simple lump-sum billing and no formal SOV requirement. Risky the moment a GC's PM asks for a line-item rollforward you haven't been tracking.
  2. QuickBooks plus a spreadsheet. The most common setup for low-volume billers. Cheap, flexible, and error-prone the second someone forgets to update prior-period columns before typing in this month's numbers. Works if one person owns the sheet and audits it every cycle.
  3. QuickBooks plus a dedicated pay-app or AIA billing integration. Middleware or standalone AIA billing software handles SOV rollforward and retainage automatically, then pushes matching invoices into QuickBooks. Before you commit, test how it handles voids, change-order reversals, and retainage releases. If those require manual fixes in QuickBooks afterward, the integration hasn't actually solved your double-entry problem.
  4. Hand it to a construction-focused ProAdvisor or bookkeeper. Costs more monthly but often pays for itself in fewer rejected pay apps and less owner time spent chasing formatting errors.

Pro Tip: Before you sign up for any AIA billing integration, ask the vendor to walk you through a change order reversal live. If they hesitate, that's your answer.

Building your Schedule of Values and matching QuickBooks invoices

Get the SOV right once, and every future draw is just updating numbers, not rebuilding logic.

Step 1: Build the original SOV.

  1. List every scope item as its own line, matching your contract breakdown, not your internal cost codes.
  2. Set the baseline scheduled value for each line so it sums to the full contract amount.
  3. Mirror those same line names in QuickBooks, whether as items, classes, or sub-customers.

Step 2: Run each period's billing.

  • Calculate current period billed, add to prior cumulative, and confirm the total against the contract value.
  • Note stored materials separately from installed work.
  • Apply retainage per line if your contract requires it, not a flat blended rate.

You've got three ways to represent this in QuickBooks:

  • One summary invoice per period — simplest, but you lose line-item detail in QuickBooks reporting.
  • Detailed invoice lines matching every SOV row — more setup, but your job cost reports and pay app numbers stay identical.
  • Product/service items mapped to SOV lines — a middle ground that works well if you're already using items for estimating.

Step 3: Attach the pay-app document. Generate your G702/G703-style PDF, use a consistent numbering convention (APP-001, APP-002, and so on), and attach that PDF directly to the matching QuickBooks invoice so the invoice number and the pay app reference the same job.

Pro Tip: Name your SOV lines the way your foreman talks about the work, not the way your estimate spreadsheet does. "Rough-in second floor" beats "Phase 2B Mechanical" every time someone has to update it fast.

Reconciling pay apps to job cost and AR

The pay app is only useful if it agrees with your books. Run these checks every cycle, not just at closeout.

  • Billed-to-date vs. cost-to-date. If you've billed 60% but only spent 35% of budgeted cost, either you're front-loading (common and fine within reason) or something's mislabeled.
  • AR aging by project. A pay app that's approved but unpaid for 45+ days needs a phone call, not just a note in QuickBooks.
  • Retainage in the general ledger. Confirm retainage held matches what's on your pay app, and that it's sitting in a separate GL account, not buried in AR.

Before you send anything: check that current period plus prior cumulative equals your new total. After payment lands: confirm the deposit matches the approved amount minus retainage, and post any short-pay difference immediately instead of letting it float.

The mistakes that get pay apps kicked back

Most rejections trace back to the same handful of errors, cycle after cycle.

  • Inconsistent SOV labels between what you billed last month and what you're billing now, even a small rename, throws off a reviewer doing a side-by-side check.
  • Misapplied retainage — using a flat rate when the contract specifies different rates by trade or phase.
  • Missing change orders that were verbally approved but never added to the SOV, so the contract sum on your pay app doesn't match the GC's records.
  • Invoice number mismatches between your QuickBooks record and the pay app reference number.

Reviewers notice sudden jumps in percent complete with no supporting documentation, and they notice fast. Run this six-point check before every submission: SOV totals tie to contract sum, current plus prior equals cumulative, retainage math matches contract terms, all approved change orders are reflected, stored materials are itemized separately, and your invoice number matches the pay app number exactly.

Pro Tip: Keep a one-page change order log next to your SOV. Every time a CO gets verbal approval, it goes on the log the same day, before it has a chance to get forgotten until the next pay app is due.

What actually helps specialty trades get this right

Name SOV lines the way your field crews and your bookkeeper both understand them. "HVAC rough-in third floor" works for everyone; a cost code number only works for one person.

Collect percent-complete updates from foremen with a two-minute weekly check-in rather than a form nobody fills out. A quick text thread beats a spreadsheet nobody opens.

Before automating anything, test the integration's handling of voids, change-order reversals, and retainage releases. If the sync breaks on any of those three, you'll be doing manual cleanup in QuickBooks anyway, which defeats the purpose of automating in the first place. Clean job cost reconciliation depends on that integration actually holding up under real-world edits, not just clean first-time entries.

What changed when we tightened the SOV process

The biggest improvement we've seen in trade shops isn't software. It's replacing a rebuilt-every-month spreadsheet rollforward with a locked SOV template that only updates current-period numbers. Fewer typos, fewer "wait, that doesn't match last month" emails from the GC's PM, and pay apps that clear on the first submission instead of the second.

— Dave

How SubAscent fits into your billing workflow

SubAscent is built for the exact gap this article walks through: it keeps your Schedule of Values organized by job, syncs with QuickBooks so your billed amounts and job costs stay in agreement, and cuts the manual rebuilding that eats an afternoon every draw cycle. For a five-person electrical crew running three commercial jobs at once, that's the difference between a pay app that takes twenty minutes and one that takes two hours.

Subascent SubAscent's job billing dashboard showing SOV line tracking synced to QuickBooks.

If you're tired of rebuilding rollforward math by hand every month, see how SubAscent handles SOV and pay-app tracking and check whether it fits your current job load.

Where to check the official forms and features

Verify formats and rollout details directly: the AIA's own form library, QuickBooks' construction billing feature notes, and Subascent's guide to progress invoicing in QuickBooks for setup specifics.

Sources