MRA e-invoicing in Mauritius: who must comply, how it works, and how to stay compliant

What is MRA e-invoicing?

The Mauritius Revenue Authority’s e-Invoicing System requires businesses in scope to fiscalise their invoices and receipts with the MRA in real time. Before an invoice reaches the customer, the business’s billing system sends it to the MRA, which validates it and returns an Invoice Registration Number (IRN) and a QR code. These appear on the invoice so the customer — including members of the public — can check that it has been fiscalised.

It is a centralised, real-time clearance model: the MRA sits directly in the path of every invoice. That makes it very different from South Africa’s proposed decentralised model, and it makes the reliability of your connection to the MRA part of your checkout.

Who must comply in 2026

The MRA is phasing the obligation in by taxpayer category and annual turnover:

Separately, under section 20A(2) of the VAT Act, the Director-General can require any taxpayer to comply from a specified date by written notice — regardless of turnover. If you’ve received a notice, its terms and timeline apply to you. Further phases are expected to extend the obligation to more businesses.

How fiscalisation works, step by step

1. Your billing system creates the invoice — in the MRA’s standard e-invoice structure (JSON).
2. It sends the invoice to the MRA in real time over the MRA’s API, signed and identified by your EBS MRA ID.
3. The MRA validates it and returns the IRN and QR code.
4. Your system prints or sends the fiscal invoice with the IRN and QR code to the customer.
5. The customer can verify it with the MRA.

Key terms

Getting on board: the MRA process

1. Use a compliant EBS. Software developers and solution providers register, customise, test and self-certify their EBS through the MRA developer portal.
2. Register as an economic operator on the MRA e-Invoicing Portal.
3. Pass the prescribed portal tests with your EBS.
4. Receive your EBS MRA ID once registration succeeds.
5. Go live and issue fiscal invoices from your compliance date.

If you invoice from several systems or locations — say an ERP for wholesale and a POS estate for retail — each EBS needs to be compliant and registered.

The practical challenges

• Real-time dependency at the point of sale. When every receipt waits for an MRA response, a slow network or a busy platform shows up as queues at the till. Your design must keep trading while staying compliant.
• Legacy and custom systems. Older ERPs, custom databases and local POS software often can’t produce the MRA format or call its API without significant development.
• Multiple systems. Groups with different systems per entity or location multiply the onboarding, testing and monitoring effort.
• Rejections and reconciliation. Invoices the MRA rejects must be caught, corrected and resent — and every fiscalised invoice must reconcile back to your books.
• Testing the wrong thing. Passing the MRA portal tests proves your connection works, not that all your real invoices will be accepted. Run a sample of real invoices of every type — especially credit notes and unusual cases — and check which ones fail, and why.
• Record keeping. Fiscal invoices and MRA responses form part of your VAT records, which generally must be kept for at least five years.

Plan for downtime explicitly. Read the MRA’s Functional Specifications for the procedure your EBS must follow when the platform can’t be reached, and make sure your integration queues invoices, retries automatically and reconciles once the connection recovers — without anyone at the till having to think about it.

Checklist for businesses in scope

1. Confirm your compliance date from the table above, or from any notice you’ve received under section 20A(2).
2. List every system that issues invoices or receipts — ERP, POS, ECR, billing platforms.
3. Check each one is a compliant EBS, or choose how you’ll make it compliant.
4. Register on the MRA e-Invoicing Portal and complete the portal tests.
5. Design for outages and rejections — queueing, retries, alerts and reconciliation.
6. Train your team on the new invoice layout, the IRN and the QR code.

How Celium Surge helps

Celium Surge connects the billing systems you already run to the MRA — without replacing or rewriting them. It picks up invoices from files or API calls your system already produces, from your existing database, or from cloud accounting, converts them to the MRA’s format, fiscalises them in real time and returns the IRN and QR code to your system.

• Built for real-time clearance: your tills get an instant acknowledgement, and Surge buffers invoices safely if the MRA platform is slow.
• One connection for every system: ERP, POS and billing platforms through a single integration.
• Rejections handled: failures are retried, held safely and flagged — never silently lost or sent twice.
• Audit-ready: every submission and MRA response archived to tamper-proof storage.

Surge is in its pilot phase, and we’re onboarding a limited first cohort of Mauritian businesses. Tell us about your systems and we’ll map your route to compliance. Also invoicing in South Africa? Read our SARS e-invoicing guide.

Frequently asked questions

Sources

Checked on 9 October 2026. Regulations change: always confirm details against the official SARS and MRA publications before acting. This guide is general information, not tax or legal advice.

1. Mauritius Revenue Authority — e-Invoicing System (official page) — phases, thresholds, EBS and onboarding
2. MRA — e-Invoicing FAQs (PDF)
3. MRA — e-Invoicing communiqué, 29 January 2024 (PDF)
4. EDICOM — Mauritius electronic invoicing system — process flow
5. VATupdate — Mauritius e-invoicing & e-reporting guide (September 2026)