Playbook: Update the controller & director registers (RORC / related registers)

When you meet it

Ownership or control of a client company changes — a share transfer or allotment moves someone across the 25% line, a controller changes their name or address, a nominee arrangement starts or ends, or an annual review turns up a change no one flagged. Any of these can require the register of registrable controllers (RORC) to be updated, and often a related director register too.

It rarely stands alone: RORC updates usually ride on the back of a share transfer or allotment. This playbook is the register-maintenance discipline that sits behind those.

Legal basis

The RORC provision comes from CorpSec AI's verified citation table; this is general information, not legal advice.

• RORC deadlines: a company must update its internal register of registrable controllers within 7 days of a controller confirming the required information, and lodge the update with the ACRA central register of registrable controllers within 2 business days (central RORC in force from 30 July 2020). Non-compliance is subject to a penalty of up to S$5,000. [Verified]
• Who is a registrable controller: broadly, an individual or entity with a significant interest (25%+ of shares or voting) or significant control over the company. The look-through follows ownership up the chain to the ultimate controller.
• Related director registers: companies also maintain registers of directors and of nominee directors, and directors' particulars (including residential addresses) are kept on record. These are maintained obligations, but their exact statutory timelines are to be confirmed by counsel — the citation table anchors the RORC deadlines, not these. [Needs counsel for the exact deadlines]

Before you start — prerequisites, materials & parties

• Prerequisites: the client's CDD is passed; the current RORC and the up-to-date register of members; and the triggering event (transfer, allotment, controller change) identified with its date.
• Materials: the controller's confirmed particulars (identity, the nature and extent of their interest/control), the date the controller confirmed the information (the 7-day clock runs from this), and any nominee-director declaration if relevant.
• Parties: the controller(s) who must confirm their information, the company (which must maintain the register), the nominee director and their nominator (if a nominee arrangement is in play), and ACRA (the central register).

The standard steps

• Identify the triggering event and re-run the beneficial-ownership look-through to see who is now a registrable controller (25%+ or significant control).
• Ask any new or changed controller to confirm their required particulars — the 7-day internal clock runs from that confirmation.
• Update the internal RORC within 7 days of the confirmation.
• Lodge the update with ACRA's central RORC within 2 business days.
• Update any related register affected (register of directors, nominee directors, directors' particulars) and keep the confirmations on file.

Common pitfalls & edge cases

• Missing the 2-business-day central lodgement. The internal 7-day update is often done, but the separate ACRA central-register lodgement within 2 business days is easy to forget — and it carries the penalty. Treat them as two deadlines, not one.
• Running the clock from the wrong date. The internal 7-day clock runs from when the controller confirms the information, not from the share transfer date. Record the confirmation date precisely.
• Look-through stopping too early. A 25% holder that is itself a company is not the end — trace up to the ultimate individual controller. Stopping at the first corporate layer misses the real controller.
• Indirect or joint control overlooked. Control can arise from agreements, joint arrangements, or the right to appoint directors, not just shareholding percentage. Someone under 25% by shares may still be a controller by control.
• Nominee arrangements not declared. A nominee director must be flagged in the relevant register; an undeclared nominee arrangement is a compliance gap. Capture it when it starts and when it ends.
• Register updated but ownership event not, or vice versa. The RORC and the register of members must agree. A transfer recorded in one but not reconciled with the other leaves an inconsistent record.
• Company with "no registrable controllers". If genuinely none can be identified, that conclusion itself has to be recorded and kept current — an empty register still needs maintaining, not ignoring.

Timing & sequence

• Triggering event → re-run look-through → controller confirms particulars (this starts the 7-day clock) → update the internal RORC within 7 days → lodge with the ACRA central register within 2 business days → reconcile related registers.
• The 7-day and 2-business-day RORC deadlines are the hard, verified figures here. The related director-register timelines are to be confirmed by counsel; not legal advice.
• When this rides on a share transfer, the stamp-duty-then-ACRA sequence of the transfer comes first; the RORC update follows once the new ownership is settled.

In CorpSec AI

1. Open the Compliance tabOn the client company, open the Compliance tab. CorpSec AI runs the beneficial-ownership look-through to identify registrable controllers (25%+ / significant control).
2. Record the controller confirmationCapture the controller's confirmed particulars and the confirmation date — the 7-day internal clock runs from here.
3. Update the internal RORC (7 days)CorpSec AI records the update to the internal register of registrable controllers, deadline-aware against the 7-day window.
4. Lodge the central RORC (2 business days)The filing step records the lodgement with ACRA's central register within 2 business days. Live BizFile submission is on the roadmap.
5. Reconcile related registersUpdate the register of directors / nominee directors and directors' particulars where the event affects them. The history sits in the Activity log.