Design-build-operate (DBO) contracts are the commercial engine of the data centre industry. They are also among the most treacherous revenue structures in corporate accounting. A single DBO agreement can bundle construction milestones, long-term service commitments and mixed capital and operating revenue streams into one customer contract spanning a decade or more. As Indonesia’s data centre market accelerates towards a projected US$6.08 billion by 2031, more operators are signing more of these contracts, and automated revenue recognition is becoming the difference between clean audits and standing risk.
Why DBO contracts strain revenue accounting
Milestone-based billing
Construction phases bill against milestones, but billing schedules and revenue recognition schedules are different things. Cash received at a milestone may relate to obligations satisfied earlier, later, or over time, and treating invoices as revenue is precisely the error modern standards were written to eliminate.
Long-term service contracts
The operate phase generates service revenue recognised over years, often with embedded SLAs, indexation clauses and renewal options. Each feature affects how much revenue belongs in each period, and mid-contract modifications reset the arithmetic.
Mixed revenue streams
Capex-style construction revenue and opex-style service revenue coexist in one contract, with a single negotiated price spread across them. Allocating that price defensibly, and re-allocating it when scope changes, is where manual spreadsheets begin to fail.
The standard is explicit: PSAK 72
Indonesia adopted the global revenue standard as PSAK 72, Revenue from Contracts with Customers, effective from 1 January 2020 and adapted from IFRS 15. It replaced the previous patchwork of revenue and construction contract standards with a single five-step model: identify the contract, identify the performance obligations, determine the transaction price, allocate the price to each obligation, and recognise revenue as each obligation is satisfied. For a DBO contract, that means formally separating the design, build and operate elements, allocating the contract price across them, and recognising each on its own schedule, with full documentation at every step.
Applied manually across a portfolio of multi-year contracts, the standard creates a compounding workload: every variation order, scope change and renewal triggers reassessment, and every reassessment is a chance for error that an auditor will later find.
What automated revenue recognition delivers
Automation moves the five-step model out of spreadsheets and into the system of record. NetSuite, extended with Netgain for advanced accounting automation, provides:
- Automated revenue recognition. Recognition rules are configured per performance obligation, and the system generates period revenue schedules and journal entries automatically, decoupled from billing timing. Milestone invoices, deferred revenue, and unbilled receivables stay continuously reconciled.
- Multi-element contract handling. Design, build, and operate elements as distinct obligations within one contract record, with the system maintaining price allocation and recalculating it systematically when modifications occur.
- Compliance with accounting standards. Every recognition decision carries an audit trail back to the contract, the obligation and the rule applied, turning PSAK 72 compliance from an annual reconstruction exercise into a standing property of the ledger.
Our approach
We implement NetSuite revenue management and Netgain for operators, developers and service providers across Southeast Asia’s data centre ecosystem. As a multi-year winner of NetSuite’s ASEAN Partner of the Year award, we configure recognition structures around how DBO contracts are actually written in this region, and we localise the surrounding tax and reporting layers for Indonesia and each of the other markets we serve.
DBO contracts are winning the data centre market. Automated revenue recognition keeps them from losing it in the audit. Speak to our team about de-risking yours.
