ERP integration troubleshooting checklist
A systematic checklist for diagnosing e-invoicing failures when submitting from an ERP or middleware API integration.
When e-invoices fail consistently from an ERP integration, work through this checklist before raising a support ticket.
1. Authentication (E2001 / E2002)
- API key is from the production environment (not sandbox)
- API key has not expired (check the portal → Settings → API keys)
- The
Authorizationheader is formatted asBearer <key>— notBasicorAPI-Key - The correct tenant ID / participant ID is in the URL path
2. XML structure (E1005 / E1009)
- Root element namespace matches
urn:oasis:names:specification:ubl:schema:xsd:Invoice-2 - All
cac:andcbc:prefixes are declared in the root element - File is UTF-8 encoded (no BOM)
- No XML comments or processing instructions above the root element
3. Mandatory fields (E1006 — PINT AE validation)
- Seller TRN (IBT-031) is exactly 15 digits, starts non-zero, ends in
03 - Buyer Peppol ID (IBT-049) is in
0235:XXXXXXXXXformat - Invoice date (IBT-002) is in
YYYY-MM-DDformat - Payment means code (IBT-081) is set (e.g.
30) - All line items have a non-empty description (IBT-153)
- Unit codes are from UN/ECE Rec 20
- BTAE-02 transaction type code is provided as an 8-character string
4. Tax calculations
- Line tax amounts sum to the document tax total (within 0.01 AED rounding tolerance)
- Standard-rate lines use exactly 5.00% (not 5 or 0.05)
- Zero-rate and exempt lines include a VAT reason code
- Total including VAT = total excluding VAT + total VAT amount
5. Test before go-live
- Use the sandbox environment with test credentials first
- Validate your XML in the XML validator before API submission
- Submit a batch of 5–10 real invoices in test mode and review each result
Useful tools
- XML validator — paste or upload your XML and see PINT AE errors
- Batch check — validate up to 50 XML files at once
- Field mapping checker — verify your ERP field mapping
See also: Top rejection causes · B2B e-invoicing walkthrough.