Playbook: Transfer shares

When you meet it

A shareholder sells or gifts their shares to someone else, a co-founder buys out another, or an investor's stake changes hands. Any move of shares from one holder to another is a share transfer.

Legal basis

Under section 196A of the Companies Act 1967, ACRA maintains the electronic register of members (eROM) for private companies — a share transfer only takes legal effect once ACRA updates that register, not when the instrument is signed. [Verified]

Section 126(3) of the Companies Act 1967 is the operative provision (for private companies, in force from 3 January 2016) under which the register of members is kept by ACRA and membership takes effect on ACRA registration. It also requires that stamp duty be paid before the BizFile transfer notification is lodged. [Verified]

Under the Stamp Duties Act 1929 (e-stamping of instruments of transfer of shares), the duty is 0.2% of the consideration or the net asset value, whichever is higher. An instrument executed in Singapore must be stamped within 14 days of execution; one executed overseas, within 30 days of first receipt in Singapore. Late stamping penalties run up to 4x the duty. Stamping is done via IRAS e-Stamping. [Verified]

If the transfer changes who is a registrable controller (broadly, someone holding 25%+), the register of registrable controllers also needs updating — see the RORC note below.

The standard steps (offline)

• Execute the instrument of transfer between transferor and transferee.
• Pay stamp duty via IRAS e-Stamping — 0.2% of consideration or net asset value, whichever is higher — within 14 days of execution in Singapore, or 30 days if executed overseas.
• Only after duty is paid, lodge the transfer notification with ACRA so the electronic register of members (eROM) is updated — this is the point the transfer legally takes effect.
• Check whether the transfer changes a registrable controller (25%+); if so, update the internal register and lodge with ACRA's central RORC register.

Before you start — prerequisites, materials & parties

• Prerequisites: the client's CDD is passed; the current register of members; a check of the constitution for pre-emption rights and any transfer restrictions or directors' approval requirement; and confirmation the shares are fully paid (partly-paid shares carry extra considerations).
• Materials: the instrument of transfer, the share certificate(s), the consideration (price) or a valuation / net asset value for the stamp-duty computation, and the transferee's CDD if they are new to the company.
• Parties: the transferor, the transferee, the directors (whose approval the constitution may require), existing members who may have pre-emption rights, and IRAS (stamp duty) and ACRA (the register update).

Common pitfalls & edge cases

• Lodging with ACRA before paying stamp duty. The order is fixed by section 126(3): stamp duty first, then the BizFile transfer notification. Reversing it is out of sequence — CorpSec AI's workflow prevents it.
• Stamp duty computed on price when NAV is higher. Duty is 0.2% of the consideration or the net asset value, whichever is higher. A nominal or nil consideration (e.g. a gift between family members) does not make duty nil — it is computed on NAV.
• Overseas execution deadline missed. An instrument executed overseas must be stamped within 30 days of first receipt in Singapore, not 14. Getting the window wrong risks a late-stamping penalty of up to 4x the duty.
• Pre-emption rights skipped. Many constitutions require shares to be offered to existing members first. Transferring straight to an outsider without following pre-emption can make the transfer challengeable.
• Directors' approval not obtained. Where the constitution gives directors a discretion to refuse a transfer, their approval (or a resolution) is needed before the register is updated.
• Forgetting the RORC knock-on. If the transfer moves someone across the 25% line, the register of registrable controllers must be updated within its tight deadlines — see the RORC playbook.
• Assuming the transfer is effective on signing. It takes legal effect only when ACRA updates the electronic register of members (section 196A) — not on execution or stamping.

Timing & sequence

• Check pre-emption / directors' approval → execute the instrument → pay stamp duty (within 14 days if executed in Singapore, 30 days if overseas) → lodge the ACRA transfer notification → transfer takes legal effect on ACRA registration → update the register and RORC if needed.
• The verified hard sequence: stamp duty before the ACRA lodgement (s126(3)); legal effect on ACRA registration (s196A); the 14-/30-day stamping windows (Stamp Duties Act 1929).

In CorpSec AI

The workflow keeps stamp duty ahead of the ACRA lodgement — it does not let you skip the order.

1. Create the taskIn the left panel click + New task, choose the company, and pick the share-transfer task type. Name the transferor, the transferee, the shares, and the consideration.
2. Let the AI draft the instrumentThe AI drafts the instrument of transfer in the Document tab. Select text and comment to adjust the consideration, class of shares, or wording.
3. Four-eyes approvalThe approval step routes the instrument to a different, suitably senior colleague before it goes out for signature.
4. Collect signaturesThe Signing tab creates a signing link for the transferor and transferee. Track Signed/Pending and remind whoever is outstanding.
5. Pay stamp duty firstOnce signed, pay stamp duty through IRAS e-Stamping — 0.2% of consideration or net asset value, whichever is higher, within the 14-/30-day window. This step is a deadline reminder and checklist item; CorpSec AI does not submit the e-Stamping itself.
6. File the ACRA transfer notificationOnly after stamp duty is paid, complete the filing step to lodge the transfer with ACRA. The transfer takes legal effect once ACRA updates the electronic register of members — this step records that lodgement.
7. Update the register (and RORC if needed)The data-update step updates the register of members. If the transfer creates or removes a 25%+ controller, open the Compliance tab to run beneficial-ownership screening and update the registrable-controllers register. Once everything is done the task status flips to Done automatically.