AIA Billing Night: How G702/G703 Processing Consumed Your Weekend and What to Do About It
Every month, the same marathon: collect sub pay apps, verify percentages, reconcile change orders, calculate retainage, assemble lien waivers, and pray the architect certifies it before the owner's payment cycle closes.
James Wright
Construction Technology Consultant
Direct Answer
Every month, the same marathon: collect sub pay apps, verify percentages, reconcile change orders, calculate retainage, assemble lien waivers, and pray the architect certifies it before the owner's payment cycle closes. Typical workflow steps include Sub pay app collection and tracking, Schedule of Values update and reconciliation, and Supporting document assembly.
Best Fit
Construction teams coordinating work across Sage, QuickBooks, and Procore.
Workflow Covered
Sub pay app collection and tracking, Schedule of Values update and reconciliation, and Supporting document assembly
Outcome
Reduces manual work across sub pay app collection and tracking, schedule of values update and reconciliation, and supporting document assembly.
Why Neudash fits this workflow
Exact Logic
Neudash writes code for the specific rules, exceptions, approvals, and edge cases in this process instead of forcing it into a fixed flowchart.
Open-Ended Integration
Built-ins are only the start. Neudash can connect the systems in this stack through APIs, webhooks, and OAuth, so the workflow is not capped by a marketplace action list.
Durable Execution
The running workflow is code. AI is used to design, document, and repair the process, and only used inside the workflow where reasoning or extraction is actually needed.
It is the last Thursday of the month. For most people, this is an ordinary day. For a construction project manager named Karen who runs three active commercial projects for a mid-size GC in Atlanta, this is billing night. And billing night is going to consume her Thursday evening, most of Friday, and a portion of Saturday morning.
I know this because I sat next to Karen through an entire billing cycle as part of a workflow assessment. What I witnessed was not inefficiency — Karen is sharp, organized, and fast. What I witnessed was a process that was designed in an era of carbon paper and typewriters, administered using tools that were not built for it, and held together by the sheer force of one person’s willpower and institutional knowledge.
This is what a single monthly billing cycle looks like, step by step, on one of Karen’s three projects.
Thursday, 5:00 PM: The Collection Phase Begins
AIA G702/G703 forms are contractually required on most commercial projects over $500K
AIA Contract Documents
The average GC spends 2-3 full days per project per month on the billing cycle
Sage Construction Industry Survey
82-day average Days Sales Outstanding in construction — every day of billing delay extends the collection timeline
CFMA Financial Benchmarker
5-10% retainage is withheld from each progress payment, requiring separate tracking and release calculation
AIA A201 General Conditions
Karen’s billing cutoff is the 25th of each month. That means all work performed through the 25th can be included in this month’s pay application. By the 25th, she needs every subcontractor’s pay application in hand, verified, and incorporated into the master billing.
She sent the first reminder email on the 15th — ten days before cutoff. “Monthly pay apps due by the 23rd. Please submit your application reflecting work through the 25th, along with conditional lien waivers for the current period and unconditional lien waivers for the prior period’s payment.”
By the 20th, she has received pay applications from 4 of the 14 subcontractors on this project. The mechanical sub, the electrician, the drywall contractor, and one of the two concrete subs. The other ten have not responded.
She sends a second reminder on the 20th. By the 22nd, she has 9 of 14. She spends Thursday morning on the phone calling the remaining five: the roofer (promises to have it by end of day), the painting sub (did not realize it was due), the fire protection contractor (their office manager is on vacation), the structural steel erector (submitted theirs to the wrong email address two days ago), and the sitework sub (wants to discuss a disputed back-charge before submitting).
By Thursday at 5 PM, she has 12 of 14 applications. The painting sub’s application arrives at 7:30 PM. The fire protection contractor’s application will not arrive until Friday morning.
Friday, 7:00 AM: Verification and Reconciliation
Karen starts verifying each subcontractor’s pay application against her own field observations and the approved Schedule of Values.
The mechanical sub claims 65% complete on the ductwork installation. Karen was on site Tuesday and estimates it at closer to 58%. She calls the mechanical foreman to discuss. They agree on 61% after walking through the building areas where work has been completed. Karen adjusts the number.
The electrician’s pay application includes a line item for a change order that Karen has not seen approved. She checks the change order log — the CO was submitted three weeks ago and is still pending architect review. She cannot bill for unapproved change order work. She removes the line item and calls the electrician’s office to explain why the billing amount is lower than what they submitted.
The drywall contractor’s application references stored materials — $18,000 in drywall board delivered to the site but not yet installed. Karen needs the material invoice and a photo of the stored materials to support billing for stored materials. She emails the drywall contractor requesting both documents.
The sitework sub’s application does not include the retainage adjustment for the phase of work they completed last month. Karen recalculates the retainage release amount and adds it to the master billing.
This verification process takes roughly four hours for one project. Karen has three projects. She will do this for the other two projects on Saturday.
Friday, 1:00 PM: The G703 Update
With verified numbers in hand, Karen updates the G703 Continuation Sheet — the Schedule of Values that tracks every line item of the contract.
This project has 47 line items on the G703, plus 6 approved change orders that were added as supplementary line items. For each line item, Karen enters:
- Work completed this period (the dollar amount of work done in the current billing month)
- Materials presently stored (materials on site or in bonded storage not yet installed)
- Total completed and stored to date (cumulative billing)
- Percentage complete (total billed divided by scheduled value)
- Balance to finish (contract amount minus total billed)
- Retainage (5% of total billed, per the contract terms)
Karen does this in a spreadsheet. Some GCs use Sage’s billing module. Some use Procore’s prime contract billing tool. Karen uses an Excel template because she has used it for twelve years and it has never failed her.
The spreadsheet calculates the G702 summary automatically: total contract value including change orders, total completed and stored to date, retainage held, previous certificates for payment, and the current payment due.
This month’s application: $387,000 net, after deducting $20,368 in retainage and $2.1 million in prior billings.
$18,000-$36,000
per year per PM
Annual cost of the manual billing cycle for one project manager handling 3 projects: 6-9 days per month at $250-$400/day loaded PM cost, plus indirect costs of delayed billing, collection delays from documentation gaps, and overtime
AIA Progress Billing Automation
Friday, 3:00 PM: The Supporting Document Package
The pay application is not just the G702/G703. The architect and owner require a supporting document package that typically includes:
Conditional lien waivers from every subcontractor for the current period’s billing. These state that the sub waives lien rights for work billed in this period, conditional on receiving payment. Karen has waivers from 10 of the 14 subs. She needs to chase the other four.
Unconditional lien waivers from every subcontractor for the prior period’s payment (the payment they received last month). These confirm that the sub was paid and unconditionally waives lien rights for that period. Three subs have not submitted their unconditional waivers because — Karen discovers with two phone calls — they have not actually received last month’s payment yet. The owner’s AP department is running behind.
Stored material documentation. The drywall contractor sent the material invoice but not the photo. Karen emails again. The HVAC sub has $42,000 in equipment stored at their warehouse — Karen needs a photo and a letter confirming the materials are dedicated to this project and stored in a secure location.
Progress photos. Karen selects photos from the job site folder that support the percentage-complete claims in the pay application. She needs photos showing the mechanical rough-in progress, the drywall completion areas, and the exterior envelope status.
Change order backup. For each approved change order billed this period, Karen includes a copy of the executed CO document and any relevant backup (T&M tags, architect direction letters, owner approvals).
Assembling this package takes two hours. Most of that time is spent tracking down lien waivers from subcontractors who treat them as an afterthought.
| Aspect | Manual Process | With Neudash |
|---|---|---|
| Sub pay app collection | PM sends reminder emails, follows up individually by phone over 5-7 days | Automated reminders at 10/7/3 days before cutoff, real-time tracking dashboard showing who has submitted |
| Percentage verification | PM compares sub claims against field observations from memory or notes | Sub claims flagged against last month's percentage plus superintendent's field progress data |
| G703 update | Manual entry of 40-60 line items into Excel spreadsheet, manual retainage calculations | Verified sub billing data auto-populates continuation sheet, retainage calculated per contract terms |
| Lien waiver collection | PM chases waivers from each sub individually, tracks which are missing on a notepad | Automated waiver requests sent with pay app reminders, missing waivers flagged on submission tracking sheet |
| Architect submission | PM compiles PDF package manually, emails to architect, tracks response via email | Complete package auto-compiled and submitted, certification status tracked with follow-up reminders |
Saturday, 9:00 AM: The Weekend Tax
Karen is at home with her laptop. She is doing the billing for her second project — another 14 subcontractors, another 52 line items on the G703, another round of verification calls and lien waiver collection. She will finish this project by noon and start the third project after lunch.
Karen’s spouse asks if she is coming to their daughter’s soccer game at 2 PM. Karen says she will try.
This is AIA billing night. It happens every month. It consumes 2-3 days of a skilled project manager’s time per project. For a PM running three projects, that is 6-9 days per month — nearly half the working month — spent on billing administration rather than project management, quality control, or the kind of proactive coordination that actually prevents problems.
And the billing cycle is not even over. After Karen submits the pay applications to the architects on Monday, she will wait 5-10 business days for certification. She will field questions from the architects about specific line items. She will deal with the architect on Project 2 who always disputes the mechanical sub’s percentage-complete claims. She will track whether the certified applications have been forwarded to the owners’ AP departments. And she will start the collection follow-up for pay applications that were certified last month but have not yet resulted in a check.
Pro Tip
The biggest time savings in progress billing is not in the G703 calculations — those are mechanical and spreadsheets handle them fine. The biggest savings is in sub pay app collection and lien waiver tracking. These two tasks account for 60-70% of the PM’s billing time and they are entirely about chasing documentation from people who do not prioritize it. Automate the reminders, automate the tracking, and automate the follow-up. When a subcontractor knows that a system will send them three reminders and then flag them to the superintendent as non-compliant, the pay apps start arriving on time. The PM’s role shifts from document chaser to document reviewer — which is what they should have been doing all along.
The Automation That Gets Karen Her Saturdays Back
The monthly billing cycle has three phases that can be substantially automated: collection, compilation, and tracking. The fourth phase — verification of percentage complete — requires human judgment and field knowledge. Automation does not replace the PM’s expertise in reviewing what work has actually been done. It replaces the 60-70% of the billing cycle spent on administrative coordination.
What Sage, QuickBooks, and Procore Handle in Billing
Sage 300 Construction and Real Estate is purpose-built for construction billing. Its Accounts Receivable module handles AIA-format billing, Schedule of Values management, retainage tracking, and integration with the job cost ledger. For contractors using Sage, the G703 update itself is well-handled within the system. The gap is everything around the system — the sub pay app collection, the lien waiver tracking, the supporting document assembly, and the architect certification follow-up all happen outside Sage via email and phone calls.
QuickBooks handles basic invoicing but does not natively support AIA-format billing, Schedules of Values, or retainage tracking. Most contractors using QuickBooks for billing maintain a separate Excel spreadsheet for the G703 and manually enter the billing totals into QuickBooks for accounting purposes. This creates a reconciliation burden and a risk of discrepancy between the billing records (in Excel) and the accounting records (in QuickBooks).
Procore provides a prime contract billing module that handles Schedule of Values, progress billing, and change order integration. For contractors on Procore, the G703 update can be done within the platform, and subcontractor pay apps can be collected through Procore’s subcontractor billing tools. The limitation is subcontractor adoption — the pay app collection workflow only works if the subs actually submit through Procore. For subs who email their pay apps as PDF or Excel attachments (the majority of small subs), the data still needs to be manually entered into Procore.
Buildertrend handles progress billing well for residential builders with its draw schedule and payment tracking features. The workflow is simpler than commercial AIA billing — typically a percentage-based draw schedule rather than a line-by-line Schedule of Values — but the core problem of tracking what has been billed, what has been paid, and what retainage is owed applies equally.
The common gap across all these tools is the connective tissue: the reminders that go out to subs, the tracking of who has submitted and who has not, the collection of lien waivers that every sub treats as an afterthought, and the follow-up with the architect that determines whether you get paid this month or next month. That connective tissue is email-based workflow, and it is precisely the kind of repetitive, deadline-driven, multi-party coordination that automation handles better than humans.
The Monthly Billing Calendar: A Day-in-the-Life View
To understand where automation creates value, here is the monthly billing calendar with and without automation:
Day 1 (15th of month) — Notification:
- Without automation: PM sends reminder email to subs, sometimes forgets a project, sometimes sends it on the 17th because the 15th was busy.
- With automation: System sends personalized reminders to all subs on all projects at 8:00 AM, including project-specific requirements and deadlines.
Day 5 (20th) — First follow-up:
- Without automation: PM realizes some subs have not submitted, starts making phone calls between other tasks.
- With automation: System identifies non-responders and sends follow-up with CC to superintendent. PM receives a dashboard showing submission status.
Day 7 (22nd) — Final follow-up:
- Without automation: PM escalates to superintendent for the last holdouts, makes urgent calls.
- With automation: System sends final urgent reminder. PM focuses only on the 1-2 subs who consistently submit late, instead of chasing all of them.
Day 8-9 (23rd-24th) — Verification:
- Without automation: PM reviews each sub’s application, manually cross-references with field observations and last month’s billing.
- With automation: System flags anomalies (percentage jumps over 15 points, amounts exceeding remaining contract balance) for PM review. PM focuses on the flagged items rather than reviewing every line item.
Day 10 (25th) — Compilation:
- Without automation: PM manually updates G703, assembles supporting documents, identifies missing lien waivers and stored material documentation.
- With automation: System compiles billing data from approved sub applications, generates a checklist of missing documents, and drafts the package summary for PM review.
Day 11-12 (26th-27th) — Submission and tracking:
- Without automation: PM emails completed package to architect, adds a mental note to follow up.
- With automation: System submits package and starts the certification tracking timer. PM receives a notification when the architect opens the submission.
The PM’s time in this automated workflow drops from 2-3 days per project to approximately 4-6 hours per project — most of it spent on the verification step, which is the part that actually requires their expertise. The collection, compilation, and tracking phases — which represent the majority of the manual effort — run on autopilot.
What Karen’s Saturday Looks Like Now
Karen does not do billing on Saturdays anymore. Her billing cycle starts automatically on the 15th. By the 23rd, she has a submission tracking dashboard showing which subs have submitted, which are outstanding, and which submissions have been flagged for review. She spends Thursday afternoon on verification — the part of the process that requires her project knowledge and professional judgment. Friday morning is compilation and submission. Friday afternoon she reviews the second project. Monday morning, the third.
Total billing time: roughly 15 hours per month across three projects, down from 50-plus hours. The quality of the billing is better because Karen is not rushing through verification at 10 PM on Thursday to hit a Friday submission deadline. The submissions are more complete because the automated reminders and follow-ups ensure that subcontractors submit on time — or are flagged early enough that Karen can intervene before the deadline passes.
Karen went to the soccer game. Her daughter scored two goals. Karen did not check her email once.
That is what progress billing automation is actually about. Not replacing the project manager. Not eliminating the AIA forms that the industry relies on. Just removing the 60-70% of the process that consists of chasing paper, entering data, and tracking deadlines — so the people who manage construction projects can spend their time managing construction projects.
Tools Referenced
Frequently Asked Questions
What is the AIA G702/G703 and why does it matter?
The AIA G702 (Application and Certificate for Payment) and G703 (Continuation Sheet) are standardized forms published by the American Institute of Architects that are used on most commercial construction projects for monthly progress billing. The G703 is the Schedule of Values — a line-by-line breakdown of the contract amount by work item. Each month, the contractor updates the percentage complete and dollar amounts for each line item on the G703, which feeds into the G702 summary showing the total amount billed to date, retainage withheld, and net amount due. The architect reviews and certifies the application before the owner processes payment. These forms are contractually required on most commercial projects and are the primary mechanism for cash flow.
How long does a typical monthly billing cycle take for a GC?
For a general contractor managing 3-5 active projects with 10-15 subcontractors each, the monthly billing cycle typically consumes 2-3 full days of a project manager's time per project. This includes: collecting subcontractor pay applications (3-5 days of follow-up), verifying percentage-complete claims against field observations (2-4 hours per project), incorporating approved change orders into the Schedule of Values (1-2 hours), calculating retainage and adjusting for any releases (1 hour), collecting conditional lien waivers from subs (2-3 days of follow-up), assembling stored material documentation (1-2 hours), compiling the complete package for architect review (2-3 hours), and tracking architect certification (ongoing). Most of the PM's time is spent chasing documentation from subcontractors, not on the actual billing calculations.
What happens when a billing deadline is missed?
Missing a billing deadline — either the contractual cutoff date for submitting the pay application or the architect's review window — pushes the entire payment to the next billing cycle. On an 82-day average DSO, this effectively means waiting an additional 30 days for payment on work already completed. For a GC billing $300,000-$500,000 per month per project, a missed deadline means carrying an extra month of unbilled work. At 8% cost of capital, that is $2,000-$3,300 in financing costs per missed deadline, plus the cash flow strain of covering payroll and material costs for an additional 30 days without revenue.
AIA billing takes my office manager an entire day. Why?
Because the data needed for one pay app usually lives across subcontractor emails, field status, stored materials, retainage math, and lien waiver collection. Neudash can run a monthly billing process that requests pay apps, checks for missing lien waivers and backup, updates the billing register, and alerts the PM before the cutoff is missed.
Stop copying data between tools.
Describe this workflow in plain English. Neudash writes the code, connects the tools involved, runs it on schedule, and repairs routine failures when something changes.
About James Wright
Construction Technology Consultant
Licensed builder turned technology consultant. Spent 15 years on job sites before helping trades businesses adopt better systems. Understands why contractors resist software — and how to make it work for them.