
The Chief Executive opened InfraEX Week on 20 November with a line aimed at one industry in particular. "[W]e are accelerating its adoption across industries, particularly construction," he said of AI, "to optimise resource allocation, enhance project productivity, and improve cost-effectiveness." The Construction Innovation Expo follows at the Convention and Exhibition Centre from 23 to 25 November. The government isn't only talking about it, either. Public works contracts over HK$30 million tendered since 1 June have had to adopt AI.
Very little of it has reached the document that gets a contractor paid. Near the end of the month somebody opens last month's interim payment application, copies the tab and starts again. Quantities come from the QS. Costs come out of the accounts system as an export. Variations come from an email chain. And since August last year, under Hong Kong's security of payment law, that document has had to state how its number was calculated.
Both sides will share one measurement record
The newest of DEVB's site mandates is the one a commercial director should notice. TC(W) No. 1/2026 requires a co-supervision platform on capital works over HK$400 million tendered from 1 April 2026. The platform is "designed for joint use by works departments, consultants and contractors", its uses include site measurements, and its data is synchronised among the contractor, the site supervisory staff and the employer. It is also designed to work with works departments' own systems. On the largest public jobs, both sides will be looking at the same digital measurement of the site.
Our reading of where that leads: claimed quantities on those jobs can be checked against a shared scan the contractor also holds. A claim whose numbers trace back to measured quantities and contract rates holds up to that. One rebuilt each month from a copied tab doesn't.
The rest of the mandates are familiar: 4S on public works over HK$30 million since 2023, with Buildings Department conditions on larger private jobs, and BIM on government capital works of that size. The AI circular, TC(W) No. 3/2026, lists design, tender checking and supervision-system reporting as its uses. None of those produces the contractor's claim.
Cap. 652 made the claim show its calculation
The Construction Industry Security of Payment Ordinance (Cap. 652) came into full operation on 28 August 2025. It applies where the main contract was signed on or after that date, for public contracts and private new works where the main contract is at least HK$5 million for construction work, or HK$500,000 for related goods and services. Every subcontract down a covered chain is covered too, whatever its value, and oral contracts count. Your own subcontract date doesn't decide it. A subcontract signed this year under a 2024 head contract is outside.
Fit-out and E&M firms should check existing-building jobs one by one: work at an existing residential unit or a building's common areas is excluded, as is non-residential work that doesn't need Buildings Department approval. We covered what the ordinance does and doesn't do for retention in our retention piece.
The part that matters for the back office is what a claim has to contain. The Construction Industry Council's briefing on the ordinance puts it plainly:
The payment claim must: a) be in writing; b) identify the construction work or related goods and services to which the payment relates; and c) state the claimed amount and how it is calculated
The same briefing adds a few rules a finance team should pin up next to the claim template. You serve one payment claim for a progress payment, and you don't put any amount under adjudication, or already adjudicated, into it. If the contract has a procedure for additional payments such as variation orders, that procedure has to be completed before the variation is claimed, unless the contract sets no period for it and the paying party doesn't finish it within a reasonable time. And the parties can still agree the basis of valuation in the contract, so the calculation follows whatever the contract says.
Commercial negotiation hasn't gone anywhere, and most interim valuations will still be agreed across a table. What's changed is that the claim is a dated document that states its calculation, and the claimant has every reason to get the numbers right before it's served.
In June the Secretary for Development told LegCo that no adjudication had yet been started, with the ordinance in force for less than a year, and said the government believes the law "carries a deterrent effect". We'd add a simpler reason, and it's our reading rather than the government's. Only jobs under main contracts signed since August 2025 are covered, and few of those had reached a disputed valuation by June. We haven't found a newer count.
When you're the one paying
A main contractor sits on both sides. It claims from the employer and receives claims from its own subcontractors, and the rules bite harder on the paying side.
The payment response is due within 30 days of a claim being served, or an earlier day if the contract says so. A certificate or assessment issued under the contract counts as the response if it meets the ordinance's requirements. Miss the deadline and you can't raise set-off, such as liquidated damages you'd planned to pass down, if that claim goes to adjudication. The ordinance also prohibits pay-when-paid terms, so the employer paying you late doesn't stop the clock on your subcontractors.
That makes the claims you receive a register problem. Every subcontractor claim needs a received date, a deadline and a response, and on a job with twenty subcontractors that's twenty clocks a month. That's hard to run from an inbox.
What breaks when the claim lives in a spreadsheet
Contractors rarely lack data. It usually sits across three places that don't agree.
The claim spreadsheet pulls measured work from one file, cost from an accounts export taken on a particular day, and variations from whoever kept the log. Each month the export is a little different, a variation gets approved after the cut-off, and a subcontractor invoice lands late. Small differences pile up until a quantity surveyor on the other side asks how a line was calculated.
Then there's the two-regime problem. Cap. 652 isn't retrospective, so a contractor with jobs under main contracts signed before and after 28 August 2025 runs different payment rules on different jobs, sometimes for the same client. In a workbook that distinction tends to end up living in somebody's head.
The claim and the WIP share inputs, not answers
The interim claim and the WIP schedule behind your year-end accounts aren't the same number, and they shouldn't be. The claim follows the contract's valuation basis, which is usually measured work at contract rates plus variations and materials on site, less retention. Revenue under HKFRS 15 can follow cost. But the two are built from the same inputs: quantities, variation status and what's sitting on site uninstalled. When those inputs live in different files the gap between claim and revenue becomes impossible to explain.
The Hong Kong Institute of CPAs is clear in its HKFRS 15 guidance for engineering and construction that there's no free choice of method for measuring progress. An entity can't pick the input method "solely on the basis that it provides a more stable profit margin". Under a cost-based method, costs of significant inefficiencies, wasted materials and required rework stay out of the measure of progress unless they were reflected in the contract price. In specific circumstances, uninstalled materials come out of the calculation too and are recognised at zero margin.
That's where the inputs pull apart. Wasted material inflates cost-to-cost progress but adds nothing to a measured valuation. Materials on site can be claimable while being excluded from progress. Neither is a problem if the ledger records why the numbers differ. It becomes one when the explanation is a cell comment.
Variations need two separate tags. Cap. 652 asks whether the contract's claim procedure is complete. HKFRS 15 asks whether the modification is approved, which can happen before the price is settled. An approved change with no agreed price gets estimated as variable consideration, under a "highly probable" test that the HKICPA calls a higher hurdle than the old "probable". So a variation can sit in revenue, constrained, before it can go in a claim.
What NetSuite does here, and what it doesn't
NetSuite isn't construction software out of the box, and we say so on our construction industry page. What it does well is hold cost, budget, billing and variation status against one project record. The relevant pieces, from Oracle's documentation:
- Project budgeting sets cost and billing budgets at project and task level, with a project P&L view showing revenue, cost and margin. Oracle's standard task-level budget-versus-actual reports cover labour only, so task-level reporting on materials and subcontract cost is something you build.
- Charge rules create billable amounts from milestones, dates or hours-based progress. Purchase charge rules create billable charges from purchase orders and vendor bills recorded against the project, but only for service and non-inventory items. That suits dayworks and cost-reimbursable items, not measured work, and stocked materials won't flow through them.
- Progress billing, a separate feature, raises an invoice for a percentage of a progress sales order as portions of the work are fulfilled.
On revenue, NetSuite's native percent complete runs on hours logged, which suits consultancies better than contractors. For cost-based progress Oracle has a separate Project Cost-to-Cost Percent Complete SuiteApp. It runs only in OneWorld accounts and needs the Project Management SKU, the Project Accounting and Management module and Advanced Revenue Management (Essentials). It ships with a Traditional Chinese interface. Without it, percent complete can be overridden manually each period, which works for a single-entity subcontractor not ready to move to OneWorld, as long as someone documents the judgement.
None of those takes a QS valuation as its input, so the work is in what gets built around them. For a contractor, we'd build three things:
- a claim record per contract per period, with valuation lines tied to BQ items or milestones, variations carrying both tags, materials on site and retention, producing both the claim document and the invoice;
- a register of subcontractor claims received, each with its 30-day clock and the response or certificate that answered it;
- a report that reconciles each claim to WIP line by line, so the difference between them is explained in the system rather than in a cell comment.
It won't measure work. Your QS still values it, and BIM and site tools stay where they are. Our implementation team can scope this per contract, and a NetSuite health check is the quicker route if you already run NetSuite and the claim still lives outside it.
Before your next claim date
Worth asking the commercial team before month end:
- Could you show, for every line of last month's claim, the valuation evidence behind it (measured quantity, rate, milestone or approved variation) without opening a second file?
- Does each variation carry two tags, one for the contract's claim procedure and one for approval?
- Does the claim follow the procedure tag and the WIP schedule follow the approval tag?
- Do you know which live jobs sit under a main contract signed on or after 28 August 2025?
- For every subcontractor claim received this month, do you know the response deadline and whether a compliant response or certificate went out in time?
If any of those takes longer than an afternoon, your claims, in and out, aren't running from your books yet.



