UAE E-Invoicing 2026–2027: The Complete Guide

The United Arab Emirates is replacing PDF, Word, scanned and emailed invoices with a single, government-verified digital standard. From 1 July 2026, e-invoicing becomes available on a voluntary basis, and mandatory rollout follows in phases through October 2027, based on annual revenue. Once a business is in scope, an invoice that is not issued in the prescribed structured XML format through an Accredited Service Provider (ASP) is not legally a tax invoice — regardless of what it looks like to a human reader.

This guide consolidates the current legal framework — including the May 2026 amendment that pushed back the Wave 1 service-provider deadline — into a single reference covering the timeline, scope, exclusions, penalties, data retention rules and a practical readiness checklist. It is built directly from the Ministry of Finance’s published Ministerial Decisions, Cabinet Decisions and eInvoicing Guidelines, and is updated as new resolutions are issued.

What Is an E-Invoice Under UAE Law?

According to the Ministry of Finance, an eInvoice is a structured invoice data set that is issued, exchanged electronically between a supplier and a buyer, and reported electronically to the Federal Tax Authority (FTA). Two conditions must both be true for a document to qualify:

• It is created and transmitted in a structured, machine-readable data format — not a document designed to be read by a human first.
• It moves electronically between the supplier’s and buyer’s systems, and a parallel data feed reaches the FTA in near real time.

The Ministry is explicit that unstructured formats — PDF, Word documents, images, scanned copies, and invoices sent as email attachments — do not meet the definition of an eInvoice, even if they contain all the same information a compliant invoice would.

The technical standard: PINT AE, in XML

UAE e-invoices must be produced as XML files that conform to PINT AE — the UAE’s national extension of the Peppol International (PINT) invoice specification. Using an international data dictionary is a deliberate design choice: it lets a UAE business exchange invoices with trading partners in any other Peppol-connected country using the same underlying data model, rather than a UAE-only format.

Why Is the UAE Introducing E-Invoicing?

The Ministry of Finance frames the programme around seven objectives, and the numbers behind them explain the urgency:

• Digitalisation — reduce manual intervention in tax reporting and make the fiscal ecosystem digitally native.
• Efficiency — the Ministry cites international experience showing e-invoicing can cut invoice processing costs by up to 66% once implemented correctly.
• Minimising VAT leakage — VAT has become a significant contributor to Emirates revenue since 2018, and real-time reporting closes both accidental and deliberate reporting gaps.
• Levelling the playing field for small business — the Ministry notes that 82% of UAE businesses are micro-businesses with annual turnover under AED 3 million, and a common national standard gives them access to the same automation as large enterprises.
• Faster cash flow — built-in validation at the point of issuance reduces invoice rejection rates and shortens the path to payment.
• Security — encrypted, authenticated data exchange reduces the risk of fraud, duplication and unauthorised alteration.
• Better policymaking — near real-time transaction data gives government agencies a live view of economic activity by sector.

The Legal Framework: Every Decision You Should Know

UAE e-invoicing did not arrive through a single law. It was built in layers between 2024 and 2026, and the layers keep being amended — most recently in May 2026. Treat this list as your primary citation set:

Instrument	What it covers
Federal Decree-Law No. 16 of 2024	Amends the VAT Decree-Law to create the legal basis for electronic invoicing.
Federal Decree-Law No. 17 of 2024	Amends the Tax Procedures Law to support e-invoicing enforcement and administration.
Ministerial Decision No. 64 of 2025	Sets eligibility criteria and the accreditation procedure for Accredited Service Providers (ASPs).
Ministerial Decision No. 243 of 2025	Establishes the Electronic Invoicing System itself — the operating rules of the model.
Ministerial Decision No. 244 of 2025	Governs the implementation of the Electronic Invoicing System — this is the decision containing the phased go-live dates.
Cabinet Decision No. 106 of 2025	Sets out violations and administrative penalties specific to e-invoicing non-compliance.
Ministerial Resolution No. 56 of 2026 (10 May 2026)	Amends Decision 64/2025 — updates ASP eligibility and accreditation procedures.
Ministerial Resolution No. 66 of 2026 (14 May 2026)	Amends Decision 244/2025 — extends the Wave 1 ASP-appointment deadline (see Section 5).

The Ministry has also published supporting technical guidance that sits underneath these legal instruments: the UAE Electronic Invoicing Guidelines (version 1.1, 1 June 2026), the UAE Electronic Invoice Mandatory Field Requirements (version 1.0, 23 February 2026), and a document on Considerations for Selecting an Accredited Service Provider. All are available on the official eInvoicing portal linked at the end of this guide.

How the System Works: The 5-Corner DCTCE Model

The UAE has adopted the Decentralised Continuous Transaction Control and Exchange (DCTCE) model, built on the Peppol 5-corner network. Instead of businesses sending invoice data directly to the tax authority, every invoice passes through two accredited intermediaries who validate it and report it in parallel. The five corners are:

• Corner 1 — the Supplier, who issues the invoice.
• Corner 2 — the Supplier’s Accredited Service Provider (ASP).
• Corner 3 — the Buyer’s Accredited Service Provider (ASP).
• Corner 4 — the Buyer, who receives the invoice.
• Corner 5 — the Federal Tax Authority (FTA), which receives Tax Data Documents (TDDs) from both ASPs.

Step-by-step exchange, as published by the Ministry of Finance

1. The supplier (Corner 1) submits eInvoice data, in an agreed format, to its ASP (Corner 2).
2. Corner 2 validates the data and converts it into the standard PINT AE XML format if it wasn’t already.
3. Corner 2 transmits the XML invoice to the buyer’s ASP (Corner 3).
4. In parallel, Corner 2 reports a Tax Data Document (TDD) to the FTA (Corner 5).
5. Once Corner 3 validates the invoice, it sends a Message Level Status (MLS) back to Corner 2.
6. Corner 3 delivers the invoice to the buyer (Corner 4) in an agreed format.
7. Corner 3 also reports its own TDD to Corner 5 — or, if validation failed, sends a negative MLS instead and does not report a TDD.
8. Corner 5 confirms successful TDD receipt with an MLS sent back to Corner 2.
9. Corner 2 forwards both the Corner 3 exchange status and the Corner 5 reporting status back to the supplier (Corner 1).
10. Corner 3 forwards the Corner 5 reporting status on to the buyer (Corner 4).

The practical implication: every invoice is validated twice (once by each ASP) and reported to the FTA twice (once by each side), which is what allows the system to run in near real time with batch submission also supported. Neither party can communicate directly with the FTA — Corner 1 never speaks to Corner 5 directly, and neither does Corner 4.

The business identifier: TIN, TRN and the Peppol address

Every participant is addressed on the network using a Tax Identification Number (TIN) — the first 10 digits of the business’s Tax Registration Number (TRN) — prefixed with the Peppol scheme identifier 0235. A business without a TRN must register with the FTA to obtain one before it can be reached on the network, even if it is not required to file VAT returns.

UAE E-Invoicing Timeline: Every Phase and Deadline

The rollout is staged by annual revenue rather than applying to everyone on a single date. This is the current, amended timeline as of the Ministerial Resolutions issued in May 2026 — note that the Wave 1 ASP-appointment deadline moved from its originally announced date of 31 July 2026 to 30 October 2026, while the 1 January 2027 mandatory go-live date was left unchanged.

Phase	Who it covers	ASP appointment by	Mandatory go-live
Pilot Programme	Selected Taxpayer Working Group members contacted directly by the Ministry (written agreement required to join)	N/A — by invitation	From 1 July 2026 (test environment)
Voluntary adoption	Any business, regardless of revenue or VAT registration status	Any time from 1 July 2026	Optional — no penalty exposure while voluntary
Wave 1 — large business	Annual revenue ≥ AED 50 million	30 October 2026 (extended from 31 July 2026 by Ministerial Resolution 66/2026)	1 January 2027
Wave 2 — remaining business	Annual revenue < AED 50 million (most SMEs)	31 March 2027	1 July 2027
Government entities	All in-scope federal and local government bodies	31 March 2027	1 October 2027

Why the voluntary phase is worth using even if you’re in Wave 2

Businesses that go live voluntarily are not exposed to the administrative penalties set out in Cabinet Decision 106 of 2025 — those only start to bite once a business has passed its mandatory implementation date. That makes the voluntary window a low-risk way to:

• Confirm your accounting or ERP system can produce every mandatory PINT AE field correctly, before it’s compulsory.
• Test the full round-trip with a chosen ASP, including error handling and rejection workflows.
• Surface master-data problems — mismatched TRNs, incomplete customer records, wrong tax categories — while there is still time to fix them without a penalty clock running.
• Give your finance, tax, IT and procurement teams hands-on experience before the deadline pressure hits.

6. Who Is In Scope?

The mandate is broader than VAT-registered companies. E-invoicing applies to any person conducting business in the UAE who is required to issue an invoice, regardless of VAT registration status, unless specifically excluded. In-scope transaction types are:

• Business-to-Business (B2B)
• Business-to-Government (B2G)
• Government-to-Business (G2B)
• Government-to-Government (G2G)

Business-to-Consumer (B2C) invoices are not in scope for this phase. If you sell mainly to individual end consumers, you are not required to e-invoice those transactions yet — although the Ministry has signalled this may be reviewed for a future phase.

Non-VAT-registered businesses

Because scope is tied to the act of issuing an invoice rather than to VAT registration, non-VAT-registered entities engaged in ongoing commercial activity are also captured. If you do not yet hold a Tax Registration Number, you will still need a Tax Identification Number to be reachable on the Peppol network, and should register with the FTA ahead of your applicable deadline.

Foreign businesses without a UAE establishment

A foreign business that has no place of residence in the UAE but is required to issue a UAE Tax Invoice under the VAT Decree-Law must also issue that invoice electronically. This is a detail multinational groups with UAE VAT registrations — but no local branch — frequently overlook.

VAT groups

Each member of a VAT group needs its own ASP endpoint and its own identification, even though the group files a single VAT return under one TRN. The group’s TRN is quoted on the invoice, but the endpoint used for delivery corresponds to the specific member entity that is actually transacting.

A transitional concession applies here: intra-group transactions — invoices exchanged between members of the same VAT group — benefit from a 24-month grace period starting 1 January 2027 and running to 31 December 2028. During that window, group members are not required to e-invoice transactions between themselves, though every other transaction they undertake remains fully in scope from their applicable go-live date.

7. What’s Excluded From the Mandate

A small number of activities sit outside the e-invoicing requirement, either permanently or for a defined transitional period:

• Sovereign activities carried out by government entities in a non-commercial capacity, where they are not competing with the private sector.
• Airline passenger services where an Electronic Ticket or Electronic Miscellaneous Document is already issued.
• Exempt financial services as defined under Article 42 of the VAT Executive Regulation — core banking and insurance activities that are VAT-exempt. Standard-rated financial services remain in scope, including those supplied to non-residents under zero-rated export treatment.
• Airline cargo services using an Airway Bill — excluded temporarily, for 24 months from the implementation date specified in Ministerial Decision 244 of 2025.

E-Invoice Categories and Tax Categories

Six document categories

The UAE framework defines six categories of electronic document, and every transaction must be mapped to one of them:

• Tax Invoice
• Self-billed Electronic Tax Invoice
• Tax Credit Note
• Self-billed Electronic Tax Credit Note
• Commercial Invoice — used where a transaction does not require a VAT Tax Invoice, for example supplies made by a non-VAT-registered entity, or exempt and out-of-scope supplies.
• Credit Note

There is no separate document type for a provisional invoice. Every provisional invoice must itself be issued as a compliant e-invoice, and any later adjustment is handled through an Electronic Credit Note or an additional Electronic Invoice — not through a revised version of the original.

Six tax categories at line level

Every line item on an e-invoice must carry one of the following tax categories:

• Standard Rate (5%) — general taxable supplies.
• Exempt from VAT — certain real estate, financial services and local passenger transport.
• Outside the scope of VAT — supplies where the place of supply falls outside the UAE.
• Reverse Charge — applies to specific B2B goods: electronic devices, precious metals and stones, crude and refined oil, natural gas, other pure hydrocarbons, and metal scrap, when supplied between VAT registrants.
• Zero Rated — exports, healthcare, education and other zero-rated categories under the VAT Decree-Law.
• Margin Scheme — second-hand goods, where VAT is calculated on the margin rather than the full sale price and the VAT amount field on the invoice is set to zero.

Note that the domestic reverse charge mechanism itself does not trigger a separate e-invoicing obligation for imports of the relevant goods or services under Article 48 of the VAT Decree-Law — the normal e-invoicing rules simply apply to the underlying supply.

Special Transaction Scenarios

The Ministry’s technical guidance sets out eight scenarios that require specific handling. These are the situations most likely to trip up a standard ERP configuration:

• Free zone transactions — where the ultimate consumer differs from the contracting party, the invoice must separately capture the “beneficiary” details alongside the buyer.
• Deemed supplies — reported using a fixed buyer endpoint (0235:9900000097); if no invoice is issued to a recipient, only Tax Data reporting to the FTA is required.
• Margin scheme supplies — VAT is not displayed as a separate amount; the VAT amount field must be populated with zero.
• Summary invoices — multiple transactions with the same customer over a period may be consolidated into one invoice; if the resulting payable total is negative, an Electronic Credit Note must be issued instead.
• Continuous supplies and retention payments — retention amounts require a separate commercial document showing the milestone calculation, while the e-invoice itself covers only the amount actually due at that point.
• Agent billing — the compliance obligation stays with the principal supplier, not the agent handling the transaction on their behalf.
• E-commerce — the underlying supplier remains responsible for the e-invoice being issued correctly, even where a marketplace or platform generates it on their behalf.
• Exports — where the overseas buyer has no Peppol participant identifier, a predefined export endpoint (0235:9900000099) is used instead.

Penalties for Non-Compliance

Two separate penalty regimes can apply once a business has passed its mandatory implementation date:

• E-invoicing-specific penalties under Cabinet Decision No. 106 of 2025, covering failures such as not appointing an ASP on time or not issuing invoices through the system as required.
• General VAT invoicing penalties under Cabinet Decision No. 40 of 2017, which continue to apply to the underlying obligation to issue a compliant Tax Invoice.

The headline penaltyA business that fails to appoint an ASP and implement e-invoicing by its applicable deadline is fined AED 5,000 per month for each month the failure continues, until it becomes compliant.No penalty applies to invoices issued during the voluntary phase, or to businesses ahead of their mandatory go-live date.

Data Retention Requirements

E-invoice data must be retained for the following periods, running from the end of the relevant period rather than the invoice date itself:

• 5 years after the end of the relevant Tax Period, for VAT-registered (Taxable) Persons.
• 5 years from the end of the calendar year of document creation, for other businesses.
• 7 years from the end of the calendar year of document creation, for real estate-related records.

An additional 4-year retention period applies on top of the above wherever there is an open dispute with the FTA, an ongoing audit, or a notified upcoming audit. Records may be stored on servers located outside the UAE, provided the business can retrieve and reproduce the full data set for the FTA on request.

How to Prepare: A 4-Step Readiness Plan

Step 1 — Understand your exposure

• Map your transaction types against the eight special scenarios in Section 9 and confirm which apply to you.
• Identify every mandatory PINT AE data field your current invoices are missing (see the Ministry’s Mandatory Field Requirements document).
• Confirm your annual revenue position to establish whether you fall into Wave 1 or Wave 2, and note your specific ASP-appointment and go-live dates.

Step 2 — Select and contract an Accredited Service Provider

• Review the current list of ASPs published on the Ministry of Finance website — this list is updated as new providers are accredited.
• Check technical fit: can your ERP or accounting system connect via the provider’s supported method (API, web portal, or SFTP/ETL)?
• Compare data-handling and lock-in risk — some vendors offer a self-hosted licence model, but you would still need to separately register and meet ASP-level obligations.
• Finalise the contract and begin onboarding through the EmaraTax portal. If you don’t yet have a TRN or TIN, register with the FTA first — every VAT group member needs its own.

Step 3 — Test end-to-end before you’re required to

• Agree the data hand-off format with your ASP and run full-cycle tests: issuance, validation, exchange, and Tax Data Document reporting.
• Confirm you receive — and can act on — both success and failure Message Level Status (MLS) notifications.
• Establish an error-resolution process and escalation hierarchy with your ASP before go-live, not after the first rejected invoice.

Step 4 — Go live and manage change

• Set a governance model for ongoing issues: who owns ASP relationship management, who resolves rejected invoices, who monitors compliance metrics.
• Notify your ASP promptly of structural changes — joining or leaving a VAT group, deregistering for VAT, or restructuring the legal entity — since these affect your Peppol endpoint.
• Build e-invoicing checks into your month-end VAT reconciliation, since Tax Data Documents will increasingly pre-populate parts of your VAT return.

Choosing an Accredited Service Provider (ASP)

Your ASP is not an optional add-on — it is the mandatory gateway through which every e-invoice you send or receive passes. A few practical points to weigh before signing:

• Coverage of both sides — the same ASP typically handles both sending and receiving on your behalf; you appoint only one ASP per business entity.
• Integration depth — does it connect natively with your existing ERP or accounting platform, or does it require custom middleware?
• Format flexibility — can it accept your data in whatever format your systems already produce and convert it to PINT AE XML, or must you re-engineer your invoicing process first?
• Support for special scenarios — free zone beneficiary fields, deemed supplies, margin scheme, and summary invoices are not all supported equally well across providers.
• Service levels around rejections — how fast are error notifications, and what tools does the provider give you to diagnose and fix a rejected invoice?

UAE vs Saudi Arabia E-Invoicing: How They Differ

Because Saudi Arabia’s ZATCA (Fatoora) e-invoicing mandate has been running since 2021, it’s a natural comparison point for groups operating across the GCC. The two systems share the same underlying motivation but differ in architecture:

Feature	UAE	Saudi Arabia (ZATCA / Fatoora)
Model	Decentralised (DCTCE) — Peppol 5-corner network	Centralised — invoices cleared or reported directly through ZATCA’s own platform
Data standard	PINT AE (Peppol International, UAE localisation), XML	ZATCA-specific XML/UBL 2.1 with QR code requirement
Intermediary	Mandatory Accredited Service Provider (ASP) on both sides	Direct integration with ZATCA, or via an approved solution provider
Scope at launch	B2B and B2G only; B2C excluded for now	B2B, B2G and B2C all in scope
Rollout basis	Phased by annual revenue (two waves plus government)	Phased by annual revenue across multiple earlier waves, largely complete

For a group with entities in both countries, the practical takeaway is that ASP selection, data mapping and internal training cannot simply be copied from one jurisdiction to the other — the exchange architecture is genuinely different, even though both rest on structured XML and real-time tax authority visibility.

Benefits of E-Invoicing for UAE Businesses

• Lower processing costs — the Ministry cites international precedent of up to a 66% reduction in per-invoice processing cost once implemented correctly.
• Faster payment cycles — built-in validation reduces the back-and-forth of rejected or disputed invoices, shortening the time between issuance and payment.
• Cleaner VAT returns — because tax data is reported to the FTA in near real time, certain VAT return fields can be pre-populated, and refund processing can move faster.
• Cross-border reach — because the UAE has adopted the international Peppol standard rather than a bespoke local format, UAE businesses can exchange invoices more easily with trading partners already on the Peppol network elsewhere.
• Fewer manual errors — structured validation at both ASPs catches mismatched VAT calculations, missing mandatory fields and incorrect tax categories before an invoice is treated as final.
• Audit readiness — a consistent digital trail, retained for the periods set out in Section 11, simplifies both internal reconciliation and FTA audits.

Common Challenges — and How to Get Ahead of Them

• Messy master data — customer and supplier records with outdated TRNs or incomplete addresses are the single most common cause of rejected invoices; clean this up before you connect to an ASP, not after.
• Underestimating ERP customisation — legacy or heavily customised accounting systems often need real development work to produce every mandatory PINT AE field correctly.
• Treating it as an IT-only project — successful rollouts involve finance, tax, procurement and accounts receivable from the start, since invoice content and approval workflows change, not just the transmission method.
• Leaving ASP selection too late — accreditation, contracting and technical onboarding all take time; starting during the voluntary window avoids a scramble against the Wave 1 or Wave 2 deadline.
• Assuming B2C is exempt forever — B2C is out of scope for now, but the Ministry has flagged it for potential future inclusion, so it’s worth monitoring rather than filing away as a permanent exclusion.

Glossary of Key Terms

Term	Meaning
ASP	Accredited Service Provider — a technology provider accredited by the Ministry of Finance to validate and transmit e-invoices on a business’s behalf.
DCTCE	Decentralised Continuous Transaction Control and Exchange — the UAE’s overall e-invoicing model.
Peppol	Pan-European Public Procurement On-Line network — the international standard and network the UAE model is built on.
PINT / PINT AE	Peppol International invoice specification; PINT AE is the UAE’s national localisation of it.
TDD	Tax Data Document — the invoice tax data reported by an ASP to the FTA.
MLS	Message Level Status — a confirmation message (success or failure) passed between corners in the exchange.
TRN	Tax Registration Number — issued to VAT-registered businesses.
TIN	Tax Identification Number — the first 10 digits of a business’s TRN, used to build its Peppol network address.
EmaraTax	The FTA’s online portal used for tax registration and ASP onboarding.

Frequently Asked Questions

Q: When does e-invoicing become mandatory in the UAE?

Mandatory implementation is phased by revenue. Businesses with annual revenue of AED 50 million or more must go live by 1 January 2027, after appointing an ASP by 30 October 2026. Businesses under AED 50 million must go live by 1 July 2027, after appointing an ASP by 31 March 2027. Government entities go live by 1 October 2027 under the same 31 March 2027 ASP-appointment deadline.

Q: Has the timeline changed recently?

Yes. Ministerial Resolution No. 66 of 2026, issued 14 May 2026, pushed the Wave 1 ASP-appointment deadline back from 31 July 2026 to 30 October 2026, while keeping the 1 January 2027 mandatory go-live date unchanged. Always check the Ministry of Finance’s eInvoicing portal for the current position before relying on a date you saw elsewhere.

Q: Does e-invoicing apply to B2C transactions?

Not at this stage. Only B2B, B2G, G2B and G2G transactions are in scope for the current phases. B2C invoicing may be reviewed for inclusion in a future phase, but no date has been set.

Q: Is a PDF invoice with an embedded XML file compliant?

No. The UAE framework does not accept a hybrid human-readable PDF format the way some other countries do. Only the structured XML transmitted through an ASP counts as the legal e-invoice — PDFs, images, scanned copies, Word documents and email attachments are all explicitly excluded from the definition.

Q: Do non-VAT-registered businesses need to comply?

Yes, if they issue invoices as part of ongoing commercial activity in the UAE. Scope is tied to issuing an invoice, not to VAT registration status. A non-VAT-registered business will still need a Tax Identification Number to be addressable on the network.

Q: What happens if we miss our deadline?

An administrative penalty of AED 5,000 per month applies for each month a business fails to appoint an ASP and implement e-invoicing as required, under Cabinet Decision No. 106 of 2025. General VAT invoicing penalties under Cabinet Decision No. 40 of 2017 can also apply to the underlying invoice.

Q: Can we build our own e-invoicing solution instead of using a vendor ASP?

Yes, provided your business itself becomes accredited as an ASP under the eligibility and accreditation procedure in Ministerial Decision 64 of 2025 (as amended by Ministerial Resolution 56 of 2026). This includes an ongoing obligation to keep pace with regulatory changes and to meet service-level commitments for the exchange, so it is a meaningful undertaking rather than a way to avoid ASP obligations altogether.

Q: How does e-invoicing interact with VAT groups?

Every VAT group member needs its own ASP endpoint and identification, even though the group shares one TRN and files a single VAT return. Intra-group transactions get a 24-month grace period from 1 January 2027 to 31 December 2028, during which they don’t need to be e-invoiced between group members — but all other transactions remain fully in scope.

Q: Can Corner 1 (the supplier) contact Corner 5 (the FTA) directly?

No. The 5-corner model requires every invoice to travel through both ASPs. There is no direct channel between the supplier and the FTA, or between the buyer and the FTA — reporting always happens through the accredited intermediaries.

Q: How long do we need to keep e-invoice records?

Generally 5 years from the end of the relevant Tax Period (VAT-registered persons) or from the end of the calendar year of creation (other businesses), extended to 7 years for real estate records. A dispute, audit, or audit notice from the FTA adds a further 4 years on top of the standard period.

19. Key Takeaways

• E-invoicing in the UAE means structured XML data exchanged through an Accredited Service Provider — PDFs and scanned invoices will no longer count as tax invoices once your phase applies.
• The voluntary window opened 1 July 2026 and carries no penalty risk — using it to test your systems is the single lowest-risk way to prepare.
• Wave 1 (≥ AED 50 million revenue) must appoint an ASP by 30 October 2026 and go live by 1 January 2027; Wave 2 and government entities follow through 2027.
• Non-compliance after your mandatory date costs AED 5,000 per month until resolved — appointing your ASP early removes that risk entirely.
• Because the legal framework is still being amended — most recently in May 2026 — always cross-check dates against the official Ministry of Finance eInvoicing portal before finalising an internal project plan.