Zimbabwe

ZW

Zimbabwe relies on fiscalisation; VAT-registered operators must issue fiscal tax invoices from fiscal devices or virtual fiscalisation software connected to ZIMRA's Fiscalisation Data Management System (FDMS), and ZIMRA's TaRMS draws input tax data from FDMS.

Guide reviewed .

Invoicing and electronic documents

Fiscalisation Data Management System (FDMS)

ZIMRA's server for fiscalised sales. Fiscal devices and virtual fiscalisation software record and transmit sales data at the time of sale, and FDMS returns the QR code and verification code printed on each fiscal tax invoice, receipt, debit note or credit note. It is a fiscalisation system, not an invoice exchange network or Peppol.

Hardware fiscal devices (fiscalised registers, fiscal printers, electronic signature devices) or virtual fiscal devices using the ZIMRA Fiscalisation API · Official source: ZIMRA · Fiscalisation explained

Virtual fiscalisation

Direct server-to-server or POS, accounting or invoicing system connections to FDMS through ZIMRA's API, available free of charge. ZIMRA presents it as suited to medium and large taxpayers, with mobile point of sale for small traders.

ZIMRA Fiscalisation API · Official source: ZIMRA · Public Notice 101 of 2024, virtual fiscalisation compliance

Tax and Revenue Management System (TaRMS)

ZIMRA's tax administration system. Since 1 December 2025 it receives fiscal tax invoice, debit note and credit note data from FDMS to build automatic input tax schedules for VAT returns.

Integration between FDMS and the TaRMS self-service portal · Official source: ZIMRA · Public Notice 63 of 2025, TaRMS and FDMS integration

Peppol

No Zimbabwean Peppol Authority is listed; OpenPeppol acts as the authority where there is no national one. No link between FDMS and Peppol was found in ZIMRA's guidance.

Peppol BIS Billing · Official source: OpenPeppol · Peppol Authorities

An invoicing system used in Zimbabwe must be fiscalised. Each fiscal tax invoice, debit note and credit note is reported to FDMS when it is issued, and must carry the QR code FDMS returns. Larger operators usually connect their ERP or POS directly through the virtual fiscalisation API.

A Peppol invoice can be delivered alongside, but on its own it is not a fiscal tax invoice. A buyer's input tax depends on the supplier's document validating in FDMS. Capture full buyer details so they reach FDMS. See Public Notice 80 of 2024.

Timeline

  1. Deadline to upgrade to FDMS

    Operators required to fiscalise had to upgrade fiscal devices or POS systems, or use virtual fiscalisation, to comply with FDMS.

    Official source: ZIMRA · Public Notice 92 of 2023, compliance with FDMS
  2. FDMS compliance tied to tax clearance

    FDMS compliance became one of the requirements for a Tax Clearance Certificate.

    Official source: ZIMRA · Public Notice 92 of 2023, compliance with FDMS
  3. Buyer details transmitted to FDMS

    Deadline for fiscal devices to transmit captured buyer details to FDMS.

    Official source: ZIMRA · Public Notice 30 of 2025, buyer details on FDMS fiscal tax invoices
  4. TaRMS and FDMS integration

    Input tax schedules began to be drawn from FDMS data. Documents issued up to 30 November 2025 had to be claimed by 10 December 2025.

    Official source: ZIMRA · Public Notice 63 of 2025, TaRMS and FDMS integration

Peppol in Zimbabwe

Directory participants
Not recorded
Document families
Not recorded

Peppol Authority: OpenPeppol.

Peppol Directory data as of .

How to read these numbers

Documents on Peppol

No document-support data has been published for this country.

Registrations over time

No registration history has been published for this country.

Registration dates in the current Directory snapshot.

Participants

No participants are recorded for this country in the Directory snapshot. This does not establish absence from Peppol.