Call Us/Whatsapp Us: +65 8385 9933 | Email: aman@amanengineering.com.sg for inquiry and free quotation

Development Charge Singapore Rules Are Now the LBC

Singapore urban construction land with survey tools

The Land Betterment Charge (LBC) is a single levy on the increase in land value created by a chargeable planning consent, and it replaced the Differential Premium, Development Charge (DC), and Temporary Development Levy (TDL) for every consent granted on or after 1 August 2022. If your project falls under the new regime, expect a Liability Order (LO) issued directly by the Singapore Land Authority (SLA), with payment due within one month of that order. This is the practical reality property developers, landowners, and investors need to plan around now.

What changes operationally for you:

  • A single agency bills you. SLA now issues the LO directly, rather than routing separate DC and Differential Premium claims through URA and SLA.
  • The clock starts fast. Payment is due within one month from the date of the LO, so cashflow planning has to happen before, not after, approval lands.
  • Feasibility work starts earlier. Pull baseline data from SLA’s INLIS system and the OneMap LBC estimator during feasibility studies, well before you lodge your first re-submission.

The rules governing computation still lean on the old DC framework’s logic, so practitioners familiar with the previous system aren’t starting from zero. But the collection mechanism, the timelines, and the paperwork trail have all shifted, and treating LBC as a footnote line item rather than a planned cost is the most common mistake we see in early-stage feasibility models.

Key Takeaways

The Land Betterment Charge consolidates DP, DC, and TDL into one SLA-administered levy, and developers who verify their baseline data and model both computation methods before submission avoid many cost surprises.

Point Details
LBC replaced three charges Differential Premium, DC, and TDL merged into one levy effective 1 August 2022.
SLA issues the bill The Liability Order comes directly from SLA, with payment due within one month.
Check baseline data early Use INLIS and the OneMap estimator during feasibility, not after approval lands.
Know the initial rate convention LBC is generally set at 70% of the increase in land value, with 100% in exceptional cases.
Valuation election is irrevocable Once you choose case-by-case valuation over Table of Rates, you cannot switch back.
Watch the half-yearly rate reviews Submission timing relative to a rate revision can change your final LBC figure.
Get feasibility-stage support Com helps verify baselines and model LBC exposure before you submit.

Table of Contents

When Does the Development Charge Singapore Regime Apply?

LBC applies whenever a chargeable consent increases the value of your land. That covers a specific, defined list of triggers rather than every planning interaction you’ll have with the authorities.

The chargeable events are:

  • Provisional Permission (PP) granted for a proposed development that increases land value beyond its existing use.
  • Written Permission (WP) issued for the same, once the development proposal is finalized.
  • Plan lodgement for an authorized development under the Planning Act’s plan lodgement track.
  • Lifting or variation of a restrictive covenant attached to the land title, where removing the restriction raises the land’s value.

The taxable person is typically the landowner, or the party to whom liability is apportioned under the sale and purchase or joint development agreement. SLA is notified once URA grants the relevant planning approval, which triggers the LO process on SLA’s end without requiring a separate application from you.

One transitional detail matters for anyone with applications straddling the changeover: the LBC regime applies to all planning permissions, plan lodgements, and covenant variations granted on or after 1 August 2022. Anything approved before that date remained under the old DC or Differential Premium rules. If your project has a long approval history, check which regime actually governs your specific consent date rather than assuming.

How Liability Orders Work and When Payment Is Due

Once URA grants approval, SLA follows up with a Liability Order that sets out the LBC amount, names the taxable person or persons, states the apportionment where liability is shared, and lists payment methods and the due date.

Payment is due within one month of the LO, and the same one-month clock applies if SLA later issues a Revised Liability Order (RLO). This isn’t a soft deadline. Developers who assume they can negotiate an extension after receiving the LO are working from an outdated mental model carried over from the old DC process.

Key operational points to work through when the LO lands:

  • Verify the apportionment. If multiple owners or joint venture partners share the land, confirm the LO reflects the agreed split before payment, not after.
  • Check for a database update fee. SLA charges a baseline update fee, generally $1,100, when the LO requires correcting or updating the parcel’s pre-chargeable valuation baseline in INLIS.
  • Confirm payment channels early. SLA’s LO specifies accepted payment methods, and coordinating internal approvals for a six or seven-figure payment inside a 30-day window needs to start the day the LO arrives, not the week before it’s due.

Coordinating this timeline with your Qualified Person and the broader statutory approval sequence is easier when you already understand the planning approval process end to end, since LO timing is directly downstream of when URA grants your approval.

Calculating LBC: Table of Rates vs Valuation Method

SLA computes LBC using one of two accepted methods, and the choice between them can materially change your cost exposure.

The Table of Rates method applies standardized rates by sector and use group, published in URA’s sector maps and rate tables. This is the default, fastest route for most projects, particularly when your proposed use fits cleanly into an existing use-group category with a published rate.

The Valuation method hands the computation to the Chief Valuer at the Inland Revenue Authority of Singapore (IRAS), who determines the actual increase in land value on a case-by-case basis. Electing valuation is irrevocable once chosen, which is worth repeating: you cannot switch back to Table of Rates partway through if the valuation outcome disappoints you.

A few structural rules govern how the numbers get set:

  • The material date matters. For Provisional Permission, the material date is generally the PP grant date, or the start date of a PP extension. For other chargeable events, WP or authorization dates apply. This date fixes which rate table version and which valuation baseline apply to your project.
  • The 1st re-submission locks the computation. To speed up approval and payment, LBC is computed based on the use and intensity declared in your first re-submission for Provisional Permission. If the final Written Permission deviates with a further increase in land value, SLA issues a Revised Liability Order requiring the additional amount within one month.
  • Tenure adjustments apply for shorter leaseholds. Where the residual unexpired tenure is 99 years or less, SLA applies the Leasehold Table to adjust the chargeable value proportionately. Temporary permissions get their own adjustment treatment reflecting the shorter consent period.
  • The initial rate convention is roughly 70%. URA’s circular sets the initial LBC rate at generally 70% of the increase in land value arising from the grant of consent, with 100% applied only in exceptional cases.

URA and SLA publish worked numeric examples in their circular appendices, and those official appendix figures are the ones to reference for actual project modeling rather than generic online calculators.

Understanding how land value gets assessed in the first place is worth a closer look if you’re new to Singapore’s valuation conventions. Our guide on building valuation practices walks through how valuers approach comparable-use assessments, which is directly relevant background for anyone weighing the Table of Rates against a case-by-case valuation election.

Where to Estimate Development Fees Before You Submit

Nobody should be discovering their LBC exposure for the first time when the Liability Order arrives. Three official tools let you model the number well before submission.

SLA’s INLIS baseline data gives you the pre-chargeable valuation baseline for a parcel, which is the starting point against which any increase in land value gets measured. Checking this early tells you what “before” looks like, so the “after” calculation isn’t a surprise.

The OneMap LBC estimator lets you model LBC payable for a proposed development scenario using current published rates. It’s genuinely useful for early feasibility screening across multiple site options or massing scenarios.

URA’s sector maps and rate tables identify which sector number and use group apply to your site, which determines the rate you’d use under the Table of Rates method. These maps are published as downloadable references and get updated when rates change.

A few things to pull at the parcel level before you commit to a feasibility number:

  • Pre-chargeable valuation baseline from INLIS.
  • Current authorized or approved development on the site, since LBC charges the increase over existing rights, not the gross new value.
  • The sector number and use group classification from URA’s current sector map.
  • The rate table version effective on your anticipated material date.

Rates aren’t static. URA reviews Development Charge rates on a half-yearly basis in consultation with the Chief Valuer, and OneMap publishes rates across review periods so you can model how a submission timed before or after a rate revision might change your exposure.

Application Checklist for Developers and Qualified Persons

Getting the sequence right at submission stage is where most cost surprises get avoided or created. Here’s the order that keeps LBC exposure visible from day one.

  1. Confirm the INLIS baseline for your parcel before drafting your feasibility model, so your starting land value figure is accurate.
  2. Capture proposed use and intensity precisely in your first re-submission to Provisional Permission, since this is the data set SLA uses to compute the initial LBC.
  3. Model LBC under both methods during feasibility, running Table of Rates against a rough valuation-method estimate, even if you expect to use the standard rate table.
  4. Budget contingency for a Revised Liability Order, particularly if your Written Permission is likely to shift from what you declared at first re-submission.
  5. Verify taxable person details and apportionment the moment the LO arrives, especially on joint-venture or multi-owner sites.
  6. Confirm whether a database update fee applies, checking whether SLA needed to update your parcel’s baseline as part of the LO process.
  7. Schedule payment within the one-month window, building internal sign-off time into your project calendar rather than treating it as a formality.
  8. Account for CORENET X processing fee timing if you’re submitting through CORENET X, since DA processing fees split 50/50 between the Design Gateway and Construction Gateway rather than landing as one upfront charge.

Pro Tip: Treat LBC, the potential RLO amount, and the CORENET X fee split as three separate line items in your cashflow model rather than one bundled “statutory fees” bucket. Each has its own trigger date, and lumping them together is how finance teams get blindsided by timing rather than amount.

Documenting your submission thoroughly also protects you if a Revised Liability Order dispute arises later. Reviewing the building plan submission requirements for your project type before your first re-submission helps ensure the use and intensity data your Qualified Person files is precise enough to avoid an unnecessary RLO down the line.

Disputing an LBC Figure or Electing Valuation

If the Table of Rates outcome looks wrong for your site, you have a formal route to a different number, not just an informal complaint process.

You can request case-by-case valuation by the Chief Valuer at IRAS instead of accepting the standardized Table of Rates figure. This is worth remembering: once elected, the valuation method is irrevocable, so you’re committing to whatever the Chief Valuer determines rather than keeping the standardized rate as a fallback.

Formal dispute routes for charge determinations sit within the procedural framework of the Planning Act and its associated rules, which set out how valuation and computation disputes get raised and processed. This is a legal and procedural mechanism, and if your case involves a significant sum, working through the specific documentation and timeline requirements with a qualified advisor is a sensible use of professional time before you commit to a dispute route.

Practical triggers for electing valuation rather than accepting Table of Rates include:

  • Unusual site characteristics that don’t fit neatly into any published use-group category.
  • No suitable comparable use group exists for a genuinely novel development type on your parcel.
  • The standardized rate produces an outcome that looks disconnected from actual local land values, based on recent comparable transactions you can point to.

This article gives general guidance on LBC procedures and is not a substitute for professional or legal advice on your specific case; confirm current rules and your options directly with SLA, URA, or a qualified advisor before making a valuation election.

What Developers Should Watch: Rate Reviews and Tool Limits

The half-yearly rate review process has real timing implications. URA reviews rates in consultation with the Chief Valuer twice a year, and because the material date for your consent fixes which rate table version applies, the timing of your submission relative to a pending review can change your final number.

  • Rate reviews aren’t announced far in advance. Developers with flexibility on submission timing sometimes weigh whether to lodge before or after an anticipated review, though this requires reading published circulars carefully rather than guessing.
  • INLIS baseline rollout increases transparency but isn’t infallible. SLA is progressively making parcel baseline data available on INLIS, which is a genuine improvement over the old system’s opacity. Still, verify the figure against your own records rather than assuming the published baseline is automatically correct for your parcel, since any correction needed at LO stage can trigger the database update fee.
  • The OneMap estimator has real limits. It’s built for standardized Table of Rates scenarios using published use groups. It won’t model a valuation-method outcome, and it won’t capture site-specific factors a Chief Valuer might weigh in a case-by-case assessment. Treat OneMap output as a planning-stage estimate, not a number to take to the bank.

Pro Tip: If your project sits close to a sector boundary on URA’s maps, don’t assume the estimator picked the correct sector automatically. Cross-check the sector number against the published map PDF directly, since a boundary error can shift your rate meaningfully.

Why Singapore Replaced the Old Development Charge System

The move to LBC consolidates what used to be three separate charging mechanisms, Differential Premium, DC, and TDL, into a single framework administered by one agency. SLA frames this as a deliberate simplification: instead of navigating parallel processes at URA and SLA depending on whether your project involved a lease upgrade, a use change, or a temporary permission, developers now deal with one billing agency and one LO process.

The underlying policy logic hasn’t changed much from the old DC regime. The government still captures a share of the land value uplift created when planning consent allows a more valuable use, and that captured value continues to fund broader infrastructure and urban development priorities. What changed is administrative architecture, not the basic principle that betterment in land value triggers a charge.

For urban redevelopment specifically, a single consolidated charge makes mixed-use and phased redevelopment sites easier to assess, since developers previously navigating both a Differential Premium calculation for a lease top-up and a separate DC calculation for a use change now face one computation under one set of rules.

LBC vs the Old DC, Differential Premium, and TDL

The core computation logic carries over from the previous system, which is genuinely good news for practitioners who built their feasibility models around the old DC framework. But three transitional differences matter.

First, collection is centralized. Previously, Differential Premium claims for lease-related land value increases were handled separately from DC claims for use or intensity changes, often through different administrative channels. Now SLA issues a single LO covering the relevant chargeable event, regardless of whether it originated as what would have been a DP or DC matter under the old system.

Second, TDL is folded in. Temporary Development Levy, previously charged for temporary permissions, now falls under the same LBC framework with its own tenure-based adjustment rather than a standalone TDL calculation.

Third, the RLO mechanism formalizes what used to be handled more informally. The explicit rule that LBC computes from your first re-submission’s declared use and intensity, with a Revised Liability Order issued if Written Permission deviates, gives both SLA and developers a clearer, documented trigger point for recalculation.

For projects with consents granted before 1 August 2022, the old DC, Differential Premium, and TDL rules still govern, so don’t assume LBC rules retroactively apply to a legacy approval.

Exemptions and Relief Under the LBC Framework

Not every planning consent triggers a chargeable LBC event. Exemptions generally track the same categories that were exempt under the old DC and Differential Premium system, since the underlying principle, charging only genuine increases in land value, hasn’t changed.

Development that doesn’t increase the land’s value beyond its existing authorized use typically falls outside LBC’s scope entirely. Minor changes of use within the same use group, or developments that don’t intensify beyond what’s already authorized on the site, generally won’t trigger a chargeable computation. Government and statutory board projects have historically received different treatment under specific provisions, reflecting their distinct funding and public-purpose status.

Because exemption criteria are fact-specific and depend heavily on your parcel’s existing authorized use and the exact nature of your proposed consent, confirm your project’s eligibility directly with SLA or URA rather than assuming a general exemption applies. A qualified consultant reviewing your specific site history against the current framework is the more reliable route than relying on generic guidance.

A Realistic LBC Calculation Scenario

Consider a site zoned for mixed commercial and residential use, currently authorized for a lower-intensity commercial development, where the owner seeks Provisional Permission for a higher-density mixed-use redevelopment.

The process would run roughly as follows. The developer first checks INLIS for the parcel’s pre-chargeable baseline, reflecting the current authorized commercial use and its existing land value. The Qualified Person then lodges the first re-submission for PP, declaring the proposed use mix and intensity, which becomes the basis SLA uses for initial computation.

Measuring wheel at land baseline survey site

SLA and URA identify the applicable sector and use group from the current sector map, then apply the published Table of Rates rate to the assessed increase in land value between the pre-chargeable baseline and the proposed new use.

If Written Permission is later granted with a higher unit count or additional gross floor area than what was declared at first re-submission, SLA issues a Revised Liability Order for the incremental increase in land value, again due within one month. If the site also carries a residual lease under 99 years, the Leasehold Table adjustment applies to scale the chargeable amount to the remaining tenure. For the actual numeric rate applicable to your sector and use group, always check the current published rate table rather than relying on a prior period’s figures, since rates shift with each half-yearly review.

What Happens if You Miss the LBC Payment Deadline

Missing the one-month payment window on a Liability Order isn’t a minor administrative lapse. SLA’s LO specifies the due date precisely because the LBC framework treats timely payment as a condition tied to your development proceeding.

Late or non-payment can hold up subsequent statutory milestones, since planning approval and its associated charges are part of the same regulatory sequence your project needs to clear before construction can commence lawfully. For projects already under construction based on Written Permission, unresolved LBC liability creates exposure that can complicate later stages of approval, including Temporary Occupation Permit processes that depend on a clean compliance record.

If cashflow constraints genuinely threaten your ability to meet the one-month deadline, raise this with SLA directly and as early as possible rather than letting the deadline pass silently. Waiting until after the due date to communicate a problem removes options that might have existed if raised proactively. This is general information on the LBC payment framework, not legal advice on enforcement consequences for a specific case, and the safeguard here is straightforward: confirm your project’s exact payment terms and any available options with SLA directly.

How to Challenge an LBC Assessment: Timelines and Practice

If you believe your Table of Rates computation misapplied the sector, use group, or material date, the first practical step is raising the discrepancy with SLA or URA directly, since administrative correction is often faster than a formal challenge when the issue is a documented classification error.

For substantive disagreement with the assessed increase in land value itself, electing case-by-case valuation by the Chief Valuer is the structured route, understanding that this election is irrevocable once made. Formal procedural challenges beyond that sit within the Planning Act’s rules framework, which governs how valuation disputes and charge determinations get formally contested.

Best practice for any challenge: document your position with comparable transaction evidence or professional valuation support before raising it, and raise discrepancies as early in the process as possible, ideally before the LO issues rather than after. Once an LO is issued and the one-month payment clock starts, your options narrow considerably, since payment obligations generally run in parallel with any dispute rather than being suspended by it. Confirm the current procedural timeline for your specific situation with SLA or a qualified advisor, since dispute mechanics can vary by case type.

A Consultancy Perspective on Managing LBC Risk

Most LBC surprises trace back to the same root cause: the first re-submission data didn’t match what the project team actually intended to build, and nobody caught the gap until the Written Permission stage forced a Revised Liability Order.

Verifying the INLIS baseline against a project’s actual site history, rather than accepting the published figure at face value, is basic due diligence that gets skipped more often than it should. Modeling LBC under both the Table of Rates and a rough valuation-method scenario during feasibility, even when Table of Rates is the obvious default, gives a project team a real sense of the range they’re working with rather than a single point estimate that might be wrong in either direction.

On a mixed-use redevelopment we’ve seen handled well, the project team caught a baseline discrepancy in INLIS during feasibility, before lodging Provisional Permission. Confirming the correction with SLA ahead of submission avoided the database update fee that would otherwise have been charged at LO stage, and it meant the feasibility model’s LBC line item was accurate from the start rather than needing revision after approval.

The value of coordinating valuation input and statutory submission work together, rather than treating them as sequential and separate tasks, comes down to catching these discrepancies before they become billed line items. A Qualified Person focused purely on submission mechanics may not flag a valuation baseline question, and a valuer working in isolation from the submission team may not know what use and intensity figures are actually being declared. Integrated oversight closes that gap.

Get Ahead of Development Fees Before You Submit

If you’re weighing a Table of Rates estimate against a case-by-case valuation election, or trying to work out whether your first re-submission data is going to trigger a Revised Liability Order down the line, guessing at the numbers is the expensive option. Com brings statutory submission work, valuation coordination, and INLIS baseline checks together under one engagement, so your feasibility model reflects an accurate LBC exposure before you commit to land acquisition or a higher gross floor area.

Com

Our team handles the practical mechanics: verifying your parcel’s pre-chargeable baseline, modeling LBC under both computation methods, and preparing submissions structured to minimize RLO risk at the Written Permission stage. We also coordinate directly with your Qualified Person and external valuers so cashflow planning around the LO’s one-month deadline isn’t left to guesswork. If your project’s financing timeline depends on getting this right, our guide on engaging engineering consultants effectively explains what to bring to a first scoping conversation.

If you’re an investor comparing how a pending LBC liability affects a property’s overall transaction cost, it’s also worth reading how decoupling a property can shift the tax picture on a Singapore acquisition.

The practical next step: book a project review with our team and bring your site plan, current tenure documents, and any existing planning approvals. We’ll walk through your INLIS baseline and flag where your LBC exposure is likely to land before you finalize your submission strategy. Start that conversation on the Aman Engineering Consultancy home page.

Frequently Asked Questions

Does the Land Betterment Charge apply to every planning permission?
No. LBC applies only to chargeable consents that increase land value, specifically Provisional Permission, Written Permission, plan lodgement, and restrictive covenant variations granted on or after 1 August 2022. Approvals granted before that date remain under the old DC or Differential Premium rules.

Who receives the Liability Order?
SLA issues the LO to the taxable person, generally the landowner or the party apportioned liability under a joint development or sale agreement. Payment is due within one month of the LO date.

Can I choose valuation instead of the Table of Rates?
Yes, you can request case-by-case valuation by the Chief Valuer at IRAS instead of accepting the standardized Table of Rates figure. This election is irrevocable once made, so weigh it carefully before committing.

What triggers a Revised Liability Order?
An RLO is issued when your final Written Permission deviates from the use and intensity declared in your first Provisional Permission re-submission, resulting in a further increase in land value beyond the original LBC computation.

Is there a fee beyond the LBC amount itself?
SLA may charge a database update fee, generally $1,100, when your parcel’s baseline in INLIS needs correcting or updating at the point the Liability Order is issued.

How often do development charge rates change?
URA reviews rates on a half-yearly basis in consultation with the Chief Valuer, so the rate applicable to your project depends on which review period covers your consent’s material date.

Sources

Rate tables, sector maps, and computation rules change, so working from the current published version rather than a cached PDF or a summary article matters more with LBC than with most statutory processes.

Download the sector map PDF and rate table appendix specific to your project’s location before finalizing a feasibility number. A generic online rate figure that isn’t tied to your parcel’s actual sector classification is a common source of early-stage estimation error.

Leave a Reply

Your email address will not be published. Required fields are marked *