E-invoicing
E-invoicing compliance by country
Every market POSMena serves has its own e-invoicing regulator, format, and clearance model. This page maps the rules side by side — Saudi Arabia, the UAE, Türkiye, Jordan, and Malaysia — so finance and IT leaders can see exactly which standard applies and how POSMena handles it.
Saudi Arabia — ZATCA Phase 2 (Fatoora)
Saudi Arabia's e-invoicing regime is operated by ZATCA (Zakat, Tax and Customs Authority) under the Ministry of Finance, on the Fatoora platform. The legal basis is the E-Invoicing Regulation (2020) together with its Controls, Requirements, Technical Specifications and Procedural Rules. All VAT-registered resident taxable persons are in scope, including third parties issuing tax invoices on their behalf. The regime runs in two phases: Phase 1 — Generation (live since December 2021) and Phase 2 — Integration (rolling out in waves from January 2023). ZATCA announces each wave by VAT-registered revenue threshold, starting at SAR 3bn+ and stepping down. B2B and B2G Tax Invoices must be cleared by ZATCA in real time before being shared with the buyer; B2C Simplified Tax Invoices are issued first and reported to ZATCA within 24 hours. POSMena is built to ZATCA Phase 2 (Integration) technical specifications, including UBL 2.1 XML, embedded QR (TLV), UUID, cryptographic stamp and hash chaining. POSMena supports clearance of B2B Tax Invoices and reporting of B2C Simplified Tax Invoices to the Fatoora platform, and issues invoices in Arabic and English with mandatory fields in Arabic as required by ZATCA.
- Regulator: ZATCA (Zakat, Tax and Customs Authority), under the Ministry of Finance
- Document types: Tax Invoice (B2B/B2G) and Simplified Tax Invoice (B2C)
- Format: UBL 2.1 XML with embedded QR (TLV), UUID, cryptographic stamp and hash chain
- Model: real-time clearance for B2B Tax Invoices; 24-hour reporting for B2C Simplified Tax Invoices
- Retention: six years, in line with current KSA VAT law
- Language: Arabic mandatory for required fields; English permitted as a secondary language
United Arab Emirates — UAE eInvoicing Programme (Peppol PINT AE)
The UAE eInvoicing Programme is owned by the UAE Ministry of Finance (MoF) as policy owner and the Federal Tax Authority (FTA) as tax administrator. The network uses Peppol PINT AE — the UAE-localised Peppol International Invoice profile — on a 5-corner DCTCE (Decentralised Continuous Transaction Control and Exchange) model, with accredited intermediaries known as ASPs (Accredited Service Providers). Published scope covers B2B and B2G transactions; B2C is out of initial scope. Indicative timeline: the ASP accreditation framework is live in 2025, with Phase 1 mandatory go-live targeted at July 2026 for large taxpayers and broader rollout to follow. Exact dates remain subject to MoF confirmation. POSMena is built on the Peppol PINT AE specification, supports the 5-corner DCTCE flow (sender → sender's ASP → buyer's ASP → buyer, with a parallel report leg to the FTA), and is preparing for UAE ASP accreditation under the FTA framework. UAE invoices are issued in AED, in English and Arabic.
- Regulator: UAE Ministry of Finance (policy) and Federal Tax Authority (tax administration)
- Document scope: B2B and B2G mandatory; B2C out of initial scope
- Format and model: Peppol PINT AE on a 5-corner DCTCE network
- Exchange: ASP-to-ASP delivery with a parallel reporting leg to the FTA
- Currency and language: AED, English and Arabic
- Timeline: ASP accreditation framework live 2025; Phase 1 mandatory go-live targeted July 2026 (subject to MoF confirmation)
Türkiye — e-Fatura and e-Arşiv (GİB e-Dönüşüm)
Türkiye's e-invoicing regime is regulated by GİB (Gelir İdaresi Başkanlığı, the Revenue Administration) under the Ministry of Treasury and Finance, as part of the e-Dönüşüm (e-Transformation) programme. The legal basis is VUK General Communiqué No. 509 and its amendments. e-Fatura is the structured invoice exchanged between taxpayers registered on the GİB system; e-Arşiv Fatura covers invoices to recipients who are not registered on e-Fatura, including B2C. Scope is set by turnover thresholds (historically updated, with recent levels in the TRY 3M–5M range for general taxpayers) and by sector-specific mandates regardless of turnover — including e-commerce intermediaries, hotels, real estate and motor vehicle dealers, and the fuel sector. Invoices are issued in UBL-TR (Turkish UBL profile) XML, digitally signed with Mali Mühür (fiscal seal) for legal entities or e-İmza for individuals. Transmission is through the GİB Portal, a licensed Özel Entegratör (private integrator), or in-house Direct Integration. POSMena outputs UBL-TR compatible invoice data ready for submission through a licensed Özel Entegratör, with TRY pricing, KDV (VAT) breakdown and Turkish-language fields aligned with GİB requirements. e-Fatura and e-Arşiv routing logic is handled per recipient registration status, and archives are retained for the statutory 10-year VUK period.
- Regulator: GİB (Gelir İdaresi Başkanlığı / Revenue Administration), under the Ministry of Treasury and Finance
- Document types: e-Fatura (registered taxpayers), e-Arşiv Fatura (non-registered / B2C), with adjacent e-İrsaliye for waybills
- Format: UBL-TR XML, digitally signed with Mali Mühür (legal entities) or e-İmza (individuals)
- Transmission: GİB Portal, licensed Özel Entegratör, or in-house Direct Integration
- Retention: 10-year archival obligation under VUK
- Currency and language: TRY with Turkish-language invoice fields
Jordan — JoFotara (ISTD national e-invoicing platform)
Jordan's national e-invoicing system is JoFotara, operated by the Income and Sales Tax Department (ISTD) under the Ministry of Finance. Invoices are issued and registered through JoFotara, which returns a QR code and UUID once accepted by the platform. Scope applies to taxpayers issuing invoices in Jordan, with phased rollout by sector and taxpayer size and broadening mandatory adoption announced by ISTD. B2B and B2G are covered, and B2C issuance is also reportable through the platform. POSMena is integrated with JoFotara and generates JoFotara-compliant tax invoices with the QR code and UUID returned by the platform. Issuance is Arabic-first in JOD, and submitted invoices are archived in line with Jordanian tax law. POSMena is ready for ISTD's phased rollout of mandatory e-invoicing in Jordan.
- Regulator: Income and Sales Tax Department (ISTD), under the Ministry of Finance
- Platform: JoFotara — the national e-invoicing system
- Document scope: B2B and B2G covered; B2C issuance also reportable
- Validation output: QR code and UUID returned by the JoFotara platform on acceptance
- Currency and language: JOD with Arabic-first invoice fields
- Model: issuance and reporting through the JoFotara API, phased by sector and taxpayer size
Malaysia — MyInvois (LHDN e-Invoice)
Malaysia's national e-invoicing system is MyInvois, operated by LHDN (Lembaga Hasil Dalam Negeri / Inland Revenue Board of Malaysia). The regime is a phased, mandatory rollout covering B2B, B2G and B2C transactions, with scope extending to credit notes, debit notes, refund notes, and self-billed e-invoices in defined scenarios such as foreign suppliers and certain agency arrangements. LHDN has published a phased timeline by turnover band: Phase 1 (annual turnover above RM100 million) from 1 August 2024; Phase 2 (above RM25 million up to RM100 million) from 1 January 2025; and Phase 3 (remaining taxpayers) staged through 2025–2026. The submission flow is: issuer transmits to MyInvois, LHDN validates, a Unique Identifier Number (UIN) plus QR code is returned, and the validated document is shared with the buyer. POSMena is MyInvois-ready: invoices are generated in the LHDN-defined JSON/XML schema and submitted via the MyInvois API, with the UIN and QR code captured on every issued document. POSMena supports self-billed e-invoice scenarios required by LHDN, issues invoices in MYR with English and Bahasa Malaysia layouts, and archives validated e-invoices in line with Malaysian tax law.
- Regulator: LHDN (Lembaga Hasil Dalam Negeri / Inland Revenue Board of Malaysia)
- Document scope: B2B, B2G and B2C — invoices, credit notes, debit notes, refund notes, and self-billed e-invoices
- Format: LHDN-defined JSON/XML schema submitted via the MyInvois API
- Validation output: LHDN Unique Identifier Number (UIN) and QR code returned on acceptance
- Phasing: Phase 1 (>RM100M) from 1 August 2024; Phase 2 (>RM25M–RM100M) from 1 January 2025; Phase 3 staged through 2025–2026
- Currency and language: MYR with English and Bahasa Malaysia document layouts
How POSMena handles all in one stack
Each regulator has its own format, clearance model and timeline — but a multi-market operator should not need a different invoicing stack per country. POSMena consolidates ZATCA Phase 2 (Fatoora), UAE Peppol PINT AE, Türkiye e-Fatura and e-Arşiv via Özel Entegratör handoff, Jordan JoFotara, and Malaysia MyInvois behind a single invoicing engine. The same product handles the local format (UBL 2.1 XML, Peppol PINT AE, UBL-TR, JoFotara schema, MyInvois JSON/XML), the correct transmission model (real-time clearance, 5-corner DCTCE exchange, Özel Entegratör submission, JoFotara API, MyInvois API), and the local language and currency requirements (Arabic, Turkish, English, Bahasa Malaysia; SAR, AED, TRY, JOD, MYR).
- One invoicing engine across KSA, UAE, Türkiye, Jordan and Malaysia
- Per-market format support: UBL 2.1 XML, Peppol PINT AE, UBL-TR, JoFotara schema, MyInvois JSON/XML
- Clearance, reporting and exchange models handled per regulator — not bolted on per project
- Bilingual or trilingual invoice layouts with local-currency rounding and tax breakdowns
- Archival aligned to each market's retention requirement (e.g. six years KSA, 10 years Türkiye)
- Ready/aligned/preparing-for posture on every market — claims are dated and sourced, never invented
أسئلة شائعة
Which countries' e-invoicing regimes does POSMena support today?
POSMena supports Saudi Arabia (ZATCA Phase 2 / Fatoora), the United Arab Emirates (UAE eInvoicing Programme on Peppol PINT AE), Türkiye (e-Fatura and e-Arşiv under GİB), Jordan (JoFotara under ISTD), and Malaysia (MyInvois under LHDN) from a single invoicing engine.
What is the difference between a clearance model and a reporting model?
In a clearance model, the regulator validates the invoice before it can be shared with the buyer — Saudi Arabia's ZATCA Phase 2 clears B2B Tax Invoices in real time, and Malaysia's MyInvois validates each document and returns a UIN plus QR code. In a reporting model, the invoice is issued first and reported to the authority within a set window — for example, ZATCA Simplified Tax Invoices are reported within 24 hours. The UAE uses a different shape again: a 5-corner DCTCE exchange where invoices flow ASP-to-ASP and a parallel report leg goes to the FTA.
Are POSMena's claims that it is 'ready' the same as being 'certified'?
No. POSMena uses 'ready', 'aligned' or 'preparing for' wherever a regulator has not issued a specific certificate, listing or accreditation. For example, the UAE Accredited Service Provider scheme is granted by the FTA framework — until that is granted, POSMena describes its posture as 'preparing for UAE ASP accreditation', not 'accredited'. Where evidence exists (such as a ZATCA-issued CSID for a taxpayer's integration), that is referenced specifically.
Does e-invoicing apply to B2C transactions in every market?
It varies. KSA covers B2C through Simplified Tax Invoices reported to ZATCA within 24 hours; Malaysia's MyInvois explicitly covers B2B, B2G and B2C with consolidated and self-billed flows; Jordan's JoFotara has B2C issuance reportable through the platform; Türkiye covers B2C through e-Arşiv Fatura rather than e-Fatura. The UAE eInvoicing Programme, as currently published, is B2B and B2G mandatory with B2C out of initial scope.
What languages and currencies does POSMena issue invoices in across these markets?
Arabic and English in SAR for Saudi Arabia, with Arabic mandatory on required fields; English and Arabic in AED for the UAE; Turkish in TRY with KDV breakdown for Türkiye; Arabic-first in JOD for Jordan; English and Bahasa Malaysia in MYR for Malaysia. Retention periods are also handled per market — for example, six years under current KSA VAT law and the 10-year VUK obligation in Türkiye.