Construction AP Automation: How Growing General Contractors Build a Unified Payments Stack

Most growing general contractors run two parallel payments processes. There's the ERP-based AP workflow for recurring vendors and there's everything else (change orders, joint checks, material purchases, T&E, international subs) which lives in spreadsheets, email approval chains, and the project manager's pile. A unified payments stack collapses that sprawl into one architecture: the construction ERP at the center, AP automation handling invoice-to-payment with pay-app and retainage awareness, commercial cards covering materials and T&E with project-level cost-code allocation, and cross-border for international subs and materials. The growing-GC sweet spot for this conversation is the $20M-$200M revenue range, somewhere in the ENR 400-600 band. Smaller and you can usually push everything through the ERP module. Bigger and you have specialists for each layer. In the middle is where the stack design either earns its keep or breaks.

Key Takeaways

• Construction AP is structurally different from corporate AP. Pay applications (AIA G702/G703), retainage, lien waivers, joint checks, and certified payroll all have to live in the workflow, not bolted on as exceptions.

• The breakage point is typically $30M-$50M in revenue, when project count exceeds AP-team capacity and the spreadsheet workflow alongside the ERP stops scaling.

• The ERP integration is the differentiator, not the AP automation engine. Vendor-specific construction ERPs (CMiC, eCMS, Sage Intacct Construction, Sage 300 CRE, Acumatica Construction, Viewpoint Vista) are where most generalist AP platforms cut corners.

• Construction is a top BEC target. 11.4% of all BEC victims in September 2025 were construction firms; a unified stack with single-path issuance, virtual-card vendor locks, and role-based approval workflows materially reduces fraud surface.

• Roughly 40% of ENR 400/600 contractors use Corpay to consolidate payments across the AP, cards, and cross-border layers — and the integration matters more than any single feature in any layer.

Why is construction AP fundamentally different from corporate AP?

Construction AP carries vocabulary, workflow, and compliance requirements that corporate AP simply doesn't. A generic invoice-automation platform that does great work for a SaaS company processing 500 vendor invoices a month will get the same construction firm halfway and then stall. The reasons are concrete and won't surprise anyone who's worked the function.

What is accounts payable in construction?

Accounts payable in construction is the full payments function for everything the company buys to deliver projects: subcontractors, materials, equipment rental, fuel, T&E, professional services, and the operating overhead. Unlike corporate AP, every payment has to tie to a project, a cost code, and a phase. The same vendor delivering steel to three different jobs needs to be tracked across three different cost codes with three different retainage schedules. The accounting can't be simplified to "this vendor, this amount, this GL account" without losing the project economics.

What are pay applications (AIA G702/G703)?

A pay application is the structured request for payment a subcontractor or general contractor submits at the end of a billing period. The standard format is the AIA G702 (the summary application) plus the G703 (the schedule of values, or SOV, showing percent complete by line item). Pay applications are how construction billing actually works at the contract-billing layer. They're not invoices in the corporate-AP sense; they're partial-completion claims that depend on schedule, retainage, and lien-waiver compliance. An AP platform that can't ingest and process G702/G703 forms misses most of what construction AP teams actually do.

How does retainage change the AP workflow?

Retainage is the percentage of every pay app the owner or GC holds back as security against contract completion (typically 5-10%, sometimes higher on public projects). On the sub side, the GC holds retainage from subs. On the owner side, retainage is held from the GC. Every pay app has to track per-contract retainage, partial releases tied to milestones, and final retainage release at substantial completion. Generic AP automation doesn't handle retainage natively. Construction-aware AP automation tracks retainage per contract and per line item, releases retainage when the milestone clears, and reports retainage balances to the project team continuously.

What role do lien waivers play in payment release?

Lien waivers are signed releases from a subcontractor or supplier that waive the right to file a mechanic's lien against the project for the work covered by the payment. Most owners require lien waivers from the GC and require the GC to collect them from subs before releasing payment. There are four common variants: conditional partial, unconditional partial, conditional final, unconditional final. The combination matters because payment shouldn't release until the correct waiver type is in hand, and the AP workflow has to know which is which. An AP platform that can't gate payment on lien-waiver receipt creates compliance risk every time a sub gets paid without the waiver in file.

What are the two parallel processes every growing GC runs, and why do they break?

The typical growing GC pattern: there's an ERP module that handles recurring vendor AP — utilities, recurring rentals, payroll-adjacent disbursements, the structured stuff. Alongside that, there's an entire parallel workflow that handles everything the ERP can't: change orders that don't tie back to the original PO, joint checks issued to sub-and-supplier pairs to protect against material liens, ad-hoc material purchases the project manager makes from a hardware store, fuel and T&E charges, payments to one-off consultants, payments to international subs and material suppliers. That parallel workflow lives in spreadsheets, email, and the PM's notebook.

Both processes work in isolation. The breakage point is the integration between them. Subcontractor pay apps don't reconcile cleanly against project budgets because change orders aren't in the ERP. Material purchases don't post to the right cost code because the PM can't get to the ERP from the job site. Retainage balances are accurate in the ERP but disconnected from what's actually paid out through the side process. The AP team spends half its time as a reconciliation function rather than a payments function.

A construction CFO on Reddit's r/PowerAutomate captured it: "I work in an accounting department for a General Contractor. Our AP person is at capacity and we are on the verge of having to hire another." The pattern shows up at roughly $30M-$50M in revenue, when project count and vendor count outpace what the spreadsheet workflow can handle. The Rabbet 2024 Construction Payments Report found 82% of contractors faced payment waits exceeding 30 days (up from 49% two years prior), with an average construction invoice payment cycle of 90 days — double the 45 days financial analysts consider healthy. Slow internal AP isn't the only cause, but it's a contributor every GC eventually has to fix.

What does a unified payments stack look like?

The architectural blueprint runs four layers, with the ERP as the system of record at the center.

1. The construction ERP at the center. Sage Intacct Construction, Sage 300 CRE, Sage 100 Contractor, Acumatica Construction Edition, CMiC, eCMS / Computer Guidance, Viewpoint Vista, Foundation Software, or a generic ERP (NetSuite, Dynamics 365) with a construction overlay. The ERP holds the chart of accounts, cost codes, project budgets, retainage balances, and contract structure.

2. AP automation as the invoice-to-payment layer. Captures invoices and pay apps, runs matching against POs and budgets, routes for approval with retainage and lien-waiver gates, and writes paid transactions back into the ERP with full project allocation. The platform has to be construction-aware to do this without manual cleanup.

3. Commercial cards for materials, fuel, T&E, and subcontractor purchases. Virtual cards lock to specific vendors for one-off material orders. Corporate cards cover routine T&E. Project-level cost codes push back into the ERP automatically rather than being manually allocated in month-end.

4. Cross-border payments for international subs and material suppliers. Currency coverage, FX risk management, 24-hour delivery, and integration with the rest of the stack so international payments don't live in a separate banking workflow.

Each layer can be replaced independently. The integration between layers is what determines whether the stack actually functions or just looks like a stack in a vendor's marketing deck.

See how Corpay configures the unified payments stack for growing GCs. Schedule a consultation to walk through your current ERP, project mix, and payment volume. The integration depth is where the conversation gets interesting.

How does construction ERP coverage actually work in practice?

The ERP integration question is the part most generic AP-automation marketing papers over with a logo wall. Every platform claims "ERP integration." The differences show up in whether the integration actually writes line-item coding, cost-code allocation, retainage data, and pay-app structure back into the ERP without manual re-keying.

Corpay's construction-ERP integration list, alphabetically:

• Acumatica Construction Edition

• CMiC

• Computer Guidance / eCMS

• Coins

• Deltek

• Foundation Software

• Sage 100 Contractor

• Sage 300 CRE

• Sage Intacct Construction

• Trimble

• Viewpoint Vista

Plus the generic ERPs construction firms also run: Microsoft Dynamics 365, NetSuite, Oracle, QuickBooks, SAP, and Xero. That's 180+ ERP integrations in total. The construction-vertical ERPs (CMiC, eCMS, Viewpoint Vista, and the Sage Construction line) are the systems where competing AP platforms most consistently fall short. Many show the logo but lack working line-item write-back, which means the AP clerk still re-enters coding in the ERP for every paid invoice.

Which construction ERPs does Corpay integrate with?

The full alphabetical list above. The depth matters more than the count. Construction ERP integration depth means the AP platform can ingest POs and budgets, push pay-app structure (G702/G703 line items), write back coded transactions with full project, cost-code, and phase allocation, sync retainage balances, and gate payment on lien-waiver receipt. Generalist AP platforms typically cover the first one or two and leave the rest to manual reconciliation. The construction-vertical ERPs handle all of it, which is why so many growing GCs end up moving to one rather than trying to make a generic ERP work with construction-specific overlays.

What does ERP-native integration actually mean?

ERP-native integration means the AP platform reads from and writes to the ERP via API or direct database connector rather than CSV export, manual upload, or middleware that requires nightly batch reconciliation. The practical test: when AP approves a pay app, the transaction appears in the ERP with full project and cost-code allocation within minutes, not in a batch posted overnight. When retainage is partially released, the ERP balance updates without an AP clerk touching it. When a lien waiver is uploaded, the payment-approval status reflects it without a separate filing step.

Case study: S.T. Wooten on eCMS Connect for Corpay

S.T. Wooten Corporation, a heavy-highway and site-development contractor in North Carolina, runs eCMS (Computer Guidance Corporation) as its construction ERP. In May 2025, Corpay and Computer Guidance released a joint case study covering the eCMS Connect integration with Corpay's AP automation platform. The S.T. Wooten implementation handles the full construction AP workflow — pay-app processing, retainage tracking, lien-waiver gating, project-level cost allocation — without the manual reconciliation work that typically eats AP-team capacity at firms of that size. The full case study is in the Corpay and Computer Guidance newsroom release.

Where do commercial cards fit in the construction stack?

Cards are the layer most growing GCs underuse. Materials and fuel typically run through cards (or should), and the difference between charging materials on a procurement card with project-level allocation versus charging them to a vendor's net-30 terms is significant in both cash-flow and rebate-revenue terms. The cards layer of the unified stack handles four main use cases.

Materials. Lumber, steel, fuel, and consumables purchased through cards (rather than invoiced on net-30 terms) post immediately to the right project and cost code if the card platform supports project-level allocation. Rebate revenue on materials spend can be substantial at GC volumes.

Fuel. Cards with MCC restrictions to fuel-pump categories work for field crews without requiring receipt management for every fill-up. Time-based and location-based controls add additional fraud reduction.

T&E. Routine business travel and entertainment for project managers, estimators, and field supervisors. Standard corporate-card controls (per-transaction limits, MCC restrictions, role-based scope) apply. The integration back to the ERP for cost allocation is what makes this work cleanly.

Single-use virtual cards for one-off material orders. Vendor lock and validity window on every virtual card mean the card only works at the one supplier and only for the time window the order needs. Eliminates the entire class of "card used somewhere it shouldn't be" risk.

The 2024 Deluxe construction-payments report found 23% of construction firms already use virtual cards, with another 33% planning adoption within 12-24 months. The trend reflects what growing GCs find once they try them: virtual cards close the materials-spend control gap most AP automation can't reach by itself.

How does cross-border fit in the construction stack?

Most growing US GCs don't need cross-border infrastructure for routine operations. Where it matters: international engineering or specialty subs, imported steel and equipment, multi-region GCs operating across the US-Canada border, and projects where the owner or GC structures payment in a non-USD currency.

For the firms that need it, the operational pattern is:

• 145+ currencies covered with same-day or 24-hour delivery

• FX risk management for projects with material currency exposure

• Integration with the same AP and approval workflow that handles domestic payments

• Sanctions screening and OFAC compliance built into the payment-issuance path

When cross-border lives in a separate banking workflow, international vendor payments take days to clear, FX rates lock in late, and the AP team spends time as a reconciliation function rather than a payments function. When cross-border is the same payments rail as domestic, the work shrinks and the international vendor experience improves.

How does a unified stack reduce construction fraud risk?

Construction is a top BEC target. SpiderLabs / LevelBlue's September 2025 BEC trends report found construction and engineering accounted for 11.4% of all ransomware and BEC victims in that month. Bernstein Shur's analysis of FBI IC3 data put construction BEC losses at over $1.2 billion in 2023 alone. The reason: construction payment flows are large, frequent, and often handled outside the formal ERP workflow, which means email-based payment instructions and last-minute wire changes are common. That's the exact attack surface BEC scammers target.

A unified stack reduces this risk in concrete ways:

• Single payment-issuance path. Every payment originates from the same platform with role-based approval rules. Email-approved wire transfers stop being a thing.

• Virtual-card vendor locking for materials and one-off purchases. The card only works at the intended supplier, so a compromised card can't be used elsewhere.

• Approval workflow with multi-level signoff for any payment above configured thresholds. The classic BEC pattern of urgent CFO email approval doesn't apply when the payment requires in-system approval.

• Real-time monitoring that flags unusual payment patterns immediately, not at month-end review.

Corpay's AP automation platform is SOC 2 Type II compliant, with audit-trail visibility and role-based access controls across the AP workflow. The card-side fraud controls are detailed in the virtual cards and automation mitigate fraud breakdown.

How does the unified stack work with Corpay?

Roughly 40% of ENR 400/600 contractors use Corpay to consolidate payments across the AP, cards, and cross-border layers. The platform is designed around the parts of construction AP that generic platforms hand off:

• AP automation with pay-app (G702/G703) handling, retainage tracking per contract and per line item, lien-waiver gating, multi-entity support for parent + project-LLC structures, and 180+ ERP integrations (including the full construction-vertical list above). Capabilities detail lives on the AP Automation product hub and the broader accounts payable automation overview, with the AP automation ROI guide covering the dollar economics.

• Commercial cards including corporate cards, virtual cards, and single-use virtual cards, with built-in spend controls (per-transaction limits, MCC restrictions, role-based scope, real-time notifications) and ERP-integrated reconciliation. Corpay is the #1 B2B Commercial Mastercard issuer in North America, with 800,000+ customer businesses. Card capabilities are detailed at the Commercial Cards hub and the Virtual Cards page.

• Construction-ERP integrations covering Acumatica Construction, CMiC, eCMS / Computer Guidance (with the May 2025 S.T. Wooten case study as a working example), Foundation, Sage 100 Contractor, Sage 300 CRE, Sage Intacct Construction, Viewpoint Vista, and the generic-ERP options (Dynamics 365, NetSuite, Oracle, QuickBooks, SAP, Xero). The ERP integrations index lists every supported system, and the CMiC integration page covers that specific connector.

• Cross-Border payments with 145+ currencies, 24-hour delivery, FX risk management, and integration with the same workflow that handles domestic payments. The Cross-Border Payments page walks through the operational scope.

The buyer's-checklist perspective on choosing construction payment software is in the construction payment software guide. The broader category overview lives in the construction payment management pillar. A working example of the integrated stack in production is the Alegis Construction customer story.

Three-way matching across pay apps and material POs uses the same workflow detailed in the three-way matching guide, and the underlying invoice processing automation engine is the same one used across non-construction AP, with the construction-aware modules layered on top.

Ready to plan your unified payments stack? Schedule a working session with the Corpay construction team. The session is built around your portfolio's project mix, your current ERP, and your actual payment volume rather than a generic demo. Most growing GCs find the integration gaps in their current workflow are bigger than they expected and easier to fix than they feared.

Frequently Asked Questions

What is accounts payable in construction?

Accounts payable in construction is the full payments function for everything the company buys to deliver projects — subcontractor pay apps, material invoices, equipment rental, fuel, T&E, and operating overhead. Every payment ties to a project, cost code, and phase, which is what makes it structurally different from corporate AP.

How is construction AP different from regular corporate AP?

Construction AP handles pay applications (AIA G702/G703), retainage, lien waivers, joint checks, certified payroll, change orders, and multi-entity (parent + project-LLC) structures. Generic AP automation rarely covers these without manual workarounds. Construction-aware AP automation builds them into the core workflow.

What is the AIA G702/G703 format and why does AP automation need to handle it?

The G702 is the summary pay-application form; the G703 is the schedule of values (SOV) showing percent complete by line item. Together they're how construction billing works at the contract-billing layer. An AP platform that can't ingest G702/G703 either rejects them or forces manual data entry, which defeats the automation case.

How do you handle retainage in an automated AP workflow?

The platform tracks retainage per contract and per line item, applies the contracted retainage percentage to every pay app, holds the retainage portion automatically, and releases it on milestone completion or substantial completion. Lien-waiver receipt typically gates the final retainage release. The retainage balance posts to the ERP continuously rather than at month-end.

Which ERP do most growing general contractors use?

The Sage Construction line (Sage Intacct Construction, Sage 300 CRE, Sage 100 Contractor) is the most common cluster at $20M-$200M revenue. Acumatica Construction Edition is the fastest-growing option in the same range. CMiC and eCMS dominate the larger GCs (typically $200M+ revenue), and Viewpoint Vista handles a similar tier. The right choice depends on project mix, integration ecosystem, and how project-management workflows are structured.

What are 3-way accounts payable in construction?

Three-way matching in construction compares the purchase order, the receiving documentation, and the invoice for material purchases. Pay applications don't fit the three-way pattern (there's no PO in the traditional sense), but material POs do. The matching logic is similar to corporate three-way matching, with the construction-specific differences in how cost-code allocation flows back to the project.

What is ASC 606 in construction?

ASC 606 is the revenue-recognition standard that affects how construction firms recognize revenue across multi-period projects. It's primarily an AR-side concern (recognizing revenue on percent-complete or completed-contract basis), but it affects AP indirectly because retainage liability, cost allocation, and project-level reporting all feed the revenue calculation.

How much does construction AP automation cost?

Platform pricing varies widely depending on transaction volume, ERP complexity, construction-module depth, and whether managed services are included. The cost-per-invoice benchmark for the industry: manual processing typically runs $18-$26 per invoice; automated processing runs $2.36-$2.78 (per NanoNets 2025 research and aggregated industry benchmarks). For a 5,000-invoice annual volume, that delta covers most mid-market platform investments within the first year.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

AP Automation