UAE E-Invoicing & FTA Compliance

We build a proper Frappe app — its own installable module with versioned DocTypes, hooks.py doc events, and whitelisted API methods — that closes that gap inside your existing ERPNext instance instead of bolting on a disconnected portal. On on_submit of a Sales Invoice, a server-side hook maps your document to the Peppol PINT AE / UBL 2.1 schema (seller/buyer TRN, tax category codes, line-level VAT, currency, invoice typologies), validates it against FTA business rules, and hands the signed payload to your chosen accredited service provider over their API. Clearance or acknowledgement responses are written back onto the invoice via a dedicated E-Invoice Log DocType, so the compliance state lives next to the transaction, not in someone's inbox.

The build covers the full document lifecycle, not just the happy path. Credit notes map to the correct UBL credit-note typology with billing references back to the original invoice; reverse-charge and zero-rated / exempt supplies get correct tax category codes and exemption reasons; TRN validation runs client-side (a Client Script on the Customer and Sales Invoice forms) and server-side before submission so bad tax numbers never reach the ASP. A scheduler event polls for pending clearances and retries transient ASP failures, and a VAT Return / FAF export builds the FTA-format audit file straight from your ledger — with role profiles and permissions so only your tax team can submit or file.

Because this is scoped to your ERPNext, we build against your actual chart of accounts, tax templates, company TRNs, and your selected ASP (Frappe/ERPNext v15 and v16 supported). This is build-to-order: after a short scoping call we confirm the exact profile version, ASP, and edge cases, then deliver, install on your staging site, run UAT, and cut over to production. Typical delivery is 2–4 weeks from confirmed scope. You receive the full source as an installable app plus the git repository, so nothing is locked to us.