How to choose e-invoicing software for Phase 2 integration

The heart of Phase 2 is an XML file to the UBL 2.1 standard and ZATCA's published specification, digitally signed — not a "smart PDF" and not a proprietary file format. Ask the vendor: can I see a test invoice's XML file and check it against the official validation tools? Software that hesitates to show its file has failed the first question.

Connected to it is correct code generation: QR codes carry a TLV structure explained in the QR code guide, and standard invoices carry a cryptographic stamp from the onboarding process — the software must generate these from the invoice's actual data, not print a static image.

Integration begins with onboarding the cryptographic solution ID (CSID): registering the business, requesting a compliance certificate, passing ZATCA's simulation, then the production certificate. Ask: who runs these steps — me or you? And what happens when the certificate expires or the device changes? Serious software explains the certificate's whole life cycle, because its interruption stops lawful invoicing.

The two routes differ technically: a standard tax invoice (business to business) needs clearance — submission and approval before issue — while a simplified invoice is reported within twenty-four hours. The software must run both routes with queues, retries and a visible status per invoice, not assume a perfect connection. Ask about working offline: sites and shops cannot apologise to the network.

Most buying decisions in the Kingdom's small firms are made by an Arabic-speaking owner, and many customers read the Arabic invoice first. Evaluate the Arabic interface yourself — not from marketing screenshots — and request a fully-fielded Arabic invoice: parties, lines and tax as your customer will see them. Software whose Arabic is poor machine translation will read poorly on every invoice you send.

ZATCA publishes a directory of e-invoicing solution providers. Being listed is an informational step, not a certificate that a given solution will pass your onboarding or that ZATCA has "approved" it for your business. Beware any vendor converting a listing into an approval stamp; ask instead: how many businesses completed onboarding with your solution in a sector near mine? Verifiable numbers outrank badges.

Choose on the assumption you may leave: can you export your complete invoices (XML and PDF), customer data and items at any time, in standard formats, without an "unlocking" fee? Software that makes leaving hard sells captivity, not a service. This criterion — like the one before it — outranks price, because the cost of a forced migration years later dwarfs subscription differences.

InstaJack today is not a Fatoora-integration product: the connection is in development and not live, and you will find no claim otherwise on these pages. What it does today: tax and simplified invoices with unbroken sequential numbering, fields that hold the invoice's complete data (parties, lines, tax, payments) in exportable, portable formats, and a quotes-claims-payments record that keeps your file ready for any integration. The six criteria above are the ones we hold ourselves to publicly: when the connection arrives it will be measured by them — and until it does, compare us by them as you compare everyone else, and choose what passes them today if your wave is near.