Bitrix24 E-Invoicing UAE 2026: Peppol PINT AE Setup and VAT Field Mapping

What the UAE 2026 E-Invoicing Mandate Actually Requires

UAE e-invoicing covers B2B and B2G invoices as structured XML documents on the Peppol PINT AE standard, with VAT declared in each document. A voluntary pilot started on 1 July 2026; the mandate arrives in phases, and businesses with revenue of AED 50 million or more must appoint an Accredited Service Provider (ASP) by 30 October 2026 and issue e-invoices by 1 January 2027.

The schedule comes from Ministerial Decision No. 244 of 2025, amended by Ministerial Resolution No. 66 of 2026. The first ASP deadline for large businesses was 31 July 2026; the Ministry of Finance moved it to 30 October 2026, and some guideline PDFs still show the old date. Both the issuer and the recipient of an invoice must appoint an ASP, the choice is registered in the FTA's EmaraTax portal, and B2C invoices are out of scope for now. A PDF or emailed invoice exported from a CRM is not an e-invoice under the UAE rules.

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:

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.

The UAE guidelines describe five corners, with Corner 5 being the FTA. The exchange network itself went live on 21 April 2026 as a four-corner model, with businesses selecting their ASP in EmaraTax, and the tax reporting corner was announced to follow. Check its status with your ASP before you design the reporting step.

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:

1. A sales manager creates or promotes a Deal in Bitrix24 to the "Invoice Ready" stage.
2. An automation rule (Robot) triggers invoice generation - either pushing data to an accounting system first, or directly to the ASP API.
3. The ASP signs, validates, and transmits the XML via Peppol to Corner 3/5.
4. The FTA-issued clearance token and document ID are written back into the Bitrix24 invoice card for audit trail purposes.
5. 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.

How do Bitrix24 invoice fields map 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.

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 Ministry of Finance publishes the list of pre-approved e-invoicing service providers: 61 companies as of 5 October 2026, including Zoho and Tally. Intuit (QuickBooks) and Xero are not on the list, so their users still need a separate ASP. No UAE e-invoicing (PINT AE) app was found in the Bitrix24 Market as of October 2026, so the connection is built through the provider's API. 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 recommended data flow.

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.

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:

1. Audit your Company card - confirm TRN is stored consistently. Create UF_TRN as a required string field on the Company entity. Set validation to accept 15-digit UAE TRN format.
2. 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.
3. Set currency to AED - in CRM → Settings → Currencies, ensure AED is the base currency. All money fields will inherit this.
4. 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.
5. 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.
6. 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_TOKEN and UF_FTA_DOC_ID. Add a follow-on automation that locks the invoice record.
7. 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.

How does Bitrix24 handle VAT calculation logic for UAE invoices?

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_AMOUNT per line and UF_TOTAL_VAT at 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.

Related: Bitrix24 Integration With Zoho Books, QuickBooks, Xero and Tally for UAE Companies

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, so a business with revenue of AED 50 million or more should appoint its ASP before 30 October 2026 and start the integration now to go live by 1 January 2027; smaller businesses have until 31 March 2027 to appoint an ASP.

A phased approach based on our project experience:

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.

Preparing for the mandate? ACP Group INT is a Bitrix24 Gold Partner in Dubai - see Bitrix24 implementation in the UAE and Middle East.