E-Invoicing & Tax Compliance
File to ZATCA, the Egyptian Tax Authority and the UAE Peppol network from one engine.
Electronic invoicing is the one thing on this site a government can compel you to buy. Three of the markets Nama operates in have moved invoicing onto national platforms, each with its own format, its own clearance rules and its own deadlines — and each with the same consequence for getting it wrong: the invoice is not valid, so the revenue is not recognised and the customer will not pay. Nama submits from inside the ledger. The invoice your team raises is the invoice that gets signed, sent and cleared. There is no export file, no middleware licence, and no second system to reconcile against at month end.
What E-Invoicing & Tax Compliance covers
4 modules, licensed together or separately.
- ZATCA E-Invoicing (Saudi Arabia) Saudi Phase 2 integration — UBL 2.1 invoices, cryptographic stamps and QR codes.
- ZATCA Phase 2 Requirements — A Practical Guide What the Integration Phase requires: clearance vs reporting, onboarding, and why invoices are rejected.
- Egypt E-Invoice & Electronic Receipt Egyptian Tax Authority invoices and electronic receipts, submitted and tracked.
- UAE E-Invoicing (Peppol) UAE e-invoicing over the Peppol network, in the PINT AE format.
How it works together
Compliance is a pipeline, and the value is in how few steps of it a human touches.
- Capture. The invoice is raised in sales, POS or e-commerce exactly as it always was. Nothing about the selling workflow changes because a mandate arrived.
- Validate. Mandatory fields are checked against the target authority’s rules before anything leaves the building. A missing tax number or an unmapped unit of measure fails here, where it costs a minute.
- Sign. The document is rendered into the format that authority accepts and cryptographically signed by the mechanism it requires.
- Submit. Invoices are gathered into a submission document that can be previewed and released as a batch, or sent as they are issued where the rules require immediacy.
- Track. Every line carries its own authority status, and on rejection the reason the authority gave.
- Correct. Credit and debit notes reference the cleared original, so the correction is traceable to what it corrected — which is what an audit actually asks for.
Because all six steps happen inside the ERP, the tax position is never a separate set of numbers. What was reported and what was posted are the same records.
Three mandates, one engine
The three country modules in this family are configurations of one submission engine rather than three integrations bolted together.
Saudi Arabia — ZATCA. Phase 2 integration: UBL 2.1 XML, digital signature, clearance for standard invoices and 24-hour reporting for simplified ones.
Egypt — ETA. Both halves of the digitisation: the e-invoice system for B2B with HSM signature and GS1 and EGS coding, and the electronic receipt system for point-of-sale.
United Arab Emirates — Peppol. Submission through an accredited service provider on the UAE’s five-corner model, which validates the document, reports the tax data and routes it to the buyer over the network.
A group operating in more than one of them runs one system. The differences are configuration on the company record, not separate installs — which matters most to exactly the businesses that find compliance hardest: the ones crossing borders.
Every screen, field and setting is documented in full.
Read the documentation →Good question — already answered
Is Nama certified by ZATCA?
Namasoft appears in ZATCA's Solution Providers Directory among the Phase 2 qualified solution providers, and the directory is public if you want to check it. The Authority is careful to describe that list as a guiding one rather than an approval of any product, so treat a claimed "ZATCA certificate" with suspicion whoever offers it. The certificate that actually authorises submission is issued against your own VAT registration during onboarding, which Nama performs from inside the system.
What happens when the tax authority rejects an invoice?
The rejection and its stated reason are recorded on the invoice line itself, so the document that has to be corrected is the document carrying the error. Invoices are gathered into a submission document that can be validated and previewed before it is sent, which is where most rejections are caught.
Do we have to re-enter tax data for every submission?
No. The reference data each platform demands — tax registration numbers, identity types, tax category codes, unit-of-measure codes — lives on the customer and item records. It is entered once, and a missing mandatory field stops the invoice before submission rather than after rejection.
We operate in more than one of these countries. Is that one system or three?
One. The country-specific behaviour is configuration on the company, not a separate install or a separate module licence. A group with Saudi, Egyptian and UAE entities runs them on the same database and reports across them.
Does this cover point-of-sale receipts as well as B2B invoices?
Yes, where the authority distinguishes them. In Saudi Arabia simplified B2C invoices are issued immediately and reported afterwards, while standard B2B invoices are cleared before they are valid. In Egypt the electronic receipt system covers point-of-sale with per-device registration.
Companies already running Nama ERP
A note of thanks and appreciation to the team at Namasoft for their effort, and every appreciation for the company's products. Thank you.
Get started with Nama today
Tell us how your business runs and we will show you how Nama ERP fits it — in your language, on your infrastructure.