# Construction Billing Software: How AIA G702 and Your Schedule of Values Build (or Break) Owner Trust

**By Dan Cumberland** · Published May 19, 2026 · Categories: AI Strategy

> Construction billing software is the most underused trust instrument on a project.  Every owner sees the G702.  Almost none of them feel they understand it.

## Why "Billing Software" Is the Wrong Frame

Construction billing software is the most underused trust instrument on a project\.  Every owner sees the G702\.  Almost none of them feel they understand it\.

Most $20M–$100M GCs treat billing as compliance work\.  Generate the pay app, file it, wait, follow up\.  The problem is that the owner experiences your billing process more often than any other interaction with your firm— more than your capabilities deck, more than your project executives, more than your superintendents on site\.

Three ways your billing reveals \(or hides\) firm character:

- **Format discipline\.** What contract type you offered and how you bill against it tells owners how you think about risk\.
- **Schedule of values craftsmanship\.** How you slice the SOV signals whether you're billing for compliance or communicating progress\.
- **Change\-order narrative\.** The way you describe scope changes is either a trust deposit or a withdrawal\.

A perfectly compliant pay app is the floor, not the ceiling\.  Before we audit the trust signal, let's be honest about what the standard AIA workflow actually shows— and hides\.

## What AIA G702 / G703 Actually Reveals \(and Hides\)

The AIA G702 is the one\-page Application and Certificate for Payment that summarizes a pay request\.  The G703 is the line\-item Continuation Sheet showing work completed, stored materials, and retainage against the schedule of values, per Autodesk[1](/blog/blog-construction-billing-software#ref-1)\.  Together they are the universal billing artifact at this scale— and they show owners only what the schedule of values categorizes, not what your firm's actual costs or judgment look like\.

The G703 line items are not your cost structure\.  They're a compressed projection of it, organized for an architect to certify, not for an owner to learn from\.

```html-table
<table><thead><tr><th>What the G702 / G703 Shows</th><th>What It Doesn't</th></tr></thead><tbody><tr><td>Percent complete by SOV line</td><td>Actual cost-to-complete</td></tr><tr><td>Stored materials value</td><td>Labor productivity vs. plan</td></tr><tr><td>Retainage held</td><td>Markup composition</td></tr><tr><td>Approved change orders</td><td>Bidding contingency assumptions</td></tr><tr><td>Net amount due</td><td>Trade-by-trade margin reality</td></tr></tbody></table>
```

The schedule of values is itself a strategic document\.  How you slice it determines what's visible\.  A 15\-line SOV protects margin and frustrates curious owners\.  A 60\-line SOV invites scrutiny and signals confidence\.  Neither is wrong\.  Both are choices\.

If owners can't see your cost structure, the next question is: what is your billing process actually communicating?  The 83\-day answer is bleak\.

## The 83\-Day Reality

Construction's average Days Sales Outstanding is approximately 83 days, materially worse than the roughly 60\-day cross\-industry average per the Construction Financial Management Association[2](/blog/blog-construction-billing-software#ref-2)\.  That's not a software problem\.  It's a system problem that software either accelerates or prolongs\.

The numbers around the 83 days are equally rough:

- ~83\-day construction DSO vs\. ~60\-day cross\-industry average \(CFMA\)[2](/blog/blog-construction-billing-software#ref-2)
- 82% of contractors face payment waits over 30 days, up from 49% two years prior, per industry estimates from DocJoist[3](/blog/blog-construction-billing-software#ref-3)
- 72% of subcontractors wait longer than 30 days for payment, per the same DocJoist estimate[3](/blog/blog-construction-billing-software#ref-3)
- Slow payments cost the U\.S\. construction industry an estimated $280 billion in 2024 \(industry estimate per DocJoist\)[4](/blog/blog-construction-billing-software#ref-4)

Translated to a $40M GC: roughly $9M tied up in receivables on any given day, financed at your line\-of\-credit rate\.  An 83\-day DSO is not a billing\-software failure\.  It's a structural feature of how construction sells, contracts, and bills— and software either accelerates the process or it gets blamed for it\.

DSO is a symptom\.  The disease lives upstream, in the billing format you chose before the first pay app went out\.

## Billing Format Is a Transparency Choice

Your contract type— lump sum, time and materials, GMP, or transparent lump sum— is the most consequential transparency decision on a project\.  And most GCs make it without naming the trust trade\-off\.

T&M maximizes owner visibility into labor, markup, and materials, with invoices that break down rates and costs line by line, per SmartBarrel[5](/blog/blog-construction-billing-software#ref-5)\.  Lump sum hides the cost build\-up but shifts overrun risk to you[5](/blog/blog-construction-billing-software#ref-5)\.  GMP is the hybrid: open book up to a cap, with a shared\-savings split below it\.  Transparent lump sum is the emerging compromise— it surfaces what the work would have cost under T&M, exposing risk premiums and inflated bids, per Management Controls[6](/blog/blog-construction-billing-software#ref-6)\.

```html-table
<table><thead><tr><th>Format</th><th>Owner Visibility</th><th>Contractor Risk</th><th>Best Fit</th></tr></thead><tbody><tr><td>T&M</td><td>High (rates, markup, materials)</td><td>Low (cost passes through)</td><td>Variable scope, sophisticated owner</td></tr><tr><td>Lump Sum</td><td>Low (percent complete only)</td><td>High (cost overruns are yours)</td><td>Well-defined scope, cost-certain owner</td></tr><tr><td>GMP</td><td>Medium-High (open book to cap)</td><td>Medium (capped)</td><td>Negotiated work, repeat owner</td></tr><tr><td>Transparent Lump Sum</td><td>High (T&M-equivalent visibility behind a fixed price)</td><td>Medium-High</td><td>Owners who want both certainty and trust</td></tr></tbody></table>
```

> **Transparency in billing is not a moral position\.  It's a strategic choice— selective and structured, not absolute\.**

Lump sum doesn't make you trustworthy\.  It makes you opaque\.  Whether opacity helps you depends on the owner, the relationship horizon, and whether the next job is repeat or competitive\.  Full transparency, meanwhile, gets gamed by sophisticated owners who use your numbers against you on the next bid\.  The real play is selective transparency: deliberate about what you reveal, deliberate about what you don't, and consistent across the firm\.

Format sets the frame\.  Inside the frame, the conversation owners actually want to have is about your markup\.

## The Markup Conversation You're Avoiding

General contractor markup typically lands between 20% and 30% in 2026, per Buildertrend[7](/blog/blog-construction-billing-software#ref-7), with experienced firms targeting 10–15% net margin after overhead and indirect costs, per Construction2Style[8](/blog/blog-construction-billing-software#ref-8)\.  Markup is not margin\.  And the gap between them is where most owner\-contractor trust gets won or lost\.

Markup pays for the firm\.  Margin is what's left after the firm pays itself\.  Owners conflate them\.  Sophisticated GCs explain the difference\.

```html-table
<table><thead><tr><th></th><th>Markup</th><th>Margin</th></tr></thead><tbody><tr><td>What it is</td><td>What you add to direct cost</td><td>What's left after all costs</td></tr><tr><td>What it covers</td><td>Overhead + risk + profit</td><td>Profit only</td></tr><tr><td>Owner perception</td><td>"That's your profit"</td><td>(Rarely discussed)</td></tr><tr><td>Healthy range</td><td>20-30% (GC range)<sup><a href="#ref-7" class="footnote-ref">7</a></sup></td><td>10-15% net target<sup><a href="#ref-8" class="footnote-ref">8</a></sup></td></tr></tbody></table>
```

Telling an owner your markup is a tactical decision\.  Refusing to even acknowledge it is a strategic mistake\.

Material and subcontractor markup varies widely by trade type and risk profile\.  Anyone who quotes you a single number is selling you something\.  The audit question that matters is closer to home: do your project executives and your finance team agree on what the firm's markup means, and how to discuss it with owners?  If they don't, every owner conversation is a Russian roulette of inconsistent answers\.

Discussing markup well requires a stack that produces clean, fast data\.  At your size, that stack has a specific shape\.

## The $20M–$100M Stack Reality

At $20M–$100M, the working stack is almost always Procore for project management plus a construction\-specific accounting system— typically Sage Intacct Construction or Foundation— because Procore has no native accounting, per Foundation Software[9](/blog/blog-construction-billing-software#ref-9)\.  Sage Intacct Construction integrates with Procore as a best\-in\-class accounting \+ project management stack for mid\-market contractors[10](/blog/blog-construction-billing-software#ref-10)\.  CMiC is usually the wrong choice at this size: implementations frequently exceed twelve months and the platform is not suited for firms under $50M[11](/blog/blog-construction-billing-software#ref-11)\.

Procore alone is not a billing solution at $20M\+\.  Procore plus the right ERP is\.

```html-table
<table><thead><tr><th>Firm Size</th><th>Working Stack</th><th>Why</th></tr></thead><tbody><tr><td>$20M</td><td>Procore + Foundation, or Sage 100 Contractor</td><td>AIA billing, certified payroll, job costing baseline</td></tr><tr><td>$50M</td><td>Procore + Sage Intacct Construction</td><td>Multi-entity, deeper financial reporting, Procore integration<sup><a href="#ref-10" class="footnote-ref">10</a></sup></td></tr><tr><td>$100M</td><td>Procore + Sage Intacct Construction (CMiC if JV/multi-entity dominant)</td><td>At this scale, integration depth begins to matter more than feature breadth</td></tr></tbody></table>
```

If your CMiC implementation is in month fourteen, the problem is not the software\.  It's the fit decision that was made eighteen months ago\.

For founders running through a stack decision under fire, our [decision frameworks for founders](/for-founders/) lay out the broader question of when to buy, when to integrate, and when to wait\.  At this scale, integration discipline matters more than feature breadth— which is the whole point of choosing a stack at all\.

A clean stack is the foundation\.  The next question— where AI actually helps— only makes sense once that foundation is real\.

## Where AI Actually Helps in Billing Today \(and Where It Doesn't\)

AI is genuinely useful in construction billing today in three places: anomaly detection across G703 line items, change\-order narrative drafting, and AR aging triage\.  It does not fix DSO, broken contracts, or owners who don't pay\.  Any vendor selling otherwise is selling hype\.

```html-table
<table><thead><tr><th>Use Case</th><th>Status</th><th>Why</th></tr></thead><tbody><tr><td>G703 anomaly detection</td><td>Real</td><td>Pattern matching across line items vs. prior pay apps surfaces issues a tired controller misses</td></tr><tr><td>Change-order narrative drafting</td><td>Real</td><td>Daily logs → auditable CO descriptions is a context-collapse problem AI handles well</td></tr><tr><td>AR aging triage</td><td>Real</td><td>Which collections call to make first is a ranking problem with clear inputs</td></tr><tr><td>Cutting DSO directly</td><td>Hype</td><td>DSO is a contract-and-financing problem, not a software problem</td></tr><tr><td>Replacing finance team judgment</td><td>Hype</td><td>The judgment is the job; AI augments it, doesn't replace it</td></tr><tr><td>"AI billing automation" without integration</td><td>Hype</td><td>If Procore and Sage don't talk to each other cleanly, AI just compounds the mess faster</td></tr></tbody></table>
```

AI is the second move in billing improvement, not the first\.  In practical terms: the first move is making sure your Procore and Sage actually talk to each other\.

The honest order of operations: integration first, data quality second, AI augmentation third\.  Most $20M–$100M GCs cannot get clean Procore \+ Sage integration working before they reach for AI— and the AI then gets blamed for problems that live one floor down\.  AI doesn't fix slow payment\.  It surfaces patterns your finance team didn't have time to notice\.

If mapping AI augmentation onto your existing stack is the next move, our [AI implementation services](/services/ai-implementation/) start there— with the integration audit, not the AI pitch\.  AI is intellectual augmentation, not artificial intelligence\.  People are still the answer\.  The job is to give your project executives and your finance team better instruments, not to replace their judgment\.

If this is starting to sound like a self\-audit, that's the point\.  Here's the 30\-day version\.

## A 30\-Day Audit of Your Billing Process

The audit is not a software replacement project\.  It's a one\-month review of five questions your finance leadership and project executives should be able to answer the same way— and usually can't\.

If your project executives and your CFO describe your markup differently, that's not a finance problem\.  It's a billing\-trust problem\.

1. **Format audit\.**  Across active jobs, what's the mix of lump sum, T&M, and GMP?  Is the mix intentional, or did it accumulate?
2. **G703 audit\.**  Pull three recent G703s\.  Could a sophisticated owner identify your firm's trust signal— or just your math?
3. **Markup audit\.**  Ask three project executives and your CFO to define markup and margin in writing\.  Compare answers\.  Don't coach\.
4. **DSO audit\.**  What is your trailing\-twelve\-month DSO?  How does it compare to the 83\-day CFMA benchmark[2](/blog/blog-construction-billing-software#ref-2)?  Where in the pay\-app cycle is the time leaking?
5. **Stack audit\.**  Where does data fall out of the Procore→Sage/Foundation integration?  What's manual that shouldn't be?  Walk through one full pay app from field log to deposit\.

If you want a structured way to run this against an [AI strategy audit](/services/ai-strategy/), the audit\-to\-implementation cadence is the same shape: five questions, four weeks, one ranked list of moves you can run yourself or hire out\.

An audit produces a list\.  The next move is deciding what to do about the list— and most of the useful answers come from running it, not from buying anything\.

## FAQ

### What is AIA billing?

AIA billing is industry\-standard progress billing using AIA G702 and G703 forms to document work completed, materials stored, and retainage on each pay application[1](/blog/blog-construction-billing-software#ref-1)\.  At $20M–$100M GCs, it is the universal pay\-app artifact\.

### What's a typical construction DSO?

Approximately 83 days per CFMA, substantially worse than the ~60\-day cross\-industry average[2](/blog/blog-construction-billing-software#ref-2)\.  The gap is structural, not a software failure\.

### Is Procore a complete billing solution?

No\.  Procore handles project management and pay\-app workflow but has no native accounting[9](/blog/blog-construction-billing-software#ref-9)\.  Mid\-market GCs typically pair it with Sage Intacct Construction[10](/blog/blog-construction-billing-software#ref-10) or Foundation\.

### What's a fair contractor markup?

20–30% is typical, with experienced firms targeting 10–15% net margin after overhead[7](/blog/blog-construction-billing-software#ref-7)[8](/blog/blog-construction-billing-software#ref-8)\.  Markup and margin are not the same thing\.

### When should I use T&M vs\. lump sum?

T&M for variable or undefined scopes \(maximum owner visibility\)[5](/blog/blog-construction-billing-software#ref-5); lump sum for well\-defined scopes \(cost certainty, more contractor risk\)[5](/blog/blog-construction-billing-software#ref-5)\.  Transparent lump sum is an emerging hybrid worth a serious look[6](/blog/blog-construction-billing-software#ref-6)\.

### Where do most billing disputes start?

Change orders are the primary cause of construction billing disputes, per SmartBarrel[12](/blog/blog-construction-billing-software#ref-12)\.

## The Billing Rate Conversation, Started

The billing rate conversation nobody has is the one between your project executives and your finance team about what your billing actually says to owners\.  Software doesn't start that conversation\.  Leadership does\.

Your G702 is what every owner sees\.  Your billing strategy is what only you can decide\.

If you want help running this audit without sitting through vendor pitches, [Dan Cumberland Labs](https://dancumberlandlabs.com) translates audit findings into an implementation plan you own\.

## References

1. Autodesk Construction, "A Guide to G702 and G703 Forms in AIA Billing" \(2024\) — [https://www\.autodesk\.com/blogs/construction/g702\-g703\-forms\-aia\-billing/](https://www.autodesk.com/blogs/construction/g702-g703-forms-aia-billing/)
2. Construction Financial Management Association \(CFMA\), via Construction Cost Accounting, "A Simple Guide to Days Sales Outstanding for Construction Business" \(2024\) — [https://www\.constructioncostaccounting\.com/post/simple\-guide\-to\-days\-sales\-outstanding\-dso](https://www.constructioncostaccounting.com/post/simple-guide-to-days-sales-outstanding-dso)
3. DocJoist, "Construction Payment Statistics 2026: Slow Pay, Lien Filings, and Cash Flow" \(2026\) — [https://www\.docjoist\.com/reports/construction\-payment\-statistics](https://www.docjoist.com/reports/construction-payment-statistics)
4. DocJoist, "Construction Payment Statistics 2026" \(2026\) — [https://www\.docjoist\.com/reports/construction\-payment\-statistics](https://www.docjoist.com/reports/construction-payment-statistics)
5. SmartBarrel, "Lump Sum vs Time and Materials: Deciding the Right Contract for Your Project" \(2024\) — [https://smartbarrel\.io/blog/lump\-sum\-vs\-time\-and\-materials/](https://smartbarrel.io/blog/lump-sum-vs-time-and-materials/)
6. Management Controls, "Transparent Lump Sum \| Optimize Cost Control and Visibility" \(2024\) — [https://managementcontrols\.com/mytrack\-platform/overview/transparent\-lump\-sum](https://managementcontrols.com/mytrack-platform/overview/transparent-lump-sum)
7. Buildertrend, "General Contractor Markup Explained" \(2026\) — [https://buildertrend\.com/blog/general\-contractor\-markup/](https://buildertrend.com/blog/general-contractor-markup/)
8. Construction2Style, "Is 30% Contractor Markup Normal? What It Covers & What's Fair" \(2024\) — [https://construction2style\.com/contractor\-markup\-30\-percent\-normal\-what\-it\-covers/](https://construction2style.com/contractor-markup-30-percent-normal-what-it-covers/)
9. Foundation Software, "Best Construction Accounting Software Options in 2026" \(2026\) — [https://www\.foundationsoft\.com/learn/best\-construction\-accounting\-software\-options\-in\-2026/](https://www.foundationsoft.com/learn/best-construction-accounting-software-options-in-2026/)
10. Sage, "Sage \+ Procore: Accounting & Construction Project Management Software" \(2026\) — [https://www\.sage\.com/en\-us/sage\-construction/procore/](https://www.sage.com/en-us/sage-construction/procore/)
11. Foundation Software, "Best Construction Accounting Software Options in 2026" \(2026\) — [https://www\.foundationsoft\.com/learn/best\-construction\-accounting\-software\-options\-in\-2026/](https://www.foundationsoft.com/learn/best-construction-accounting-software-options-in-2026/)
12. SmartBarrel, "Lump Sum vs Time and Materials" \(2024\) — [https://smartbarrel\.io/blog/lump\-sum\-vs\-time\-and\-materials/](https://smartbarrel.io/blog/lump-sum-vs-time-and-materials/)


---

Source: https://dancumberlandlabs.com/blog/construction-billing-software/