If you sell through your own storefront, Amazon.ae, Noon, or social commerce channels, your UAE compliance picture is now more complex than a traditional retailer’s. UAE rules require e-commerce sellers above certain thresholds to report VAT by the Emirate where the customer receives the supply, and marketplaces themselves can be treated as the supplier for tax purposes. Layer the incoming FTA e-invoicing mandate on top, and every order, refund, and cross-border sale becomes a structured data event. This guide explains what emirate-level reporting requires, when platform liability shifts to the marketplace, and how to prepare your systems before the 2027 deadlines.
E-commerce transactions rarely follow one clean path. A single seller may push orders through their own website, one or two marketplaces, a POS in a warehouse showroom, and a social channel that routes payment through a payment gateway. Each channel carries its own customer data, its own tax logic, and its own record of where the buyer actually received the goods. Under UAE VAT and the incoming e-invoicing framework, that fragmentation is the risk.
The Federal Tax Authority (FTA) treats an “Electronic Commerce Medium” as any platform, application, store on social media, or online marketplace used to list, order, or deliver goods and services. The tax treatment then depends on two things: your annual e-commerce turnover, and the agency relationship between you and the platform.
Under Ministerial Decision No. 26 of 2023 and VAT Public Clarification VATP033, a taxable person whose e-commerce supplies exceed AED 100 million in a calendar year is classified as a “qualifying registrant.” Once you cross that threshold, standard-rated e-commerce supplies must be reported in Box 1 of the VAT return by the Emirate in which the customer receives the supply, not the Emirate of your fixed establishment.
That single change reshapes the data you need to capture on every order. You need reliable delivery address data at the invoice level, a rule to map each address to the correct Emirate, and an audit trail that ties the reported figure back to source transactions. Sellers who previously aggregated sales at the entity level now need transaction level Emirate tagging inside their ERP or accounting stack.
Smaller sellers below the AED 100 million threshold still report under the general rule, based on the Emirate of the fixed establishment most closely related to the supply. Non-resident sellers into the UAE have reported on an Emirate basis since VAT was introduced in 2018, and that obligation continues regardless of turnover.
In practice, the difficulty is not the calculation but the data. Marketplace order feeds, 3PL delivery confirmations, and payment gateway records often disagree on the customer address. Reconciling those sources into a single, defensible Emirate value per invoice is the operational core of the requirement.
Platform liability is the second issue often missed. Where the Electronic Commerce Medium operates as an undisclosed agent, the FTA treats the underlying seller as making a supply to the platform, and the platform as making the onward supply to the customer. In practice, the marketplace steps into the seller’s shoes for VAT purposes and must account for output tax on the full sale value.
For sellers, this changes invoice flow, reconciliation, and VAT return values. For platforms, it means the marketplace itself may qualify as a qualifying registrant based on the aggregate value of supplies flowing through it. Contract terms, storefront disclosures, and payment collection mechanics all feed into whether the platform is acting as a disclosed or undisclosed agent, and getting that wrong distorts both parties’ returns.
The UAE’s Electronic Invoicing System introduces a Peppol-based 5-corner model, in which structured invoices are exchanged through Accredited Service Providers (ASPs) in PINT-AE (Peppol International Invoice, UAE profile) format and reported to the FTA in near real time. Under Cabinet Decision No. 106 of 2025 and Ministerial Decisions No. 243 and 244 of 2025, the scope of e-invoicing B2B B2G UAE covers domestic business to business and business to government transactions, with a voluntary pilot from 1 July 2026 and mandatory go-live from 1 January 2027 for businesses with revenue of AED 50 million or more.
For e-commerce, three practical implications stand out:
If your platform currently emails PDF invoices, that flow is not compliant.
Preparing an e-commerce operation for both emirate-level reporting and e-invoicing is less about buying a tool and more about fixing data at the source. The work usually falls into four areas:
This is where advisory led support earns its place. Vendor neutral guidance on ASP selection, ERP integration design, and Emirate mapping logic prevents the two most common outcomes: buying a compliance tool that does not fit your channel mix, or building emirate reporting that cannot be audited back to the order.
E-commerce and marketplace sellers in the UAE now sit at the intersection of three moving parts: emirate-level VAT reporting for qualifying registrants, platform liability under the Electronic Commerce Medium rules, and structured e-invoicing through the Peppol network. Each has its own trigger, its own data requirement, and its own audit exposure. Treating them as one integrated compliance programme, rather than three separate projects, is what keeps returns clean, penalties off the table, and finance teams out of month end firefighting.
AA Technologies works with UAE e-commerce operators and marketplace platforms to design that programme from readiness assessment to ASP integration and post go-live operations. Book a compliance assessment with AA Tech to map your emirate reporting logic, review your platform agency position, and build an e-invoicing rollout plan tailored to your channel mix.
The FTA e-invoicing mandate primarily covers B2B and B2G transactions in structured PINT-AE format through an ASP. B2C consumer sales may use simplified invoices, but your systems still need to generate structured digital records that can be reported and retrieved on request. If your storefront also handles corporate or bulk orders, those B2B sales must move through the full e-invoicing flow once the mandate applies to you.
You become a qualifying registrant when your e-commerce supplies exceed AED 100 million in a calendar year. From the first tax period after crossing that threshold, standard-rated e-commerce supplies must be reported in the VAT return by the Emirate where the customer receives the supply. The obligation runs for 18 months or two years depending on when the threshold was first crossed, as set out in Public Clarification VATP033.
Liability depends on whether the marketplace acts as a disclosed or undisclosed agent. If the platform is an undisclosed agent, the FTA treats the seller as supplying goods to the platform, and the platform as supplying them to the customer, so the platform accounts for output VAT on the full sale. Review each marketplace contract closely, because the tax treatment follows the contractual and operational reality.
Emirate-level reporting applies to supplies received inside the UAE. For zero-rated exports to customers outside the UAE, you report the supply as a zero-rated export in the VAT return, with supporting export evidence retained on file. You do not allocate cross-border sales to an Emirate. Qualifying registrants should keep clear separation in their data between domestic supplies by Emirate and export supplies.
Non-compliance with the e-invoicing mandate carries penalties under Cabinet Decision No. 106 of 2025, and unstructured PDF invoices will not satisfy the requirement. The practical path is to run a readiness assessment now, select an ASP that supports your ERP, and map order, invoice, and credit note flows to the UAE data dictionary during the pilot phase in 2026. Testing early avoids emergency remediation before go-live.
