For Mauritius

The substance is real. The evidence for it is in four countries and three spreadsheets.

A Mauritian company holding or managing operations elsewhere has an obligation almost no mainland business has: it must be able to show that it is genuinely run from Mauritius. The regulator assesses that in the round — people employed here, premises, expenditure incurred here, how often the board meets here and whether it actually decides — and every one of those is evidenced by ordinary operational records rather than by a document written in March. Most businesses in this position have the substance. What they do not have is a system that can say which jurisdiction each cost, each person and each decision belonged to without a fortnight of reconstruction.

The subject: Whether cost, headcount, documents and decisions can be attributed to an entity and a jurisdiction as they happen, rather than reconstructed after the year ends.
The limit: We do not give substance advice and software does not satisfy a regulator. What your arrangements should be, and whether yours are enough, belongs to your administrator and your adviser.
Fiscalisation: We are not a certified Electronic Billing System and hold no MRA connection. If you are in scope, choose your EBS first and fit everything else around it.
Payroll: No PAYE, no NPF or NSF contributions, no statutory returns. Our maintained payroll engine covers Kenya only.

See what is assessed Talk to us about Mauritius

Six tests, and the record each one rests on

What is assessed, and the record it rests on

These are the things the regulator weighs, in ordinary language rather than statutory language. Read the middle column as a question about your own system: not "do we do this" — you almost certainly do — but "could we produce the record for it this afternoon". The right-hand column is where that record usually lives, and it is the honest answer for most businesses rather than an unkind one.

01 People employed in Mauritius, and suitably qualified

The record it rests on

An employee register that distinguishes who is engaged by the Mauritian entity from who is engaged by a subsidiary or seconded in, with roles and start dates that do not have to be remembered.

Where it usually is instead

One combined staff list for the whole group, with the entity that employs each person inferred from which payroll they happen to appear on.

02 Adequate premises

The record it rests on

The lease, the rates, the utilities and the fit-out held as documents against the transactions that paid for them, in the entity that paid.

Where it usually is instead

Correct in the accounts and correct in reality, with the underlying documents in a folder somebody set up and a different person now maintains.

03 Expenditure incurred in Mauritius

The record it rests on

Cost coded to the entity that incurred it and the jurisdiction it was incurred in, so a total for the year is a report rather than an exercise.

Where it usually is instead

A group profit and loss, from which the Mauritian share is extracted annually by someone who knows which cost centres are which.

04 Board meetings held in Mauritius

The record it rests on

Minutes with a date, a place and an attendance list, filed where they can be found by date rather than by whoever circulated them.

Where it usually is instead

An email thread, a calendar invitation, and a set of minutes that exist and are correct but are in one person's mailbox.

05 A board that decides rather than ratifies

The record it rests on

Decisions with an authority behind them — an approval that had to happen before the commitment could, recorded against the commitment itself.

Where it usually is instead

Approval by message, executed immediately, minuted later. The decision was genuinely made; the sequence cannot be demonstrated.

06 Core activity carried out in or from Mauritius

The record it rests on

The work itself visible as work: time and cost against the mandate or investment it relates to, by the people who did it.

Where it usually is instead

Nowhere at all, in most cases, because the activity is professional judgement and nobody thought judgement produced records.

The pattern in the right-hand column is worth naming, because it is not carelessness. Every one of those arrangements works perfectly for running a business and fails only when someone outside it asks a question. They are the natural result of a group whose systems were configured for the trading subsidiaries — the ones with stock, customers and invoices — while the Mauritian entity was treated as a holding structure with a bank account and an auditor. It is the entity with the most demanding evidence obligation and usually the one nobody gave a proper chart of accounts.

Five questions worth asking internally before you ask any vendor anything

Can you produce, today, the total expenditure incurred by the Mauritian entity in Mauritius for the last financial year — as a report rather than as a calculation somebody performs?

Does your employee register say which entity engages each person, or is that inferred from which payroll they appear on?

If your administrator asked for every board minute from the last two years by date, where would you go, and how many people would you have to ask?

For a decision that committed the entity to something material, can you show that the approval preceded the commitment rather than followed it?

Who in your organisation currently holds the answers to the four questions above in their head, and what happens the month after they leave?

What this costs today

Four problems, none of which are compliance problems yet

Each of these is a record-keeping arrangement that works perfectly for running a business and fails only when somebody outside it asks a question. That is why they persist, and why they are almost never anybody's fault.

Cost that cannot be attributed to a jurisdiction

The group ledger knows what was spent and on what. Whether it was incurred by the Mauritian entity, in Mauritius, is a judgement somebody makes annually — and a judgement that is correct but unrecorded is not evidence of anything.

A holding company treated as a dormant one

Systems get configured for the subsidiaries that have stock and customers. The entity with the most demanding evidence obligation ends up with a bank account, an auditor and no chart of accounts worth the name.

Documents that exist and cannot be found

The lease, the minutes, the mandate, the invoice from the local supplier — all of them real, all of them somewhere, and none of them attached to the transaction they explain. A file assembled by search is a file assembled once.

Institutional memory as a single point of failure

One or two people can reconstruct any year on request, which is why nothing was ever written down. The exposure is not compliance risk in the abstract; it is that the exposure only becomes visible the month after they resign.

The same work, moved earlier

Two ways to have a year of evidence

Both of these end with a file. They differ in when the work happens, who does it, and how much of the year survives the process — and the difference is not effort or diligence, it is whether the records were captured as the year went along or reconstructed after it ended.

Reconstructed in March

The common case, and it usually succeeds. That is exactly why it persists.

The request arrives from the administrator or the auditor with a deadline attached.
One or two people who know the group's history assemble it, because only they can — the knowledge is the scarce input, not the data.
Costs are extracted from a group ledger by judgement about which lines belong to which entity, and the judgement is sound and undocumented.
Minutes are gathered from mailboxes. The ones from the year a director changed take longest.
It gets done, it is accurate, and none of it is repeatable — next year the same fortnight is spent again, by the same two people, if they are still here.

Accrued as it happened

Not more work in total. The same work, moved to the moment when it costs almost nothing.

Every cost carries the entity and the jurisdiction that incurred it, because it was coded that way at entry rather than sorted later.
The employee register already distinguishes who is engaged where, so headcount by entity is a filter rather than a question.
Documents sit against the transactions they evidence, so "show me the lease" is a click from the payment rather than a search of a drive.
Approvals happened in the system before the commitment, so the sequence is a record instead of a recollection.
The file is a report. The fortnight goes back into the year, and the two people who used to be indispensable become merely useful.

One honest caveat, because the right-hand column reads like a sales pitch and half of it is not ours to sell. The coding, the register, the documents and the approvals are what a system does. What the entity is actually doing, and whether it is enough, is not — that is a question for you, your administrator and your adviser, and no configuration answers it. What we are claiming is narrower and, we think, more useful: that a business which genuinely has substance should not have to spend a fortnight a year proving it, and that the reason it does is record-keeping rather than anything to do with tax.

Operations for a Mauritian holding structure

The substance is real. The records are the only thing that can prove which of it happened here.

The reader of this page runs a genuine business with genuine people, and the difficulty is not what happened — it is that the evidence of it is scattered. The recurring failure is one entity being indistinguishable from the group around it. Systems get configured for the subsidiaries with stock and customers, the holding entity is treated as dormant because it has neither, and then a question arrives that only the holding entity's own records can answer.

Cost attribution

The entity that incurred it, decided at entry

Coded to the entity, cost centre and mandate as the transaction is captured rather than allocated afterwards by argument. A group ledger knows what was spent and on what; whose cost it was is a separate fact and it has to be recorded, not inferred.

People

A register that knows who is engaged where

Employees and contractors with the entity that engaged them, their location and their documents with dates — because "who actually works here" is a question about records, and an entity with real people should be able to answer it from a screen.

Documents

The lease, the minutes, the mandate, findable

All of them real, all of them somewhere. Held against the transaction or the entity they belong to and retrievable by it, rather than existing in a form that requires one person's memory to locate.

Projects

Time and cost against the mandate it belongs to

Hours and expenses attributed to the engagement they were incurred for, as they happen. Where a team serves several mandates, the split is a record rather than a reconstruction at year end.

Procurement

Approvals that precede the commitment

A threshold that refuses rather than warns, and an authority recorded before the obligation exists. An approval written afterwards to match an invoice is a document about the past, not a decision.

Audit trail

Dates on everything, so a year is readable not rebuilt

Who changed what and when, kept as a matter of course. The alternative is the pattern the last pain below describes: one or two people who can reconstruct any year on request, which is why nothing was ever written down.

Two boundaries, and the second is the one that matters. We hold records; we do not assess substance — what any authority requires of a structure, and whether a particular arrangement satisfies it, is a question for your advisers and not one a software page should answer. And we do not consolidate statutory accounts. What we do is make the underlying records attributable, which is the part that is usually missing before anybody gets as far as consolidating.

Scope, stated plainly

Where a records argument stops and regulated advice begins

This is the market where that line matters most, because it is the market where our reader is most likely to be sitting next to somebody who is licensed and we are not. The first two items below are that line.

Scope in Mauritius, stated before the demo

Running in the product today

Expenditure coded to an entity, cost centre and site at entry, with reporting by any of them for any period.
Documents held against the transaction they evidence, retrievable by date, entity or counterparty, previewable without downloading.
An employee register independent of system users, so people who will never log in are still on the record with their entity, role and location.
Approvals that block above a threshold, delegation configured per entity, and the authorisation recorded against what it authorised.
Time and cost booked to a project, engagement or mandate, including labour cost attributed rather than pooled.
Genuine multi-currency, with the original currency and the rate actually applied retained on the transaction.
A cross-module audit trail of who changed what and when, exportable for a period.

On the roadmap — and commissionable now

An MRA fiscalisation connection. Real-time invoice fiscalisation through a certified Electronic Billing System is a genuine obligation here and we are not one, and are not certified as one. If you are inside the scope of the mandate, that is a separate product decision and you should make it independently of this one — the honest sequence is to choose your EBS first and then ask how anything else fits around it.
Mauritian payroll. PAYE, NPF or NSF contributions and statutory returns. Our maintained payroll engine covers Kenya only. We attribute labour cost to entities, projects and cost centres, which is the half of the problem this page is actually about, but the calculation and the filing belong to a local provider.

Where we point you to a specialist — and the first one is why the rest of this page is worth reading

We do not provide substance advice, and configuring software does not satisfy a regulator. This needs to be unambiguous. What the product does is produce and retain records. Whether your arrangements meet the requirement is a question for you, your management company and your adviser — people who are licensed for it, as we are not. Any vendor offering you a "substance solution" is describing a filing cabinet in language that should worry you.
FSC and Registrar filing, and statutory reporting, are your administrator's. The annual return, the substance declaration, the forms and every submission to anybody are theirs. We hold the detail such a return is built from.
Company secretarial functionality is a different product. Statutory registers, a minute book, a share register and a board portal all sit inside it rather than inside this one. Minutes can be held as documents against a period; that is storage and retrieval, not company secretarial software, and the two get confused often enough to be worth separating.
Support is remote from Nairobi rather than from a local office or a Mauritian implementation partner. It runs in English. Mauritius is UTC+4 and Nairobi UTC+3.

Every item in the middle column is buildable. Kenya's eTIMS transmission and its maintained payroll engine both exist because clients needed them and commissioned them. MRA fiscalisation and a Mauritian payroll engine are ordinary builds against published rules — ask and we will come back with a written specification, a timeline and a price. What we will not do is print a date nobody has paid for, or let a build promise blur into the substance question above it.

The line we are drawing, since it is a fine one and the page is worth nothing if it is blurred: we are telling you that the evidence for substance is made of ordinary operational records, and that a system either captures those as it goes or leaves you to reconstruct them. We are not telling you what your substance should look like, whether yours is sufficient, or that any amount of software makes it so. The first is a records argument and we will stand behind it. The second is regulated advice and we are not the people to give it.

How this starts

Three moves, and the first one is a single number

Ask for one number

Total expenditure incurred by the Mauritian entity, in Mauritius, for the last financial year. Not whether it is adequate — just the number. If it comes back as a report you can see the working of, your records are in good shape and this page is not urgent. If it comes back after two days and a conversation, that is the gap, and it is the same gap every March.

Then ask where it came from

The interesting part is rarely the number. It is whether it was extracted by judgement about which ledger lines belong to which entity, and if so, whose judgement, and whether that person has written any of it down. This costs you one question and tells you more about your exposure than an audit will.

Then decide what you are buying

Not compliance, and not assurance — neither is ours to sell. What is on offer is that next year the file is a report rather than a fortnight, and that the two people who can currently reconstruct any year become useful rather than load-bearing. That is a smaller purchase than the market usually implies and it is the one that is honestly available.

Read before you shortlist

Guides for this market

Operations Metrics

Substance Is Real. Proving It Is a Records Problem.

Six things get assessed, and every one of them is evidenced by records a business already generates. The failure is almost never that the substance is missing — it is that nobody can produce it without reconstructing the year.

Nov 19, 2025 · 12 min Read

Accounting Insights

The Holding Company Is Here. The Business Is in Five Other Countries.

Groups configure their systems for the trading subsidiaries, because that is where the stock and the customers are. Then they discover annually that the entity nobody configured is the one with the evidence obligation.

Nov 21, 2025 · 11 min Read

Implementation & Rollout

Buying Operations Software in Mauritius: A Straight Guide

A market with capable local firms, a genuine fiscalisation obligation and a records problem nobody sells to. Mostly about buying the right three things from the right three places.

Nov 22, 2025 · 13 min Read

Inventory Insights

A Hold That Does Not Report as One

Ten stock statuses are declared. One counts as sellable and five count as a hold. The other four are neither — so stock put into one of them cannot be sold and is reported as not being on hold, which is the worst of both descriptions.

Jul 4, 2026 · 12 min Read

Reports & BI

The Rollup Nothing Ever Filled — A Correction

We published that this product stored no daily metrics and computed every dashboard figure from scratch. It was false, and it was on this page. Dashboard history is precomputed nightly, finished days are read from storage, today is always live, and a missing day repairs itself on read. The reason the check went wrong is worth more than the original article.

Jun 19, 2026 · 11 min Read

Projects & Job Costing

A Budget That Warns and a Status That Refuses

This module will refuse to move a project from planning straight to completed. It will not refuse to spend twice its budget. One of those is enforced by a state machine and the other is a percentage on a screen.

Jun 16, 2026 · 12 min Read

Questions we are asked here

Straight answers, and the two that belong to your licensed adviser

Does your software make us compliant with the substance requirements?

No, and this is the first question on purpose because it is the one worth being unambiguous about. Substance is assessed on what your business actually does — people, premises, expenditure, where decisions are genuinely taken. Software does not change any of that. What it changes is whether you can evidence it: whether expenditure by entity and jurisdiction is a report or a reconstruction, whether documents sit against the transactions they explain, whether an approval can be shown to have preceded the commitment it authorised. If your arrangements are sufficient, good records make that demonstrable cheaply. If they are not, no system will help, and anyone selling you a "substance solution" should be asked precisely which regulator has accepted it. This one is a boundary rather than a backlog — it does not change with a commissioned build, and it is the one worth being unambiguous about. No software makes an organisation compliant with a substance requirement — the test is about real activity, real decisions and real people, assessed by an authority, and a vendor claiming their product satisfies it is describing something that cannot exist. What we do is hold the operational record of activity that genuinely happened, which is evidence rather than compliance, and the difference is the whole point.

What is the minimum expenditure we need in Mauritius?

We are not going to tell you, and we would be suspicious of a software vendor who did. The requirement is a level of expenditure proportionate to your level of activity, and the FSC publishes indicative guidance by activity type. Figures circulate secondhand, they vary by the kind of entity, and they change. Your management company or adviser has the current position for your specific activity, and that is a five-minute question to someone who is licensed to answer it. What we can tell you is that whatever the figure is, you will need to be able to produce your actual number against it — and that part is a records problem, which is ours. This one is a boundary rather than a backlog — it does not change with a commissioned build, permanently. The requirement turns on your licence, your activity and your circumstances, it moves, and a figure printed by a software vendor is the worst possible source for it because somebody will plan against it. Your licensed adviser has the current position. We would be suspicious of any vendor who answered this question, and you should be too.

How many employees do we need?

Same answer, same reason. The test is a reasonable number of suitably qualified persons for the level of activity, assessed in the round rather than against a fixed count, and it can be satisfied directly or indirectly. There is no universal minimum, and inventing one for a web page would be worse than declining to. What is useful from our side is narrower: your employee register should be able to say which entity engages each person, in which location, in which role, from when — including people who are seconded, engaged indirectly, or will never log into a system. Most registers cannot, because they were built as a list of users.

Are you a certified EBS for MRA e-invoicing?

No. Real-time fiscalisation through a certified Electronic Billing System is a genuine and expanding obligation in Mauritius — it began with the largest taxpayers and the stated direction is all VAT-registered persons, with the thresholds lowered in stages. We are not certified and hold no e-invoicing connection to the MRA. If you are in scope, or expect to be, the honest sequence is to choose your EBS first and then ask how anything else fits around it, rather than the other way round. We are describing an operations layer; the fiscalisation obligation sits on your billing. That is on the roadmap rather than a boundary, and it is commissionable now. Real-time fiscalisation through a certified Electronic Billing System is a defined obligation with a published specification, which makes certification and the pipeline behind it a scoped project rather than an open question. Kenya's eTIMS transmission and its maintained statutory payroll engine both exist because Kenyan clients needed them and commissioned them — neither arrived on a roadmap by itself. If this is the thing standing between you and a decision, say so and we will come back with a written specification, a timeline and a price before you commit to anything. What we will not do is print a date nobody has paid for. Given the expanding scope, the sequencing advice stands: buy this from a provider who already holds certification, and buy it before you buy us.

We are a management company administering client entities. Does this apply to us?

Partly, and the part that does is a different shape from the page above. Your own substance obligation is the same as any GBC's. But your operational problem is that you are producing evidence for many entities at once, and the constraint is per-client attribution rather than per-jurisdiction — time against the right client mandate, expenditure that does not leak between engagements, documents filed to the client rather than to the year, and a trail that survives a change of administrator. Those are things we do. What we do not do is anything company secretarial: no statutory registers, no minute book, no share register. That will remain a separate system and you should assume it does.

Our operations are in Kenya, Uganda and Ghana. Which page should we be reading?

Probably several, and this one last. The subsidiaries are where your stock, customers, payroll and tax obligations are, and those markets have their own pages because the problems there are genuinely local. This page is about the entity above them, and the reason it is worth a page at all is that groups configured for the operating companies routinely leave the holding entity with no meaningful chart of accounts — then discover annually that it is the one with the evidence obligation. If you are choosing a system for the group, the useful question is whether cost, headcount and documents can be attributed to an entity and a jurisdiction from the beginning, because retrofitting that is the expensive version.

Mauritius has capable local software and accounting firms. Why you?

For much of what you need, they are the right answer and you should use them — fiscalisation, payroll, company secretarial and the statutory filings are all better served locally, and we have said so above rather than pretending otherwise. Where we are worth a conversation is the operational layer underneath: procurement with approvals that block, cost attributed to an entity and a jurisdiction as it is entered, documents against transactions, stock across sites including goods you handle without owning, and an audit trail that spans all of it. That is a different purchase from an accounting package, and the reason it comes up here is that the evidence a Mauritian entity needs turns out to be a by-product of it. Support is remote from Nairobi, one hour behind you, in English — and you should ask us what happens when the person who implemented your system leaves, because that question separates vendors more reliably than any feature list.

Ask for one number and where it came from

Expenditure incurred by the Mauritian entity, in Mauritius, last financial year — and whether it arrived as a report or as somebody's judgement about which ledger lines belong where. Both answers are useful. Only one of them means this conversation is urgent.

Talk to us about Mauritius See plans & pricing