Four of the five ongoing conditions behind a Section 13O/13U exemption are measured over a quarter, a year, or the life of the exemption. One is not. The UBO register — the record of who beneficially owns or controls a Singapore-incorporated entity — has to be kept current, and any change has to be reported to ACRA within two business days. Not two weeks. Not the next filing cycle. Two business days from the moment the underlying fact changes.
What the UBO register actually tracks
For every fund entity, the register holds each natural person with meaningful ownership or control: the percentage held, the nature of that control (direct shareholding, voting rights, the ability to appoint directors), the date they became a UBO, and the date any of that ceased. It has to reflect natural persons — tracing through holding companies and trusts to the individuals who ultimately control them, not stopping at the first corporate layer.
Why family offices trip on this more than most entities
A family office's ownership structure changes more often than a typical operating company's. A trust gets restructured across a generation. A family member is added to, or removed from, a holding vehicle. Voting control shifts as part of succession planning. Each of these is a UBO change — and each one starts a two-business-day clock the moment it happens, whether or not anyone has told the compliance team yet.
That last part is the actual failure mode. The deadline does not start when someone gets around to updating the register — it starts when the underlying fact changes. If the family's lawyer executes a trust amendment on a Tuesday and nobody logs it until the following Monday, the filing is already late, and there is no batching this at quarter-end to catch up.
What "meeting the SLA" actually requires
It is not enough to have filed on time — you need to be able to show you filed on time if a MAS-appointed screening provider or auditor asks. That means three things working together:
- A change-detection trigger the instant a UBO record is edited, not a manual reminder someone has to remember to set.
- Escalating reminders before the deadline — early enough that a missed notification on day one doesn't become a missed filing on day two.
- A filing log recording what was submitted, when, and by whom — an audit trail, not a to-do list that gets deleted once the task is "done."
What this looks like without a system for it: the UBO register lives in a spreadsheet or a company secretary's inbox, changes get logged whenever someone remembers, and the two-day SLA is met by luck as often as by process. There is usually no record of exactly when the underlying change happened versus when it was filed — which is precisely the gap an auditor will probe.
What this looks like on aama.io: editing a UBO record starts a visible countdown on a compliance task dashboard immediately, with reminders at defined intervals before the two-day deadline, and every filing logged with what was submitted, when, and by whom — evidence generated as a byproduct of doing the filing, not reconstructed afterward from memory. Access to edit the register is role-based, so only authorized compliance or admin users can trigger a change in the first place, with full edit history retained.
Why this is the requirement most worth automating first
CDR and LBS give you room to course-correct within a quarter or a year. The UBO/ACRA SLA gives you two days, with no equivalent buffer — which makes it the single condition where a manual process is most likely to produce an outright breach rather than a slow drift. If a family office automates only one of the five conditions first, this is usually the one with the shortest fuse.
This guide is general information, not legal or regulatory advice. Confirm current ACRA filing obligations and timelines with your corporate secretary and legal adviser. For the other four ongoing conditions, see the full compliance overview.
Relying on someone remembering to update the UBO register? See how aama.io starts the ACRA countdown automatically, or talk to our team about your entity structure.