E-Invoicing Platform
The global e-invoicing platform for small business
Live in 17 jurisdictions across 5 regions: ZATCA, MyInvois, GST IRN, Peppol, FIRS, MTD, eTIMS, GRA, BIR, SARS, ZIMRA, SRC, NF-e, IPP, and CRA. Every invoice carries the local cryptographic artefact the tax authority requires.
18 live mandates
5 regions covered
Certified Peppol Access Point partner
Audit trail on every invoice
Definition
What e-invoicing actually is
E-invoicing is the issuing of an invoice as a structured, machine-readable file — not a PDF — in the format a tax authority prescribes, carrying the artefact that authority requires (a CSID, IRN, UUID, QR code, or fiscal signature), and delivered over the mandated transport: a direct authority API, a Peppol Access Point, or a national portal.
A PDF emailed to a client is a digital invoice, not an e-invoice. Only the structured file that the authority accepts and stamps counts as compliant, and in a mandated market an unstamped invoice is not a valid tax document — which is why invoicing software and an e-invoicing platform are not the same product.
What a mandate changes for you
- The file format is chosen for you
- You issue UBL, XML, or JSON in the authority-defined schema (FatturaPA, Peppol BIS Billing 3.0, ZATCA UBL 2.1, GST e-invoice JSON), with every mandatory field populated and validated before it leaves.
- The invoice must be cleared or reported
- Depending on the market, the invoice is pre-cleared before you send it, reported in near real time after issue, or routed to the buyer over a certified network. Send it the old way and it never becomes a legal invoice.
- The artefact must be on the document
- The stamp the authority returns — CSID, IRN, UUID, QR, or signature — has to be embedded on the invoice the buyer receives, or their accountant cannot claim the input tax.
- You must archive what you issued
- The structured original, its authority response, and the audit trail have to be retained for the statutory period and produced on request.
Billing clients in markets with no mandate? See Invoicemonk invoicing software.
Live mandate matrix
Authority, artefact, transport — for every mandate we cover
The full reference: what each tax authority requires and how Invoicemonk delivers it.
| Jurisdiction | Authority | Mandate | Artefact | Transport | Applies to | Live since |
|---|---|---|---|---|---|---|
| Middle East | ||||||
| Saudi Arabia | ZATCA (Zakat, Tax and Customs Authority) | Fatoorah Phase 2 — Integration Phase | CSID-signed XML (UBL 2.1) with embedded QR (TLV, Base64) and UUID | Direct API integration with the ZATCA Fatoorah portal (clearance for B2B, reporting for B2C) | All VAT-registered businesses in Saudi Arabia (B2B clearance, B2C reporting). | 2024-04-01 |
| Saudi Arabia | ZATCA (Zakat, Tax and Customs Authority) | Fatoorah Phase 1 — Generation Phase | Structured electronic invoice (XML or PDF/A-3 with XML), tamper-resistant, with QR for Simplified Tax Invoices | On-system generation and archival (no portal submission in Phase 1) | All VAT-registered businesses that have not yet onboarded to Phase 2. | 2021-12-04 |
| Asia-Pacific | ||||||
| Malaysia | LHDN (Inland Revenue Board of Malaysia) | MyInvois e-Invoicing | MyInvois UUID, validated XML/JSON, embedded QR linking to the LHDN validation record | Direct API submission to the LHDN MyInvois portal for validation and UUID issuance | Phased by turnover: >MYR 100m since Aug 2024; >MYR 25m since Jan 2025; all taxpayers from Jul 2025. | 2024-08-01 |
| India | GSTN / NIC (Invoice Registration Portal) | GST e-Invoicing (IRN + QR) | IRN (Invoice Reference Number), digitally signed JSON, signed QR with IRN | Direct API submission to the NIC Invoice Registration Portal (IRP) | All GST-registered businesses with aggregate turnover above INR 5 crore (current threshold). | 2023-08-01 |
| Philippines | BIR (Bureau of Internal Revenue) | EIS — Electronic Invoicing System (CAS / e-Invoice / e-Receipt) | JSON e-invoice transmitted to BIR EIS, BIR-issued reference number, QR | Direct API submission to the BIR Electronic Invoicing System | Phased: top 100 large taxpayers since 1 July 2022; expansion to all VAT-registered taxpayers ongoing per BIR Revenue Regulations. | 2023-01-01 |
| Europe | ||||||
| European Union | OpenPeppol / national Peppol Authorities | Peppol BIS Billing 3.0 (B2B and B2G) | UBL 2.1 / CII XML conforming to Peppol BIS 3.0, signed and routed via a Peppol Access Point | Four-corner model: Invoicemonk → certified Peppol Access Point → buyer Access Point → buyer | EU sellers and buyers exchanging structured e-invoices, including all B2G in EU member states (Directive 2014/55/EU). | 2024-01-15 |
| United Kingdom | HMRC (His Majesty's Revenue and Customs) | Making Tax Digital for VAT | Digital VAT records linked to invoice IDs, digital VAT return submitted via MTD API | Direct OAuth2 submission to the HMRC MTD VAT API | All UK VAT-registered businesses (mandatory since 1 April 2022). | 2022-04-01 |
| Italy | Agenzia delle Entrate (AdE) — Sistema di Interscambio (SdI) | FatturaPA via Sistema di Interscambio (clearance) | FatturaPA XML (v1.2.x) signed with CAdES-BES (.xml.p7m) or XAdES, delivered through SdI with the AdE delivery receipt (ricevuta di consegna) | Direct submission to the AdE Sistema di Interscambio (SdI) via SDICoop web service, PEC, SDIFTP, or accredited intermediary | All Italian VAT-registered businesses for B2B, B2C, and B2G invoices. Mandatory for flat-rate (regime forfettario) taxpayers from 1 January 2024. | 2024-02-01 |
| Bulgaria | НАП — Национална агенция за приходите (NRA, National Revenue Agency) | SAF-T BG reporting + B2G Peppol BIS Billing 3.0 and planned domestic e-invoicing | SAF-T BG XML (OECD SAF-T 2.0 with Bulgarian extensions); Peppol BIS Billing 3.0 UBL routed via certified Access Point for B2G | SAF-T XML submitted to NRA portal monthly/annually; B2G invoices through the Peppol four-corner network | Phased SAF-T: large enterprises from 1 January 2026; medium enterprises from 1 January 2027; small enterprises from 1 January 2028; micro from 1 January 2030. B2G Peppol mandatory since 2019. Domestic B2B e-invoicing in public consultation. | 2026-01-01 |
| Africa | ||||||
| Nigeria | FIRS (Federal Inland Revenue Service) | FIRS Merchant-Buyer Solution (MBS) e-Invoicing | IRN issued by FIRS MBS, signed JSON payload, QR with FIRS verification URL | Direct API submission to the FIRS MBS platform | Phased: large taxpayers from 1 August 2025; medium and small in subsequent waves per FIRS schedule. | 2025-08-01 |
| Kenya | KRA (Kenya Revenue Authority) | eTIMS (Electronic Tax Invoice Management System) | Control Unit Invoice Number (CU Invoice Number), QR, signed invoice transmitted to KRA in real time | Direct API submission to the KRA eTIMS portal (online VSCU/OSCU model) | All taxpayers with annual turnover above KES 5 million, plus all VAT-registered businesses regardless of turnover. | 2024-03-31 |
| Ghana | GRA (Ghana Revenue Authority) | Certified Invoicing System (E-VAT) | Invoice Reference Number (IRN) issued by GRA, signed XML, QR with GRA verification URL | Direct API submission to the GRA E-VAT platform via the certified invoicing system integration | Phased: large taxpayers since October 2022; medium and small in subsequent waves announced by GRA. | 2024-04-01 |
| South Africa | SARS (South African Revenue Service) | SARS Tax Invoice Requirements (VAT Act s.20) + e-Filing VAT201 | Tax invoice with SARS-required fields, digitally signed PDF, VAT201 return submitted via SARS e-Filing | SARS-compliant invoice issued to buyer; VAT201 submitted via SARS e-Filing API | All South African VAT vendors (registered above ZAR 1 million turnover, voluntary above ZAR 50 000). | 2023-06-01 |
| Zimbabwe | ZIMRA (Zimbabwe Revenue Authority) | Fiscalisation Data Management System (FDMS) | Fiscal Device Identifier signature, fiscal invoice number, QR with ZIMRA verification URL | Real-time submission to the ZIMRA FDMS platform (virtual fiscal device model) | All VAT-registered operators in Zimbabwe (Statutory Instrument 153 of 2023). | 2024-01-01 |
| Seychelles | SRC (Seychelles Revenue Commission) | VAT Act tax invoice requirements + SRC e-Filing | SRC-compliant tax invoice with sequential numbering, digital signature, VAT return filed via SRC e-Filing | SRC-compliant invoice to buyer; VAT return submitted via SRC e-Filing | VAT-registered businesses in Seychelles (above SCR 2 million annual turnover threshold). | 2024-05-01 |
| Americas | ||||||
| Brazil | SEFAZ (state) / Receita Federal (federal) | NF-e (Nota Fiscal Eletrônica) and NFS-e (services) | NF-e/NFS-e XML signed with ICP-Brasil A1 certificate, Chave de Acesso (44-digit access key), DANFE PDF | Direct API submission to the state SEFAZ for NF-e; to the municipal portal for NFS-e | All Brazilian businesses issuing invoices for goods (NF-e) or services (NFS-e). | 2024-06-01 |
| United States | US Federal Government (Treasury Bureau of the Fiscal Service) | Invoice Processing Platform (IPP) — Federal B2G e-Invoicing | IPP-compliant invoice (UBL or CSV-converted) submitted to the IPP portal | Direct submission to the Treasury Invoice Processing Platform (IPP) | Suppliers invoicing US federal agencies that use IPP. | 2024-09-01 |
| Canada | CRA (Canada Revenue Agency) + Peppol Authority Canada | CRA GST/HST tax invoice + Peppol BIS Billing Canada | CRA-compliant GST/HST invoice; Peppol BIS Canada UBL routed via certified Access Point | CRA-compliant invoice to buyer; Peppol UBL routed through certified Peppol Access Point (Canada PA model) | All Canadian GST/HST registrants; Peppol routing for buyers on the Canadian Peppol network. | 2024-10-01 |
Cryptographic artefacts, in every jurisdiction we cover
Invoicemonk issues cryptographically signed structured invoices in every one of the 18 jurisdictions we cover, using the local artefact the tax authority requires:
- CSID — ZATCA (Saudi Arabia)
- IRN — GST India (NIC IRP), FIRS Nigeria, GRA Ghana
- UUID — MyInvois Malaysia
- QR + Control Unit Number — KRA eTIMS (Kenya)
- Chave de Acesso — NF-e / NFS-e (Brazil)
- Fiscal signature — ZIMRA FDMS (Zimbabwe)
- XAdES digital signatures — Peppol (EU), MTD (UK)
- ICP-Brasil A1 — Brazilian NF-e / NFS-e signing
Each mandate page documents the local artefact, signing algorithm, certificate authority, and the spec section that requires it.
By region
Coverage across 5 regions
Middle East
2 mandates
Asia-Pacific
3 mandates
Europe
4 mandates
Africa
6 mandates
- Nigeria (FIRS Merchant-Buyer Solution (MBS) e-Invoicing)
- Kenya (eTIMS (Electronic Tax Invoice Management System))
- Ghana (Certified Invoicing System (E-VAT))
- South Africa (SARS Tax Invoice Requirements (VAT Act s.20) + e-Filing VAT201)
- Zimbabwe (Fiscalisation Data Management System (FDMS))
- Seychelles (VAT Act tax invoice requirements + SRC e-Filing)
Who it's for
Built for every team that bills
One platform, four buying contexts, the same mandate coverage.
Freelancers
Issue mandate-compliant invoices in every country you bill from, with the local artefact pre-attached.
Small businesses
Clear ZATCA, MyInvois, GST IRN, FIRS, eTIMS, and Peppol from one workspace, with audit trails per invoice.
Agencies
Bill clients across regions, route Peppol invoices to public-sector buyers, and reconcile in one ledger.
Accountants
Onboard CSID, IRN, and UUID issuance for every client, with per-client signing certificates managed centrally.
FAQ
Frequently asked questions
Source authorities
Verified against tax-authority specifications
Every mandate page links to the authority's published guideline. Below are the source portals Invoicemonk's implementations are validated against.
Middle East
Africa
Mandate-compliant from day one
One platform, 18 mandates, every artefact your tax authority requires.