Contact Info
Canadian Contracting
What does a contracting ERP consultant cover for Canadian contractors?
For Canadian general and trade contractors, the focus is contract administration in both directions: subcontracts on standard forms or your own terms, change orders and change directives passed down to trades, holdback and trust obligations by province, notices of non-payment where prompt payment rules apply, and backcharges through to closeout. I map how your team handles these, specify the ERP rules, compare platforms neutrally and support implementation remotely.
Last reviewed by Vikas Saroj
A Canadian contractor working across provinces administers contracts under different holdback, trust and prompt payment rules, often on the same standard forms. The owner or general contractor holds back on you, you hold back on your trades, change directives are priced long after the work is done, and backcharges get argued at closeout. Without one commercial record, nobody can say quickly what is owed to whom.
This page covers that commercial layer: subcontract terms, change management, holdback and trust tracking, payment notices and backcharges. Lien timelines, sales tax and T5018 reporting are on my Canadian construction ERP page. I work remotely with Canadian contractors, planning sessions around your head office time zone.
What I Do
Each engagement begins with your contracts, change logs and holdback schedules, because they show where the commercial process actually breaks.
Sessions with project managers, estimators and accounting to document how contracts and subcontracts are awarded, how proper invoices or progress draws are prepared, and how change, holdback and backcharges are handled on each side.
Requirements for storing the governing province, the applicable holdback and payment regime, notice periods and release conditions on each contract, so the system applies the right rule instead of relying on memory.
A register that links owner change orders and change directives to the subcontract changes they trigger, with priced, disputed and agreed values, so work proceeding under a directive is never invisible to finance.
Holdback held and owed by contract, with release conditions and, where your counsel confirms trust obligations, reporting that shows how funds received on a project relate to amounts owing to trades and suppliers.
Where prompt payment rules apply, defined steps for disputing a trade's invoice or answering a notice from the payer, with deadlines calculated from contract data and dated records of what was sent.
Neutral demos using your own subcontract scenarios from more than one province, independent scoring, and review of migration and testing so holdback and change balances are right on day one.
What to Measure
An ERP for contracting should make these numbers available without a spreadsheet. I design the data model and reports around them from the start.
Platform Fit
How I Work
Contracts, provinces and trades
Owner contract forms reviewed
Subcontract terms sampled
Holdback practice by province
Change and backcharge history
Rules, requirements and vendor tests
Province-aware data model
Notice and holdback rules
Multi-province demo scripts
Fit-gap and scoring
Build through the first draw
Design reviews
Holdback balances reconciled
Draw cycle UAT
First month-end check
Canadian contracting relies heavily on standard forms. Owner contracts are often based on CCDC documents, and subcontracts on industry standard subcontract forms or a general contractor's own terms, usually with supplementary conditions. Across these forms, change is commonly handled through change orders, agreed in price and time, and change directives, which require work to proceed before the price is agreed. That second route is where commercial control slips.
A directive from the owner usually leads to instructions to one or more trades. If those instructions are tracked in emails and the cost of the work sits unpriced in job cost, the contractor ends up funding change while negotiating it. I specify a change register in which each owner change order or directive links to the subcontract changes it generates, with status and value per side: directed, priced, submitted, agreed or disputed. Time and material records from the field attach to the change, because they become the basis for valuing directed work. Finance sees committed but unpriced change by job; project managers see which trades are working on directives the owner has not yet valued. I capture this during requirements gathering, working from your own recent change logs.
Holdback is set by provincial legislation, and so are the rules for releasing it. Several provinces also treat money received on a construction project as trust funds for the benefit of trades and suppliers further down the chain, and some regimes expect certain holdback amounts to sit in a separate account. Where prompt payment legislation is in force, a payer who disputes an invoice generally has to give notice within set timelines, and payment timelines then cascade to the next tier. The details differ by province and change over time, so your legal counsel should confirm what applies to each contract.
For the ERP, the point is that one company-wide holdback setting is not enough. I specify contract-level fields for the province, the regime, holdback terms and release conditions, plus ledgers for holdback receivable and holdback payable that can be reported by project and by release date. Where trust obligations apply, finance needs to show how receipts on a project relate to amounts owed to trades on that project, which is a reporting and allocation design question. Notices of non-payment are generated from the invoice record with a dated trail. Lien deadlines and tax reporting have their own place on my Canadian construction ERP page.
Backcharges on Canadian projects usually arise from deficiencies, cleanup, damage, safety infractions and schedule recovery. Many are discussed at site meetings and noted in minutes, but never priced, notified or deducted properly. By closeout the evidence is scattered and the trade disputes the amount.
I design a backcharge record linked to the event, the deficiency or meeting reference, the cost incurred, the notice to the trade and the agreed or disputed value. The deduction then appears on the subcontract account with its source. Deficiency holdbacks, where part of a payment is held against incomplete or defective work, get the same treatment and stay separate from statutory holdback, because their release rules differ.
Closeout ties these together. A subcontract is commercially complete when its value, approved changes, backcharges, holdback and payments reconcile, and when the closeout documents your contract requires have arrived. I define a closeout checklist the ERP can report against, so project managers know which trades still have open items before final holdback is released. Quebec projects may also need French versions of subcontract statements and notices, which I include in the document requirements where relevant.
Many Canadian contractors keep their books in Sage, QuickBooks, a construction accounting package or an older ERP, with change logs and holdback schedules in spreadsheets. Moving to a new system means migrating each open contract and subcontract with its approved changes, billed to date, holdback, backcharges and payments, then reconciling to the ledger before the first draw on the new system. I plan and verify that through data migration support.
With no software to sell, I am free to recommend a general ERP plus job costing, a construction-specific package, or an add-on, depending on which one your contracts actually need. My demo scripts use your own contracts from more than one province, including a directive priced late, a disputed invoice with a notice of non-payment and a holdback release. The market-neutral version of this commercial model is on ERP for contracting. GST/HST, PST and cross-border trade questions are handled on the Canada ERP consultant page, and the Canada hub gathers the rest of my country notes. All work is delivered remotely.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
FAQ
It can if the rules are stored at contract level rather than as one company setting. I define province, regime, holdback terms and release conditions per contract and test release scenarios with each shortlisted platform. Your legal counsel confirms the rules; the system applies them consistently.
As their own status, separate from agreed change orders. Work under a directive carries cost before the price is agreed, so I link each directive to job cost, field time and material records and any trade instructions it triggers. That shows unpriced exposure clearly to both finance and project managers.
No. Those are legal questions for your counsel. I make sure the ERP records the facts those rules depend on, such as receipts by project, amounts owed to trades, invoice dates and notices issued, so you can follow the advice you receive and show that you did.
Video workshops are booked around your head office day, with recordings and written summaries for teams in other provinces. Process maps and sample documents are shared on screen. A trip to site or head office can be discussed if a particular stage really calls for it.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Insights
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.
