SAP Integration
UAE E-Invoicing for SAP — Enterprise API Integration
TrustBill connects your SAP system to the FTA e-invoicing network via Microvista Technologies. API-first integration for SAP Business One, S/4HANA, and other SAP solutions. No ERP migration required.
How TrustBill integrates with SAP
TrustBill connects to SAP via REST API integration, pulling invoice data automatically from your SAP system. The integration supports all SAP invoice types: sales invoices, credit notes, debit notes, and proforma invoices. Once connected, every invoice you create in SAP is synced to TrustBill in real-time, converted to PINT-AE XML format, validated against FTA requirements, and submitted to the accredited ASP network.
The API integration is designed for enterprise environments with robust security, error handling, and monitoring. TrustBill provides comprehensive API documentation, SDKs, and dedicated technical support for SAP implementations. The integration works with SAP Business One, SAP S/4HANA, SAP ERP/ECC, and other SAP solutions deployed on-premise or in the cloud.
Enterprise setup guide
Setting up the SAP API integration typically takes 2-4 weeks depending on your SAP configuration:
1. **Create your TrustBill account** — Sign up and obtain API credentials. 2. **API documentation review** — Review TrustBill's REST API documentation and SAP integration guide. 3. **SAP middleware configuration** — Configure SAP middleware (PI/PO, CPI, or custom ABAP) to call TrustBill APIs. 4. **Data mapping** — Map SAP invoice fields to TrustBill's PINT-AE schema. 5. **Testing in sandbox** — Test the integration in TrustBill's sandbox environment with sample invoices. 6. **Production go-live** — Switch to production credentials and enable real-time submission.
TrustBill provides dedicated technical support throughout the implementation process, including API testing, data mapping assistance, and go-live support.
PINT-AE compliance for SAP invoices
TrustBill automatically converts SAP invoice data to PINT-AE XML format, the UAE's national e-invoicing standard. The conversion handles all required data elements: invoice UUID, issue date, seller/buyer TRN, line-item details, VAT rates, and UAE-specific fields like free zone flags and margin scheme indicators.
SAP stores invoice data in its proprietary format, which differs from PINT-AE requirements. TrustBill's mapping engine transforms SAP data structures to PINT-AE specifications, ensuring every field is correctly populated. The system validates each converted invoice against the FTA's 51 mandatory data elements before submission, catching errors like missing TRNs, invalid VAT rates, or incomplete line-item details. Validation errors are reported via API callbacks and in the TrustBill dashboard, allowing your SAP system to handle corrections programmatically.
SAP field → PINT-AE mapping
The exact mapping TrustBill applies when converting an SAP billing document to PINT-AE XML. Field names below use SAP standard table conventions (VBRK/VBRP for S/4HANA and ECC; OINV/INV1 for Business One). The same mapping works whether the source is a BAPI call, an iDoc, or the S/4HANA OData billing API. Bookmark this table before wiring up your CPI iFlow or PI/PO channel.
| SAP field | PINT-AE / UBL 2.1 field | Note |
|---|---|---|
| VBRK-VBELN (S/4HANA / ECC) / OINV.DocNum (B1) | cbc:ID | Billing-document number. Must be unique across all submissions. |
| VBRK-FKDAT / OINV.DocDate | cbc:IssueDate | ISO date. Must not be in the future. |
| KNA1-STCEG (customer VAT reg. no.) | cac:AccountingCustomerParty/cac:PartyTaxScheme/cbc:CompanyID | Buyer TRN — 15 digits. Populate STCEG on the KNA1 record with country AE. |
| T001-STCEG (company code VAT reg.) | cac:AccountingSupplierParty/cac:PartyTaxScheme/cbc:CompanyID | Your TRN. Set once per company code via SPRO. |
| VBRP-ARKTX / INV1.Dscription | cac:InvoiceLine/cbc:Description or cac:Item/cbc:Name | Line-item text. UTF-8; Arabic supported once Unicode fonts are installed. |
| VBRP-FKIMG × KOMV-KBETR / INV1.Quantity × Price | cbc:LineExtensionAmount, cbc:BaseQuantity, cac:Price/cbc:PriceAmount | PINT-AE reconstructs line total from qty × price. |
| KOMV / T007A tax code → tax rate | cac:ClassifiedTaxCategory (S=5%, Z=0%, E=exempt, O=out-of-scope) | SAP MWST condition and tax code must map to a PINT-AE category via TrustBill Tax Mapping. |
| VBRK-WAERK / OINV.DocCurrency | cbc:DocumentCurrencyCode | AED for domestic; non-AED needs the header conversion rate (VBRK-KURRF) populated. |
| VBRK-NETWR + KWSTE (total) | cac:LegalMonetaryTotal/cbc:PayableAmount | Reconciled against line totals + tax; mismatch = validation failure. |
| Customer master ZZFREEZONE (Z-field or classification) | Extension namespace flag; VAT category derived | Standardise on a Z-field or KLAH classification value; TrustBill reads either. |
| VBRK-XBLNR / OINV.U_AdvanceUUID (custom) | cac:DocumentReference for advance-payment linking (type 386) | Populate on any invoice that recovers a prior advance. |
| VBRK-FKART="S1" (cancellation) / ORIN.BaseEntry (B1 credit) | cbc:InvoiceTypeCode="381"; cac:BillingReference/cac:InvoiceDocumentReference | Cancellation / credit memo must reference the parent billing document via VBFA (S/4) or BaseEntry (B1). |
Common SAP → PINT-AE validation errors
The eight most-hit validation errors when an SAP-sourced invoice fails PINT-AE checks, and exactly what to fix on the SAP side to clear each one. TrustBill returns these codes via the API callback and surfaces them in the dashboard with plain-English explanations; the table below is the reference version for your ABAP / CPI teams.
| Error code | Meaning | Fix in SAP (S/4HANA / ECC / Business One) |
|---|---|---|
| PAE-BR-01 | Buyer TRN missing or malformed. | SAP → XD02 (Change Customer) → set STCEG (VAT reg. no.) to the 15-digit TRN. B1 → Business Partner Master Data → Federal Tax ID. |
| PAE-BR-04 | Seller TRN missing. | SPRO → General Settings → Set Up Countries → assign STCEG on the company code T001. B1 → Company Details → Federal Tax ID. |
| PAE-BR-11 | Line-total mismatch (qty × price ≠ line total). | In VF02 (S/4/ECC), edit the pricing procedure or fix rounding on KBETR. B1 → the marketing document line's price/quantity fields. |
| PAE-BR-12 | SAP tax code not mapped to a PINT-AE category. | TrustBill → Settings → Tax Mapping. Map each SAP MWST tax code (V5, VZ, VE, etc.) to a PINT-AE category (S / Z / E / O). |
| PAE-BR-14 | Currency is not AED and no FX rate reference supplied. | In VBRK, populate KURRF (exchange rate to local currency) before release. B1 → set the Rate on the document header. |
| PAE-BR-21 | Credit note lacks a valid parent invoice reference. | In S/4, create cancellations via VF11 or invoice corrections with reference to the original billing document (VBFA). In B1, use Copy To → Credit Memo from the source invoice. |
| PAE-BR-22 | Advance-payment invoice not linked to its recovery. | Populate VBRK-XBLNR (reference document) or a Z-field with the advance-invoice UUID before release. In B1, use U_AdvanceUUID UDF. |
| PAE-BR-31 | Free-zone flag set but supply-place code not present. | In the customer master, set the ZZFREEZONE Z-field (or KLAH classification value) and ensure the ship-to address is in the free zone. |
Key features for SAP users
TrustBill's SAP integration includes:
- **REST API** — Comprehensive API for invoice submission, status tracking, and error handling. - **Real-time sync** — Invoices are submitted seconds after creation in SAP. - **Webhook callbacks** — Receive real-time status updates (submitted, accepted, rejected) via webhooks. - **Error handling** — Validation errors are returned with clear error codes and explanations. - **Bulk processing** — Handle high-volume invoicing with batch API support. - **Rejection management** — Rejected invoices can be corrected in SAP and re-submitted programmatically. - **VAT 201 integration** — Submitted invoices auto-populate your VAT 201 return draft. - **Multi-entity support** — Configure multiple SAP company codes for different entities. - **Data residency** — All invoice data stays in UAE (AWS me-central-1). - **Enterprise SLA** — 99.9% uptime guarantee with dedicated support.
The integration is SOC 2 Type II compliant and supports enterprise SSO.
Enterprise pricing for SAP integration
TrustBill offers enterprise pricing for SAP customers based on invoice volume and support requirements. Plans start at AED 1,000/month for 5,000 invoices, with custom pricing for higher volumes.
Enterprise plans include: - Dedicated technical support - API documentation and SDKs - Sandbox testing environment - 99.9% uptime SLA - Implementation assistance - Custom data mapping support
Contact our sales team for a custom quote based on your SAP configuration and invoice volume.
Frequently Asked Questions
Which SAP versions are supported?
TrustBill supports SAP Business One, SAP S/4HANA, SAP ERP/ECC, and other SAP solutions. Both on-premise and cloud deployments are supported.
Do I need to modify my SAP system?
Minimal changes are required. You'll need to configure SAP middleware to call TrustBill APIs, but no changes to your core SAP configuration or workflows are necessary.
Is the integration secure?
Yes. TrustBill uses OAuth 2.0 for API authentication, TLS 1.3 for encrypted communication, and is SOC 2 Type II compliant. All data is encrypted in transit and at rest. Your invoice data stays in UAE (AWS me-central-1).
What happens if an invoice is rejected?
Rejected invoices trigger webhook callbacks with error details. Your SAP system can programmatically handle corrections and re-submission based on these callbacks.
How long does implementation take?
Typical SAP implementations take 2-4 weeks depending on your SAP configuration and data mapping complexity. TrustBill provides dedicated technical support throughout.