Custom Integration Development in Riyadh, Saudi Arabia

Healthcare / Hospital Group

A Riyadh-based private hospital group (4 hospitals, 12 clinics, and 3 pharmacies across Riyadh, Jeddah, and Dammam — 6,500 employees, annual revenue SAR 3.2B) operated disconnected systems that required extensive manual effort to comply with Saudi government platform requirements. The integration challenges: ZATCA e-invoicing (the group generating 28,000+ invoices daily — patient bills, insurance claims, pharmacy sales, laboratory services, and B2B invoices to corporate clients and insurance companies. 6 different billing systems across the hospitals and clinics — each needing ZATCA Phase 2 integration. B2B invoices (to insurance companies — approximately 40% of volume) requiring real-time ZATCA clearance. B2C invoices (patient direct payments — 60%) requiring 24-hour reporting. Multi-entity: the group operating through 4 legal entities (different CR numbers for each city) plus a separate pharmacy entity — each requiring independent ZATCA registration and certificate management), Mudad compliance (6,500 employees across 5 entities — monthly salary disbursement requiring Mudad submission within the mandated timeline. Payroll processed in SAP — but the Mudad file format requiring specific data transformations that the payroll team performed manually in Excel. The manual process taking 3-4 days each month — and any error in the Mudad file blocking salary transfers for the entire workforce, causing employee dissatisfaction and MHRSD compliance risk), GOSI contributions (employer social insurance contributions for 6,500 employees — calculated monthly based on employee salary, nationality (different rates for Saudi vs non-Saudi), and age. GOSI calculations performed in SAP — but GOSI frequently updating rates and rules, and the SAP configuration lagging behind GOSI changes. Result: discrepancies between SAP calculations and GOSI expectations requiring manual reconciliation — the HR team spending 5 days per month on GOSI reconciliation across all entities), Qiwa contract management (6,500 employment contracts required to be registered and maintained in Qiwa — the labour market platform. Contract data in the HR system (SAP HCM) — but Qiwa requiring specific contract formats and regular updates. New hires, terminations, salary changes, and contract renewals all requiring Qiwa updates. The HR team performing Qiwa updates manually — entering data into the Qiwa portal for each employee change. With 150+ employee changes monthly across the group — the manual process consuming significant HR time and introducing errors (delayed Qiwa updates causing visa processing delays for new hires)), and insurance claims integration (the group filing insurance claims with 15 insurance companies — each with different claim submission formats, different portals, and different rejection handling. Claims data generated in the hospital billing system — transformed manually into each insurer's required format. Monthly claim volume: 35,000+ claims. Rejection rate: 8.2% — each rejection requiring investigation, correction, and resubmission. The claims team of 12 people spending most of their time on data formatting and rejection handling rather than clinical documentation review).

We built a centralised government and partner integration platform over 16 weeks: ZATCA integration (weeks 1-6): unified e-invoicing across all entities. All 6 billing systems connected to the integration platform — each invoice captured via API or CDC and normalised to a unified format. ZATCA transformation: invoice data transformed to ZATCA XML specification with proper Arabic item descriptions (medical procedures, medications, laboratory tests — all with Arabic descriptions from the medical coding system), VAT calculation validation (healthcare services: some exempt, some standard-rated — the integration validating VAT treatment per item against ZATCA rules), and entity-specific certificate application. Multi-entity routing: each invoice automatically routed to the correct entity's ZATCA registration based on the originating hospital/clinic. B2B insurance invoices: real-time clearance (average 1.5 seconds). B2C patient invoices: batch reporting every 4 hours. Rejection handling: Arabic rejection reasons displayed to billing staff with corrective guidance — "وصف الخدمة غير مطابق لرمز النظام المنسق" (service description doesn't match HS code) with specific instructions for correction. Mudad integration (weeks 3-8): automated wage protection compliance. Payroll data extracted from SAP HCM automatically after each payroll run — employee data, salary components, bank account details, and payment amounts. Mudad file generated per specification — with proper handling of Saudi-specific payroll components (housing allowance, transport allowance, and other allowances that Mudad tracks separately). Multi-entity Mudad files generated simultaneously — each entity's file containing only its employees. Automated submission to Mudad — with status tracking (submitted, accepted, rejected, payment verified). Bank payment files generated in parallel — ensuring salary payments and Mudad submission are synchronised. The entire monthly Mudad process: from 3-4 days manual to 2 hours (automated generation + human review + submission). GOSI integration (weeks 5-10): automated contribution management. GOSI rate tables maintained in the integration platform — updated immediately when GOSI publishes changes (monitored via GOSI announcements and API). Monthly GOSI contributions calculated from SAP payroll data using the integration platform's rate engine — not relying on SAP configuration alone. Reconciliation: integration platform calculation compared against SAP calculation — discrepancies flagged for investigation before submission (catching SAP configuration lag). GOSI submission file generated and submitted per entity. Payment: GOSI payment initiated automatically after submission approval. The monthly reconciliation effort: from 5 days to 4 hours. Qiwa integration (weeks 6-12): automated contract management. Employee lifecycle events in SAP HCM triggering Qiwa updates: new hire → Qiwa contract registration, salary change → Qiwa contract amendment, termination → Qiwa contract end notification, renewal → Qiwa contract renewal. Real-time sync — employee changes in SAP reflected in Qiwa within 1 business day (vs 1-2 weeks manual). Saudisation dashboard: real-time Nitaqat zone calculation per entity — the HR director seeing whether each entity is in green, silver, or platinum zone, and what hiring actions would change the zone status. Insurance claims integration (weeks 8-16): automated claim submission and follow-up. Each of the 15 insurance companies connected through the integration platform — claims data from the hospital billing system transformed into insurer-specific formats and submitted via API (for insurers with APIs) or portal automation (for insurers with only web portals). Claim validation: automated pre-submission checks — verifying: patient coverage active, procedure covered under the plan, required pre-authorisation obtained, supporting documentation attached, and claim amount within policy limits. These checks catching errors before submission — reducing rejection rate. Rejection handling: rejected claims automatically analysed for rejection reason, categorised (documentation issue, coding error, coverage dispute, pre-authorisation missing), and routed to the appropriate team member with specific correction guidance.

The platform launched progressively over 16 weeks. ZATCA compliance: 100% Phase 2 compliance across all entities and locations by the mandatory deadline. Zero ZATCA penalties. 28,000+ invoices processed daily with 99.6% first-submission acceptance rate (0.4% rejection rate — mostly data quality issues in legacy systems being progressively resolved). Mudad compliance: processing time from 3-4 days to 2 hours per month. Zero Mudad rejection since launch (previously: 1-2 rejections per quarter requiring emergency correction). Salary transfers never delayed due to Mudad issues — employee satisfaction improved (salary-related complaints reduced 60%). GOSI compliance: reconciliation effort from 5 days to 4 hours per month. GOSI discrepancies caught before submission — zero post-submission amendments since launch (previously: 2-3 per quarter). Rate change lag eliminated — integration platform updating within 24 hours of GOSI announcements vs 2-4 weeks for SAP configuration changes. Qiwa compliance: employee changes reflected in Qiwa within 1 business day (from 1-2 weeks). Nitaqat zone visibility: real-time — the HR director making informed hiring decisions based on current Saudisation status. New hire visa processing: no longer delayed by pending Qiwa updates. Insurance claims: rejection rate from 8.2% to 2.9% — pre-submission validation catching most errors before they become rejections. Each rejected claim costing approximately SAR 450 in administrative effort to investigate and resubmit — the 5.3 percentage point reduction saving significant cost. Claims processing team: from 12 to 7 (5 redeployed to clinical documentation improvement — higher-value work that improves future claim acceptance). Claim cycle time: from 45 days average to 28 days (faster submission, fewer rejections, faster resubmission). Financial impact: compliance penalty avoidance: estimated SAR 2.8M annually (ZATCA, Mudad, GOSI penalties avoided). Staff redeployment: SAR 1.2M annually (7 fewer staff needed for manual processes — redeployed to higher-value roles). Insurance claim improvement: SAR 1.6M annually (reduced rejections, faster payments, less administrative rework). Cash flow from faster insurance claims: SAR 4.2M accelerated (shorter claim cycle time freeing working capital). Total annual benefit: SAR 5.6M (operational) + SAR 4.2M (cash flow). Platform development cost: SAR 1.8M. Annual operating cost: SAR 240,000. First-year ROI: 211% on operational benefits alone.