What the UAE 2026 E-Invoicing Mandate Actually Requires
The UAE Federal Tax Authority (FTA) mandates that from July 2026, taxable businesses must exchange invoices as structured XML documents through a 5-corner Peppol network, with VAT at 5% explicitly declared in each document.
The mandate follows the internationally recognised Peppol PINT AE (Peppol International Invoice — Arab Emirates) specification. Unlike PDF invoices sent by email, PINT AE documents are machine-readable XML files transmitted via accredited access points. The key structural elements of the framework are:
| Corner | Role | Who operates it |
|---|---|---|
| Corner 1 | Seller's internal system (ERP/CRM) | Your Bitrix24 + accounting system |
| Corner 2 | Seller's Peppol Access Point (AP) | Your accredited service provider (ASP) |
| Corner 3 | Buyer's Access Point | Buyer's ASP |
| Corner 4 | Buyer's internal system | Buyer's ERP/accounting |
| Corner 5 | FTA Tax Authority platform | UAE FTA |
Every invoice must carry a valid Tax Registration Number (TRN), line-level VAT amounts at the applicable rate (standard rate 5%, or zero/exempt where relevant), and a Peppol document ID traceable back to the seller's system. Businesses already registered for VAT should treat this as a hard infrastructure deadline, not a software upgrade.
How Bitrix24 Fits Into the 5-Corner Model
Bitrix24 sits at Corner 1: it is where the commercial transaction originates — deal terms, line items, pricing, and customer legal data — and it must feed all of that cleanly into your ASP connector before a compliant XML document can be generated.
Out of the box, Bitrix24 stores invoices as either native Invoice entities or as Smart Process elements. In integration-heavy deployments, the invoice smart process acts as a staging record: it holds the draft, triggers the outbound flow to the accredited provider, and receives back the FTA-assigned document reference. Based on our implementation experience, the cleanest architecture works like this:
- A sales manager creates or promotes a Deal in Bitrix24 to the "Invoice Ready" stage.
- An automation rule (Robot) triggers invoice generation — either pushing data to an accounting system first, or directly to the ASP API.
- The ASP signs, validates, and transmits the XML via Peppol to Corner 3/5.
- The FTA-issued clearance token and document ID are written back into the Bitrix24 invoice card for audit trail purposes.
- The invoice status field updates automatically — locking the record from further editing, consistent with the principle that a cleared e-invoice is immutable.
This mirrors how mature Bitrix24–accounting integrations handle invoice locking: once payment or clearance is confirmed from the authoritative system, the CRM record becomes read-only, and all subsequent changes flow inbound only.
Mapping Bitrix24 Invoice Fields to PINT AE Requirements
Every mandatory PINT AE field must have a permanent home in your Bitrix24 invoice card — either as a native field or a custom UF_ field — before you connect an accredited provider, because the ASP connector reads directly from these field codes.
The table below maps the PINT AE mandatory elements to their Bitrix24 equivalents. Fields marked custom do not exist by default and must be created in CRM settings.
| PINT AE Field | Bitrix24 Field / Location | Field Type | Notes |
|---|---|---|---|
| Invoice number | ACCOUNT_NUMBER (Invoice) or smart process TITLE |
String | Must be unique; ideally assigned by the accounting system, not manually |
| Invoice issue date | DATE_BILL / DATE |
Date | Auto-populated on stage transition |
| Seller TRN | Custom UF_TRN_SELLER on Company card |
String | Pulled from the seller's legal entity profile |
| Buyer TRN | Custom UF_TRN_BUYER on Contact/Company |
String | Required for B2B; blank for B2C |
| Buyer legal name | COMPANY_ID → Company TITLE |
Linked entity | Must match FTA-registered name exactly |
| Line item description | Products table NAME |
System | Sync from catalogue |
| Unit price (AED) | Products table PRICE |
Money | Currency must be set to AED |
| Line VAT rate (%) | Products table custom tax field or UF_VAT_RATE |
List/Number | Values: 5, 0, exempt |
| Line VAT amount (AED) | Calculated or UF_VAT_AMOUNT |
Money | Can be computed by automation |
| Total excl. VAT | OPPORTUNITY |
Money | Standard deal/invoice amount |
| Total VAT (AED) | Custom UF_TOTAL_VAT |
Money | Sum of all line VAT amounts |
| Total incl. VAT | Custom UF_TOTAL_INC_VAT |
Money | Displayed on invoice template |
| Payment terms | Custom UF_PAYMENT_TERMS |
String/List | e.g. Net 30 |
| ASP clearance token | Custom UF_PEPPOL_TOKEN |
String | Written back by ASP after clearance |
| FTA document ID | Custom UF_FTA_DOC_ID |
String | Written back by ASP; triggers lock |
A practical rule: any field that the ASP connector will read must have its UF_ code documented in your integration specification before development begins. Renaming fields after the connector is built causes mapping breaks that are time-consuming to fix.
Connecting an Accredited Service Provider (ASP)
Bitrix24 does not transmit Peppol messages natively — you must connect an FTA-accredited service provider via API or middleware, and the integration architecture determines whether compliance is reliable or fragile.
The UAE FTA publishes a list of accredited Peppol service providers. When evaluating an ASP, the key technical criteria from a Bitrix24 integration perspective are:
- REST API availability — the ASP must expose endpoints for invoice submission, status polling, and clearance token retrieval that your Bitrix24 connector can call.
- Webhook support — the ASP should be able to push status updates back to Bitrix24 (clearance confirmed, rejected, error) rather than requiring your system to poll.
- PINT AE XML generation — either the ASP generates the XML from a JSON payload you send, or you generate it on your side. Generating on your side gives more control but adds complexity.
- Sandbox environment — mandatory for testing field mapping before go-live.
The connection itself is built as a Bitrix24 Smart Process automation or a dedicated middleware layer. The diagram below illustrates the recommended data flow.
The diagram shows how a Bitrix24 Deal transitions to an Invoice smart process, which pushes structured data to the ASP. The ASP generates and transmits the PINT AE XML to the FTA platform and the buyer's access point, then returns the clearance token to Bitrix24.
flowchart LR
DEAL[Bitrix24 Deal] -->|Stage: Invoice Ready| INV[Invoice Smart Process]
INV -->|JSON payload\nvia REST API| ASP[Accredited Service Provider]
ASP -->|PINT AE XML| FTA[FTA Platform\nCorner 5]
ASP -->|PINT AE XML| BUYER_AP[Buyer Access Point\nCorner 3]
ASP -->|Clearance token\n+ FTA Doc ID| INV
INV -->|Lock record\nUpdate status| DEAL
For companies already running a Bitrix24–accounting system integration (a common setup in the UAE manufacturing, trading, and real estate sectors), the most efficient architecture routes invoice data through the accounting system first: Bitrix24 triggers the accounting system to create the invoice, the accounting system calls the ASP, and the clearance token flows back through the same chain. This avoids duplicating VAT calculation logic.
Custom Fields Setup: Step-by-Step
Setting up the required custom fields before connecting your ASP takes roughly half a day for an experienced Bitrix24 administrator, but skipping this step makes compliant integration impossible.
Follow this sequence:
- Audit your Company card — confirm TRN is stored consistently. Create
UF_TRNas a required string field on the Company entity. Set validation to accept 15-digit UAE TRN format. - Extend the Invoice entity (or Smart Process) — add all custom
UF_fields from the mapping table above. Use the CRM field editor in Bitrix24 settings. - Set currency to AED — in CRM → Settings → Currencies, ensure AED is the base currency. All money fields will inherit this.
- Configure VAT rates in the product catalogue — add a "VAT Rate" attribute to products with list values: 5% Standard, 0% Zero-rated, Exempt. This allows line-level VAT to be correct per product, not just per invoice.
- Build the automation — create a Robot on the Invoice smart process that fires when status moves to "Submit to ASP." The Robot calls your middleware or ASP endpoint via outbound webhook, passing the field codes documented in step 2.
- Configure the write-back — set up an inbound webhook handler (or use a Bitrix24 app) that receives the clearance token from the ASP and writes it to
UF_PEPPOL_TOKENandUF_FTA_DOC_ID. Add a follow-on automation that locks the invoice record. - Test in sandbox — submit at least 10 test invoices covering: standard VAT, zero-rated, credit note, and partial payment scenarios before live submission.
For teams setting up Bitrix24 from scratch or migrating from another CRM, the compliance field architecture should be designed at the onboarding stage — the Bitrix24 onboarding questionnaire is a good starting point to capture all legal entity and tax data requirements before implementation begins.
VAT Calculation Logic Inside Bitrix24
Bitrix24's native tax engine can handle UAE VAT at 5% per line item, but for PINT AE compliance you need the calculated amounts stored in discrete fields — not just displayed on a template — so the ASP connector can read exact figures.
The key principle: the ASP will read field values, not rendered PDF output. This means:
- Do not rely on invoice PDF templates to "calculate" VAT visually. The XML payload must contain explicit numeric values.
- Use Bitrix24 automation (Business Process or Robot with calculated fields) to write
UF_VAT_AMOUNTper line andUF_TOTAL_VATat header level when the invoice is finalised. - If your product catalogue has mixed VAT rates (5% on goods, 0% on certain exported services), the line-level VAT field on each product must drive the calculation, not a single header-level rate.
- For credit notes (required under PINT AE when correcting a cleared invoice), create a separate Smart Process stage or entity type. Credit notes reference the original FTA document ID — stored in
UF_FTA_DOC_ID— so the link must be preserved in your data model.
Companies in industries with complex VAT treatment — such as real estate in the UAE or manufacturing — should map their VAT categories explicitly at the product catalogue level during setup, not as an afterthought.
Data Sovereignty and Hosting Considerations
If your business has data localisation requirements — common in UAE financial services and government-adjacent sectors — a self-hosted Bitrix24 deployment gives you full control over where invoice data and TRN records reside before they leave your environment to the ASP.
Cloud Bitrix24 (bitrix24.com) stores data on Bitrix's infrastructure. For most UAE SMBs this is acceptable, but regulated entities should check whether invoice data at rest must remain within UAE borders. A self-hosted deployment on UAE-based infrastructure (or a UAE region of a major cloud provider) resolves this cleanly. See the self-hosted vs cloud TCO analysis for a full cost comparison across a 3-year horizon.
Key points for the compliance architecture decision:
- Cloud Bitrix24 — faster to set up, ASP connector is built as a standard REST integration. Data leaves your environment to Bitrix24 servers and then to the ASP.
- Self-hosted Bitrix24 — all invoice data stays on your servers until the ASP API call. The integration architecture is identical but you control the network path. Relevant for entities handling sensitive financial data alongside invoicing.
- In either case, the ASP itself is an external party that receives your invoice data — review the ASP's data processing terms independently of your Bitrix24 hosting decision.
Implementation Timeline and What to Do Now
A realistic Bitrix24 e-invoicing compliance project — from field audit to live ASP connection — takes 6 to 10 weeks, meaning teams targeting the July 2026 mandate should begin no later than Q1 2026.
A phased approach based on our project experience:
| Phase | Duration | Key deliverables |
|---|---|---|
| Discovery & field audit | 1–2 weeks | TRN data quality check, field gap analysis, ASP selection |
| Bitrix24 field configuration | 1 week | All custom UF_ fields created, VAT catalogue updated, AED currency confirmed |
| ASP connector development | 2–3 weeks | Outbound webhook / REST integration, XML mapping, error handling |
| Write-back & locking logic | 1 week | Clearance token storage, record locking automation |
| Sandbox testing | 1–2 weeks | 10+ test scenarios, edge cases (credit notes, zero-rated, partial payment) |
| Go-live & monitoring | 1 week | Live submission, ASP dashboard monitoring, staff training |
If your Bitrix24 is not yet fully configured for UAE operations — or if you are mid-migration from another platform — factor in the base implementation cost and timeline before scoping the e-invoicing layer on top.
Companies in IT and software services with subscription billing models should pay particular attention to the recurring invoice and credit note flows — see how Bitrix24 for IT companies handles project-based billing, which shares structural similarities with the smart process architecture needed here.