For decades, specialized industries across the United Arab Emirates have relied heavily on self billing arrangements. In sectors like scrap metal recycling, agricultural supply, independent contracting, and heavy manufacturing, it is often more practical for the corporate buyer to determine the final value of the goods received. Instead of waiting for the supplier to calculate the totals and send a bill, the buyer officially generates the tax invoice on behalf of the supplier.
As the Federal Tax Authority accelerates its new digital tax rollout, chief financial officers are urgently asking: does the continuous transaction control model eliminate the ability to use self billing? The short answer is no. You can absolutely still operate under a self billing agreement. However, the exact technical execution of this process changes drastically under the new mandate. Let us explore how self billing survives in the digital era and exactly how your enterprise resource planning system must adapt.
The Legal Framework for Buyer-Generated Invoices
To understand how this operates digitally, we must look at the Value Added Tax Executive Regulations. Under Article 59, the Federal Tax Authority legally permits a registered buyer to issue a tax invoice on behalf of a registered supplier. This requires a formal, written agreement stating the supplier will not issue their own tax invoices for these specific transactions.
Even though the buyer presses the button to generate the invoice, the legal liability for the Value Added Tax accuracy remains entirely with the supplier. In the traditional paper era, the buyer would print a PDF clearly labeled as a self billed invoice and email a copy to the supplier for their accounting records. Under the incoming UAE E-invoicing mandate, that manual PDF exchange is completely banned. The buyer must now generate the transaction natively within their enterprise resource planning software, strictly format the data as a cryptographic PINT-AE XML file, and transmit it directly through the central Peppol network.
Document Type Code 389 and Technical Routing
When your corporate buyer generates an invoice on your behalf, they cannot process it like a standard outbound sales invoice. Doing so would incorrectly log the revenue in their own ledger. Instead, the PINT-AE data dictionary provides specialized Document Type Codes to handle this exact scenario.
While a standard UAE tax invoice uses the document type code 380, a self billed invoice must explicitly use the document type code 389. Similarly, if the buyer needs to adjust a past self billed transaction, they must issue a self billed credit note using type code 261, rather than the standard 381 credit note code.
This specific type code 389 signals to the central government gateway that the roles are legally reversed. The buyer acts as the physical transmitter of the XML file, but the supplier remains the legal seller. The buyer’s Accredited Service Provider extracts the mandatory Tax Data Document and reports the revenue event directly to the Federal Tax Authority under the supplier’s Tax Registration Number. The network then securely routes the full XML payload back to the supplier’s endpoint, allowing the supplier to ingest the final financial data directly into their own accounting backend.
The Operational Risks of Decentralized Billing
While legally permitted, self billing under a continuous transaction control model introduces massive operational risks for the supplier. When you allow a buyer to generate a type code 389 XML file on your behalf, that file instantly hits the Federal Tax Authority ledgers. If the buyer calculates the Value Added Tax incorrectly, or applies the wrong zero rated category codes, the government algorithms will register a tax discrepancy under your corporate profile.
Because you remain legally liable for the accuracy of these files, you cannot simply trust that the buyer configured their software correctly. You must possess the technical architecture to instantly receive the inbound PINT-AE XML files from the buyer, decrypt them, and automatically reconcile them against your internal delivery notes and purchase orders.
Secure Your Architecture with Cherrie Business Solutions
Managing complex XML type codes and inbound network routing requires highly intelligent financial software. Disconnected web portals cannot automatically ingest inbound self billed XML files or reconcile them against your ledger.
As an authorized Microsoft Dynamics 365 implementation partner, Cherrie Business Solutions delivers a highly robust, native UAE E-invoicing solution engineered perfectly for complex billing scenarios. Our specialized architecture integrates directly inside your Microsoft Dynamics 365 Finance or Business Central platform. Whether you are a buyer needing to automate type code 389 self billed XML generation, or a supplier needing to securely receive and audit inbound self billed files, our software handles the entire cryptographic exchange flawlessly.
By upgrading your financial systems with our native e-invoicing solution today, you can confidently maintain your specialized billing agreements while ensuring absolute digital tax compliance with the Federal Tax Authority.
