From retail transactions to secure, structured e-invoicing. Explore the unsigned UBL XML preparation workflow, learn the mandatory clearance/reporting routes, and see exactly what requires business onboarding before live use.
MCHILS develops the software. Each subscribing retailer owns its invoices, seller VAT identity, fiscal EGS and authorization. Explore the separated merchant/branch/EGS architecture using only fictional examples.
Open Multi-Tenant Provider Console ↗Read-only status from the deployed Retail backend. The buttons below open actual demonstration workspaces.
Real B2B tax invoices are submitted as structured XML for ZATCA clearance. The cleared document must be obtained before presenting it to the buyer.
A compliant simplified tax invoice requires a locally generated cryptographic stamp and Phase 2 QR data, followed by ZATCA reporting within 24 hours of issuance.
Legal business name (Arabic/English), VAT number, CRN, registered national address and branch setup.
Generate secure device keys and CSR with exact ZATCA attributes; obtain OTP and Compliance CSID via FATOORA.
Verify UBL XSD/Schematron, canonical hash, signatures, Phase 2 QR and sample invoice/credit/debit-note tests.
Complete compliance checks; securely store certificates and credentials outside public web folders.
Install signed XML transport, request/response tracking, retries, deadline alerts, monitoring and archiving.
Finance-approved settlement and tax reconciliation, audit logs, compliant credit notes and independent sign-off.
Inside each Company workspace, select the floating ZATCA 2 button to generate a fictional XML draft from a sample order.
Production onboarding must be tied to the correct Saudi legal entity. We can finalize verified seller fields, EGS registration, signing and a secure ZATCA sandbox compliance run only after the responsible business owner authorizes the credentials. Do not enter OTPs, passwords or private keys in a public demo.
Open commercial pilot checklist ↗