E-invoicing, tax and digital product passports
E-invoicing mandates met from inside your ERP, before the deadline
Tax authorities now see invoices as they are issued
Across MENA, Europe and Asia, tax authorities are moving to continuous transaction controls (CTC). Invoices go to the authority, or through its network, in a set structured format, and are cleared or reported as they are issued. Paper, PDF and late batch uploads no longer count.
Each mandate has its own format, signing, QR code and deadline, and an invoice the authority rejects is an invoice the customer cannot pay. Disconnected ERP invoicing modules put compliance, and cash flow, at risk.
What changes for you
Compliance built into the invoice run
Every invoice is generated, signed, validated and cleared from the ERP, with no manual uploads to a tax portal.
An audit trail for every invoice
Each submission, response and correction stored against the invoice, ready for the tax authority and your auditors.
Ready for the next mandate
One integration layer that takes a new country or a new phase as configuration and tests, not a new project.
What we deliver
MENA e-invoicing and clearance
Integrations for Saudi Arabia's ZATCA Phase 2 through its FATOORA platform, the UAE's PINT-AE format and EmaraTax, and Oman's mandate. ZATCA is the Zakat, Tax and Customs Authority; Phase 2 is its integration phase.
European and APAC continuous transaction controls
Connections for the EU's VAT in the Digital Age package (ViDA), the PEPPOL e-invoicing network and national tax APIs.
Signing, stamping and QR codes
Cryptographic stamping, QR generation and validation in real time, with keys and certificates held in a vault, never in code.
Digital product passports and traceability
EU Digital Product Passport (DPP) integrations that share a product's materials, origin and lifecycle data along the supply chain.
ERP and POS connectors
Invoice data taken from SAP, Oracle, Microsoft Dynamics 365, Odoo or your POS, mapped to each mandate's format and posted back with the authority's response.
Rejections and corrections
Rejected invoices routed to a person with the authority's reason, corrected and resubmitted, with credit and debit notes handled the same way.
How we work
Gap analysis
We compare your invoice data, ERP configuration and processes with each mandate in scope, and list what must change.
Design the integration
We map every invoice type to the required format and choose the connection: direct to the authority, through its network or through an accredited provider.
Connect in the sandbox
We build the connector and run it against the authority's sandbox or test environment with real invoice scenarios.
Onboard and go live
We complete the authority's onboarding, issue the production certificates and switch over entity by entity.
Monitor and keep current
We watch clearance rates and rejections, and update the integration as authorities publish new phases and rules.
Mandates, formats and platforms
We build from each authority's published specifications. Naming a product does not mean a partnership with its vendor.
- ERP systems
- SAP S/4HANA
- Oracle Fusion Cloud ERP
- Oracle NetSuite
- Microsoft Dynamics 365 Finance and Supply Chain Management
- Odoo
- Integration
- REST
- Webhooks
Proof in production
For a Tier-1 GCC bank and regional conglomerate, we built a real-time stamping, QR and clearance pipeline for ZATCA Phase 2 and PINT-AE. It runs directly from SAP S/4HANA.
How to start
The Mandate E-Invoicing and ERP Readiness Sprint gives you a gap analysis and a live sandbox connector, integrated with your ERP. It covers PINT-AE, ZATCA Phase 2, or ViDA and PEPPOL.
What happens next
Readiness review
In a free 48-hour readiness review, a Principal Architect checks your project against the 6-point Definition of Ready and recommends the track that fits.
Binding proposal
After architecture validation at no cost, you receive a binding, fixed-scope proposal within 3–5 business days: milestones, architecture, team structure and SLAs. We sign a non-disclosure agreement (NDA) with you on request, before you share your requirements.
Mobilisation
Once you sign, our engineering pods begin Sprint 0 within 5–10 business days of contract signature.
Delivery in five stages
Mobilisation, sprints with live demonstrations, integration and hardening, acceptance and go-live, then managed services. After launch comes a warranty period, then optional support and maintenance.
Fixed-outcome projects and round-the-clock managed services
Fixed-scope, milestone-driven delivery with named delivery leads, and round-the-clock application managed services under SLA governance.
Embedded specialists and strategic augmentation
Nearshore and on-site principal engineers and specialists, and embedded solution, transformation, PQC and integration architects.
The quickest way in is the Mandate e-invoicing and ERP readiness sprint package, one of our rapid engagement packages.
Questions and answers
What does ZATCA Phase 2 require?
Phase 2, the integration phase, requires taxpayers' systems to connect to ZATCA's FATOORA platform. Standard tax invoices are cleared by ZATCA before they reach the buyer, and simplified invoices are reported shortly after. Each invoice carries a cryptographic stamp and a QR code, so the ERP or POS must produce them in the required format.
What is PINT-AE?
PINT-AE is the UAE's specification of the PEPPOL International invoice format, used in the UAE e-invoicing programme. Invoices are exchanged in this structured format through accredited service providers and reported to the Federal Tax Authority, whose EmaraTax platform handles UAE tax.
What is ViDA, and does it affect us outside the EU?
VAT in the Digital Age (ViDA) is the EU's package that moves cross-border business invoicing to structured e-invoices and digital reporting. It affects any business that invoices EU customers or runs EU entities, wherever its head office is.
What is a digital product passport?
A Digital Product Passport (DPP) is the EU's record of a product's materials, origin, repairability and recycling, shared through a data carrier such as a QR code. It is phased in by product group. It depends on supply-chain data that usually sits in ERP and manufacturing systems.
Our ERP has an e-invoicing add-on. Do we still need you?
Often the add-on is the right starting point, and we configure and extend it rather than build around it. The work that remains is usually the data: invoice types, tax codes, master data and exceptions the add-on does not cover. POS and other systems that also issue invoices need connecting too.
What happens when the tax authority rejects an invoice?
The rejection comes back with the authority's reason and goes to a review list, linked to the invoice. Your team corrects the data, or we adjust the mapping if the cause is systemic, and the invoice is resubmitted. Every attempt is kept for audit.
Can one integration cover several countries?
Yes. We build one integration layer with a connector per mandate. The ERP produces one invoice, and the layer formats, signs and submits it for each country. Adding a country becomes configuration, mapping and tests.
Ready to build? Ask for a proposal.
Send your requirements or RFP. Our architects validate them and return a binding, fixed-scope proposal.