One of the most practical – yet often overlooked – parts of the UAE eInvoicing guidelines is the section on special scenarios. These are specific transaction types that have their own rules, additional mandatory fields, or unique handling requirements. Get them wrong and your invoice will either fail validation or be incorrectly reported to the FTA.

The good news is there are only 8 scenarios to understand. And once you know which ones apply to your business, you can prepare your ERP and processes accordingly – well before your go-live date.

Let’s go through each one clearly.

Why Scenarios Matter

Not every invoice is the same. A standard B2B sale between two mainland UAE companies is straightforward. But what about a sale to a Free Zone company? Or a recurring monthly retainer? Or goods exported to a client in Europe? Each of these situations has specific requirements that must be reflected in the Electronic Invoice – using the 8-flag transaction type code built into every invoice.

Think of this flag system like a checklist on every invoice: for each of the 8 scenarios, you mark “1” if it applies and “0” if it doesn’t. Getting these flags right is non-negotiable for compliance.

Scenario 1: Free Zone Transactions

Who it applies to: Any transaction involving a Free Zone entity – whether as the supplier, buyer, or beneficiary – or where the supply itself takes place within or from a Free Zone.

What’s different: When your customer is a Free Zone entity, you may need to record a “Beneficiary” on the invoice – in addition to the customer details. In most standard B2B transactions, the customer and beneficiary will be the same legal entity. But where the ultimate user of the goods or services is different from the contracting party, that end user must be identified separately as the beneficiary.

Practical example: A UAE mainland company supplies IT services to a JAFZA-registered entity, which uses the services for an end client within the Free Zone. The end client must be recorded as the beneficiary.

Action point: Review your customer base for Free Zone registrations and update your ERP to capture beneficiary data where applicable.

Scenario 2: Deemed Supply

Who it applies to: VAT-registered businesses making supplies that are treated as taxable under UAE VAT law – even though no payment is received. This includes free-of-charge supplies, gifts above the prescribed threshold, and private use of business assets or inventory.

What’s different: Two important rules apply here:

• The buyer’s electronic address must always be set to a predefined value: 0235:9900000097 – regardless of who the supplier is.
• In cases where no invoice is actually issued to a recipient (because there is no real “buyer”), there is no exchange of Electronic Invoices between parties. Only the supplier’s ASP reports to the FTA.

Practical example: A company gives promotional gifts worth above the VAT threshold to customers at an event. This is a deemed supply and requires an Electronic Invoice – even though no money changed hands.

Action point: Identify all deemed supply scenarios in your business and ensure your ERP can flag and handle these correctly.

Scenario 3: Margin Scheme

Who it applies to: Businesses that calculate VAT only on their profit margin – the difference between the purchase price and the resale price – rather than on the full selling price. This is common in sectors like used car dealerships and art galleries.

What’s different: Even though the PINT-AE standard mandates inclusion of VAT information on the invoice, the VAT amount for margin scheme transactions should be displayed as “0” – because the VAT is embedded in the margin and not separately charged.

Practical example: A used car dealer buys a vehicle from a private individual (non-VAT registered) for AED 40,000 and sells it for AED 50,000. VAT is calculated only on the AED 10,000 margin – and the invoice shows VAT amount as “0.”

Action point: If you operate under a margin scheme for any product category, ensure your invoicing system applies the “0” VAT display rule and correctly flags this scenario.

Scenario 4: Summary Invoice

Who it applies to: Businesses that consolidate multiple transactions with the same customer over a defined period into a single invoice. This is common in banking, financial services, and businesses with high-frequency recurring transactions.

What’s different: Certain fields at the document level can be zero or a positive number to pass Peppol validation. However, there is an important rule: if the total payable amount is negative (i.e. a credit scenario), the transaction must be documented using an Electronic Credit Note – not a summary invoice.

Practical example: A bank makes 35 separate service charges to a corporate customer during October and issues one consolidated monthly Tax Invoice covering all charges.

Action point: If you issue summary invoices today, review your process to ensure credit scenarios are handled with Credit Notes – not negative summary invoices.

Scenario 5: Continuous Supply

Who it applies to: Businesses providing ongoing or recurring services – such as monthly retainers, subscription services, or milestone-based contracts in construction and consulting.

What’s different: For contracts involving retention payments, the calculation of milestone amounts and retention deductions must be documented in a separate commercial document – these details should not appear on the Electronic Invoice itself. When the retention amount is finally due for payment, a separate Electronic Tax Invoice should be issued with the applicable VAT.

Practical example: A consulting firm provides advisory services on a monthly retainer, invoicing each month. A construction company invoices based on project milestones with a 10% retention – the retention calculation goes in a separate commercial document, while the invoiced amount appears cleanly on the Electronic Invoice.

Action point: If you handle retention contracts, update your invoicing workflow to separate retention calculations from Electronic Invoices.

Scenario 6: Agent Billing

Who it applies to: Situations where a disclosed agent raises invoices on behalf of a principal supplier. Note: this scenario does not apply to undisclosed agents.

What’s different: Even when an agent issues the invoice, the responsibility to comply with eInvoicing obligations remains with the supplier – not the agent. The agent acts on the supplier’s behalf, but the liability for correct issuance stays with the principal.

Practical example: An insurance broker collects premiums from clients and issues invoices on behalf of a VAT-registered insurance company. The insurance company (principal) remains responsible for eInvoicing compliance – not the broker.

Action point: If you use disclosed agents for billing, ensure your agency agreements clearly define e-invoicing responsibilities and that your ASP setup reflects the correct supplier identity on every invoice.

Scenario 7: Supply Through E-Commerce

Who it applies to: Businesses making electronic commerce supplies through an electronic commerce medium – including online retailers, marketplace sellers, and digital service providers.

What’s different: Similar to agent billing, if an e-commerce platform issues invoices on behalf of a seller, the compliance responsibility remains with the original supplier – not the platform.

Practical example: A UAE-based retailer sells products through an e-commerce marketplace. The platform generates the invoice on the seller’s behalf. The seller is still responsible for ensuring the invoice meets eInvoicing requirements.

Action point: If you sell through third-party platforms, understand whether the platform will issue compliant Electronic Invoices on your behalf – and get contractual clarity on who carries the compliance risk.

Scenario 8: Exports

Who it applies to: Any business supplying goods or services to customers outside the UAE.

What’s different: Export transactions have two specific rules:

• The Tax Invoice for VAT purposes must be issued as an Electronic Invoice — and the same may be submitted to Customs.
• If the overseas buyer does not have a Peppol ID, the supplier must use a predefined endpoint: 0235:9900000099 as the buyer’s electronic address on the invoice.

Practical example: A UAE wholesaler exports cosmetic to a retailer in Saudi Arabia. The Saudi buyer doesn’t have a UAE Peppol ID, so the supplier uses the predefined export endpoint on the Electronic Invoice.

Action point: Identify your export customers. For those without a UAE Peppol ID, ensure your ERP defaults to the correct predefined endpoint automatically.

Can Multiple Scenarios Apply to One Invoice?

Absolutely yes – and this is where it gets interesting. A single transaction can trigger multiple scenarios simultaneously. For example, a supply to a Free Zone customer that is also an export transaction would require both the Free Zone flag and the Export flag to be set to “1.”

When multiple scenarios apply, the specific requirements for each applicable scenario must all be included within the same Electronic Invoice. Your ERP and ASP need to be able to handle scenario combinations correctly.

Quick Reference: 8 Scenarios at a Glance

FAQs

1) How do I know which scenarios apply to my business?
Start by mapping your transaction types – who are your customers, where are they located, how are services delivered, and are there any special pricing or supply arrangements? Most businesses will identify their applicable scenarios quickly once they go through this exercise. Your tax advisor or ASP can also assist.

2) What happens if I set the wrong scenario flag?
The invoice may pass technical validation but be incorrectly reported to the FTA – leading to compliance issues, potential penalties, or queries during an audit. Accurate scenario flagging is just as important as accurate invoice values.

3) We have a mix of Free Zone and mainland customers. Do we need two different invoice templates?
Not necessarily two templates, but your ERP needs to be flexible enough to trigger the Free Zone flag and beneficiary field automatically based on customer classification. Good master data setup is key here.

4) We export to multiple countries. Do all our export customers need Peppol IDs?
Overseas buyers won’t typically have UAE Peppol IDs. For all such buyers, you use the predefined export endpoint (0235:9900000099) by default. Only UAE-registered businesses will have their own Peppol participant identifiers.

5) Our business has continuous supply contracts with retention clauses. What do we need to change?
You need to separate the retention calculation documentation from the Electronic Invoice. Practically, this means issuing a commercial supporting document for the retention schedule and a clean Electronic Invoice for the invoiced amount – your finance and billing teams need to agree on this workflow before go-live.