Construction Invoicing: How To Manage Invoices Across Projects and Phases

Construction invoicing across multiple projects or phases requires three things most GCs and owners get wrong, including a consistent cost-code structure before the first invoice arrives, a clear allocation method for shared vendor costs, and a system that ties every approved invoice to the draw package automatically. 

Manual allocation on a five-project portfolio with 15 subs per project produces a 3%-5% error rate, and one miscoded invoice can delay an entire draw cycle. Platforms like Built cut invoice-to-payment time from 53 days to 26 days by automating cost-code extraction and draw assembly.

What Is Construction Invoicing and Why Is It Different?

Construction invoicing isn’t retail billing. A general contractor running five active projects doesn’t send one invoice and collect a check. Each project has its own budget, its own cost codes, its own lender requirements, and its own payment schedule. An invoice that arrives on a Tuesday might touch three different cost codes, two different phases, and a retainage holdback that won’t release for 90 days.

That complexity is the baseline. On top of it, every invoice has to connect to a draw request before anyone gets paid. The draw is what releases capital from the lender to the owner to the GC to the sub. If the invoice doesn’t match the draw, the draw stalls. If the draw stalls, the sub waits. If the sub waits long enough, the project feels it.

Compare that to standard business invoicing. A SaaS company sends an invoice, the client pays net-30, and the transaction is done. No cost-code allocation. No lien waiver exchange. No lender review. Construction invoicing carries the weight of compliance, allocation, and multi-party approval that most industries never touch.

The core difference comes down to three things. First, invoices must map to a budget and a schedule of values, not just a purchase order. Second, every invoice is part of a larger draw package that includes waivers, inspection reports, and compliance documentation. Third, payment depends on approval from parties the GC may never meet (the lender, the title company, the fund administrator).

For general contractors managing construction billing processes, that means a single miscoded invoice blocks capital from moving.

Types of Construction Invoices and Billing Methods

The billing method dictates the invoice format, the supporting documentation, and how much back-and-forth happens before payment clears. Choosing the wrong method for a project type creates friction at every pay cycle.

Progress billing and AIA G702/G703

Progress billing is the standard for commercial construction. The subcontractor or GC submits an Application and Certificate for Payment (AIA G702) with a Continuation Sheet (AIA G703) that breaks the contract into line items, shows the percentage completed, and calculates the amount due for that period.

The G702 is the summary. It shows the original contract sum, approved change orders, total completed to date, retainage, and the current payment due. The G703 is the detail. Each line maps to a specific scope of work with its scheduled value, previous billings, current work completed, materials stored, and the balance to finish.

This format matters because lenders require it. Most construction loan agreements reference AIA documents as the standard for draw requests. When a GC submits a draw, the lender’s analyst compares the G703 line items against the inspection report and the budget. Mismatches create questions. Questions create delays.

The discipline here is consistency. Every sub needs to bill against the same schedule of values that was approved at contract execution. When a sub submits a G703 that doesn’t match the original breakdown, the GC has to reconcile before the draw goes out.

Time and materials vs. cost-plus invoicing

Time and materials (T&M) billing charges for actual labor hours and material costs, plus a markup. The invoice includes hourly rates, hours worked, material receipts, and the agreed markup percentage. Cost-plus works similarly but applies to the full project cost rather than individual tasks.

T&M invoices require more documentation than progress billing. Every line needs backup. Timesheets, material receipts, equipment logs. Without that backup, the owner or lender will reject the invoice or hold payment until documentation arrives.

The risk with T&M on multi-project portfolios is tracking. When a crew works across two projects in the same week, the invoice has to split hours accurately between them. A concrete crew that pours foundations on Project A Monday through Wednesday and Project B Thursday and Friday needs separate billing entries, not a blended total.

Cost-plus billing adds another layer. The “cost” portion requires verified actual expenses, and the “plus” portion (usually a fixed fee or percentage) has to reconcile against the contract terms. Owners and lenders audit these invoices more heavily because the contractor’s profit isn’t locked into a fixed price.

Lump sum and unit price billing

Lump sum contracts set a fixed total price. Invoicing is straightforward. The sub bills a percentage of the fixed price based on completion. The challenge is proving completion. Without a clear schedule of values, “50% complete” is a judgment call that the owner, GC, and lender may each see differently.

Unit price billing charges per unit of work (per cubic yard of concrete, per linear foot of pipe, per square foot of drywall). Each invoice includes the quantity installed, the unit rate, and the total. This method works well for site work and utilities where quantities are measurable but hard to predict at bid time.

Both methods require the GC to validate quantities or completion percentages before including them in a draw. On a multi-phase project, the GC also needs to allocate each invoice to the correct phase and cost code. A lump sum drywall invoice on a mixed-use project might need to split between the residential phase and the commercial phase based on the square footage installed in each.

How to Split Invoices Across Projects or Phases

Spreadsheets don’t have an error rate problem. They have a discovery problem. The miscoded invoice doesn’t show up until the draw gets rejected.

That’s the real cost of manual invoice splitting. The error is quiet. It sits in a spreadsheet cell until a lender’s analyst catches it, sends the draw back, and adds a week to the payment cycle.

Here’s a concrete example. A $25M mixed-use development with 12 subs, 8 trades, and a 30-day payment cycle. The GC receives 40 to 60 invoices per month. Ten of those touch multiple phases (foundation, vertical, envelope). Three come from vendors who serve all phases (the concrete supplier, the equipment rental company, the safety consultant). Every one of those shared invoices needs to split correctly before the draw goes out.

Allocating by cost code

Cost codes are the foundation of accurate invoice allocation. Every project should have a standardized cost-code structure established before the first invoice arrives. The Construction Specifications Institute (CSI) MasterFormat is the most common framework, but what matters more than the framework is consistency across projects.

When a sub submits an invoice for $85,000 in concrete work, the GC needs to know whether that’s $50,000 against 03 30 00 (Cast-in-Place Concrete) on Project A and $35,000 against the same code on Project B. If the cost-code structure differs between projects, reconciliation becomes manual, slow, and error-prone.

The discipline is front-loaded. Every subcontract should reference the project’s cost-code structure, and every invoice should include the cost code. When an invoice arrives without a code, it goes back before it enters the system. Fixing it later is always more expensive than catching it at the door.

Splitting shared vendor invoices

Shared vendors are the hardest allocation problem in multi-project invoicing. A crane rental company doesn’t send separate invoices for each project. They send one invoice for the month. The GC has to split it.

Three allocation methods work in practice. First, there’s direct measurement. If the crane was on Project A for 12 days and Project B for 8 days, this should split by days. Second, square footage or scope-based allocation means dividing the invoice proportionally by the scope each project represents. Third, contractual allocation involves establishing the split percentage in the vendor agreement before work starts.

The mistake most GCs make is allocating by feel. A project manager estimates that “about 60%” of the crane time went to Project A, codes it that way, and moves on. That estimate compounds across every shared vendor, every month. By the third draw cycle, the cumulative allocation error can shift tens of thousands of dollars between project budgets.

Reconciling allocations at month-end

Month-end reconciliation is where allocation errors surface, or don’t. The process requires comparing every invoice’s cost-code assignment against the project budget, the draw request, and the general ledger.

For GCs running multiple projects, reconciliation means checking that the total invoiced across all projects for a shared vendor equals the vendor’s actual invoice. If the concrete supplier billed $120,000 for the month, and the GC allocated $75,000 to Project A, $30,000 to Project B, and $20,000 to Project C, that’s $125,000. The $5,000 overage needs to be found and corrected before the draw goes out.

The reconciliation also catches timing mismatches. An invoice coded to April’s draw might cover work completed in March. Without a disciplined cutoff process, the same work can appear in two consecutive draws or disappear from both.

When the reconciliation is clean, the draw packages assemble faster, lenders approve faster, and subs get paid faster. When it isn’t, the entire payment chain slows down.

Common Construction Invoicing Mistakes That Delay Payment

Most payment delays in construction start with a data error three steps upstream. The invoice was coded wrong, the waiver was missing, or the draw package didn’t match the lender’s format.

Miscoded cost allocations across projects

The most common invoicing mistake is also the quietest. A sub’s invoice gets coded to the wrong project or the wrong cost code. It doesn’t look wrong on the surface. The dollar amount is right. The vendor is right. But the allocation sends $40,000 to Project B’s budget when it belongs on Project A.

This shifts the budget variance on both projects. Project A looks like it’s under budget (it isn’t). Project B looks like it’s over (it isn’t). The error compounds when the draw goes to the lender. The lender’s analyst compares the draw against the inspection report and the budget. The numbers don’t match. The draw comes back with questions.

Every error in a draw package triggers a lender question, then a resubmission, then more days on the clock. A draw that should clear in three days clears in ten. On a $50M project at 6% interest, every week of draw delay costs $5,800.

Missing lien waivers that block the draw

A lien waiver is a legal document where the sub or supplier confirms they’ve been paid and waive the right to file a lien against the property. Most lenders won’t fund a draw without conditional or unconditional waivers from every sub who received payment in the prior period.

The problem is tracking which waivers are outstanding, chasing them down, and matching them to the correct pay period. On a project with 15 subs, that’s 15 waivers per draw cycle. One missing waiver holds the entire draw.

Lien waiver laws vary by state. Some states require specific statutory forms. Some require notarization. Some have deadlines that, if missed, eliminate the right to lien entirely. The GC’s job is to know which rules apply and ensure compliance before the draw goes out. When in doubt, you should consult qualified legal counsel in the project’s jurisdiction.

Invoice-to-draw disconnects

The draw package is an assembly of invoices, waivers, inspection reports, and budget comparisons. When the invoices don’t tie to the draw, the package falls apart.

The most common disconnect is a timing mismatch. The GC approves invoices on a rolling basis but assembles the draw on a fixed schedule. An invoice approved on the 28th might not make it into the draw assembled on the 25th. The sub expects payment based on the invoice approval date. The lender funds based on the draw submission date. The gap creates confusion and delays.

Another disconnect happens when invoice line items don’t map cleanly to the draw’s schedule of values. The sub billed for “rough plumbing, second floor,” but the schedule of values has “plumbing” as a single line item across all floors. The GC has to translate, and translation introduces error.

The fix is structural. Align the invoice approval cycle with the draw assembly schedule. This means requiring invoice line items to match the schedule of values exactly and building the draw from approved invoices, not from manual data entry.

What Subcontractors Need to Know About Construction Invoicing

For subs, the invoicing process often feels like a black box. You submit the invoice, and then you wait. Understanding what happens on the other side helps subs get paid faster and avoid the mistakes that push invoices to the bottom of the stack.

The first rule is format compliance. If the GC requires AIA G702/G703 format, it should be submitted in that format. If the contract specifies cost codes, they should be included on every line item. If the GC requires backup documentation (timesheets, material receipts, delivery tickets), it should be attached with the invoice, not after someone asks for it.

The second rule is waiver readiness. This means knowing which waivers the GC needs and having them ready to sign before the draw cycle starts. Conditional waivers (signed before payment is received) and unconditional waivers (signed after payment clears) serve different purposes and different draw cycles. Signing the wrong type at the wrong time creates compliance problems.

Sub-tier visibility matters too. On larger projects, the GC and the owner need to see not just the sub’s invoices but the sub’s payment status to their own vendors and lower-tier subs. This isn’t just curiosity. Unpaid lower-tier subs can file liens against the project, even if the GC paid the prime sub in full. Many GCs now require lower-tier lien waivers as part of the draw package.

What subs see in the process depends on the GC’s system. On a well-run project, the sub can track invoice status, see when the draw is submitted, know when funding is expected, and sign waivers electronically. On a poorly run project, the sub submits a PDF and hears nothing until the check arrives (or doesn’t).

For example, Waltz Construction reduced compliance documentation time by 1-2 hours per cycle by giving subs a clear, digital workflow for invoices and waivers. The payoff wasn’t just internal. Subs who know where they stand in the payment cycle are subs who show up on time and prioritize your project.

For closeout, subs should prepare final waivers, AIA G706 Contractor’s Affidavit of Payment, and any required warranty documentation well before the last draw. Closeout delays often come from missing sub documentation, not from unfinished work.

How to Choose Construction Invoicing Software

The right invoicing platform connects every invoice to a cost code, a budget line, a draw package, and a payment. The wrong one adds a login without removing the spreadsheet.

Before evaluating features, it’s necessary to define the problem. Is the bottleneck invoice collection (subs sending PDFs by email)? Invoice coding (manually assigning cost codes)? Draw assembly (compiling invoices, waivers, and compliance docs into a package)? Payment tracking (knowing which subs have been paid and which waivers are outstanding)?

Most GCs running multiple projects have all four problems. The question is which one hurts the most right now.

Must-have features for multi-project GCs

For GCs managing three or more active projects, the following features separate functional software from digital paperwork:

• Cost-code extraction: The system reads the invoice and maps line items to the project’s cost-code structure without manual entry.
• Multi-project allocation: One invoice can split across projects or phases with a clear audit trail.
• Lien waiver tracking: Automated waiver requests tied to payment status, with state-specific form compliance.
• Draw package assembly: Approved invoices, waivers, and supporting documents compile into a lender-ready package.
• Sub portal: Subs submit invoices, sign waivers, and track payment status in one place.
• Budget comparison: Real-time visibility into invoiced-to-date vs. budgeted amounts by cost code and project.

A free construction invoice template can help standardize what subs submit, but the template doesn’t solve the allocation, compliance, or draw assembly problems. That requires a connected system.

Integration with your ERP and PM tools

No invoicing platform should replace the ERP. The accounting system of record (Sage Intacct, Sage 300, QuickBooks, Yardi, CMiC, Vista) is where the general ledger lives. The invoicing platform’s job is to sit in front of the ERP, validate and approve transactions, and push only clean data downstream.

The integration checklist includes cost-code mapping between systems, automatic journal entry creation, two-way sync on payment status, and retainage tracking that matches the ERP’s methodology.

For GCs using Procore for project management, the invoicing platform should complement Procore’s field operations with financial workflows. Procore handles RFIs, submittals, schedules, and field reports. The financial layer handles invoices, waivers, payments, and lender connectivity. The two systems should share project data without duplicating entry.

How Built Manages Construction Invoicing from Invoice to Draw

Built is the front door to your ERP. We don’t replace Sage, Yardi, or QuickBooks. We sit between the project and the accounting system, making sure every invoice is coded, approved, and tied to a draw before it touches the general ledger.

Here’s how it works. A sub submits an invoice through the portal. Our AI reads the invoice, extracts cost codes, and maps line items to the project budget. The project manager reviews and approves. The approved invoice flows into the draw package with the matching lien waivers and compliance documentation. The draw goes to the lender. The lender funds. The sub gets paid.

That workflow cuts invoice-to-payment time in half. Its AI Invoice Ingestion handles cost-code extraction 51% faster than manual processing. Its AI Draw Assembly produces lender-ready packages 67% faster than manual compilation. Project accountants save 20-25 hours per week on invoicing, coding, and draw preparation.

Another example comes from Janna Ryan, CFO of John Kraemer & Sons, who put it this way: “Built is very cost effective in the time saved but more importantly in eliminating potential errors in billings from the subcontractors. The subcontractors are getting paid faster which is an added bonus.”

That sub experience matters. Built sees an 85% or higher subcontractor adoption rate on the platform, and 95% of subs report it’s “very easy to use.” When subs adopt the platform, waivers come back faster. Rod Heisler Construction uses its invoice-to-waiver workflow to maintain full sub-tier visibility across every project. Lien waivers that used to take 15-30 minutes to track down now complete in under four minutes.

Built connects to 300+ lenders across the platform and supports $317B or more in real estate dollars. The network effect means your lender likely already knows the format, which means fewer questions and faster funding.

Built integrates with Procore for field operations and with your ERP for accounting. Procore handles the field. Built handles the money. Approved payables push directly into your accounting system. No double entry.

See how Built manages construction invoicing.

Construction Invoicing FAQs

How do you split construction invoices across projects or phases?

Splitting construction invoices across projects or phases involves assigning a standardized cost-code structure to every project before the first invoice arrives. When an invoice touches multiple projects or phases, each line item should be allocated to the correct project and cost code based on direct measurement, scope-based proportions, or contractual allocation percentages. This means requiring subs to include cost codes on every invoice And reconciling total allocations against each vendor’s actual invoice monthly to catch splits that don’t add up.

What should a construction invoice include for progress billing?

A progress billing invoice should include an AIA G702 (Application and Certificate for Payment) and G703 (Continuation Sheet). The G703 breaks the contract into line items with the scheduled value, previous billings, current work completed, materials stored, and balance to finish. It should include the cost code for each line item, the project name or number, the billing period, and any backup documentation the GC or owner requires.

How do GCs track invoices from multiple subcontractors?

GCs track sub invoices by tying each one to a project budget, cost code, and draw cycle. The process starts with a standardized invoice submission format and a clear approval workflow. Each invoice gets reviewed for accuracy, coded to the correct budget line, and held until the draw assembly window. Tracking lien waiver status alongside invoice status prevents compliance gaps from stalling the draw.

How do you reconcile construction invoices at month-end?

Month-end reconciliation compares every invoice’s cost-code allocation against the project budget, the draw request, and the general ledger. For shared vendors, that means verifying that allocations across all projects equal the vendor’s actual billed amount. This includes checking for timing mismatches where invoices cross billing periods and flagging any invoices approved but not yet included in a draw, as well as any draw line items without a matching approved invoice.

What’s the difference between an AIA G702 and a standard construction invoice?

An AIA G702 is a standardized Application and Certificate for Payment used in commercial construction. It includes the original contract sum, approved change orders, total completed and stored to date, retainage, and the net amount due. A standard invoice may include only a description, quantity, and amount. Most lenders and owners on commercial projects require the AIA format because it ties directly to the schedule of values and supports draw-level review.

How do you avoid duplicate invoicing on multi-phase construction projects?

Duplicate invoicing happens when the same work appears in invoices for two different phases or two consecutive billing periods. It can be prevented it by requiring unique invoice numbers tied to specific phases, establishing clear billing-period cutoff dates, and matching every invoice line item to a specific cost code and phase. During reconciliation, this should include comparing current-period invoices against prior-period submissions for the same vendor and scope.