Module
E-invoicing that never stops you selling
Signing and numbering happen locally and in order; submission is separate and networked. So an authority outage queues documents instead of stopping a till, a rejected document never consumes a counter, and a trial run leaves your real sequence exactly where it was.
What it does
Signing and submission are separate
Only hashing and signing are order-dependent, and both run locally in milliseconds. Submission is networked and can wait. So an authority outage queues documents instead of stopping a till — invoicing and printing carry on.
Gapless numbering, validated first
A document is validated before it takes its place in the chain, so a rejected one never consumes a counter. A gap in an authority sequence cannot be closed afterwards, which is why the order matters.
A trial run changes nothing
Shadow mode builds, hashes and signs exactly as a live submission would, and leaves your real counter where it was. A dry run that advanced the sequence would mean your first genuinely reported invoice arrives with a number the authority has never seen.
Egypt and Saudi Arabia, one set of screens
Egyptian ETA and Saudi ZATCA Phase 2 behind one abstraction, so a business operating in both does not learn two systems. Each document type can be switched on independently.
The QR code and the tax identity
Tax registration on your company, your customers and your suppliers; per-line tax and taxable amounts as the rules require; and the QR code on the printed invoice.
A queue you can see, and retry
Every document shows its state with the evidence behind it. A rejection shows the authority's own reason rather than a generic failure, and a retry is one action rather than a re-issue.
Why teams choose it
What your business gains:
Keep selling through an authority outage: invoices are signed and printed locally, and submissions queue until the service is back.
Clean, gapless numbering: every document is validated before it takes a number, so a rejection never leaves a hole.
Go live with confidence: a trial run signs exactly like a live submission and leaves your real counter untouched.
One set of screens for Egyptian ETA and Saudi ZATCA, with rejections shown in the authority's own words and resent in one action.
Questions about this
Do you handle e-invoicing?
Yes, for Egypt (ETA) and Saudi Arabia (ZATCA Phase 2), from one set of screens.
The part worth asking about is what happens when the authority is unreachable. Signing and numbering are local and ordered; submission is separate and networked. So an outage queues documents instead of stopping a till, and a rejected document never consumes a number from your sequence.
Does it handle VAT correctly?
Yes, with per-line tax amounts and taxable amounts rather than a tax total bolted on at the end, which is what the authorities require.
One setting is worth knowing about: a whole-invoice discount can be applied before or after tax. Applied after, it does not reduce the taxable base — which overstates VAT and is incompatible with ZATCA. New workspaces on the Saudi regime are set to pre-tax for that reason.
Can an auditor see who changed what?
Yes, from the Professional plan: an audit trail on every change, with the user, the time, and the before and after values. A posted document is corrected with a correcting entry rather than edited in place, which is the distinction an auditor is actually asking about.
See it with your own data
Start a free trial, or talk to us and we will show you the module running on your own workflow.