Construction ERP in Singapore: Progress Claims, Retention and Variations

Why Generic ERP Breaks in Construction

Most ERP software is built around a simple commercial cycle: quote, order, deliver, invoice, get paid. Construction does not work that way. You bill progressively against work done, a portion of every payment is held back for years, the scope changes constantly by design, and the whole payment cycle sits under a statutory regime with deadlines that carry real legal consequence.

Drop a standard ERP into a Singapore contractor and the finance team ends up running the actual business in Excel alongside it. This guide covers the five things a construction system in Singapore has to handle, and what to check before you buy or build one.

1. Progress Claims and the Security of Payment Act

This is the part generic ERP handles worst, and it is the part with legal teeth.

Singapore's Building and Construction Industry Security of Payment Act creates a statutory regime for progress payments in the construction industry, with strictly enforced time limits and a fast adjudication route before an independent adjudicator. The mechanics that matter for your system: a payment claim is served, the respondent must serve a payment response within the statutory period setting out what they propose to pay and the reasons for any amount withheld, and failing to respond in time has serious consequences for the respondent. Adjudication then runs on its own short timetable.

Sources: BCA Security of Payment Act, DLA Piper on adjudication in Singapore

Because the deadlines are strict and dated from service, the system requirement is specific. Your platform should record the date of service of every claim, not just the date it was created, calculate and surface the response deadline, and alert before it lapses. It should hold the claim, the response and any withholding reasons together as one auditable record, because that record is your evidence if the matter goes to adjudication.

A generic sales-invoice module records none of this properly. It records an invoice date and an amount, which is not what the Act cares about.

Do not take legal timelines from a software vendor, including us. Confirm the periods that apply to your specific contracts with your own advisers, since they differ by contract type and can be varied by the contract itself. What we are telling you is what your system must be able to track.

2. Billing Against a Bill of Quantities

Construction bills percentage completion against BOQ line items, not quantity shipped. Your system needs to:

• Hold the BOQ as a structured, versioned document rather than an attached spreadsheet
• Record cumulative certified quantity per line, with this claim calculated as cumulative minus previously certified
• Handle the gap between claimed and certified, because the two are frequently different and the difference is the conversation
• Roll up to a claim certificate the QS or architect will actually accept

The cumulative model is the crux. Standard invoicing is stateless: each invoice stands alone. Construction claims are cumulative and every one references everything claimed before it. Systems that model claims as independent invoices produce reconciliation errors that surface months later.

3. Retention: The Money You Have Earned But Cannot Touch

A percentage of every certified payment is withheld as retention, typically released in two tranches: part at practical completion and the balance at the end of the defects liability period, often a year or more later.

Most contractors track this badly, and it is usually the largest single sum they lose track of. Your system should hold retention per project and per claim, model both release milestones with their expected dates, and produce a live retention register showing what is held, by whom, and when it becomes due. It should also flag retention that has passed its release date and is still outstanding, because that is cash sitting on someone else's balance sheet.

If you build one report in a construction system, build this one. Contractors regularly discover six figures of aged retention nobody was chasing.

4. Variation Orders

Variations are not exceptions in construction, they are routine, and they are where margin is won and lost. The system needs to track each variation from instruction through pricing, approval and inclusion in claims, and critically, to track instructed but not yet approved work.

That last state is the one that costs money. Work proceeds on a verbal or site instruction, it is never formally approved, and at final account it is disputed. A system that makes unapproved-but-executed variations visible on a dashboard, with the instruction record attached, converts an argument into a document.

5. Subcontractor and Retention-Payable Management

You are usually both claimant and respondent. Upstream you claim from the main contractor or developer; downstream your subcontractors claim from you, and the same statutory regime applies to those claims.

Your system should mirror the upstream logic downstream: subcontractor claims received, your payment responses and their deadlines, retention you hold against subcontractors and when you must release it, and back-charges. It should also let you see the position per project on both sides at once, since that is what tells you the real cash position.

What Else a Singapore Contractor Needs

InvoiceNow and the GST E-Invoicing Mandate

The GST InvoiceNow requirement is being phased in across GST-registered businesses through to 2031, based on the Peppol network. Construction is not exempt, and progress claims will need to flow through structured e-invoicing like everything else. If you are choosing a system now, ask how it handles InvoiceNow rather than treating it as a later problem. We cover the phase dates in our InvoiceNow mandate guide and on our InvoiceNow Singapore page.

Multi-Project Cost Control

Committed cost is the number that matters, and it is not the same as spent. A purchase order raised is money committed even though no invoice has arrived. Contractors who only watch actuals discover overruns one to two months late, which in construction is usually too late to act.

Site Reality

Whatever you choose has to work on a phone, in the field, with poor signal, for people who will not tolerate a slow form. If site staff will not use it, your data is wrong and every report built on it is wrong too.

Buy or Build

Both are legitimate. The honest split:

Note the grant asymmetry, because it is the single biggest commercial difference. Pre-approved packaged solutions can access the Productivity Solutions Grant at up to 50% of qualifying costs, capped at S$30,000 per company per financial year. Custom builds cannot use PSG at all, and go through the Enterprise Development Grant instead, which supports up to 50% of eligible costs for local SMEs with no pre-approved vendor list, covering consultancy, software and internal manpower. Both require the project to be new, with no payment or signed contract before applying. See our PSG grant guide.

Sources: Enterprise Singapore Productivity Solutions Grant

What to Ask Any Vendor

Take these to every demo. They separate construction-capable systems from general ERP with a construction brochure:

1. Show me a progress claim built cumulatively against a BOQ, where certified differs from claimed.
2. Where is the date of service recorded, and where does the system warn me before a statutory deadline lapses?
3. Show me the retention register: held, release dates, and what is overdue for release.
4. Show me variations that were instructed but never approved.
5. Show me my position as respondent on subcontractor claims, on the same project.
6. Show me committed cost versus actual, this month, across projects.
7. Show me all of that on a phone.

If a vendor cannot demonstrate items one to three on live data, the system is not built for construction regardless of what the website says.

Frequently Asked Questions

What makes construction ERP different from normal ERP?
Cumulative progress claims against a bill of quantities rather than standalone invoices, retention held and released across two milestones often years apart, variations as routine rather than exceptions, statutory payment deadlines under the Security of Payment Act, and being both claimant and respondent on the same project.

Does the Security of Payment Act affect what my software must do?
Yes. Because the statutory timelines run from the date a claim is served and are strictly enforced, your system needs to record service dates, calculate and surface response deadlines, and keep claims, responses and withholding reasons together as an auditable record for adjudication. Confirm the specific periods for your contracts with your own legal advisers.

Can I use the PSG grant for construction ERP in Singapore?
Yes if the solution is on the IMDA pre-approved list, at up to 50% of qualifying costs capped at S$30,000 per company per financial year. Custom-built systems are not PSG eligible and go through EDG instead. Apply before making any payment to the vendor.

How should retention be tracked?
Per project and per claim, with both release milestones modelled and dated, surfaced as a live register showing what is held, by whom, when it is due, and what is overdue. This is the report most contractors lack and the one that most often recovers real money.

How long does it take to implement a construction ERP?
A focused first module, usually progress claims and retention, can be live in four to eight weeks. A full multi-project rollout across finance, procurement and site should be phased over several months so site teams adopt each part properly.

Talk It Through

We build construction operations systems for Singapore contractors, from progress claims and retention through to subcontractor management and site capture. If you want a straight read on whether to buy or build, get in touch or see our construction ERP page.