Invoice Reconciliation in Construction: A Guide for Owners and GCs

Construction invoice reconciliation at month-end requires matching every subcontractor and vendor invoice against the approved schedule of values, verifying cost codes, confirming retainage withholding, and collecting conditional lien waivers before any draw package moves to the lender. 

The process is more complex than standard AP matching because construction invoices reconcile against contracts (not purchase orders), carry retainage deductions of 5%-10%, and trigger lien waiver compliance requirements that vary by state. When reconciliation drags past the lender’s submission window, the draw stalls, and every week of delay creates carry cost the project didn’t need to absorb. Platforms like Built automate invoice ingestion, match invoices to schedules of values using AI, and enforce compliance documentation before payment releases. On Built’s platform, invoice-to-payment timelines drop from 53 days to 26 days.

Invoice reconciliation in construction is a cash-flow gate. When your project accountant spends three days matching invoices to cost codes across a dozen desktop spreadsheets, two things happen. First, the draw package misses the lender’s submission window, and second, interest keeps accruing. Based on Built platform data, on a $50M project at 6% interest, that’s $5,800 a week in carry the project didn’t need to pay.

This guide walks through what invoice reconciliation looks like in construction, why it breaks down, and what the process should look like at month-end. If you’re an owner, developer, or GC managing active projects, the goal here is fewer errors, faster draws, and less time chasing paper.

What Is Invoice Reconciliation?

Invoice reconciliation is the process of matching incoming invoices against approved contract values and verifying that the amount billed, the work completed, and the documentation submitted all align before payment is released. In construction, this means confirming that every line item on a subcontractor’s pay application ties back to the schedule of values (SOV) and that the project’s financial records reflect what actually happened on the job site.

The simplest form is two-way matching, where you compare the invoice to the contract or commitment amount. Three-way matching adds a third layer, comparing the invoice to both the contract and the proof of work completed (inspection reports, field logs, or percentage-of-completion certifications).

Why Invoice Reconciliation Is Different in Construction

Every construction invoice references a living contract with shifting change orders, cumulative billing, and retainage deductions that carry forward across the life of the project. That operational complexity is what separates construction reconciliation from standard AP workflows.

Schedule of values vs. purchase orders

The schedule of values (SOV) is the financial backbone of every construction contract. It breaks a lump-sum or GMP contract into line items (foundations, framing, mechanical, electrical) with an approved dollar amount for each. When a sub submits a pay application, the billed amount must tie back to the SOV, accounting for prior billings, current work completed, stored materials, and retainage withheld.

The match is cumulative, not a simple quantity-times-price check. If a sub billed 40% completion on framing last month and now bills 65%, the reconciliation requires verifying that the incremental 25% is supported by field documentation. Standard AP systems don’t track cumulative progress against an SOV because they were never designed to.

The AIA G702/G703 billing format is the industry standard for this process. The G702 is the application and certificate for payment. The G703 is the continuation sheet that breaks down billing by SOV line item. Every pay application your project accountant reviews follows this structure, and every reconciliation error traces back to a mismatch between the G703 detail and the approved SOV.

Multi-project cost coding and job costing

Construction cost codes add another layer of complexity. Every invoice must be coded to the correct project, the correct cost code within that project, and the correct commitment within that cost code. Owners running 5-10 active projects with 10-15 subs each are processing hundreds of invoices per month across thousands of cost code combinations.

A misclassified cost code distorts job costing, which means budget-versus-actual reporting shows the wrong numbers, and the CFO makes decisions based on data that doesn’t reflect reality. Retainage calculations compound the problem because retainage is typically withheld at the commitment level, not the invoice level.

How to Reconcile Construction Invoices at Month-End

Month-end reconciliation in construction follows a specific sequence. Skip a step or change the order, and you’ll spend the first week of the next month cleaning up discrepancies instead of managing your projects. Here’s the process, step by step:

1. Enter all costs and close the cost cutoff: Every invoice, purchase order, and subcontractor pay application received through the cutoff date must be entered into the system. Late invoices that arrive after cutoff get pushed to the next period. This is non-negotiable. Without a clean cutoff, your budget-versus-actual numbers are unreliable, and the draw package reflects incomplete data.
2. Match invoices to commitments and schedules of values: Each invoice must tie back to an approved commitment (subcontract, purchase order, or professional services agreement) and align with the SOV line items. For subcontractor pay applications, verify that the current billing plus prior billings doesn’t exceed the committed amount, including approved change orders.
3. Verify retainage calculations: Retainage is typically 5%-10% of each progress payment, withheld until substantial completion. Confirm that retainage is being withheld at the correct rate, that it’s calculating against the right base (gross billing or net billing), and that any retainage releases have proper documentation.
4. Collect lien waivers and compliance documents: Before any payment processes, collect conditional lien waivers for current payments and unconditional waivers for prior payments from every sub and material supplier. This also includes verifying current insurance certificates, contractor licenses, and any project-specific compliance requirements.
5. Resolve discrepancies with vendors: Flag any invoices where the billed amount doesn’t match the SOV, where cost codes are incorrect, or where change orders haven’t been formally approved. Document every discrepancy and its resolution. This step is where most delays happen, because resolving a billing dispute with a sub can take days.
6. Package approved payables into the draw request: Once reconciliation is complete and all compliance documents are collected, assemble the approved payables into the construction billing process format your lender requires. This typically follows the AIA G702/G703 structure and includes backup documentation for every line item.

The entire sequence should take three to five business days for a project accountant managing two to three active projects. In practice, teams using spreadsheets and email report it takes significantly longer because steps four and five create bottlenecks that cascade through the rest of the process.

Common Invoice Reconciliation Errors That Cost Construction Projects Money

Consider a $25M mixed-use development with 12 subs, 8 trades, and a 30-day payment cycle. Every month, the project accountant processes 40-60 invoices across three active projects. The reconciliation window is five business days. The errors that cost real money fall into the following:

• Duplicate invoices across projects: A sub working on two of your projects submits the same invoice to both project folders. Without a centralized system that cross-references invoice numbers across projects, the duplicate goes undetected until the bank flags it during draw review, or worse, after payment has already been released.
• Cost code misclassification: An electrical sub’s invoice for switchgear gets coded to general conditions instead of electrical rough-in. The budget report now shows electrical under budget and general conditions over budget, neither of which is true. The CFO approves a contingency draw based on the inflated general conditions number.
• Retainage calculation errors: Retainage should be 10% through 50% completion and 5% after. The spreadsheet formula doesn’t account for the rate change, so the sub is under-withheld by $40,000 across three pay periods. That $40,000 is now unrecoverable negotiating power if the sub’s work needs correction.
• Missing change order approvals: A sub bills for $85,000 in approved change order work, but the change order was only verbally approved, never executed in writing. The construction accounts payable process has no record of it, and the project accountant either delays payment (straining the sub relationship) or pays without documentation (creating audit exposure).
• Incomplete lien waiver chains: The general contractor collects waivers from first-tier subs but not from second-tier suppliers. When a material supplier files a lien for unpaid invoices, the owner discovers the waiver chain was never complete.

Based on Built platform data, manual pay application processes carry error rates of 3%-5%. On a $25M project, that’s up to $1M in potential billing discrepancies. A 2025 AutoRek payments survey found that spreadsheets remain integral to financial operations in 90% of organizations. Construction is no different. Spreadsheets don’t flag duplicates, don’t enforce waiver collection, and don’t catch cost code errors until someone manually reviews every line.

What Your ERP Misses About Construction Invoice Matching

The most common objection from owners evaluating their reconciliation process is, “Our ERP handles accounts payable.” It does. ERPs like Sage Intacct, QuickBooks, Yardi, and CMiC are excellent at recording journal entries, managing the general ledger, and processing payments. That’s their job.

What they don’t do is match invoices against schedules of values, track cumulative billing against contracts, enforce compliance documentation before payment releases, or package approved payables into a draw request that meets your lender’s format requirements. Those are construction finance workflows, not accounting workflows.

Here’s the gap in practice. Your ERP records that you owe a subcontractor $150,000. It doesn’t tell you whether that $150,000 aligns with the SOV, whether retainage has been correctly withheld, whether the conditional waiver for last month’s payment has been returned, or whether the change order that increased the commitment from $1.2M to $1.35M was formally approved.

That gap is where errors live. The ERP processes whatever transaction it receives. If the invoice is wrong, the ERP processes the wrong amount. If the cost code is misclassified, the ERP records the misclassification. It doesn’t validate against the construction contract because it wasn’t designed to.

Procore solves a different piece of this problem. It handles field operations (RFIs, submittals, schedules, daily logs) and gives project teams visibility into what’s happening on the job site. However, Procore isn’t a financial execution platform. It doesn’t process invoices, manage lien waivers, or submit draws to lenders. The operational and financial layers are complementary, not interchangeable.

The right architecture puts a construction finance layer between the project and the ERP. Invoices get matched, validated, and approved in the construction finance layer. Only clean, coded, compliant transactions push downstream to the ERP. No double entry. No reconciliation after the fact.

How Lien Waivers and Retainage Complicate the Reconciliation Process

Lien waivers and retainage are the compliance backbone of reconciliation. Get either one wrong, and you’re exposed to financial risk that no amount of spreadsheet auditing can fix after the fact.

State-by-state lien deadline variation

Lien waiver requirements vary by state, and the variation is significant. Some states require statutory waiver forms (California, Texas, Georgia). Others accept any written waiver that meets common-law standards. Deadlines for filing a mechanic’s lien range from 30 to 120 days depending on the state, the project type, and whether the claimant is a first-tier sub or a second-tier supplier.

Missing a waiver collection deadline creates lien exposure. Based on Built platform data, a single lien event can cost between $50,000 and $500,000 when you factor in legal fees, project delays, title complications, and the impact on lender relationships. State-level prompt payment statutes add another layer, establishing payment timelines that vary by jurisdiction and can trigger penalties if contractors aren’t paid within the statutory window. The federal Prompt Payment Act (31 U.S.C. sections 3901-3907) applies to federal contracts specifically, requiring payment within 30 days.

This is an area where you should consult with legal counsel familiar with the lien laws in your specific project jurisdictions. The rules are precise, the deadlines are hard, and the penalties are real.

What subcontractors need from the reconciliation process

Subs don’t think about your reconciliation timeline. They think about getting paid. When your reconciliation process adds two weeks to their payment cycle, they price that risk into their next bid, or they stop prioritizing your projects.

Sub-tier visibility matters here. Your first-tier sub may have collected a waiver from you, but if they haven’t collected waivers from their material suppliers, you have an incomplete chain. And incomplete chains create lien exposure for the owner, not the GC.

The reconciliation process needs to work for subs, not just for your accounting team. That means clear submission requirements, fast turnaround on waiver requests, and a process that doesn’t require subs to log into six different portals to submit one construction invoice template.

How Built Connects Invoice Reconciliation to the Draw Cycle

Reconciliation doesn’t end when invoices are approved. It ends when the draw funds hit your account and contractors get paid. That’s the full cycle, and it’s where the process either works or falls apart.

Built connects every step of the reconciliation process to the draw cycle in one platform. Invoices arrive and get read, coded, and validated automatically. The finance team reviews a queue of pre-matched invoices instead of building one from scratch. Compliance is enforced before any payment releases, not chased down after the fact.

The results are measurable. On Built’s platform, invoice-to-payment timelines drop from 53 days to 26 days (51% faster). Draw submissions go from three days to one day (75% faster). Admin burden drops by 60%. And because the platform connects to 300+ lenders, the draw package arrives in the format your lender already expects.

Waltz Construction saw this firsthand. “Before implementing Built, we were spending one to two hours tracking down compliance documentation and cutting checks,” their team reported. “Now we can actually get into the financial part of our projects.”

Spreadsheets are a reconciliation delay, not a reconciliation system. Every hour your project accountant spends copying data between tabs is an hour they’re not managing the project. Every missing waiver that delays a draw submission is interest accruing on capital the project already earned.

Built is the front door to your ERP. Approved payables push directly into Sage Intacct, QuickBooks, Yardi, or CMiC. There’s no double entry. No reconciliation after the fact. We handle the construction finance layer so your accounting system only receives clean, compliant, coded transactions.

Talk to our team to see how your reconciliation process connects to the draw cycle.

Invoice Reconciliation FAQs

What is invoice reconciliation in construction?

Invoice reconciliation in construction is the process of matching subcontractor and vendor invoices against approved contracts, schedules of values, and cost codes to verify that billed amounts align with completed work before payment is released. Unlike standard AP matching, construction reconciliation tracks cumulative billing, retainage withholding, and lien waiver compliance across the life of the project.

How do you reconcile construction invoices at month-end?

Month-end reconciliation follows six steps: close the cost cutoff and enter all invoices, match each invoice to its commitment and SOV line items, verify retainage calculations, collect lien waivers and compliance documents, resolve discrepancies with vendors, and package approved payables into the draw request. The process typically takes three to five business days per project.

What are the most common invoice reconciliation errors in construction?

The most common errors include duplicate invoices submitted across multiple projects, cost code misclassification that distorts budget reporting, retainage calculation mistakes (especially when rates change at completion milestones), missing change order approvals that create audit exposure, and incomplete lien waiver chains that leave the owner exposed to mechanic’s liens. Manual reconciliation processes produce billing discrepancies that can reach six figures on mid-size projects.

Why is construction invoice reconciliation harder than standard AP?

Construction invoices reconcile against contracts and schedules of values, not purchase orders. They carry retainage deductions of 5%-10%, require cumulative progress tracking across months or years, and trigger lien waiver compliance requirements that vary by state. Standard AP automation tools are built for fixed-quantity, fixed-price PO matching and don’t support these construction-specific workflows.

What software automates construction invoice reconciliation?

Construction-specific platforms automate invoice ingestion, match invoices to schedules of values, enforce lien waiver collection before payment, and package approved payables into lender-ready draw requests. These platforms sit between the project and the ERP, handling the construction finance layer while pushing clean transactions downstream to accounting systems like Sage Intacct, QuickBooks, Yardi, or CMiC.

How does invoice reconciliation affect the construction draw cycle?

Every reconciliation delay pushes back the draw submission, which delays funding, which delays contractor payments. The carry cost on delayed capital adds up weekly, eating directly into project margin. A clean reconciliation process compresses the cycle from invoice receipt through draw funding, reducing capital costs and keeping lender relationships intact.