Compliance Checklist
UAE E-Invoicing Compliance Checklist: Your Step-by-Step Guide
Follow this comprehensive checklist to ensure your business is fully compliant with the UAE FTA e-invoicing mandate. Covers all phases, deadlines, and technical requirements for 2026-2027.
Phase 1: Large Businesses (Revenue ≥ AED 50M)
Select an FTA-accredited ASP from the Ministry of Finance register. Evaluate ERP integration capability, pricing, data residency, and SLA. TrustBill includes ASP submission in all plans.
Assess your current ERP's PINT-AE capability. Many systems require upgrades or middleware. Identify if your system can generate PINT-AE XML or needs integration layer.
Ensure all TRNs are accurate and valid. Verify legal registration identifiers (TL, EID, PAS, CD). Standardize product codes and descriptions. Clean customer and supplier master data.
Set up technical connection with your ASP (OAuth API, desktop agent, or file upload). Test integration in sandbox environment. Validate data mapping and PINT-AE conversion.
Educate finance staff on new e-invoicing workflows. Train on handling rejected invoices and validation errors. Establish escalation procedures for technical issues.
Switch to production credentials. Begin submitting all invoices through ASP. Monitor submission status and error rates. Establish daily compliance monitoring.
Phase 2: SMEs (Revenue < AED 50M)
Select an FTA-accredited ASP. For SMEs, prioritize ease of integration and cost-effectiveness. TrustBill offers free tier (50 invoices/month) for testing.
Evaluate if your accounting software supports e-invoicing. Popular systems like Zoho, QuickBooks, Tally are adding PINT-AE support. Consider upgrade if needed.
Verify all TRNs are correct. Ensure product codes are standardized. Check customer and supplier data completeness. Fix any data quality issues.
Connect your ERP to ASP via available method (API, desktop agent, or Excel upload). Test with sample invoices. Validate PINT-AE output.
Train relevant staff on new workflows. Document procedures for handling rejections. Set up monitoring for submission status.
Enable production submission. Start submitting all invoices. Monitor for errors and compliance. Address issues promptly.
Phase 3: Government Entities
Select ASP with government sector experience. Ensure integration compatibility with government financial systems. Consider security and compliance requirements.
Configure integration between government ERP and ASP. Test with government-specific invoice types. Validate compliance with government procurement rules.
Set up internal governance for e-invoicing compliance. Designate compliance officers. Establish audit trails and reporting procedures.
Enable production submission for all government invoices. Monitor compliance across departments. Report compliance status to oversight bodies.
Ongoing Compliance Requirements
Check dashboard for pending, submitted, accepted, and rejected invoices. Address rejections within 24 hours. Track submission success rates.
Keep master data up-to-date. Update TRNs when they change. Maintain accurate product codes and customer data. Regular data quality audits.
Investigate rejection reasons. Fix issues in source system. Re-submit corrected invoices. Document rejection patterns for process improvement.
Notify FTA within required timeframe if system failures occur. Document outage duration and impact. Maintain communication with ASP during outages.
Inform ASP of changes to TRN, company details, or other registered data. Ensure ASP records are current. Update integration if business structure changes.
Monitor FTA and Ministry of Finance announcements. Review updated guidelines as they're published. Adjust processes for new requirements.
Technical Requirements Checklist
Ensure all invoices meet PINT-AE specification. Validate all 51 mandatory data elements. Test with FTA validation tools if available.
Confirm all invoice data is stored and processed within UAE (AWS me-central-1 or equivalent). Verify ASP's data residency compliance.
Ensure data is encrypted in transit (TLS 1.3) and at rest (AES-256-GCM). Verify ASP's security certifications (SOC 2 Type II).
Confirm ASP infrastructure meets uptime requirements. Understand failover procedures. Test business continuity plans.
Implement automatic retry for transient failures. Log all errors with timestamps. Establish escalation for persistent issues.
Maintain logs of all submissions. Record timestamps, user IDs, and submission status. Enable compliance auditing and reporting.
Frequently Asked Questions
What if I miss my deadline?
Missing your deadline triggers penalties under Cabinet Decision 106/2025: AED 5,000 per month for failure to implement, plus AED 100 per non-compliant invoice. Contact the FTA immediately if you anticipate missing a deadline to discuss options.
Can I use multiple ASPs?
Yes, you can use multiple ASPs for different business units. However, this adds complexity to compliance management. Most businesses use a single ASP for simplicity.
How do I know if my ERP is ready?
Check with your ERP vendor about PINT-AE support. Many vendors are releasing updates. If your system cannot generate PINT-AE XML, you'll need middleware or a desktop agent like TrustBill provides.
What happens to my existing invoice templates?
Your existing invoice templates can remain unchanged for customer-facing PDFs. The e-invoicing requirement applies to the structured XML data submitted to the FTA, not your customer-facing documents.
Do I need to change my VAT reporting process?
E-invoicing simplifies VAT reporting by populating your VAT 201 return automatically. However, you should review your internal VAT reconciliation processes to leverage the new data flow.
How long does master-data cleanup typically take?
For a mid-sized business (5,000-20,000 customers/suppliers), plan on 2-4 weeks of focused work: TRN validation against the FTA lookup, canonical address formatting, product-code alignment. Most delays we see are TRN mismatches — running the FTA TRN validator against your customer master early avoids most of them.
Do we need to keep our own copies of submitted invoices?
Yes. UAE record-keeping rules under Federal Decree-Law 47/2022 require you to retain tax records for at least 5 years (15 for real-estate-related supplies). TrustBill retains signed PINT-AE XML plus PDF renders in AWS me-central-1 for the full period at no extra cost.
Who inside the business owns the mandate — finance or IT?
Both. Ownership sits with finance (the mandate is a tax obligation), but IT owns the integration path (ERP config, agent install, API keys). We recommend forming a joint task force with a named executive sponsor — the failure mode we see is finance assuming IT is handling it and vice versa.
What testing evidence should we retain?
Sandbox submission receipts (invoice UUID, timestamp, status), sample rejection/acceptance responses, a signed test summary from your ASP, and change-management records showing sign-off. This is what the FTA looks for if the mandate compliance is audited later.
Can we run the mandate in one country of a multi-country group first?
Yes. The UAE mandate applies to your UAE-registered TRN(s). Group entities in other jurisdictions are unaffected unless those jurisdictions have their own e-invoicing mandate. A staged rollout — UAE first, then KSA (ZATCA), then any Peppol countries — is a common pattern.
What if we onboard mid-phase and miss the ASP appointment date?
Appoint the ASP first, immediately, then work backwards on data + integration. The AED 5,000/month non-appointment penalty ticks from your phase's mandatory date regardless of when you started onboarding — stopping the meter is the priority. TrustBill can complete appointment within 48 hours for expedited cases.
Do bulk uploads (Excel/CSV) count as compliant submission?
Only after the file is transformed to PINT-AE XML, signed, and submitted via an ASP to Peppol. Uploading Excel to a spreadsheet or emailing a CSV to your ASP without transformation does not satisfy the mandate. TrustBill's bulk upload performs the transformation automatically; the FTA acknowledgement is the compliance proof.
What's the acceptance criteria for 'go-live ready'?
Three things: (1) ASP appointment confirmed by the FTA, (2) at least one successful end-to-end sandbox submission with a returned acknowledgement UUID, and (3) production credentials issued and stored securely. Miss any one and you are not go-live ready.
How do we handle historical invoices issued before go-live?
Invoices dated before your phase's mandatory date do not need to be reissued in PINT-AE. From your go-live date forward, all new invoices (and any amendments to old ones — corrective notes) must be issued electronically. Cut-over date is best fixed to a month boundary so VAT 201 aligns cleanly.