UAE B2G E-Invoicing: Complete Guide for Government Suppliers

If your business supplies goods or services to a UAE federal ministry, federal authority, or emirate-level government body, you're dealing with a compliance requirement that has its own separate timeline. Most e-invoicing coverage focuses on the Phase 1 and Phase 2 deadlines for businesses. Government entity transactions have a third wave: go-live on 1 October 2027, with an ASP appointment deadline of 31 March 2027.

That later date can feel reassuring. It isn't. B2G transactions carry some of the most demanding PINT AE configuration requirements, and suppliers who wait until early 2027 to start will find themselves rushing a process that typically takes three to six months once you factor in ERP mapping, ASP onboarding, and government-side readiness. This guide covers what B2G e-invoicing means in practice, who's in scope, how the five-corner model works for government buyers, and the steps your finance team needs to take now.

Key Takeaways- B2G transactions are fully in scope under Federal Decree-Laws 16 & 17 of 2024. Government entity go-live is 1 October 2027; suppliers must appoint an ASP by 31 March 2027 (UAE Ministry of Finance, Electronic Invoicing Guidelines V1.1, June 2026).- Non-compliance carries a penalty of AED 5,000 per month under Cabinet Decision No. 106 of 2025.- Government entities receive B2G invoices at Corner 4 via their own Buyer ASP; the FTA receives tax data at Corner 5.- The PINT AE standard covers 130+ fields across 16 scenarios, with 51 mandatory. B2G-specific fields include buyer entity type, government procurement reference numbers, and the correct transaction type flag.- A voluntary pilot runs penalty-free from 1 July 2026. It's the most practical way to test B2G flows before the mandatory deadline.

---

In 2026, the UAE's e-invoicing mandate distinguishes government entities as a distinct implementation phase. Under the UAE Electronic Invoicing Guidelines V1.1, published by the Ministry of Finance on 1 June 2026, government entities (including federal ministries, federal authorities, and emirate-level government bodies) must appoint an ASP by 31 March 2027 and go live on 1 October 2027 (UAE Ministry of Finance, Electronic Invoicing Guidelines V1.1, June 2026). That's three months after the Phase 2 general go-live.

Why a separate timeline? Government entities face unique procurement system complexity. Federal ministries and emirate-level bodies often run bespoke ERP and procurement platforms that require longer integration lead times than commercial software. The extra window gives public sector buyers time to configure their own Buyer ASP at Corner 4. Without that configuration, their suppliers can't actually deliver a valid B2G e-invoice to them. Both sides of the transaction need to be ready.

From the supplier side, this creates a nuance worth noting. A business with annual revenue of AED 50 million or more falls into Phase 1 for its B2B transactions, going live 1 January 2027. Those same B2G transactions to government buyers officially move to the Phase 3 go-live date of 1 October 2027, but the supplier's ASP appointment deadline stays at 30 October 2026. A Phase 1 supplier can't maintain two separate ASP setups; the ASP they appoint for B2B handles B2G as well, with configuration adjusted for government buyer routing.

The legal basis is Federal Decree-Laws 16 and 17 of 2024, which extended the e-invoicing obligation to all B2B and B2G transactions regardless of VAT registration status. B2C remains excluded. For the full mandate framework, the UAE e-invoicing guide covers scope, penalties, and the Peppol architecture.

---

Which Government Entities Are in Scope?

The UAE Electronic Invoicing Guidelines V1.1 confirmed that "government entities" in scope include federal ministries, federal authorities, and emirate-level government bodies (UAE Ministry of Finance, June 2026). The scope is broad. If you invoice any of the following, B2G e-invoicing applies to those transactions:

• Federal ministries: Ministry of Finance, Ministry of Health, Ministry of Education, Ministry of Economy, and all other federal departments
• Federal authorities: Federal Tax Authority, General Civil Aviation Authority, Securities and Commodities Authority, and equivalent bodies
• Emirate-level government bodies: Dubai Government entities, Abu Dhabi Government departments, and equivalent bodies in Sharjah, Ajman, Fujairah, Ras Al Khaimah, and Umm Al Quwain

One consequence that often surprises finance teams: a business below the AED 50 million revenue threshold falls into Phase 2 (go-live 1 July 2027) for its commercial B2B invoicing. But that same business's invoices to government entities carry a later effective go-live: 1 October 2027. In practice, a small supplier whose entire customer base is government entities has until 1 October 2027 for mandatory compliance, but still needs an ASP appointed by 31 March 2027. The ASP appointment deadline and the go-live deadline are not the same date, and confusing them is a common planning error.

Sovereign-capacity government activities (certain acts carried out under legislative, judicial, or executive authority) may fall outside the invoicing obligation. These exclusions are defined at the transaction level, not the entity level. A government body that also operates commercial activities (government-linked companies, public utilities with commercial billing) remains in scope for those commercial transactions. Confirming whether a specific government buyer's activity qualifies as sovereign-capacity work requires a qualified UAE tax adviser's review.

---

How Does the Five-Corner Model Work for B2G Transactions?

B2G e-invoicing follows the same Peppol five-corner architecture as B2B, but with a government entity at Corner 4 instead of a commercial buyer (KPMG, "UAE: Framework, Scope and Implementation of the Electronic Invoicing System", October 2025). Understanding who sits at each corner matters for configuring your ASP correctly.

Here's how the flow works for a supplier invoicing a UAE federal ministry:

• Corner 1 (Your business, Supplier): creates the PINT AE invoice in your accounting system or ERP, including all mandatory B2G-specific fields.
• Corner 2 (Your Supplier ASP): validates the invoice against the PINT AE schema, ensures all 51 mandatory fields are populated correctly, and transmits it onto the Peppol network.
• Corner 3 (The Peppol network): routes the validated invoice to the Buyer ASP at Corner 4 using the government entity's Peppol Participant Identifier.
• Corner 4 (The Government Entity's Buyer ASP): receives the invoice and delivers it into the government entity's procurement or finance system. The government entity itself never receives an invoice directly from you. It arrives via their ASP.
• Corner 5 (Federal Tax Authority - FTA): receives tax-relevant data from the Peppol network in near real time, independent of the buyer delivery flow.

The government entity's Peppol Participant Identifier follows the same format as any other participant: the prefix 0235 followed by their 10-digit Tax Identification Number. Your ASP must have this registered correctly as the routing address for that buyer, or the invoice will fail to deliver. Government entities with multiple departments may use separate TINs per department. Confirm the specific identifier with the procurement team at each entity before you go live.

For a deeper explanation of how the Peppol five-corner model works across all transaction types, see the Peppol network guide.

---

What PINT AE Fields Apply Specifically to B2G Invoices?

The PINT AE standard defines over 130 data fields across 16 invoice scenarios, with 51 mandatory across all transactions (Deloitte Middle East, "MoF Publishes PINT AE Specifications for E-Invoicing", 2026). B2G transactions don't use a separate schema, but several fields that are conditional in B2B contexts become essential or practically mandatory in B2G.

Buyer identification fields. In a B2B transaction, buyer fields are populated from commercial registration data. In a B2G transaction, the buyer entity type, legal name, and government-assigned identifier must reflect the specific ministry or authority. The Peppol Participant Identifier (0235 + 10-digit TIN) is how the network routes the invoice to the correct Buyer ASP. An incorrect TIN means the invoice is undeliverable. Confirming the exact TIN with the government entity's finance or procurement team before your first live invoice is non-negotiable.

Government procurement reference number. Most government entities operate under a formal purchase order or contract reference system. Including the relevant procurement reference in the invoice supports matching on the government entity's side and reduces payment delays caused by manual query-and-match processes. While not universally mandated in PINT AE as a standalone field, it typically maps to buyer reference or order reference fields in the standard. Your ASP can advise on the correct field placement.

Transaction type classification. PINT AE requires a transaction type code on every invoice. B2G transactions should carry the appropriate code for business-to-government supplies. Getting this wrong doesn't cause a schema validation failure, but it can cause reporting anomalies at the FTA's Corner 5 that may trigger follow-up queries.

In practice, B2G invoice field mapping takes longer to finalise than B2B. Government entities often have procurement teams that issue their own required formats: fields they expect in specific positions, reference codes with internal naming conventions. The PINT AE schema accommodates most of these as optional supplementary fields, but mapping them correctly requires a conversation between your finance team, your ASP, and the government entity's procurement contact. Build that dialogue into your onboarding timeline rather than assuming standard B2B configuration will cover it.

For the full field-by-field breakdown of mandatory and conditional PINT AE data points, the PINT AE data fields guide covers all 16 scenarios including government-specific mappings.

---

What Are the Deadlines for B2G E-Invoicing Suppliers?

The UAE Electronic Invoicing Guidelines V1.1 set out a three-wave rollout. Suppliers to government entities must plan against both their own supplier phase deadline and the government entity go-live date (UAE Ministry of Finance, June 2026).

Here's the practical implication for suppliers at different revenue levels:

If your revenue is AED 50 million or above (Phase 1): Your ASP appointment deadline is 30 October 2026. Your B2B invoicing goes live 1 January 2027. Your B2G invoicing to government entities follows the government entity timeline, with an effective go-live of 1 October 2027. You'll be running live B2B e-invoicing for nine months before B2G becomes mandatory. Use that window to test B2G flows with government buyers during the pilot period.

If your revenue is below AED 50 million (Phase 2): Your ASP appointment deadline is 31 March 2027, shared with government entities. Your B2B invoicing goes live 1 July 2027. Your B2G invoicing to government entities follows the 1 October 2027 date. You have the shortest testing window: three months between your B2B go-live and your B2G go-live.

A voluntary pilot runs from 1 July 2026 with no penalties for any transaction type until the relevant mandatory go-live date. Using the pilot to test B2G invoice flows with government buyers before October 2027 is the most effective way to catch Peppol Participant Identifier errors and field mapping problems without financial consequence.

---

How Do Suppliers Configure Their ASP for Government Buyers?

Selecting and configuring an ASP for B2G invoicing requires a few steps that don't apply to standard B2B configuration. As of June 2026, the Ministry of Finance lists 41 pre-approved ASPs on its e-invoicing portal (UAE Ministry of Finance, "E-Invoicing Portal", 2026). Not all of them have equal experience with government buyer routing, so evaluating B2G-specific capability should be part of your shortlisting process.

Step 1: Confirm government buyer Peppol Participant Identifiers. Contact the finance or procurement department of each government entity you invoice. Ask for their registered Peppol Participant Identifier (format: 0235 + 10-digit TIN). Without this, your ASP can't route invoices to them on the Peppol network.

Step 2: Verify your ASP has government buyer routing configured. Some ASPs operate primarily in the commercial B2B space. Ask explicitly whether they have existing connections to government Buyer ASPs at Corner 4. If a government entity's Buyer ASP isn't already in their network, ask how long onboarding a new Corner 4 connection takes.

Step 3: Map your B2G-specific data fields. Work with your ASP to confirm that buyer entity type, procurement reference numbers, and transaction type codes for government supplies are mapped correctly in your ERP or invoicing system. This is distinct from your B2B field mapping.

Step 4: Register your own Peppol Participant Identifier. Your identifier is 0235 followed by your 10-digit Tax Identification Number. Your ASP handles this registration as part of onboarding. Confirm it's complete before attempting any pilot transactions.

Step 5: Test B2G flows during the voluntary pilot. From 1 July 2026, you can send live invoices through the Peppol network without penalty. Use this to test a representative sample of B2G transactions with each government entity you supply.

Government buyer readiness is the variable most suppliers can't control. A supplier can complete every configuration step correctly and still experience delays if the government entity's Buyer ASP isn't yet operational. The 31 March 2027 ASP appointment deadline applies to government entities themselves, meaning some may not have a live Buyer ASP connection until Q2 or Q3 2027. Suppliers that begin conversations with government procurement contacts now, before that ASP onboarding rush begins, are in a materially stronger position.

For help evaluating and comparing the 41 pre-approved ASPs, including questions to ask about B2G capability, see the UAE ASP selection guide.

---

What Are the Penalties for B2G Non-Compliance?

The penalty regime for B2G e-invoicing is identical to B2B: it's set by Cabinet Decision No. 106 of 2025 and applies from the mandatory go-live date for each transaction type (UAE Ministry of Finance, "Cabinet Decision No. 106 of 2025", October 2025). The penalty structure includes:

• AED 5,000 per month for failure to implement e-invoicing or appoint an ASP
• AED 100 per invoice or credit note not transmitted through the Peppol network, capped at AED 5,000 per month
• AED 1,000 per day for failure to notify the FTA of a system malfunction
• AED 1,000 per day for failure to notify your ASP of changes to your registered data

For a Phase 1 supplier (revenue ≥ AED 50M) that fails to configure B2G by 1 October 2027, the monthly penalty starts immediately and compounds. Across a full year, that's AED 60,000 in base penalties before any per-invoice fines. The per-invoice penalty is particularly relevant for suppliers with high-volume, lower-value government contracts.

Is there a grace period for B2G? The voluntary pilot running from 1 July 2026 provides a penalty-free testing window for all transaction types, including B2G. After the mandatory B2G go-live on 1 October 2027, penalties apply from day one of non-compliance. There's no announced grace period specific to B2G beyond the pilot.

One important point for Phase 1 suppliers: your B2B invoicing must be compliant from 1 January 2027. Penalties for B2B non-compliance accumulate from that date. Don't treat the B2G deadline as a reason to delay overall ASP appointment. The 30 October 2026 deadline for Phase 1 suppliers covers both B2B and B2G configuration.

*This article is general information, not legal or tax advice. Confirm your specific obligations with a qualified UAE tax adviser.*

---

How Should Suppliers Prepare for B2G E-Invoicing Right Now?

The most common mistake we see with B2G preparation is treating it as an extension of B2B readiness. It isn't, quite. The technical infrastructure is identical, but the data collection, buyer confirmation, and testing steps require engagement with government procurement contacts who operate on different timelines and priorities than commercial buyers.

Here's a practical preparation sequence for suppliers to government entities:

Now (June to August 2026):

• Identify every government entity in your customer base: ministry, authority, or emirate-level body.
• Contact each entity's finance or procurement team and request their Peppol Participant Identifier (0235 + TIN).
• Begin ASP shortlisting using the MoF's pre-approved list of 41 providers. Ask specifically about B2G routing capability.

September to October 2026:

• Appoint your ASP (mandatory by 30 October 2026 for Phase 1 suppliers, 31 March 2027 for Phase 2).
• Register your Peppol Participant Identifier via your ASP.
• Begin ERP field mapping for both B2B and B2G invoice types.

From 1 July 2026 onwards (pilot period):

• Use the voluntary pilot to send test B2G invoices to government entities that have already configured their Buyer ASP.
• Catch Peppol Participant Identifier mismatches, field mapping errors, and procurement reference formatting issues before they become compliance failures.

January to September 2027:

• Phase 1 suppliers maintain live B2B compliance from 1 January 2027.
• Monitor government entity readiness as they approach their 31 March 2027 ASP appointment deadline.
• Complete full B2G testing before the 1 October 2027 mandatory go-live.

The UAE e-invoicing readiness checklist covers all 20 implementation steps from system audit through go-live testing, applicable to both B2B and B2G flows. It's a useful complement to the B2G-specific steps above.

---

---

Sources

• UAE Ministry of Finance, "UAE Electronic Invoicing Guidelines V1.1," 1 June 2026, retrieved 2026-06-22, https://www.mof.gov.ae/en/resourcesAndBudget/pages/e-invoicing.aspx
• UAE Ministry of Finance, "Cabinet Decision No. 106 of 2025 on Administrative Penalties for Non-Compliance with the Electronic Invoicing System," retrieved 2026-06-22, https://mof.gov.ae/en/news/ministry-of-finance-announces-the-issuance-of-cabinet-resolution-on-administrative-fines-related-to-electronic-invoicing-system/
• UAE Ministry of Finance, "Federal Decree-Law No. 17 of 2024 (amending Federal Decree-Law No. 28 of 2022 on Tax Procedures) and Federal Decree-Law No. 16 of 2024 (amending Federal Decree-Law No. 8 of 2017 on VAT)," retrieved 2026-06-22, https://mof.gov.ae/en/news/issuance-of-amendments-to-federal-decree-law-on-tax-procedures-and-federal-decree-law-on-value-added-tax-to-support-the-einvoicing-system/
• UAE Ministry of Finance, "E-Invoicing Pre-Approved ASP Portal," retrieved 2026-06-22, https://www.mof.gov.ae/en/ourpoliciesandinitiatives/Pages/eInvoicing.aspx
• KPMG, "UAE: Framework, Scope and Implementation of the Electronic Invoicing System," October 2025, retrieved 2026-06-22, https://kpmg.com/us/en/taxnewsflash/news/2025/10/uae-framework-scope-implementation-e-invoicing-system.html
• Deloitte Middle East, "MoF Publishes PINT AE Specifications for E-Invoicing," 2026, retrieved 2026-06-22, https://www.deloitte.com/middle-east/en/services/tax/perspectives/mof-publishes-pint-ae-specifications-for-e-invoicing.html
• Deloitte Middle East, "Release of UAE E-Invoicing Legislation," September 2025, retrieved 2026-06-22, https://www.deloitte.com/middle-east/en/services/tax/perspectives/release-of-uae-einvoicing-legislation.html
• EY Global, "UAE Formally Announces Introduction of E-Invoicing," retrieved 2026-06-22, https://www.ey.com/en_gl/technical/tax-alerts/uae-formally-announces-introduction-of-e-invoicing-launches-e-invoicing-portal-and-amends-vat-law-provisions
• KPMG UAE, "Implementation of the Electronic Invoicing System in the UAE," retrieved 2026-06-22, https://kpmg.com/ae/en/insights/tax-insights/implementation-of-the-electronic-invoicing-system-in-the-uae.html