Archdesk

Construction ERP Software for Canadian Contractors

One ERP from estimate to closeout, on one data model.

Estimating, scheduling, job costing, procurement, documents and finance on one data model. Committed cost runs months ahead of the invoices, WIP reporting is produced from live records, and builders lien holdback is tracked per subcontract instead of living in a spreadsheet.

Trusted by construction companies of every size, worldwide

Higgins Partnerships logo
QBRE logo
Mitie logo
Daikin logo
VINCI Construction logo
Ballast Nedam logo
Madinet Masr logo
QGMI logo
CDC City Diamond Contracting logo
CSI Energy logo
Polenergia logo
ib vogt logo
TeraWulf logo
Utilligence logo
TaskSpace logo
Echospace logo
EEE Elevator Enterprise logo
Eomac logo
QTS logo
MacLennan logo
Conditioned Environment logo
DVM logo
ADP logo
DMDC logo
Inuti logo
Oakwrights logo
JH logo
K4 logo

Committed cost, WIP and holdback on one set of records

Construction ERP software for Canadian contractors has to answer the questions the bank and the bonding company ask: where does each job stand against budget, what is committed but not yet invoiced, and where over- and under-billing sit across the book. Archdesk runs the full cycle on one data model: the estimate becomes the budget, purchase orders and subcontracts commit against it at approval, progress draws and site records land on the same project, and WIP reporting reads it all live. Builders lien holdback is tracked per subcontract with the rest of the commercial record, from the first draw to closeout.

Engineer reviewing live project data on a tablet on site

Committed cost, not invoice archaeology

Every purchase order and subcontract commits against a budget line at approval, so committed cost runs months ahead of the invoices and WIP reporting reads from current numbers.

Finance without double entry

Progress billing and invoicing run in the platform, holdback is tracked per subcontract, and the QuickBooks Online integration keeps the ledger in step without double entry.

The field and the office on one record

Site forms, timesheets, drawings and RFIs land on the same project record the office bills from, so progress draws and field records read together.

The estimate becomes the budget

Won work converts into delivery without re-keying: rates, quantities and scope carry over, so the budget you run the job on is the one you actually bid.

One data model underneath every draw

Every module reads and writes the same records, so WIP, CPI, SPI and custom KPIs report live at project and portfolio level, and the report you take to the bank is produced from current numbers, not assembled at month end. A no-code engine shapes workflows to your process.

Two workers in hi-vis reviewing plans on a tablet

Job Costing & Cost Control

Actual cost lands against the budget line the moment it is committed. Budget versus actual, cost to complete and margin run live per job and across the portfolio.

Committed cost visible at order time

Budget vs actual on every cost code

WIP reporting

Margin visible while you can still act

Job Costing & Cost Control screenshot

Finance & Accounting Integration

Payment applications, invoicing and payment tracking run in the platform; the ledger stays in your accounting system via integrations with QuickBooks, Sage, Xero and others.

Progress draws and holdback tracking

Sales and purchase invoicing

Certified Xero partner; Sage and QuickBooks integrations

No double entry between systems

Finance & Accounting Integration screenshot

Reporting & Dashboards

Live dashboards and custom KPIs built on the one data model underneath it all: WIP, CPI, SPI and cash position at project and portfolio level.

Project and portfolio dashboards

WIP, CPI, SPI and custom KPIs

Work in progress and cost to complete

Reports built from live records, not exports

Reporting & Dashboards screenshot

Procurement & Supply Chain

Purchase orders, subcontracts and progress draws run through approval workflows against budget. Supplier records, insurances and performance history stay current in one register.

POs and subcontracts committed against budget

RFQs and side-by-side bid comparison

Supplier compliance and performance records

Three-way invoice matching

Procurement & Supply Chain screenshot

Estimating to Closeout

The estimate that wins the job becomes the budget that runs it. Rates, quantities and scope carry from bid to delivery without re-keying, so the commercial baseline is real from day one.

Estimates priced from live rate libraries

Won bids convert straight into project budgets

Scope and quantities carried into delivery

One record from first estimate to closeout

Estimating to Closeout screenshot

Scheduling & Delivery

Gantt schedules with baselines and critical path, connected to the same projects your costs and site records live on, so program and money are read together.

Gantt schedules with baselines

Critical path and resource conflicts

Progress tracked against program

Schedule and cost on one project record

Scheduling & Delivery screenshot

Documents & Site Records

Drawings and documents with revision control, and site forms, timesheets and attendance captured in the field, all landing on the project record the office already works from.

Document and drawing revision control

RFIs raised and answered on the record

Site forms and daily records from the field

Timesheets feeding job costs directly

Documents & Site Records screenshot

What construction ERP covers, and how to compare systems

Construction ERP covers the full operating cycle of a contracting business: estimating and bidding, project budgets and cost control, procurement and subcontracts, documents and site records, and the invoicing and payment cycle that turns delivered work into cash. Most vendors list the same modules, so the module list is a poor basis for comparison. What separates systems is whether those modules work one shared project record or pass exports between compartments.

One boundary holds in every comparison: a construction ERP does not replace the accounting ledger. The workable architecture keeps finance in the accounting system and the project cycle in the ERP, connected without re-keying.

The ledgers Archdesk connects to, and how each connection works, are on the accounting integrations page.

  1. 01

    One project record underneath every module

    The estimate should become the budget, orders should commit against it, and site records should land on it with no export in between. Ask the vendor to show the estimate converting into a live budget, not a slide about integration.

  2. 02

    Cost known at commitment, not at invoice

    The system should show the cost position the moment a purchase order or subcontract is approved. If actual cost only appears when invoices arrive, the system reports history, not position.

  3. 03

    A clear boundary with accounting

    Check which ledgers the system connects to and how: native integration, file export, or custom work. The answer decides how much double entry your finance team keeps.

  4. 04

    Configuration your own team can change

    Approval chains, fields and workflows change as the business grows. A no-code engine keeps those changes in your hands; anything that needs a developer will lag the process it is meant to control.

  5. 05

    A field experience the site will accept

    Site forms, timesheets and records only feed the numbers if the field teams find them usable on the day. Judge that part of the system with the people who will live in it.

  6. 06

    Reporting that reads live records

    WIP reporting, CPI, SPI and custom KPIs should read from the same records the teams work in, at project and portfolio level, with no month-end spreadsheet assembly.

New to the topic? Read the complete guide to construction ERP, or go deeper on composable cloud ERP architecture.

Plant and equipment run through the same records: construction asset management sits inside the ERP.

Frequently Asked Questions: Construction ERP

What is construction ERP software?

Construction ERP software runs the whole business on one data model: estimating, scheduling, cost control, procurement, document control, site records and finance read and write the same project records instead of living in separate tools. That is what keeps the commercial position live rather than reconciled after the fact. In Archdesk that one data model spans more than 30 modules, from the first estimate to closeout.

How is a construction ERP different from generic ERP software?

Generic ERPs are built around products, stock and repeatable processes. Construction runs on projects: every job has its own budget, program, supply chain and payment cycle. A construction ERP is built around the project record, with cost codes, progress draws, change orders, holdback and subcontractor workflows as first-class features rather than customizations.

Does Archdesk replace our accounting software?

Archdesk runs the operational and commercial side: budgets, commitments, progress draws and invoicing. It integrates with accounting systems including QuickBooks, Sage and Xero (as a certified partner), so finance keeps its ledger while the project data flows without re-keying. The full roster of supported ledgers, and how each connection works, is on the accounting integrations page.

Can the ERP adapt to how we already work?

Yes. A no-code configuration engine lets you shape workflows, approvals, fields and automations to your operating model without custom development, so the system follows your process rather than the other way round.

How does reporting work in a construction ERP?

Because every module writes to the same records, reporting is live: budget versus actual, WIP reporting, CPI and SPI, and custom KPIs, at project and portfolio level, without exporting spreadsheets from five systems first.

What does Archdesk cost?

Pricing is quote-based: pay per user, or choose an unlimited-users package priced on annual construction volume. Every quote includes all modules, unlimited data, implementation and support, and external collaborators such as subcontractors, clients and consultants are free of charge.

How do holdback and lien waivers fit into a construction ERP?

In Canadian practice, paying a subcontractor runs on the progress draw cycle under provincial lien legislation: holdback is retained and released on statutory timelines, often with lien waivers exchanged along the way. An ERP built around the project record keeps documents, approvals and payment records together, so the paper trail sits with the numbers.

How does Archdesk track builders lien holdback?

Under Canadian construction contracts, holdback is retained on each subcontract until release falls due. Archdesk tracks holdback per subcontract on the same records as the budget and billing, so balances and release timing stay visible instead of sitting in a side spreadsheet until closeout.

Does the ERP produce WIP reports?

Yes. Work-in-progress reporting comes straight from the live commitment, cost and billing records at project and portfolio level, so over- and under-billing positions read from current numbers rather than being reconstructed at month end.

Does Archdesk integrate with QuickBooks Online?

Yes. Archdesk integrates with QuickBooks Online, so job cost records and the ledger stay in step without double entry: finance keeps its own system while estimating, procurement and billing run in the ERP.

How do progress draws fit into the ERP?

Progress draws live on the same project records as commitments and costs, so the drawn, certified and committed positions read together per job and across the book, first draw to last.

See your next project on Archdesk

Book a demo and walk through a fully worked example project: one platform running everything from winning the work to closing it out.

Book a Demo
Archdesk rating on Software AdviceArchdesk rating on CapterraArchdesk rating on GetApp