QuickBooks Desktop QuickBooks Enterprise G702/G703 workflow

AIA Billing in QuickBooks Desktop & Enterprise

By the PayAppPro Construction Billing Team · Last reviewed July 2026

Quick answer:

No — QuickBooks Desktop and Enterprise do not produce AIA G702/G703 pay applications. They handle job costing, estimates, and progress invoicing well, but they don’t generate the G702 summary and G703 continuation sheet with prior-period rollforward, retainage, and stored materials that a GC’s reviewer expects. Most contractors keep Desktop for accounting and build the pay app package separately.

PayAppPro outputs are AIA-style only and are not licensed AIA documents. AIA®, G702®, and G703® are registered trademarks of the American Institute of Architects. QuickBooks, QuickBooks Desktop, QuickBooks Enterprise, and Intuit are trademarks of Intuit Inc. PayAppPro is not affiliated with or endorsed by Intuit.

Using QuickBooks Online instead? Read does QuickBooks do AIA billing?

What people usually mean when they ask this

Contractors searching for “AIA billing in QuickBooks Desktop” or “QuickBooks Enterprise AIA billing” are rarely asking a software trivia question. They are usually in one of three situations:

“We already run Desktop”

Years of job history, job costing, and payroll live in Desktop or Enterprise. Nobody wants to migrate. The question is really: can we keep this and still bill AIA-style?

“A GC just asked for a G702/G703”

The company has billed fine for years, then wins a job where the GC requires a formal pay application package. Desktop doesn’t have that button.

“Contractor Edition should do this”

Enterprise Contractor Edition adds construction reporting, so people reasonably expect pay apps to be in there. They aren’t.

The honest framing: the gap is not that QuickBooks is bad accounting software. The gap is that a pay application is a reviewer-facing billing package, not an accounting document — and no edition of QuickBooks was designed to produce one.

What QuickBooks Desktop & Enterprise can and can’t do

Where the accounting stops and the pay app package begins.

Task QuickBooks Desktop / Enterprise What the GC’s reviewer expects
Job costing & estimates Strong. Job costing is one of Desktop’s real advantages, and Enterprise Contractor Edition adds more construction reporting. Not what they review. Useful to you, invisible to them.
Progress invoicing Available — you can invoice a percentage against an estimate. An invoice is not a pay application. See progress billing vs pay apps.
G702 summary Not produced. No native AIA-style application and certificate for payment. A signed summary tying to the continuation detail.
G703 continuation sheet Not produced. No line-item continuation sheet with the expected columns. Scheduled value, previous applications, this period, stored materials, total to date, %, balance to finish, retainage.
Prior-period rollforward No native object carries “previous applications” forward line-by-line. Teams rebuild it monthly. This period must tie to last period exactly. Drift is what gets you rejected.
Retainage Can be tracked with setup and discipline, but usually needs manual handling. See retainage tracking. Held and released consistently, visible on every application.
Stored materials No dedicated pay-app treatment. Usually a spreadsheet column. Separated, documented, and not double-counted when installed.

Feature availability varies by QuickBooks edition, version, and year. Treat this as a workflow comparison, not a statement of Intuit’s current feature set.

Worth knowing: many Desktop shops fill this gap with a Desktop-integrated billing add-on such as Quantum Project Manager, which prints onto original AIA® documents and works well while your books stay on Desktop. The catch comes when your accountant moves you to QuickBooks Online — those Desktop integrations don’t follow. If that migration is on your horizon, see our Quantum Project Manager comparison.

Is AIA billing easier in Desktop or in QuickBooks Online?

This is the question people really want answered, and the honest answer is a little deflating: the pay app gap is the same in both. Neither product generates a G702/G703-style package. What changes is how you get billing data out of the system and into the package.

QuickBooks Desktop / Enterprise

  • Generally deeper job costing and estimate-based progress invoicing
  • Enterprise Contractor Edition adds construction-oriented reporting
  • Data tends to be more local; getting it out often means exports
  • Still produces no G702/G703 package

QuickBooks Online (QBO)

  • Easier to connect to other tools and keep values aligned
  • Generally lighter job costing than Desktop
  • Still produces no G702/G703 package
  • Details: QuickBooks AIA billing
The practical takeaway

Do not switch editions hoping the pay app problem disappears — it won’t. Choose the edition that fits your accounting and job-costing needs, then add the AIA-style pay app workflow on top of it.

Where Desktop teams usually get stuck

The failure pattern is almost always the same, and it isn’t a bookkeeping error. The accounting is usually correct. What breaks is the reviewer-facing rollforward.

The export-to-Excel spiral

Desktop exports a job report, someone rebuilds the G703 in Excel, and the spreadsheet becomes the real system of record. Next month it gets copied and edited. By period four, nobody is certain which file is current.

Change orders shift the SOV

An approved change order changes contract value and line items. The Desktop estimate and the Excel G703 drift apart, and the “to date” column stops tying to last month’s application. See billing change orders.

Stored materials move columns

Materials billed as stored have to move into completed work once installed, without being counted twice. Desktop has no view of this. See billing stored materials.

Retainage math diverges

Retainage held in the accounting file and retainage shown on the pay app start to disagree. See calculating retainage.

The result is predictable: the reviewer catches the drift and the application gets kicked back — even though QuickBooks was right the whole time. That is the core reason pay applications get rejected.

The workflow that actually works with Desktop

Keep your accounting where it is. Add the pay app package on top.

1

Keep Desktop as the books

Job costing, payroll, and the general ledger stay exactly where they are. Nothing migrates.

2

Build the pay app separately

Manage the Schedule of Values, prior billing, stored materials, change orders, and retainage in a tool built for pay apps.

3

Submit the AIA-style package

Produce the G702-style summary and G703-style continuation sheet that ties to the prior period.

4

Mirror the approved amount

Once approved, record the invoice in Desktop for the approved value so the books and the billing agree.

The one rule that prevents most problems
Decide whether submitted, approved, or invoiced is your accounting trigger — and never change it mid-project. Most “integration” problems are really workflow-definition problems.

Keep QuickBooks Desktop. Stop rebuilding the G703.

PayAppPro handles the AIA-style pay application package — the Schedule of Values, prior billing, stored materials, change orders, and retainage — so the rollforward carries itself forward each period instead of being rebuilt in a spreadsheet. Your accounting stays in Desktop or Enterprise.

The AI Quality Check reviews the package before you submit and flags tie-out issues, retainage drift, and missing backup — the things reviewers reject over.

FAQ: QuickBooks Desktop, Enterprise & AIA Billing

Short answers for contractors who don’t want to leave Desktop.

Not in the sense reviewers mean. QuickBooks Desktop can track jobs, costs, and invoices, and some editions include progress invoicing against an estimate. What it does not do is produce the AIA-style G702 summary and G703 continuation sheet, with prior-period rollforward, retainage, and stored materials laid out the way a GC’s reviewer expects to approve them.

QuickBooks Enterprise Contractor Edition adds construction-oriented reporting and job costing, which many contractors find useful. It is still an accounting product, so it does not generate an AIA-style G702/G703 pay application package. Most teams keep Enterprise for accounting and produce the pay app package separately.

Neither one produces AIA-style G702/G703 pay applications on its own, so the gap is the same in both. Desktop and Enterprise generally offer deeper job costing and progress invoicing against estimates, while QuickBooks Online is easier to connect to other tools. The practical difference is how you get billing data out, not whether the pay app problem goes away.

Progress invoicing against an estimate can get you a percentage-complete invoice, and that is genuinely useful for accounting. It is not the same as a pay application. A reviewer wants a line-item continuation sheet showing scheduled value, previous applications, this period, stored materials, total completed to date, percentage, balance to finish, and retainage, all tying back to the prior period.

No. The common approach is to keep QuickBooks Desktop or Enterprise as the accounting system of record and handle the AIA-style pay application package in a dedicated tool, then keep the invoice and the approved pay app amount aligned. You are adding the pay app workflow, not replacing your accounting.