Running multiple entities means carrying multiple sets of statutory numbers in your head — or more likely, in a folder of folders that nobody has organized since the accountant last visited. VAT registration, PAYE, UIF, Skills Levy, Comp Commissioner, SDR — each issued by a different body, each required by a different party at a different moment, each with a different format.
The moment an auditor, a bank, or a procurement officer asks for a specific number, the scramble begins.
The Registration Stack That Never Stays Sorted
South African corporate compliance runs on a specific taxonomy of identifiers, and the Group Details template is built around that stack. Each statutory registration gets its own field: VAT Registration #, Tax Registration #, PAYE Registration #, UIF Registration #, UIF Reference #, Skills Registration #, Comp Commissioner #, SDR Registration #.
That's eight separate registration identifiers for a single entity. In practice, each is maintained by a different person — payroll handles UIF, finance handles VAT, the accountant handles CIPC — and they live in different systems, different folders, different email threads. When the company's banking details change and you need to notify SARS, you're pulling from three separate places just to populate one form.
Storing all of it in a single Memento record doesn't just save lookup time. It means one person can do a compliance audit — are all registrations current for this entity? — without chasing four different departments. The Status field (Active/Dormant) lets you filter immediately: dormant entities don't need annual returns, but they do need to retain their registration numbers for potential reactivation.
Cipro Submissions and the Audit Trail
The Cipro Submission field is an entries link — it connects to a separate submissions library rather than storing flat text. That architecture matters: each CIPC annual return has a submission date, a reference number, and a status. Storing those as entries rather than a text blob means you can query submission history, identify gaps, and produce a clean audit trail without digging through email confirmations.
For a company secretary managing submissions across a portfolio of entities, this is the difference between knowing you filed and being able to prove you filed at a specific date with a specific reference.
Members, Officers, and the Accountability Layer
The template tracks up to six members plus a designated Public Officer — the individual SARS holds responsible for the entity's tax compliance. Officer ID Number, Officer Email, Officer Cellphone, postal and physical addresses are all captured in dedicated fields.
When SARS correspondence arrives at the wrong address because the officer moved eighteen months ago and nobody updated the record, the consequence isn't administrative inconvenience — it's missed correspondence, compounding penalties, and a dispute that could have been prevented by a field update. The physical and postal addresses for both the entity and the officer are separate because they're often different and they're updated at different times for different reasons.
Banking details — Bank, Bank account, Branche, Branche Code — sit in the same record. Payment processing, EFT setup, and BEE verification all require this data. Having it alongside the VAT and PAYE numbers means a finance officer pulling entity details for an EFT batch doesn't need to call anyone.