ZTABS builds workflow automation in Riyadh where Saudi government compliance platforms create an enormous automation opportunity. Saudi businesses manage workflows across ZATCA e-invoicing, Qiwa labour compliance, Mudad wage protection, GOSI social insurance and Absher/Muqeem immigration systems, each with distinct data requirements, submission formats, deadlines and penalty structures. ZTABS is remote-first by design from our Houston, Texas office.
A mid-sized Riyadh company may interact with six or more government platforms monthly. Manual management is error-prone (each platform having different validation rules), time-consuming and deadline-sensitive with penalty structures for non-compliance.
Workflow automation in Riyadh at a glance
| Need | What we build | Key consideration |
|---|
| ZATCA e-invoicing | XML generation, signing, submission | Phase 2 notified waves, CSID |
| Labour compliance | Qiwa contracts, Mudad salary, GOSI | Saudisation monitoring |
| Procurement | Multi-level approval, supplier management | Authority matrix, Arabic POs |
| Financial approvals | Budget-based routing, delegation | Hijri calendar, prayer-time aware |
| Immigration | Visa tracking, permit renewal | Absher/Muqeem coordination |
ZATCA e-invoicing automation
ZATCA Phase 2 (Integration Phase) requires businesses to connect invoicing systems directly to ZATCA's platform, submitting invoices electronically.
ZATCA Phase 2 scope. Actual notified taxpayer and wave determines which entities are currently required to integrate. Standard tax invoices require ZATCA clearance before the buyer receives them; the cleared invoice receives ZATCA's cryptographic stamp. Simplified invoices require reporting within 24 hours, with the EGS applying its own stamp via a valid CSID. An optional seller digital signature may be applied but is not compulsory for all invoice types. The CSID identifies and authenticates the EGS unit or device during onboarding, not each individual invoice.
E-invoice generation. Invoices in ZATCA-mandated XML format per UBL 2.1 standard with appropriate cryptographic handling based on invoice type and phase. Real-time submission to ZATCA's Fatoora platform with QR code generation for simplified invoices.
Pre-submission validation. Automated validation against ZATCA business rules before submission, catching formatting errors, missing fields and calculation discrepancies before they generate rejections or penalties.
VAT reconciliation. Automated VAT return preparation matching input VAT on purchases against output VAT on sales. Current VAT monthly versus quarterly actual thresholds determine filing frequency for each entity.
Multi-entity compliance. Conglomerates with multiple commercial registrations require ZATCA EGS registration mapped to their actual VAT taxpayer, group, branch and device topology. Unified platform with entity-specific configurations reduces duplication while maintaining separate compliance per the applicable registration structure.
Automating your Riyadh government compliance?
Tell us about your ZATCA integration status, employee count for Mudad/GOSI and ERP system. We start with the compliance workflow that carries the highest penalty risk.
Labour compliance automation
Riyadh's largest employers manage thousands of employees with complex compliance across Qiwa, Mudad and GOSI.
Qiwa automation. Automated employee lifecycle management through Qiwa's supported authorised routes: new hire contract registration, contract updates for salary and position changes, termination processing and transfer management. Saudisation monitoring with real-time ratio tracking and alerts when ratios approach current Nitaqat band thresholds based on entity size and activity.
Mudad automation. Monthly salary file generation from payroll data in Mudad-compatible format through authorised submission channels. Automated validation against Mudad requirements including bank account verification, employee ID matching and salary amount validation. Submission before the monthly deadline with buffer for exception resolution. Rejected records automatically routed to HR with Arabic error descriptions and suggested corrections.
GOSI automation. Monthly contribution calculation from payroll data applying configured effective-dated rates based on actual insured branch, subscriber cohort and earnings. The new Social Insurance Law applies to entrants with no prior civil or social insurance periods before 3 July 2024 with a staged annuity contribution schedule; the official 1 July 2026 rate is 10% each for employer and employee for this cohort. Old-law rates apply separately to existing subscribers. Occupational hazard and SANED unemployment insurance branches have distinct scope and rates. Automated submission with employee registration when hired and deregistration when employment ends.
EOS calculation. End of service benefit calculation uses last wage with actual statutory eligibility conditions. Workflow automation applies the correct calculation based on employment duration and termination type.
Procurement and financial approvals
Saudi organisations operate with formal approval hierarchies reflecting Saudi business culture where defined authority levels are respected.
Purchase approvals. Multi-level approval chains based on SAR amount thresholds with configurable routing per department, category and project. Mobile approval enables decision-making from project sites and during travel.
Arabic-first design. Arabic workflow interfaces, approval forms, notifications and audit trails are scoped and tested as part of the engagement. Bilingual support for organisations with mixed Saudi and expatriate teams. Actual Arabic coverage for templates, documents and notifications is agreed and validated before deployment.
Nafath integration. National Single Sign-On digital identity verification for accessing government services, signing contracts and authorising transactions. Nafath, Absher and Muqeem have actual organisation, service, user and permission scopes.
SPL addressing. SPL National and Short Address apply within their actual scope, distinct from Dubai Makani or other addressing systems.
Mega-project and contractor management
Vision 2030 mega-projects require complex contractor coordination and compliance workflows.
Contractor onboarding. Contractor qualification verification, insurance confirmation, safety certification, site access provisioning and training completion tracking. Multi-tier subcontractor management with compliance rollup to prime contractor.
Progress reporting. Automated progress tracking against project milestones with percentage completion, earned value calculation and variance analysis. Dashboard visibility for project sponsors and government stakeholders.
Invoice reconciliation. Contractor invoice verification against PO, contract terms, work completion certificates and retainage calculations. Multi-level approval with delegation during travel and site visits.
Saudisation tracking. Real-time Saudisation ratio monitoring against current Nitaqat requirements with automated alerts when ratios approach band thresholds. Recruitment workflow prioritisation based on Saudisation impact.
Document management. Official Arabic document generation, routing, approval and archival. Government correspondence, contracts and regulatory filings with proper Arabic formatting, dating and organisational signatures. Complete document lifecycle from drafting through distribution with version control.
Vendor prequalification. Supplier assessment against technical, financial and compliance criteria. IKTVA scoring support for actual Aramco procurement where the entity participates in that programme. Automated questionnaire distribution, response collection, evaluation scoring and committee routing with audit trail for each vendor decision.
PDPL and data protection
PDPL scope. Applies with actual controller, activity, data purpose and transfer mechanisms. Legitimate interest excludes public entities and sensitive data with actual assessment requirements. Marketing consent and withdrawal have actual conditions that differ from GDPR.
Health data. Health-derived referral and appointment data is not automatically ordinary simply by separating records from clinical systems. The classification depends on the nature of the information.
Sector regulation. SAMA, CST and NCA have actual entity, classification and contract scope. The applicable regulatory framework depends on the entity and activity.
IKTVA. Actual Aramco procurement programme with specific scope, scoring methodology and entity eligibility conditions, not applicable to all Saudi organisations. Workflow automation for IKTVA-qualifying companies supports documentation and compliance tracking.
How delivery works
ZTABS is remote-first by design from our Houston, Texas office, delivering workflow automation with Arabic-first design and Saudi system integration.
ERP integration. Connection to SAP S/4HANA, Oracle Cloud ERP and Microsoft Dynamics 365 through supported APIs and integration routes for the applicable edition and licence. Integration scope depends on actual vendor permissions and available interfaces for each product version.
Platform selection. n8n self-hosted for compliance workflows with local primary processing. The applicable n8n edition determines execution limits, features and support scope. Power Automate for Microsoft ecosystem organisations. Temporal for complex long-running workflows. Custom engines for ZATCA-specific automation.
Trigger and event semantics. Workflows triggered by invoice creation, payroll completion or compliance deadlines handle stale, duplicate and out-of-order events. Bounded retry with backoff, timeouts and unknown-outcome reconciliation before replay.
Human approval boundaries. Compliance exceptions, financial commitments and regulatory submissions include human gates. Automation prepares and routes; authorised staff decide.
Deterministic rules versus AI inference. ZATCA validation, Mudad formatting and GOSI calculation use deterministic rules. AI-assisted document classification requires confidence thresholds and human review.
Illustrative Example
Hypothetical: Riyadh construction conglomerate automating compliance
A Saudi construction conglomerate with 12,000 employees across 28 active projects processes 3,200 monthly e-invoices, 12,000 salary records to Mudad, 12,000 GOSI contributions and 2,000 immigration transactions. A 22-person compliance team spends 90% of time on routine government platform submissions.
Automation would unify compliance data from SAP through supported APIs for the applicable edition, automate ZATCA e-invoice generation with pre-submission validation, generate Mudad salary files with automated bank account verification, calculate GOSI contributions with configured effective-dated rates per subscriber cohort and track immigration permit expiry dates with renewal alerts.
Assumptions: SAP S/4HANA supports standard OData API integration for the applicable licence, the compliance team transitions to exception handling and monitoring, and government platform APIs remain stable. Residual risks include government platform changes requiring integration updates, complex employment arrangements needing manual GOSI classification, and the ongoing need for compliance expertise regardless of automation level. No guarantee of specific penalty reduction or staff reallocation numbers.
This is a hypothetical scenario for illustration. Actual scope, timeline and cost depend on your requirements.
Cost and timeline
Custom workflow automation follows the published cost guide. These are planning ranges for custom build scope, not minimums for every configuration task.
| Tier | Range | Timeline | Example |
|---|
| Internal Tool | $25K to $60K | 6 to 14 weeks | ZATCA e-invoicing connection |
| Business Application | $60K to $150K | 14 to 28 weeks | Labour compliance unified |
| Enterprise Platform | $150K to $300K | 28 to 40 weeks | Full compliance platform |
| Large-Scale System | $300K to $500K+ | 40 to 60+ weeks | Multi-entity with HA and DR |
Optional recurring costs depend on actual platform edition, plan tier, execution volume and support contract. Ongoing support depends on scope and SLA requirements.
2026 US business application planning benchmark
A representative 2026 US business-application build at this scope typically involves multi-role access with SAML or OIDC single sign-on, a workflow engine orchestrating approval chains, ERP and HRIS integrations, audit logging, and applicable SOC 2 or HIPAA readiness preparation where the engagement requires it. That combination touches front-end, back-end, integration, infrastructure and compliance architecture work. The Business Application and Enterprise Platform tiers in the table above reflect this benchmark scope.
Budget look right for your Riyadh project?
Share your ZATCA status, employee count, ERP system and compliance requirements. We provide a scoped estimate based on the published guide ranges.
Evaluating a workflow automation proposal
Use these six criteria to compare any vendor proposal, including ours.
| Criterion | What to verify |
|---|
| Scope, deliverables and acceptance | Written scope with named deliverables, acceptance criteria and what is explicitly excluded |
| Data, integration and action authority | Which systems are accessed, what editions, licences or interfaces are required, who retains data ownership, and which party holds filing, payment or clinical action authority for each external system |
| Baselines, evaluation and acceptance | Current-state metrics, how improvement will be measured, held-out evaluation when AI components are used, and conditions for accepting each milestone |
| Operational exception, reconciliation and support | How the system handles partial failures, duplicate events, unknown-outcome reconciliation before replay, operating handover and after-hours incidents |
| Staff and user languages, resources and coverage | Agreed staff working languages, user interface languages, document and reviewer languages, translation and review resources, tested locale and template coverage, and key personnel commitments |
| Commercial terms, change control and exit | Payment schedule, change-order process, IP ownership, support responsibilities and data-export provisions at contract end |
When this engagement is not the right fit
- A point ZATCA solution covers the requirement. If a standalone ZATCA e-invoicing product covers requirements without broader workflow automation, evaluate those first.
- The engagement requires on-site embedded staff. ZTABS is remote-first by design. If the proposed engagement requires daily on-site coverage, the customer should arrange an on-site team or select a provider who offers that model.
- The scope requires the customer's own mega-project procurement or security clearances. Specific NEOM, Red Sea or Qiddiya procurement and security processes are the customer's responsibility to obtain.
- The engagement requires separately contracted professional advisory. Arabic copywriting, legal counsel and compliance advisory are separately contracted from qualified professionals, not included in workflow automation scope.
Risks and mitigations
Government platform changes. ZATCA, Qiwa, Mudad and GOSI platforms evolve with new requirements and API changes. Architecture supports configuration updates. Monitoring detects submission failures early.
Multi-entity complexity. Conglomerates with multiple legal entities require separate compliance mapped to the actual VAT taxpayer, group, branch and EGS device topology. Unified data layer with entity-specific submission routing.
Arabic document precision. Official Arabic document formatting requires Saudi government standards. Template-based generation with validated formatting, proper Arabic dates and culturally appropriate phrasing. Template coverage agreed and reviewed as part of engagement scope.
Irreversible submissions. ZATCA invoices, Mudad salary files, GOSI contributions and Qiwa transactions cannot be easily reversed after submission. Pre-submission validation, review workflows, owner-approved action boundaries and approval gates reduce exposure.
Subprocessor assessment. Full stack assessment determines actual data flows including connected services and subprocessor terms. Sector regulators (SAMA, NCA) have actual requirements based on entity classification and contract scope.
Ongoing support model
Post-deployment support covers platform management, workflow optimisation, integration maintenance and expansion planning. Monthly automation reports show execution volumes, error rates, processing times and business impact.
Operating handover. Documentation for ongoing operation, exception handling and troubleshooting. Recovery drills validate that the client's team can diagnose and resolve common failure modes independently. The goal is operational independence, not ongoing consultant dependency.
Ready to automate your Riyadh workflows?
Tell us about your ZATCA status, labour compliance requirements and operational bottlenecks. We build from the highest-value workflow.