From tender to cash: how a construction ERP protects project margin.

Construction does not usually lose margin in one dramatic transaction. It loses margin between handovers: tender to budget, request to purchase, receipt to site issue, measurement to certificate, and certificate to cash.

A project can be busy on site and still be commercially unclear. The tender team has one BOQ, procurement has a purchase tracker, the store has issue sheets, the quantity surveyor has measurements, finance has posted bills, and management has a summary assembled after the month closes. Every file may be individually correct while the project picture remains late.

A useful construction ERP does not force those teams into one mixed screen. It gives each team a clean operating lane—commercial, procurement, stores, site, people and finance—while carrying the same project, cost centre, work package and document references across every handover.

01 / Project control model

One project needs six connected views—not one vague “cost” total.

Each view answers a different management question. Combining them too early hides the very variance the system should explain.

The project dashboard can place these views side by side, but their source documents remain distinct. A purchase order is a commitment; a goods receipt proves receipt; a material issue charges a work package; a vendor bill creates the payable. Treating all four as the same event creates false cost timing.

02 / Tender to contract

The commercial baseline must survive the award.

The process begins with the client BOQ and tender conditions. Rate build-up should preserve direct material, labour, equipment, subcontract, indirect cost, overhead and intended profit instead of storing only a final selling rate. Internal approval records who accepted the commercial position before submission.

Once submitted, the priced tender is locked as history. A lost tender remains useful for rate history and estimating feedback. A won tender creates the owner contract or sales order, project, cost centre or analytic account, and the controlled BOQ baseline used by delivery and billing.

Variations should add history, not rewrite it.

Extra items, revised quantities and scope changes need a variation order with a clear status: proposed, internally approved, submitted, client approved, rejected or pending. An approved variation updates revised contract value, the delivery budget and later billing. It should never silently replace the original BOQ or make an unapproved claim look like secured revenue.

03 / Budget, procurement & stores

Cost control starts when demand is raised—not when the vendor bill arrives.

The project budget translates the commercial estimate into work packages the site can execute. Each material request identifies the project, cost code, task, required date, specification and quantity. Approval checks necessity, available budget and procurement route before a commercial commitment is made.

At purchase-order confirmation, management should see committed cost even though accounting has not yet received a bill. At receipt, the store records what physically arrived, including partial delivery, rejected quantity or quality hold. Material issue then transfers consumption to the correct project and work package. Returns, site transfers and surplus material follow their own traceable movements.

04 / Site execution & subcontractors

Site evidence is what turns activity into accountable cost and billable progress.

Daily work, measurement sheets, material issues, labour attendance, project expenses and equipment use should carry the same project and work-package context. The purpose is not to collect more forms. It is to make the cost and progress behind a management figure available while the work is still current.

Subcontractors need a dedicated commercial lane. The agreement records scope, BOQ item, quantity, rate, advance, retention, security and payment terms. Site measurement establishes completed work. The subcontractor bill or certificate applies previous work, retention, advance recovery, tax and other approved deductions before finance records the payable.

This separation matters: a material issue is not an employee transaction, and attendance is not proof of installed quantity. They remain different records. What joins them is the project and cost structure used for analysis.

05 / Progress billing, deductions & cash

An IPC should explain the journey from measured work to money in the bank.

The progress-billing process begins with cumulative measurement against the owner contract BOQ. The current claim separates previous certified value from current-period work. Approved variations appear explicitly. Retention, advance recovery, withholding tax and other contractual deductions remain individually visible.

The approved certificate supports the customer invoice; it is not automatically the same accounting event. Finance posts the invoice, manages credit or adjustment documents where authorised, and allocates the receipt. The project view then distinguishes measured, claimed, certified, invoiced, due and received values instead of calling them all “revenue.”

06 / People, approvals & mobile work

The site should capture evidence; the ERP should govern the transaction.

HR and payroll remain a separate hire-to-pay process: employee master, contract, attendance, leave, payroll approval and salary payment. Where project costing requires it, approved attendance or labour allocation carries project and site dimensions into costing. That connection supports analysis without mixing employee records with procurement documents.

Mobile apps are useful when the work happens away from a desktop. Site attendance, project expenses, receipts, location, photos, measurements or approval actions can be captured in the field and synchronised through a controlled review. Odoo or the central ERP remains the source for employees, projects, cost codes, budgets, approvals, posted documents and management reports.

07 / Project MIS & close-out

Management needs an explanation of margin, not a decorative dashboard.

A dependable project-control view uses one reporting cut-off and shows whether every value is original, revised, committed, incurred, certified, invoiced or paid. Drill-down should lead to the BOQ line, purchase order, material movement, subcontract certificate, journal entry or receipt behind the number.

Close-out is a controlled process as well: final measurement and account, completion status, unbilled value, open purchase orders, surplus material, pending subcontract liabilities, snag work, asset handover and retention release. The final margin should reconcile to the full commercial history—not only the final general-ledger balance.

The result is a construction system that supports tendering, project delivery, procurement, stores, subcontractors, HR, billing and finance without turning them into one confused workflow. Each team owns its record; management owns the connected outcome.