Clearance at issue
Phase two, with the stamp and QR generated as part of the document rather than added by a second tool afterwards.
A clinic in the Kingdom has two obligations that shape the software rather than sit on top of it: invoices that clear with ZATCA as they are issued, and insurance that runs through NPHIES. Both are much harder to add afterwards than to build in.
The distinction that catches clinics out is between phase one and phase two. Phase one wanted a compliant-looking invoice. Phase two wants the invoice cleared with the authority at the moment it is issued, carrying a cryptographic stamp and a QR code that encodes the seller, the VAT number, the timestamp and the totals.
That means clearance has to happen inside the action reception is already performing. A system that generates invoices and submits them in a nightly batch is not compliant; it is compliant-ish, until somebody checks.
It also means the invoice has to survive the things a clinic invoice actually contains: an insurance share, a patient share, a package being drawn down, a discount. All of it has to come through the tax calculation intact and still clear.
Phase two, with the stamp and QR generated as part of the document rather than added by a second tool afterwards.
Not a translated layer over a left-to-right layout. Invoices, patient messages and the interface itself, right-to-left.
Eligibility answered before the service, pre-authorisation raised from the visit, and claims followed to the remittance.
Issued documents held for the statutory period, produceable with their clearance status attached.
The expensive error is not a rejected invoice. It is treating a patient whose cover did not extend to what you treated them for — and that is an eligibility problem, which happens before any invoice exists.
Eligibility checked in a separate portal, by whoever remembers, on a busy morning, is eligibility that gets skipped. It has to be part of the patient arriving, or it is decorative.
The second most expensive is rejections read one at a time. Grouped by reason they are usually two or three recurring documentation problems; read individually they look like bad luck for a year.
Compliance is the floor. Above it, the requirements that actually shape daily work in the Kingdom are a shared patient list across branches, an interface and documents that are Arabic first rather than Arabic-translated, and both calendars — Hijri and Gregorian — wherever a date is read by a person.
Insurance mix varies by location more than owners expect. A branch in one city can run a quite different set of payers and TPAs from a branch two hundred kilometres away, which means approval rules, documentation requirements and rejection patterns are per-branch facts, not company-wide ones.
And support hours are a real requirement, not a soft one. A clearance failure at nine in the morning is a reception queue; a vendor whose working day starts when yours ends turns it into a lost morning.
Ask whether invoices clear at the moment of issue or in a batch, and ask to watch it happen. Ask what the invoice does when it carries an insurance share, a patient share and a package draw-down at once. Ask whether eligibility is answered inside the arrival workflow or in a separate portal.
Then: whether rejections can be read grouped by reason rather than one at a time, whether Arabic is the interface or a layer over it, and what the retention story is for issued documents with their clearance status attached.
Six answers, and the honest ones are specific. A vendor who answers the first in terms of a roadmap is answering all six that way.
Medicolize is built for clinics and medical centres in Egypt and Saudi Arabia — packages, records, billing, insurance, WhatsApp and multi-branch reporting on one record. Request a demo to see it on your own clinic's cases.
It applies to VAT-registered businesses above the thresholds set by the authority, which covers most established clinics. The rollout has been in waves, so the date you were brought in depends on your turnover.
You can, and many clinics started that way. It means an export, a second portal and a reconciliation between two systems — which is exactly the manual work the requirement was meant to remove.
For exchanging eligibility and claims with insurers in the Kingdom it is the route. A clinic that treats insured patients will be working through it.
Yes, and in practice you want both languages on one document rather than two versions of it.
Only if it clears with ZATCA at issue and speaks to NPHIES. Both are specific integrations rather than settings, so the question is whether the vendor has them working for clinics in the Kingdom today — not whether the architecture could support them.
You need them wherever a person reads a date: appointment cards, patient messages, reports that go to a regulator. Storing one calendar and displaying both is the arrangement that does not go wrong.
Thirty minutes on how your clinic actually runs. We will call you within 24 hours.