ERP for Construction Companies

Construction firms need an ERP built around job costing, progress (AIA) billing, and subcontractor compliance — not a generic finance package retrofitted with a "projects" tab. The right platform tracks every cost against a contract, recognizes revenue on a percentage-of-completion basis, generates AIA G-702/G-703 pay applications with retainage, and manages certified payroll, lien waivers, and insurance tracking for every sub on the job. Which platform fits depends mostly on revenue band: lighter tools like Foundation or Sage 100 Contractor for sub-$25M contractors, cloud mid-market systems like Acumatica Construction Edition, Microsoft Dynamics 365, or Sage Intacct for the $25M–$500M band, and purpose-built heavy/civil suites like Trimble Viewpoint, CMiC, or IFS above that.

This guide breaks down exactly what construction-specific capability you should demand from an ERP, how the major platforms compare, what it costs, and how to choose without overbuying.

Why construction is a different ERP problem

Construction is the rare industry where the "product" is a one-off, long-running, fixed-price contract executed across dozens of subcontractors and suppliers, often in multiple states, under prevailing-wage and bonding rules. That makes the accounting genuinely hard in ways a generic ERP simply does not model. You are not shipping widgets from a warehouse — you are billing a customer for work completed to date on a schedule of values, holding back retainage, accruing work-in-progress (WIP), and proving to a surety that your cost-to-complete estimates are sound.

The stakes are large and the digitization gap is real. U.S. construction spending ran at a seasonally adjusted annual rate of roughly $2.14 trillion in mid-2025, according to the U.S. Census Bureau's Value of Construction Put in Place survey. Yet construction remains the second-least-digitized industry globally on McKinsey's digitization index, and roughly 73% of construction firms still struggle with digital adoption — a productivity gap McKinsey estimates costs the sector trillions in unrealized value. A separate McKinsey analysis notes that construction productivity has "flatlined" for decades even as a ~$50 billion wave of software investment has started to close the gap.

An ERP is the system that closes that gap inside your own company. But only if it actually models how a construction company earns and recognizes money.

The four capabilities a construction ERP must have

If you are evaluating systems, filter ruthlessly on four pillars. A platform that is weak on any one of them will cost you in rework, audit findings, or cash-flow surprises.

1. Job costing — the spine of the whole system

Job costing is the single non-negotiable. It is the ability to capture every cost — labor, material, subcontract, equipment, overhead — against a specific project, phase, and cost code, and compare actuals against the original estimate in real time. Without it, you cannot produce a credible WIP schedule, you cannot recognize revenue correctly, and your surety will not trust your work-in-progress numbers.

A proper construction job-cost engine lets you structure each job by cost code (e.g., 03100 Concrete Formwork), phase, and cost type (labor, material, sub, equipment), then roll those up into a WIP schedule that compares estimated costs to actuals, computes percentage of completion, calculates over- and under-billings, and derives earned revenue. As Black Peak CFO's construction WIP guide explains, WIP accounting tracks revenue recognition on active projects using the percentage-of-completion or completed-contract method, and a proper WIP schedule is what tells you whether you have billed too much (a liability) or too little (under-billing that starves cash). WhippleWood Advisors goes further and connects job costing and WIP directly to bonding capacity — sureties read these schedules to decide how much work you can back, so sloppy job costing literally shrinks the deals you can pursue.

In practice, this means the ERP must let field time-entry, AP invoices, and payroll load directly into job cost without rekeying, and it must surface a real-time "cost to complete" on every project.

Percentage-of-completion and revenue recognition

Construction revenue is recognized under the percentage-of-completion method (historically ASC 605-35, now aligned with ASC 606's over-time guidance for most fixed-price construction contracts). The mechanics matter for ERP selection: the system must compute earned revenue as (% complete × total contract value), where % complete is derived from costs incurred divided by the latest estimate of total costs — and it must do this every period, automatically, for every open job.

The output is the over/under-billing line on your balance sheet. If you have billed more than you have earned, you carry a contract liability (over-billing); if you have earned more than you have billed, you carry a contract asset (under-billing, often called "costs and estimated earnings in excess of billings"). A construction ERP that cannot produce these two balances per job cannot close its books correctly. This is the single biggest reason a generic ERP fails in construction: its revenue recognition assumes you recognize revenue when you ship or invoice, not as work progresses on a multi-month contract. The WIP schedule that drives these entries is exactly what your surety and auditor will inspect, which is why job costing and revenue recognition are really one capability, not two.

2. Progress billing and retainage — cash flow on long contracts

Commercial and public-works contractors do not invoice with a standard invoice; they submit AIA progress billing documents (the G-702 continuation sheet and G-703 summary), which bill for the percentage of the schedule of values completed to date, less retainage — typically held back at 5–10% until project closeout. Construction invoicing guides routinely note that construction billing must handle AIA G-702/G-703, retainage holdback, lien waivers, and change orders as a connected workflow, not as separate documents.

Your ERP needs to generate these pay applications directly from the job-cost and project-management data, apply retainage automatically, track what has been billed versus what is approved, and carry the retainage receivable on the balance sheet until release. Subcontractor-focused tools like Siteline and enterprise suites like CMiC exist precisely because managing pay applications, lien waivers, and compliance documents across many general contractors is a full-time back-office function. The same logic applies in reverse when you are the GC paying subs: the system must track each sub's schedule of values, prior payments, and retainage held.

3. Subcontractor and compliance management

A general contractor may have hundreds of subcontractors across active jobs, and each one carries a compliance burden: certified payroll reports (required on federal Davis-Bacon and many state public works projects), lien waivers with each pay application, current insurance certificates (COIs) with the right additional insureds and limits, W-9s, and licenses. Letting a sub's insurance lapse or a lien waiver slip is how contractors get dragged into litigation or lose bonding.

A construction-grade ERP treats subcontractors as managed entities with expiring documents, not just vendor records. It should flag a sub whose COI expired yesterday before you approve their invoice, generate certified payroll reports from the time the sub's crew logged, and store executed lien waivers against each pay app. Generic ERP vendor modules generally do none of this out of the box.

4. Change order and document control

On a fixed-price contract, every change is margin or loss. The ERP must capture change events (potential changes) separately from committed change orders (approved and priced), route them for approval, and roll approved changes into the contract value, the schedule of values, and the WIP estimate. This is where most construction margin leaks: an unapproved change gets built anyway, the cost lands in job cost, but it never reaches the billing schedule. A construction ERP closes that loop so committed costs, approved changes, and billings stay in sync.

Construction ERP vs. generic ERP vs. construction management tools

Buyers frequently confuse three categories, and the distinction drives the whole selection.

Construction accounting software (Foundation, Sage 100 Contractor, Sage 300 CRE) focuses on job costing, payroll, and billing. Construction ERP extends that foundation with project management, procurement, subcontractor management, field operations, and enterprise reporting on a single system of record, as ERP Research summarizes. Construction management platforms like Procore are not ERP at all — they excel at field operations, RFIs, submittals, and drawings, and most contractors run them alongside an accounting ERP, pushing data between the two through a connector.

• Field ops, RFIs, submittals, drawings — Construction management (e.g., Procore): Strong · Construction accounting (e.g., Foundation): Weak · Construction ERP (e.g., Acumatica, Viewpoint, CMiC): Varies (often integrated)
• Job costing & WIP — Construction management (e.g., Procore): Limited · Construction accounting (e.g., Foundation): Strong · Construction ERP (e.g., Acumatica, Viewpoint, CMiC): Strong
• AIA progress billing & retainage — Construction management (e.g., Procore): Add-on/connector · Construction accounting (e.g., Foundation): Strong · Construction ERP (e.g., Acumatica, Viewpoint, CMiC): Strong
• Subcontractor compliance (certified payroll, COIs, lien waivers) — Construction management (e.g., Procore): Partial · Construction accounting (e.g., Foundation): Partial · Construction ERP (e.g., Acumatica, Viewpoint, CMiC): Strong
• General ledger, multi-entity, financials — Construction management (e.g., Procore): None · Construction accounting (e.g., Foundation): Strong · Construction ERP (e.g., Acumatica, Viewpoint, CMiC): Strong
• Procurement, inventory, equipment — Construction management (e.g., Procore): Partial · Construction accounting (e.g., Foundation): Partial · Construction ERP (e.g., Acumatica, Viewpoint, CMiC): Strong
• Best as — Construction management (e.g., Procore): The field/ops layer · Construction accounting (e.g., Foundation): The books for a smaller contractor · Construction ERP (e.g., Acumatica, Viewpoint, CMiC): The integrated system of record

The healthiest stack for a growing mid-market contractor is often a construction ERP as the financial backbone, with a field-operations tool layered on top and integrated — rather than forcing one tool to do both jobs poorly.

Certified payroll, prevailing wage, and equipment costing

Three construction-specific accounting functions separate the serious construction ERP from the pretenders. If you do public works, union work, or heavy civil, evaluate all three explicitly.

Certified payroll and prevailing wage. Any contract subject to the federal Davis-Bacon Act (or a state "little Davis-Bacon" law) requires weekly certified payroll reports — statements signed by the contractor affirmating that workers on the project were paid the prevailing wage for their classification, including the correct fringe benefits. This is not a manual exercise you can sustain across hundreds of workers and dozens of jobs. The ERP's payroll engine must tag every employee and time-entry with a work classification and a prevailing-wage determination, compute the correct base + fringe split, flag underpayments before payroll runs, and generate the signed Statement of Compliance and the weekly report (the federal WH-347 format and its state equivalents) directly. For union contractors, the same engine must handle multi-trade fringe and dues allocations (vacation, health, pension, apprenticeship) per the relevant collective-bargaining agreement. Generic payroll modules do none of this.

Multi-state and multi-entity complexity. A contractor working across state lines accumulates sales/use tax, contractor's tax, and payroll-tax obligations in every jurisdiction, often across multiple legal entities. The ERP must allocate job cost and overhead across entities, handle intercompany billing cleanly, and consolidate for reporting — a capability that pushes mid-market contractors toward Sage Intacct, Acumatica, or Dynamics 365 Finance, all of which handle multi-entity and multi-currency natively.

Equipment and fleet costing. For heavy and civil contractors, owned equipment is often the largest cost pool after labor. A construction ERP must track each piece of equipment as a cost center — capturing depreciation, fuel, maintenance, and repair costs, then charging equipment time to jobs at an internal rental rate. Without this, equipment costs pile up in overhead and distort job margins. Enterprise suites like Trimble Viewpoint, CMiC, and IFS model equipment deeply; the lighter mid-market systems typically require an add-on or integrate with a dedicated fleet/maintenance tool. If equipment utilization is a material driver of your cost structure, treat fleet costing as a first-tier evaluation criterion, not an afterthought.

Which platform fits which contractor

Revenue band and project type are the strongest filters. The bands below reflect how independent analysts segment the market.

• Small trade / specialty sub — Typical revenue: Under ~$25M · Best-fit platforms: Sage 100 Contractor, Foundation, Procore + QuickBooks · Why: Lighter cost, fast to value, enough job costing without enterprise overhead
• Mid-market GC / design-build / specialty — Typical revenue: ~$25M–$500M · Best-fit platforms: Acumatica Construction Edition, Sage Intacct + Construction, Microsoft Dynamics 365 / Business Central, NetSuite · Why: Cloud, scalable, native job costing, multi-entity, integration-friendly
• Large GC / heavy civil / infrastructure — Typical revenue: Above ~$500M · Best-fit platforms: Trimble Viewpoint, CMiC, IFS, SAP, Jonas · Why: Deep equipment, union/prevailing-wage payroll, enterprise multi-jurisdiction, heavy-job controls

ERP Research's ranking names Acumatica Construction Edition as the best all-around mid-market choice because of its unlimited-user cloud pricing and native job costing; large GCs typically prefer Trimble Viewpoint or CMiC; finance-led firms favor Sage 300 CRE or Sage Intacct. ERPfocus reaches a similar conclusion: for general contractors, Viewpoint and Jonas are strong, while Acumatica, Microsoft Dynamics 365, Sage, and IFS offer the most cloud flexibility. The full field of credible options is laid out in Forbes Advisor's construction ERP roundup and SoftwareConnect's pricing guide.

A note on the mid-market cloud systems

The mid-market band is where most contractors actually buy, and it is also where Flectic spends most of its implementation time, so it is worth a closer look. Three patterns dominate:

• Acumatica Construction Edition is built specifically for contractors, with native construction job costing, AIA billing, retention, certified payroll connectors, and a consumption-based pricing model that does not penalize you for adding field users. It is the default shortlist entry for contractors that want one cloud system for finance and operations.
• Microsoft Dynamics 365 (Business Central for smaller mid-market, Finance + Supply Chain for larger) provides a strong general ledger and a native Jobs/Projects module that handles job costing, resource scheduling, and project invoicing. Microsoft documents the project setup and posting groups in Business Central, and the ecosystem of construction ISV add-ons adds AIA billing, retention, and certified payroll on top. If you want to understand how that native project module actually works before committing, our Business Central Jobs and Projects walkthrough covers the setup, cost tracking, and invoicing flow in detail.
• Sage Intacct (often paired with Sage Construction) is the finance-led choice, favored by contractors whose CFO wants best-in-class dimensional reporting and multi-entity consolidations, with construction dimensions layered on.

For a neutral head-to-head of the two most common mid-market contenders, ERP Research's Acumatica vs. Dynamics 365 for construction comparison is a useful starting point. If your evaluation is broader than one industry, our general ERP implementation services cover how we scope, configure, and roll out these platforms — and note that the construction build is meaningfully different from, say, how ERP is configured for professional-services firms, where the unit of work is a time-and-materials engagement rather than a fixed-price contract with retainage.

What construction ERP actually costs

Pricing in construction ERP is famously opaque because license is only a fraction of the true cost. ERP Research's cost FAQ gives the most concrete anchors: cloud construction ERP generally runs $20–$250 per user per month, with implementation, data migration, and training that often equal one to two times the first-year license. By company size, the same source cites typical year-one spend of $15,000–$60,000 for small contractors, $60,000–$250,000 for mid-market firms, and $300,000 or more for large contractors. Acumatica is the notable exception to per-seat pricing — it prices on consumption (transactions and resources) rather than named users.

Budget for the implementation, not the subscription. The line items that inflate construction ERP projects are almost always: cleansing and migrating historical job-cost and WIP data, recreating your chart of accounts and cost-code structure in the new system, building the AIA billing and retainage workflows, and integrating field time-entry and construction management tools. A realistic total cost of ownership model is license + 1.5× implementation in year one, then license + ~15–20% annual support thereafter.

How to choose without overbuying

The most expensive mistake in construction ERP is buying enterprise software for a company that needs construction accounting — and the second most expensive is buying construction accounting for a company that has outgrown it. Use this sequence to avoid both.

1. Start from your financial complexity, not the demo. Count concurrent active projects, average subcontractor count per job, number of entities and states, and whether you carry bonded work. Those four numbers tell you whether you need accounting software or a full ERP.
2. Filter on the four pillars first. Before any feature checklist, demand a live demo of job costing flowing into a WIP schedule, an AIA pay application generating with retainage, a subcontractor COI expiring and blocking an invoice, and a change order flowing into contract value. If a vendor cannot show all four in their own product, cross them off.
3. Size the platform to your band. Resist the urge to buy Viewpoint or SAP because "we might need it someday." Over-platforming a $30M contractor is a common, expensive failure mode. Match the platform to today's revenue plus a realistic five-year horizon.
4. Decide your field-operations strategy up front. If you already run Procore (or plan to), pick an ERP with a mature connector to it and budget for the integration. Trying to replace a field-ops tool with an ERP, or vice versa, is where implementations stall.
5. Evaluate the partner, not just the software. Construction ERP is a configured product, and the implementer's construction experience matters as much as the platform. Ask for two contractor references in your trade and revenue band, and call them.
6. Pressure-test the reporting. Have the vendor build the three reports your surety, your bank, and your project executives actually read — a WIP schedule, a backlog report, and a job-cost variance by cost code — during the evaluation, not after go-live.

Common pitfalls that sink construction ERP projects

Most construction ERP failures are not software failures; they are data and process failures. The recurring patterns:

• Migrating dirty job-cost history. If your old system's WIP and cost codes are inconsistent, the new ERP will faithfully reproduce the mess. Budget time to standardize the cost-code dictionary and reconcile open jobs before migration.
• Recreating the old chart of accounts. An ERP rollout is the moment to restructure for project-centric reporting. Cloning a legacy GL usually buries job cost behind too many segments.
• Under-investing in field adoption. If superintendents and field crews do not enter time and quantities accurately and promptly, job cost is always weeks behind and WIP is fiction. Plan mobile time-entry training and hold the field accountable from day one.
• Treating AIA billing as an afterthought. Contractors that leave billing configuration to the end of a project routinely go live unable to produce compliant pay applications, then bill late and starve cash for a quarter.
• Ignoring the construction management integration. A Procore-to-ERP (or equivalent) connector that nobody owns will silently drop sub invoices or duplicate cost entries. Assign an integration owner before go-live.

The bottom line

Construction companies do not need "ERP with a projects module." They need a system whose entire data model is the job — one that turns field time and vendor invoices into real-time job cost, job cost into a defensible WIP schedule, and WIP into compliant AIA billings with retainage, all while keeping every subcontractor's certified payroll and insurance current. Match the platform to your revenue band, demand the four pillars, budget for implementation at roughly 1.5× license, and choose a partner with construction scars. Get those right and the ERP stops being overhead and becomes the system that lets you bid more, bill faster, and bond higher.

If you are ready to map your job-cost and billing requirements to a specific platform, Flectic's ERP delivery team can run a requirements workshop and a shortlist against Acumatica, Microsoft Dynamics 365, and the other construction-grade options — or, if you are deeper in the Microsoft stack already, start with the Business Central Jobs and Projects guide to see exactly how project costing works before you commit.