Daftra Integration
Daftra UAE E-Invoicing: FTA PINT-AE Integration 2026
TrustBill bridges Daftra with the UAE Federal Tax Authority e-invoicing network. Keep using your UAE-born accounting ERP — we convert invoices to PINT-AE, validate them, and transmit them through an FTA-accredited ASP.
How TrustBill integrates with Daftra
Daftra is a UAE-born accounting and ERP platform that supports local VAT, tax mapping, and FTA-aligned invoice export. To send structured invoices over the national Peppol network, an FTA-accredited ASP connector is still required. TrustBill reads invoice data from Daftra, converts it to PINT-AE XML, runs FTA validation checks, and submits it through our accredited ASP. Arabic buyer and supplier names are preserved as required by PINT-AE.
One-time setup guide
Setting up the Daftra integration is quick and requires no code:
1. **Create your TrustBill account** — Sign up for free and enter your UAE TRN. 2. **Connect Daftra** — Authorise TrustBill to read invoices from your Daftra account via the supported connector. 3. **Map your taxes** — Verify that Daftra tax codes align with official FTA tax categories. 4. **Review Arabic fields** — Confirm supplier and buyer legal names in Arabic and English. 5. **Go live** — Send a test invoice and then enable automatic submission.
After setup, invoices posted in Daftra are transmitted as PINT-AE e-invoices without manual export.
PINT-AE compliance for Daftra users
PINT-AE is the UAE-specific Peppol standard for B2B e-invoicing. TrustBill converts Daftra invoice records into structured PINT-AE XML with all FTA-mandated fields: invoice UUID, issue and due dates, seller and buyer TRNs, line-item details, UAE VAT categories, Arabic legal names, and FTA reporting parameters. This ensures compliance with the 1 January 2027 large-business deadline and the 1 July 2027 SME deadline.
Daftra field → PINT-AE mapping
The exact mapping TrustBill applies when converting a Daftra invoice (read via the Daftra REST API) to PINT-AE XML. Daftra's UAE-native data model already covers most PINT-AE requirements; the mapping below documents where each Daftra field lands in the outbound XML. Arabic legal names on client records flow through unchanged.
| Daftra field | PINT-AE / UBL 2.1 field | Note |
|---|---|---|
| invoice.no | cbc:ID | Daftra invoice number. Must be unique across all submissions. |
| invoice.date | cbc:IssueDate | ISO date. Must not be in the future. |
| client.tax_number | cac:AccountingCustomerParty/cac:PartyTaxScheme/cbc:CompanyID | Buyer TRN — 15 digits. Set on the client record. |
| company.tax_number | cac:AccountingSupplierParty/cac:PartyTaxScheme/cbc:CompanyID | Your TRN. Set once in Daftra → Settings → Company. |
| client.legal_name_ar | cac:AccountingCustomerParty/cac:Party/cac:PartyLegalEntity/cbc:RegistrationName | Arabic legal name — Daftra's UAE-first advantage. Preserved verbatim. |
| invoice.items[].description | cac:InvoiceLine/cbc:Description or cac:Item/cbc:Name | Line-item text. UTF-8; Arabic supported natively. |
| invoice.items[].quantity × unit_price | cbc:LineExtensionAmount, cbc:BaseQuantity, cac:Price/cbc:PriceAmount | PINT-AE reconstructs the line total from qty × price. |
| invoice.items[].tax_id → tax.type | cac:ClassifiedTaxCategory (S=5%, Z=0%, E=exempt, O=out-of-scope) | Daftra tax types must map to a PINT-AE category via TrustBill Tax Mapping. |
| invoice.currency_code | cbc:DocumentCurrencyCode | AED for domestic; non-AED needs the exchange rate populated. |
| invoice.total | cac:LegalMonetaryTotal/cbc:PayableAmount | Reconciled against line totals + tax; mismatch = validation failure. |
| client.custom_fields.free_zone | Extension namespace flag; VAT category derived | Create the custom field on the client once in Daftra. |
| invoice.notes / custom_fields.advance_uuid | cac:DocumentReference for advance-payment linking (type 386) | Populate on any invoice that recovers a prior advance. |
| credit_note.invoice_id | cbc:InvoiceTypeCode="381"; cac:BillingReference/cac:InvoiceDocumentReference | Daftra credit note must be linked to the source invoice. |
Common Daftra → PINT-AE validation errors
The eight most-hit validation errors when a Daftra invoice fails PINT-AE checks, and exactly what to fix in Daftra to clear each one. TrustBill's dashboard surfaces these codes with plain-English explanations; the table below is the reference version.
| Error code | Meaning | Fix in Daftra |
|---|---|---|
| PAE-BR-01 | Buyer TRN missing or malformed. | Daftra → Clients → edit → set Tax Number to the 15-digit TRN. |
| PAE-BR-04 | Seller TRN missing. | Daftra → Settings → Company → set Tax Number. |
| PAE-BR-11 | Line-total mismatch (qty × price ≠ line total). | In the Daftra invoice, edit the item and correct rounding on Quantity or Unit Price so the amount reconciles. |
| PAE-BR-12 | Daftra tax type not mapped to a PINT-AE category. | TrustBill → Settings → Tax Mapping. Map each Daftra tax to a PINT-AE category (S / Z / E / O). |
| PAE-BR-14 | Currency is not AED and no FX rate reference supplied. | In Daftra, ensure the invoice's currency and exchange rate are both set before syncing. |
| PAE-BR-21 | Credit note lacks a valid parent invoice reference. | In Daftra, create the credit note from the source invoice's Actions menu → Credit Note. Do not create it standalone. |
| PAE-BR-22 | Advance-payment invoice not linked to its recovery. | Add the advance-invoice UUID to the recovery invoice's advance_uuid custom field before re-syncing. |
| PAE-BR-31 | Free-zone flag set but supply-place code not present. | Set the client's address in Daftra to the free-zone address, and enable the free_zone custom field on the client. |
Key features for Daftra users
TrustBill's Daftra integration includes:
- **ASP connector for PINT-AE** — FTA-accredited transmission despite Daftra's UAE focus. - **Bilingual Arabic/English support** — Preserves Arabic fields and supports English invoice data. - **Automatic PINT-AE conversion** — No manual XML generation or tax-code lookup. - **Validation engine** — Catches missing TRNs, tax mismatches, and formatting errors before submission. - **Status tracking** — Monitor pending, submitted, accepted, and rejected invoices. - **VAT 201 alignment** — Submitted invoices feed your VAT 201 draft. - **Data residency** — Invoice data is processed and stored in the UAE.
Security and data protection
TrustBill uses read-only access to pull invoice data from Daftra. All traffic uses TLS 1.3, data is encrypted at rest, and customer data is hosted within UAE boundaries. We do not store your Daftra credentials, and no invoice data is used outside the e-invoicing workflow.
Frequently Asked Questions
Is Daftra FTA-certified?
Daftra is marketed as an FTA-approved Accredited Service Provider (ASP) for UAE e-invoicing and supports FTA-aligned tax mapping and XML export. However, transmitting PINT-AE invoices over the national Peppol network still requires a certified ASP connector. TrustBill provides that connector on top of Daftra.
Does the integration support Arabic?
Yes. Daftra is widely used for Arabic billing, and PINT-AE requires supplier and buyer legal names in Arabic alongside Latin script. TrustBill preserves Arabic fields throughout conversion and submission.
How long does setup take?
Most businesses complete setup in under an hour. The steps are connecting Daftra, mapping tax codes, checking Arabic/English fields, and sending a test invoice. No developer work is needed.
Is my data secure?
Yes. TrustBill uses TLS 1.3 in transit and AES-256-GCM encryption at rest. We request the minimum read access required, do not store Daftra credentials, and keep data within the UAE.
Is this suitable for local UAE businesses?
Yes. Daftra is popular with UAE SMEs and trading businesses. TrustBill helps these companies meet the 1 January 2027 large-business mandate and the 1 July 2027 SME mandate for FTA e-invoicing.