Sage Integration
Sage UAE E-Invoicing: FTA PINT-AE Integration 2026
TrustBill connects Sage to the UAE FTA e-invoicing network. Sage does not natively submit PINT-AE invoices, so our connector extracts invoice data, converts it to the 51-field PINT-AE XML format, and submits it through an FTA-accredited service provider.
How TrustBill integrates with Sage
Sage accounting and ERP editions do not include native FTA submission. TrustBill adds a connector layer that reads invoice data from Sage 50cloud, Sage Business One or Sage X3, validates it against UAE e-invoicing rules, and converts it to PINT-AE XML. The connector then submits the invoice through an accredited service provider on the Peppol 5-corner network, covering supplier, supplier ASP, buyer ASP, buyer and the FTA.
Sage editions supported in the UAE
TrustBill supports the Sage product families most commonly used in the UAE:
- **Sage 50cloud** — A hybrid desktop-cloud accounting suite for small and mid-sized businesses. TrustBill connects to the underlying Sage data and sends PINT-AE invoices without replacing your existing setup. - **Sage Business One** — A unified business management solution for growing SMBs. We extract A/R invoices and credit notes and map them to the mandatory FTA fields. - **Sage X3** — The enterprise edition for larger or multi-entity organisations. TrustBill can handle high invoice volumes, multiple VAT registrations and complex tax-code scenarios.
PINT-AE compliance for Sage invoices
UAE e-invoices must be issued, transmitted and received in structured XML following the Peppol PINT-AE specification. The FTA data dictionary contains 51 mandatory fields, including invoice UUID, issue date, seller and buyer TRN, line-item details, VAT rates and UAE-specific qualifiers such as free-zone and margin-scheme flags. TrustBill automatically maps Sage invoice data to these fields and validates every document before submission.
Sage field → PINT-AE mapping
The exact mapping TrustBill applies when converting a Sage export or SData payload to PINT-AE XML. Field names below use Sage Business One / Sage X3 conventions; Sage 50cloud maps 1:1 via the same OData surface. Bookmark this table before configuring tax codes and business-partner masters.
| Sage field | PINT-AE / UBL 2.1 field | Note |
|---|---|---|
| OINV.DocNum (Business One) / SINVOICE.NUM (X3) | cbc:ID | Your invoice number. Must be unique across all submissions. |
| OINV.DocDate / SINVOICE.INVDAT | cbc:IssueDate | ISO date. Must not be in the future. |
| OCRD.LicTradNum (buyer TRN) | cac:AccountingCustomerParty/cac:PartyTaxScheme/cbc:CompanyID | Buyer TRN — 15 digits. Set on the business partner master. |
| OADM.CompanyGSTRegNo / X3 company TRN | cac:AccountingSupplierParty/cac:PartyTaxScheme/cbc:CompanyID | Your TRN. Set once in Company Details. |
| INV1.Dscription | cac:InvoiceLine/cbc:Description or cac:Item/cbc:Name | Line-item text. UTF-8; Arabic supported on Sage X3 v11+. |
| INV1.Quantity × INV1.Price | cbc:LineExtensionAmount, cbc:BaseQuantity, cac:Price/cbc:PriceAmount | PINT-AE reconstructs the line total from qty × price. |
| INV1.VatGroup / X3 VAT rate code | cac:ClassifiedTaxCategory (S=5%, Z=0%, E=exempt, O=out-of-scope) | Sage VAT group must map to a PINT-AE category via TrustBill Tax Mapping. |
| OINV.DocCurrency | cbc:DocumentCurrencyCode | AED for domestic; non-AED needs the FX rate populated on the invoice. |
| OINV.DocTotal | cac:LegalMonetaryTotal/cbc:PayableAmount | Reconciled against line totals + tax; mismatch = validation failure. |
| OCRD.U_FreeZone (UDF) | Extension namespace flag; VAT category derived | Create the User-Defined Field once on the BP master. |
| OINV.U_AdvanceUUID (UDF) | cac:DocumentReference for advance-payment linking (type 386) | Populate on any invoice that recovers a prior advance. |
| ORIN.BaseEntry (credit-memo → source invoice) | cbc:InvoiceTypeCode="381"; cac:BillingReference/cac:InvoiceDocumentReference | Sage credit memo must link back to the source invoice's DocEntry. |
Common Sage → PINT-AE validation errors
The eight most-hit validation errors when a Sage invoice fails PINT-AE checks, and exactly what to fix in Sage 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 Sage (Business One / X3 / 50cloud) |
|---|---|---|
| PAE-BR-01 | Buyer TRN missing or malformed. | Sage → Business Partner Master Data → edit → set Federal Tax ID / LicTradNum to the 15-digit TRN. |
| PAE-BR-04 | Seller TRN missing. | Sage → Administration → System Initialization → Company Details → set Federal Tax ID. |
| PAE-BR-11 | Line-total mismatch (qty × price ≠ line total). | In the marketing document, edit the row and correct rounding on Quantity or Price so the total reconciles. |
| PAE-BR-12 | Sage VAT group not mapped to a PINT-AE category. | TrustBill → Settings → Tax Mapping. Map each Sage VAT group to a PINT-AE category (S / Z / E / O). |
| PAE-BR-14 | Currency is not AED and no FX rate reference supplied. | In the Sage invoice, ensure the Rate field on the header is populated for the document currency before posting. |
| PAE-BR-21 | Credit note lacks a valid parent invoice reference. | In Sage, create the credit memo by right-clicking the source invoice → Copy To → Credit Memo. Do not create as a standalone. |
| PAE-BR-22 | Advance-payment invoice not linked to its recovery. | Populate the recovery invoice's U_AdvanceUUID UDF with the advance-invoice UUID before posting. |
| PAE-BR-31 | Free-zone flag set but supply-place code not present. | In the BP master, set the U_FreeZone UDF and ensure the shipping address is in the free zone. |
Setup time and go-live workflow
Most Sage integrations are configured in one business day. The typical workflow is:
1. **Create your TrustBill account** — Sign up for free and enter your business TRN. 2. **Connect Sage** — Install the TrustBill connector for your Sage edition and authorise read-only access. 3. **Map tax codes** — Match your Sage VAT codes to UAE PINT-AE tax categories (standard, zero, exempt, reverse charge, margin scheme). 4. **Test a sample invoice** — Create a test invoice in Sage and verify that TrustBill validates it successfully. 5. **Go live** — Invoices are synced automatically in the background and submitted to the FTA network.
No Sage upgrade or ERP replacement is required.
Data security and tax-code mapping
TrustBill requests the minimum read-only access required to extract invoice and credit-note data. We do not create, modify or delete transactions inside Sage. All traffic uses TLS 1.3, data is encrypted at rest, and tax data is stored within the UAE. Tax codes are mapped once during onboarding; the connector then applies the mapping consistently to every invoice, preventing rejections caused by incorrect VAT treatment.
Frequently Asked Questions
Which Sage editions are supported?
TrustBill supports Sage 50cloud, Sage Business One and Sage X3. Sage 50cloud works through a hybrid on-premise or cloud connector, while Business One and X3 are typically connected via API or a secure on-site agent.
Is Sage 50cloud supported?
Yes. Sage 50cloud is a hybrid product and is fully supported. TrustBill reads invoice data from the Sage 50cloud company file and submits compliant PINT-AE XML without forcing a full cloud migration.
How long does setup take?
Most businesses are live within one business day. The longest step is usually tax-code mapping, which is completed with our onboarding checklist and pre-filled Sage-to-PINT-AE templates.
Is my Sage data secure?
Yes. TrustBill uses read-only access, TLS 1.3 in transit and AES-256-GCM at rest. Your Sage company data is never modified, and invoice data is stored in UAE data centres.
How does tax-code mapping work?
TrustBill maps each Sage tax code to the equivalent UAE PINT-AE tax category, such as standard rate, zero rate, exempt, reverse charge or margin scheme. This mapping is validated during onboarding and applied automatically to every invoice.