Statute Details
- Title: Road Traffic (Electronic Road Pricing System) Rules 2015
- Act Code: RTA1961-S226-2015
- Legislation Type: Subsidiary Legislation (SL)
- Authorising Act: Road Traffic Act (Cap. 276), in particular sections 34D and 140(1)
- Commencement: Comes into operation on 21 April 2015
- Current Version: Current version as at 27 Mar 2026
- Key Parts: Part 1 (Preliminary); Part 2 (In-Vehicle Units); Part 3 (Levying of Road-User Charge); Part 4 (Offences and Other Miscellaneous Provision); Part 5 (Motor Cars Not Registered Under Act)
- Key Definitions (Section 2): “ERP”, “ERP card”, “in-vehicle unit”, “ERP facility”, “restricted hours”, “specified entry point”, “participating bank”, “credit card”, “card machine”, “relevant checkpoint”
- Schedules: First Schedule (specified roads/entry points/restricted hours/amounts); Second Schedule; Third Schedule (electronic road pricing sign)
What Is This Legislation About?
The Road Traffic (Electronic Road Pricing System) Rules 2015 (“ERP Rules”) are Singapore’s detailed regulatory rules for operating and enforcing the Electronic Road Pricing (“ERP”) system under the Road Traffic Act. In plain language, the Rules set out how road-user charges are imposed and collected electronically when vehicles enter or move into designated roads during specified “restricted hours”.
ERP is designed to manage traffic congestion by charging vehicles for use of certain roads at certain times. The Rules therefore focus on the practical mechanics of the system: what equipment must be installed in vehicles (notably “in-vehicle units”), how charges are calculated and debited, what payment methods are recognised, and what conduct is prohibited (including interference with ERP signals and unlawful entry into specified entry points).
For practitioners, the ERP Rules are important because they create compliance obligations for vehicle owners and drivers, define the technical and administrative framework for charge collection, and provide offence provisions that can lead to enforcement action. They also include special rules for motor cars not registered under the Road Traffic Act, which affects how ERP charges are handled for certain vehicle categories.
What Are the Key Provisions?
1) Preliminary framework and definitions (Part 1; Section 2). The Rules begin with a citation and commencement provision (Section 1) and then provide a comprehensive set of definitions (Section 2). These definitions are not merely interpretive; they determine the scope of who must comply and what devices and payment instruments trigger charging. For example, the Rules define “ERP card” as a stored-value card that, when used with an in-vehicle unit, results in automatic debiting of the appropriate road-user charge when the vehicle is ridden, driven, or moved into a specified entry point during restricted hours. Similarly, “ERP facility” refers to electronic/computerised facilities installed by the Authority at specified entry points, and “in-vehicle unit” refers to a transponder or other approved device installed in a motor vehicle to facilitate electronic levying and payment of road-user charges.
2) In-vehicle units and authorised installation (Part 2; Sections 3 and 4). A central compliance requirement is that motor vehicles must be installed with in-vehicle units (Section 3). This is the technical backbone of ERP enforcement: the system relies on an approved device in the vehicle to detect entry into specified points and to enable charging. Section 4 then regulates the installation, repair, replacement, and related work on in-vehicle units, requiring that such work be carried out by “authorised persons”. This provision is practically significant because it ties compliance to approved service channels and helps ensure that devices are correctly configured for ERP operations.
3) Levying and payment of road-user charge (Part 3; Sections 5 and 6). The Rules specify when the road-user charge is payable and how it is paid. Section 5 provides that the road-user charge is to be paid during restricted hours. Section 6 addresses payment mechanics. Together, these provisions link the charging event to (i) the vehicle’s movement into a specified entry point, (ii) the road being one of the “specified roads” listed in the First Schedule, and (iii) the time falling within “restricted hours” also set out in the First Schedule. The First Schedule is therefore a key practitioner reference point: it effectively determines the operational scope of ERP on a day-to-day basis by listing the roads, entry points, restricted hours, and charge amounts.
4) Offences and enforcement-related prohibitions (Part 4; Sections 7 to 9). Part 4 sets out offence provisions and other miscellaneous enforcement rules. Section 7 addresses “unlawful entry into specified entry point”, which targets conduct where a vehicle enters a controlled point in circumstances that breach the ERP charging regime. Section 8 prohibits “interference, etc., with transmission of signals”, which is aimed at tampering with ERP communications or otherwise disrupting the system’s ability to levy charges. Section 9 concerns “electronic road pricing sign”, which reflects the system’s reliance on signage and the public-facing indication of ERP-controlled entry points. For lawyers, these provisions are important because they can be invoked where there is evidence of non-payment, evasion, or technical tampering, and they often require careful factual analysis of what the driver did, what equipment was installed, and whether the ERP system detected entry during restricted hours.
How Is This Legislation Structured?
The ERP Rules are structured into five Parts, supported by multiple Schedules:
Part 1 (Preliminary) contains the citation/commencement and definitions. The definitions in Section 2 are foundational for interpreting all later obligations.
Part 2 (In-Vehicle Units) sets out the requirement to install in-vehicle units and the requirement that installation/repair/replacement be performed by authorised persons.
Part 3 (Levying of Road-User Charge) deals with when charges are levied (restricted hours) and how they are paid. This Part operationalises the ERP charging event by tying it to specified roads and entry points.
Part 4 (Offences and Other Miscellaneous Provision) includes offences relating to unlawful entry, interference with signal transmission, and provisions concerning electronic road pricing signs.
Part 5 (Motor Cars Not Registered Under Act) provides special treatment for motor cars that are not registered under the Road Traffic Act. It includes provisions on whether such cars need in-vehicle units (Section 10), how daily road-user charge is calculated (Section 11), payment (Section 12), offences (Section 13), and revocation (Section 14). This Part is particularly relevant for cross-border or special registration scenarios where the standard ERP equipment and registration framework may not apply.
Schedules support the operational details: the First Schedule lists specified roads, entry points, restricted hours, and charge amounts; the Third Schedule relates to the electronic road pricing sign. The Second Schedule is also included in the legislative structure, though its specific content is not reproduced in the extract provided.
Who Does This Legislation Apply To?
The ERP Rules apply primarily to motor vehicle users who ride, drive, or move vehicles into specified entry points on specified roads during restricted hours. In practice, this includes vehicle owners and drivers who must ensure that the vehicle is equipped with the required in-vehicle unit and that road-user charges are properly paid when the vehicle enters the ERP-controlled areas.
The Rules also apply to authorised persons involved in the installation, repair, and replacement of in-vehicle units. In addition, Part 5 extends the charging and compliance framework to motor cars not registered under the Road Traffic Act, meaning that certain categories of vehicles may be subject to alternative charging arrangements (including daily road-user charge) and corresponding offences.
Why Is This Legislation Important?
The ERP Rules are important because they convert the policy objective of traffic management into enforceable legal duties. For practitioners, the Rules matter not only for understanding how ERP charges are calculated and collected, but also for assessing liability where charges are disputed or where enforcement action is taken for alleged offences.
Operational compliance and evidential issues. The Rules create a compliance ecosystem around approved technology (in-vehicle units), authorised installation, and electronic facilities at entry points. Disputes frequently turn on whether the correct equipment was installed and functioning, whether the vehicle entered a specified entry point during restricted hours, and whether payment was made in the manner recognised by the Rules. The definitions also indicate the payment instruments and systems involved, such as “credit card” and “ERP card”, and the role of “participating bank” arrangements for credit card payment.
Enforcement and offence risk. Part 4 offences—unlawful entry, interference with signal transmission, and related provisions—highlight that the law is not limited to mere non-payment. Where there is evidence of tampering or deliberate evasion, the offence provisions can be engaged. Lawyers advising clients in ERP-related enforcement matters should therefore focus on both (i) the factual timeline of vehicle movement and charging events and (ii) the technical and behavioural aspects that may distinguish inadvertent non-compliance from conduct that could be characterised as interference or unlawful entry.
Related Legislation
- Road Traffic Act (Cap. 276) — the enabling Act for ERP, including sections 34C, 34D and enforcement-related provisions such as 140(1)
- Banking Act (Cap. 19) — relevant for the definition of “credit card” used in the ERP Rules
- Road Traffic (Electronic Road Pricing System) Rules — this specific instrument (SL 226/2015) and its subsequent amendments
Source Documents
This article provides an overview of the Road Traffic (Electronic Road Pricing System) Rules 2015 for legal research and educational purposes. It does not constitute legal advice. Readers should consult the official text for authoritative provisions.