.svg)
In short: NetSuite for construction and contracting connects project budget, procurement, contract certification, and payment into a single system — so any payment traces back to an approved commitment, a measured quantity, and a named approver in seconds.
Ask any project finance manager what keeps them up at night, and it isn’t the size of the budget. It’s the question a lender’s auditor asks without warning: “Why was this payment made, against what commitment, certified by whom, and net of what deductions?”
On most construction projects, answering that means reopening a purchase order, a bill of quantities, a certificate, and spreadsheets that don’t quite reconcile. This walkthrough shows how a NetSuite construction implementation built around project costing and approval controls answers it directly — using real screens, and the terms contracting teams already use: three-way match, retention, advance recovery, CWIP, maker-checker.
Key takeaways
How money moves through a construction project in NetSuite
Every dollar follows the same circuit: approved budget becomes a commitment through a priced contract or a purchase, gets tested against evidence before it’s certified or matched, clears approval and control gates, and settles as a paid, reconciled, reported transaction.
The two decision points are where the real controls sit: the three-way match on the procurement side, and the vendor bank change / maker-checker check before payment.
Project cost control dashboard: one live position
The top-level view shows approved budget, committed value, certified-to-date / CWIP, available to commit, retention held, and advance outstanding as six live figures rather than a month-end report.
An exceptions panel flags open items — a certificate awaiting posting, a pending vendor bank change, an overdue approval — each with a named owner, generated automatically. Every figure updates the moment a transaction is approved, so this is a current position, not a historical snapshot.
Budget position by work package
The approved budget is broken into work packages — civil works, mechanical equipment, electrical, owner’s costs, financing costs, contingency.
Each package carries allocated, committed, certified, available, and percentage consumed. Packages running close to fully consumed are visible immediately, well before an overrun becomes a variance report.
Cost breakdown structure (CBS) and budget version control
The project master record holds fixed reference data — project company, offtaker, concession term, financial close date, base currency, approved budget — with budget version control: a revised budget archives the prior version rather than overwriting it, so future variance is measured against a baseline that can’t quietly move.
The cost breakdown structure (CBS) runs four levels — overall → parent → package → contingency — carrying allocated, committed, expensed, certified, and available values. The key rule: commitment can only happen at package level, which keeps the cost structure disciplined instead of becoming a catch-all ledger.
Requisition to bill: the three-way match
For non-contract spend, the standard chain applies: requisition → purchase order → goods receipt → vendor bill. The budget check happens at the requisition stage — available balance drops the moment a request is raised, not weeks later when the bill lands.
Here, a short-shipped delivery combined with an invoiced rate above the purchase order rate produces a three-way match failure — a SAR 392,000 variance between what was ordered, received, and invoiced. The option to send the bill for payment approval isn’t available until the mismatch is resolved: return the invoice, raise a debit note, or approve the variance under a documented override.
Approval routing and segregation of duties
Every approval — requisitions, certificates, vendor bank changes, back-charges, payment runs — routes through a single queue.
Routing rules are driven by transaction type, amount, and cost category, so a requisition above a set threshold on an equipment cost code escalates automatically. Self-approval is blocked by default, and every reject or return requires a documented reason, turning rejection patterns into reportable data.
For smaller teams, segregation of duties gets addressed realistically: a small finance team can’t fully separate every function, but the boundaries that matter most — preparer never certifies, certifier is independent, payment requires dual release — can be enforced and logged as compensating controls.
Vendor bank changes: maker-checker fraud control
Vendor bank detail changes are one of the most common vectors for payment fraud on construction projects.
The moment a change is requested, all payments to that vendor are automatically held, regardless of urgency. Release requires maker-checker verification — two separate approvers independently reviewing supporting evidence before the change is accepted. The hold applies instantly, without anyone needing to remember to trigger it.
Project contracts and the bill of quantities (BOQ)
Contract award is where budget converts to commitment. Value and dates are validated against available budget before approval; on a pass, the full contract value moves from available to committed — which is why the dashboard reflects exposure long before the first invoice arrives.
The contract carries its advance payment percentage, retention rate, and contract type, alongside the bill of quantities (BOQ): every priced line item the contract will be measured and certified against. Pricing at line-item level is what makes granular progress certification possible downstream.
Variation orders and extension of time (EOT)
Each variation order is tested against the specific package budget before approval and adds its own priced BOQ lines, so it’s measured and certified like any other contract work rather than applied as a lump adjustment.
A running cumulative variation percentage is tracked against a reclassification threshold — cross it, and the change requires a different approval path. Extension of time (EOT) is recorded separately from cost by design: an approved EOT updates the revised completion date automatically but carries no implied entitlement to additional payment, which protects the commercial position if either is disputed.
Interim payment certificates, retention, and advance recovery
This is the core of construction accounting. The interim payment certificate (IPC) is built from priced BOQ lines, not the contractor’s submitted total. Where claimed and certified percentages differ — reinforced concrete claimed at 30%, certified at 25% because two pours haven’t passed strength testing — the reason is recorded against the specific line, with the certifying engineer named.
From the certified position, a calculation ladder applies retention withheld at the contracted percentage, advance payment recovery deducted pro-rata automatically, and any back-charges or contract penalties, each posted as its own approved record. In this example, a SAR 101.3 million claim nets down to a SAR 20.1 million certified payment — with every step traceable to a line, a measurement, and an approver.
Payment runs, multi-currency settlement, and bank reconciliation
Approved certificates and bills join the payment run, often across multiple currencies, with realised FX differences recognised at settlement rather than discovered at year-end.
If a vendor’s bank change is still pending its second checker, that vendor’s payment is automatically excluded from the run — even if it’s the largest amount in it. Releasing the run requires dual release: one person prepares it, another releases it.
Capital work in progress (CWIP) and period close
During construction, the project is building an asset, not running a profit and loss. CWIP is the roll-forward where every certified cost, milestone, and capitalised borrowing cost (IAS 23) accumulates period over period.
At commercial operation, the accumulated balance transfers to the fixed asset register in a single controlled transaction rather than a year-end reconstruction. None of this closes without the period-close checklist — bank reconciliation, certificate posting, accruals, FX revaluation, management sign-off — each task with a named owner and due date. The period cannot be locked until every task is complete.
Frequently asked questions
What is a three-way match in NetSuite construction accounting?
A three-way match compares a purchase order, the goods receipt, and the vendor invoice before a bill can be paid. If the quantity invoiced doesn’t match what was received, or the invoiced rate doesn’t match the purchase order rate, NetSuite blocks the payment action until the variance is resolved.
What is an interim payment certificate (IPC)?
An interim payment certificate certifies how much of a construction contract’s work has actually been completed, based on measured bill-of-quantities lines rather than the contractor’s claimed total. Retention, advance recovery, and approved deductions are applied automatically to arrive at the net amount payable.
What is retention and advance recovery in construction contracts?
Retention is a percentage of each certified payment withheld as security until defined milestones are met. Advance recovery is the pro-rata repayment of an upfront mobilisation advance, deducted automatically from each certificate until fully recovered.
How does NetSuite prevent vendor payment fraud on construction projects?
Through a maker-checker control on vendor bank detail changes: the moment a change is requested, all payments to that vendor are held automatically, and release requires two independent approvers to verify supporting evidence.
Can segregation of duties work with a small finance team?
Not completely — a small team can’t fully separate every function. But the boundaries that matter most can still be enforced and logged: the person who prepares a payment cannot release it, the certifier is independent, and self-approval is blocked automatically. That gives auditors and lenders a documented set of compensating controls.
How does NetSuite handle CWIP and IAS 23 capitalised interest?
Every certified cost, equipment milestone, and capitalised borrowing cost accumulates into a capital work in progress (CWIP) ledger throughout construction, rather than running through the profit and loss statement. At commercial operation, the balance transfers to the fixed asset register in one controlled transaction.
The bottom line
Every control above exists to answer one recurring question quickly and completely: why was this payment made, against what commitment, certified by whom, and net of what deductions? Because budget, commitment, procurement, certification, and payment are linked records rather than separate systems reconciled by hand, that answer is a matter of opening the right screen — not reconstructing a paper trail under pressure.
