# Africa E-Invoicing and Fiscal Device Regimes Reference

> Source: https://netray.co/tools/africa-e-invoicing-and-fiscal-device-regimes-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A lookup of the electronic invoicing and fiscal device systems used by African revenue authorities, and what each one means for ERP billing design.

## Category

regional

## Region

Africa

## Audience

- ERP administrator
- Finance controller
- ERP developer
- Tax manager

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### Country

**Key:** country

**Type:** text

#### Authority

**Key:** authority

**Type:** text

#### System

**Key:** system

**Type:** text

#### Model

**Key:** model

**Type:** select

**Options:**

- Real time reporting
- Clearance
- Fiscal device
- No mandate
- Phased rollout

#### ERP implication

**Key:** erp

**Type:** text

**Rows:**

**Country:** Kenya

**Authority:** KRA

**System:** eTIMS (electronic Tax Invoice Management System)

**Model:** Real time reporting

**Erp:** Sales invoices are reported to KRA and receive a control unit invoice number and QR code. Purchases need eTIMS valid supplier invoices to be deductible.

**Country:** Kenya

**Authority:** KRA

**System:** eTIMS buyer initiated invoice

**Model:** Real time reporting

**Erp:** Used when a supplier is not able to issue an eTIMS invoice. Needs a purchase side process and a supplier consent record.

**Country:** Egypt

**Authority:** ETA

**System:** E-Invoice portal

**Model:** Clearance

**Erp:** Invoices are digitally signed, submitted and validated before they are valid. Needs a signing certificate, activity codes and item codes such as GS1 or EGS.

**Country:** Egypt

**Authority:** ETA

**System:** E-Receipt

**Model:** Real time reporting

**Erp:** Covers business to consumer retail sales through a point of sale. Keep it separate from the B2B invoice flow.

**Country:** Nigeria

**Authority:** FIRS, now moving to the Nigeria Revenue Service

**System:** Merchant Buyer Solution (MBS) e-invoicing

**Model:** Phased rollout

**Erp:** Rollout began with large taxpayers. Expect an invoice reference number and QR code on each invoice. Confirm your phase and the current technical specification.

**Country:** Tanzania

**Authority:** TRA

**System:** EFD (Electronic Fiscal Device)

**Model:** Fiscal device

**Erp:** Receipts come from a registered device. The ERP needs a way to store the fiscal receipt number against the sales document.

**Country:** Tanzania

**Authority:** TRA

**System:** VFD (Virtual Fiscal Device)

**Model:** Fiscal device

**Erp:** Software based receipts issued through the TRA VFD system. Often integrated by API rather than a hardware printer.

**Country:** Uganda

**Authority:** URA

**System:** EFRIS (Electronic Fiscal Receipting and Invoicing Solution)

**Model:** Real time reporting

**Erp:** Invoices and credit notes are sent to URA and return a fiscal document number and QR code. Item and unit codes must be registered first.

**Country:** Rwanda

**Authority:** RRA

**System:** EBM (Electronic Billing Machine)

**Model:** Fiscal device

**Erp:** Invoices are generated through certified EBM software or hardware. Needs a sign and send step before the document is final.

**Country:** Zambia

**Authority:** ZRA

**System:** Smart Invoice

**Model:** Real time reporting

**Erp:** Invoices are issued through the Smart Invoice application and a Virtual Sales Data Controller. Check which ERP integration pattern your version supports.

**Country:** Zambia

**Authority:** ZRA

**System:** VSDC (Virtual Sales Data Controller)

**Model:** Fiscal device

**Erp:** Component that signs and records each invoice. Plan for downtime handling and resubmission.

**Country:** Zimbabwe

**Authority:** ZIMRA

**System:** FDMS (Fiscalised Device Management System)

**Model:** Fiscal device

**Erp:** Fiscal devices or software are registered with FDMS. Invoices carry a fiscal day and receipt counter.

**Country:** Malawi

**Authority:** Malawi Revenue Authority

**System:** EIS (Electronic Invoicing System)

**Model:** Real time reporting

**Erp:** VAT registered businesses issue invoices through the EIS. Credit notes and debit notes follow the same path.

**Country:** Ghana

**Authority:** GRA

**System:** E-VAT invoicing

**Model:** Phased rollout

**Erp:** Rolling out in phases. Confirm the status for your taxpayer category and the technical specification before building.

**Country:** South Africa

**Authority:** SARS

**System:** No national e-invoicing mandate for VAT invoices

**Model:** No mandate

**Erp:** A valid tax invoice must carry the fields required by the VAT Act. VAT201 is filed through eFiling. Customers may still demand EDI or portal based invoices.

**Notes:** Systems, phases and deadlines change quickly in this area. Always check the authority's current technical specification and the latest public notices. This list is a map of the landscape, not compliance advice.

## Content

**Intro:** African revenue authorities are moving from paper invoices to real time reporting and fiscal devices. Each system has a different model, a different set of mandatory fields and a different failure mode. This reference lists the main regimes and what each means for the billing process in your ERP.

**Sections:**

#### How to use the list

**Body:** Filter by country or by model to see which pattern applies to you. Real time reporting means your ERP creates an invoice and then sends it to the authority, which returns an identifier. Clearance means the invoice is not valid until the authority has accepted it. Fiscal device means a certified device or virtual device signs the receipt. Use the ERP implication column to decide whether you need an integration layer, a country localization package or a certified third party connector.

#### Three integration patterns

**Body:** Most ERP projects end up with one of three patterns. A localization package from the ERP vendor or a partner covers the common cases. A middleware connector sits between the ERP and the authority API and handles retries and queues. A custom build calls the authority API directly from the billing process. The right pattern depends on volume, number of countries and how tightly your invoice workflow is customized. A single country plant with simple invoicing can be well served by a packaged connector.

**Bullets:**

- Localization package: fastest, limited customization.
- Middleware connector: good for several countries.
- Custom API integration: most control, most maintenance.

#### What to design around

**Body:** Plan for the authority being unreachable. Decide whether an invoice can be printed before it is accepted, how it is resubmitted, and how credit notes reference the original. Store the authority identifier, QR code and timestamp on the sales document, and keep the signed payload for audit. Map item codes and units of measure early because rejected items are the most common cause of failed submissions in the first weeks.

#### Common mistakes

**Body:** Teams often test only the happy path. They forget credit notes, partial deliveries, foreign currency invoices and rounding differences between ERP and authority. Others assume the same rules apply across the border in a neighboring country. Run a test pack that covers returns, discounts, exempt lines and zero rated exports before go live, and agree who watches the submission queue daily.

**Cta:** If you need to see which invoices failed submission or are missing authority identifiers, Netray can build a read only exception view on top of your ERP billing tables.

**Faq:**

#### Is e-invoicing mandatory in every African country?

**Answer:** No. Some countries have mandates, others use fiscal devices, and some, like South Africa, have no national e-invoicing mandate for VAT invoices today. Rules change, so check the authority notice for your taxpayer category.

#### What is the difference between clearance and real time reporting?

**Answer:** In clearance, an invoice is not legally valid until the authority validates it. In real time reporting, the invoice is issued and then reported immediately. Both need an integration, but clearance blocks the sale if the authority is unavailable.

#### Can the ERP vendor handle this for me?

**Answer:** Sometimes. Large vendors ship localization packages for some countries, but coverage and version support vary. Ask for the exact system names, supported versions and who maintains the integration when the authority changes its specification.

#### Do purchases matter too?

**Answer:** In some regimes, yes. Kenya, for instance, ties expense deductibility to eTIMS valid supplier invoices. Your purchase process may need to capture the control unit invoice number from suppliers.

## Search terms

africa e-invoicing systems list, eTIMS EFRIS ETA smart invoice comparison, fiscal device africa ERP, electronic invoicing mandate africa, kenya eTIMS ERP integration, uganda EFRIS integration, zambia smart invoice VSDC, tanzania EFD VFD

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json