Insurance approvals and claim rejections: where hospital revenue leaks, and how to stop it
Most insurance losses are not lost in a dispute with the payer. They are lost quietly: an expired approval, a missing code, a rejected line nobody resubmitted. Here is a workflow that closes those gaps.
Where the money actually goes
Ask a hospital finance manager in Cairo, Riyadh or Dubai where insurance revenue is lost and the answer is rarely “the payer refused to pay”. It is usually a chain of small process failures: a service delivered without a valid approval, an approval that expired two days before the operation, a claim sent in a layout the payer does not accept, or a rejected line that was written off because nobody had time to appeal it.
Each of these is preventable, but only if the hospital system knows about approvals, coverage and rejections at the moment the service is ordered and the invoice is issued, not weeks later when the remittance arrives. This article walks through that workflow step by step and shows how Nabd handles each step today.
The reality of insurance exchange in Egypt
In Egypt, no insurer or third-party administrator (TPA) publishes an open API for providers today. Approvals go through TPA web portals and apps, e-mail, WhatsApp, phone or fax. The payer’s answer carries an approval code, often a one-time code sent by SMS, and a validity that is typically 7 or 14 days, sometimes bound to the facility that requested it. MedNet integrates with hospital systems at contracting, and the Universal Health Insurance Authority (UHIA) uses an e-mail based approval process while its digital provider link has no public specification yet.
In the Gulf the picture is different: Saudi Arabia’s NPHIES platform is based on HL7 FHIR R4 with mandatory vendor certification, while Abu Dhabi (Shafafiya) and Dubai (eClaimLink) use XML transactions. A system built for the region has to work well with the manual channels of today and be ready for the electronic ones.
Step 1: check eligibility before the patient is seen
A large share of rejections start at registration: an expired card, a plan that does not cover the department, or a member number typed incorrectly. In Nabd, every eligibility check is recorded with its status, plan, co-payment, limit and remaining balance, a message and the payer’s reference. The check can be a phone or portal result typed by staff, or an electronic call where a connector is configured. The latest result appears on the patient’s Insurance tab.
Price quotes and charge capture then carry warnings such as coverage not started, coverage expired or eligibility failed. The payer is still billed, because the decision belongs to the hospital, but the cashier and the billing team see the risk before the invoice leaves.
Step 2: treat every approval as a tracked request
An approval is not just a number written on a file. In Nabd each pre-authorisation request is created from the planned services, a surgery case, an admission or unbilled charges, with the requested amounts priced from the payer’s price list. Its full history is recorded as events: created, sent, responded, resubmitted, appealed, extended, verified, cancelled, expired. Every event has the user, the time and the channel.
- Document channels Egyptian payers use today: a printable bilingual request, a prefilled e-mail to the payer’s approvals address, a link to the payer portal, WhatsApp or phone, each logged with what was sent and what came back.
- One-time codes: for payers that send an OTP with the approval, the code must be entered before the approval can be used, and it is masked in lists and in the audit summary.
- Validity and facility binding: when the payer gives no end date, the payer’s default validity sets it; an hourly job marks approvals past their end date as expired.
- Approved versus used: approved amounts are tracked per line against the linked charges, so the team sees what is left before the next service is ordered.
- Rejected or partially approved requests can be resubmitted or appealed, and approved ones extended, with attachments kept on the request.
Step 3: decide how strict the hospital wants to be
Some hospitals want a warning; others want the system to stop a service that has no valid approval. Nabd has a facility setting for this. In the default WARN mode behaviour is unchanged and invoicing shows a “pre-authorisation missing” warning. In BLOCK_AT_ORDER mode, charge capture links a usable approval of the same coverage (approved or partially approved, inside its validity, at the same facility when the approval is location-bound, with enough remaining amount) or refuses the charge.
Emergency visits and bed-days are never blocked. A user with the insurance override permission can grant a time-limited override per patient or per visit, with a written reason; every override is audited and can be revoked.
Step 4: send claims the way each payer wants them
Claims are built per payer and period from issued payer invoices. Because every payer has its own expectations, each claim can be downloaded in the payer’s own column layout (CSV or Excel, with its column order, headers and date format), as a plain CSV or Excel file, as a FHIR R4 Claim bundle, or as a Shafafiya Claim.Submission XML file. A printable claim statement accompanies the file. Where a payer’s electronic connector is live, the claim can be sent electronically.
Step 5: code every rejection, then work the list
When the payer answers, rejections and deductions are recorded per invoice line, not per claim. Nabd ships a catalogue of common rejection reasons (medical necessity, coverage, eligibility, authorisation, documentation, coding, pricing, duplicate, timely filing, administrative), general or per payer with the payer’s own code. The rejections report then groups amounts by code and payer, so management can see whether the problem is documentation in one department or coding for one payer.
Each rejected line is either written off (the payer receivable is reduced and the amount posts to an insurance-rejections account) or re-billed to the patient, who is then invoiced for that amount. The accounting entries are created automatically, as described in our billing and insurance overview.
Step 6: resubmit, and recover the write-off
Written-off lines are not the end of the story. They can be claimed again in a resubmission with a justification and a rejection code. The payer’s answer is recorded per line; accepted amounts reverse the write-off in the general ledger and reopen the invoice balance, and the payment is then received on the resubmission. Lines that were re-billed to the patient cannot be resubmitted, so nothing is collected twice.
Step 7: watch payer receivables every week
Payer payments are allocated to the claim’s invoices, oldest first or explicitly, and move the claim to partially settled or settled. The payer receivables aging report (0–30, 31–60, 61–90 and more than 90 days) and the rejection rate by payer show where follow-up is needed. A weekly review of these two reports, combined with the open approvals list and its SLA timers, catches most leaks before they become write-offs.
Electronic connections: what is ready and what needs an agreement
Nabd’s payer exchange is integration-ready; live connectors are added per payer after an agreement. The table below gives the exact status of each connector today.
| Connector | Status |
|---|---|
| Document channels (print, e-mail, portal, WhatsApp, phone) | Live, every exchange logged |
| Generic FHIR R4 connector (NPHIES-style eligibility, pre-authorisation, claims, remittance) | Built and tested against a test payer; enabled per payer once its endpoint and credentials are configured; not certified against NPHIES or any national profile |
| Shafafiya (Abu Dhabi) and eClaimLink (Dubai) XML | File export only, no live calls |
| MedNet, GlobeMed, NEXtCARE | Prepared connectors that show “requires agreement” until a signed agreement, the payer’s specification and test credentials exist |
Connector credentials are never stored in the database; each payer’s settings name an environment variable on the server. If you operate in Saudi Arabia or the UAE, our Saudi Arabia page and UAE page describe what a live connection there requires.
A short checklist for your billing team
- Record an eligibility check for every insured patient at registration or admission.
- Create approval requests from the planned services so the requested amounts match the price list.
- Enter OTP codes and validity dates when the approval arrives, and link the approval to the charges.
- Choose WARN or BLOCK_AT_ORDER per facility, and agree who may grant overrides.
- Export each claim in the payer’s layout and keep the printed statement with it.
- Code every rejected line, and review the rejections report by code each month.
- Resubmit justified rejections within the payer’s deadline and track the answers per line.
- Review payer aging and rejection rates every week.
Known limit: plan annual limits and deductibles are stored on the plan and shown to staff, but they are not yet consumed automatically at pricing time; this is on the roadmap.
If you are evaluating hospital systems, this workflow is a good test to run in any demo: ask the vendor to show an approval with an OTP, a blocked order, a rejected line and its resubmission. You can request a Nabd demo on fictional data and see each step, or read our checklist for choosing an HIS.