ZATCA e-invoicing
Tax and simplified invoices with a QR code, invoice signing, and Phase 2 Fatoora onboarding once the organisation registers.
Solutions
Integration with government platforms
Connecting systems to Saudi government platforms through official channels: e-invoicing runs in our systems today; Nafath, the Government Service Bus and others are built within an entity's project.
Government platform integration
We connect systems to Saudi government platforms through their official interfaces and channels. This page separates clearly what runs in our systems today from what we build within an entity's project.
Live in our systems today
Wage protection file
A wage protection file ready to upload, produced from payroll. The organisation uploads it to the platform itself; a direct connection is built on request.
Platforms we integrate within an entity's project
Each integration is built once the entity has access to the platform, and tested in that platform's sandbox before go-live.
National Single Sign-On (Nafath)
Sign-in for beneficiaries and staff with their national identity instead of passwords.
Government Service Bus
Data exchange between the entity and other agencies through the approved integration channel.
Identity and registry checks
Verifying personal and commercial-registry data at the official source instead of typing it in.
National Address
Address verification and auto-fill in forms and requests.
HR and social insurance
Employee and wage data sent to the competent platforms instead of uploading files by hand.
Health insurance
Eligibility, approvals and claims for healthcare providers through the approved national platform.
Government payments
Issuing, collecting and reconciling bills automatically with the accounts.
Platform names are used only to describe the type of integration. They do not imply a partnership with, or endorsement by, the organisations that own them.
How we build an integration
Analysis
We define the data exchanged, its direction and frequency, and the access the platform requires.
Secure design
Encrypted connections, keys kept out of the code, and the least privilege each service needs.
Sandbox testing
Every scenario is tested, including failures and rejections, before anything goes live.
Operations and monitoring
A log of every request and its result, alerts on failure and a dashboard for the owner.
Integration FAQ
Have you integrated with these platforms before?
The integrations live in our systems today are listed in the first section of this page. We build the ones in the second section within an entity's project.
Who requests access to the platform?
The entity or organisation that owns the system obtains access from the platform concerned. We prepare the technical requirements, then build and test the integration.
What happens if the external platform goes down?
We design integrations with retries, queues and a log of every request, so no transaction is lost and the owner is alerted on failure.
Request an integration study for your system
Tell us which platforms you need to connect to, and we will come back with the requirements and the timeline.