Billing, insurance and revenue cycle

Hospital billing, insurance approvals and claims in one revenue cycle

Nabd follows the money from the moment a service is ordered: the charge is priced and split between patient and payer, the approval is tracked until it is used, the invoice posts to the accounts, and the claim, its rejections and its resubmission are recorded line by line. Every exchange with a payer is logged.

Nabd insurance claims screen with claim status and rejected amounts
Insurance claims
  • Split at capture

    Patient and payer shares are calculated when the service is recorded, from the payer’s price list.

  • Approvals with history

    Every pre-authorisation keeps its channel, answer, approval code, validity and usage.

  • Claims in the payer’s layout

    CSV or Excel in each payer’s columns, a FHIR R4 Claim bundle or Shafafiya XML.

  • Rejections you can recover

    Coded rejection reasons, resubmission and automatic reversal of recovered amounts.

  • Doctor fees and Form 41

    Automatic accrual, payouts with withholding tax and Form 41 data.

  • ETA e-invoices and e-receipts

    Documents and a submission queue built in, for Egyptian hospitals.

Every service becomes a priced charge

Consultations, tests, scans, drugs, operations and bed-days are captured as charges by the department that performs them. The price comes from the payer's price list and coverage rules, the patient share and the payer share are split at capture time, and fixed-price packages, interim bills and final inpatient bills are built from the same charges. Documents are never edited after issue; corrections are cancellations and credit notes with their own journal entries.

A cashier built for hospital front desks

Pre-authorisations that do not get lost

Each approval request keeps a full history: when it was sent, through which channel (printed form, prepared e-mail, payer portal, WhatsApp or phone), what the payer answered, the approval code and, where the payer sends one, the verification code. Validity follows the payer’s answer or its default validity period, and approved amounts are tracked against the charges that use them. Rejected or partially approved requests can be resubmitted or appealed; approved ones extended.

A facility setting decides how strict Nabd is: warn only, or block an order without a valid approval. Emergency visits and bed-days are never blocked, and authorised users can grant an audited, time-limited override with a written reason.

Eligibility and coverage warnings

Eligibility checks, whether typed in by staff after a call or a portal check, or returned by an electronic connector, are recorded with plan, co-payment and limits, and the last check shows on the patient’s insurance tab. Expired or not-yet-started coverage raises a warning on price quotes and charges.

Claims, rejections and resubmission

Each claim can be downloaded in the payer’s own column layout (CSV or Excel, with its headers and date format), as plain CSV or Excel, as a FHIR R4 Claim bundle or as Shafafiya Claim.Submission XML. Rejections are recorded per line with codes from a catalogue of common reasons (medical necessity, eligibility, authorisation, documentation, coding, pricing and more). Rejected lines can be resubmitted with a justification; amounts the payer accepts reverse the write-off and reopen the invoice balance. Receivables aging and rejection reports per code show where revenue leaks. More in insurance approvals and claim rejections.

Connecting with payers: the honest status

Nabd is integration-ready; live connectors are connected per payer after an agreement with that payer.

Payer connection status
ChannelStatus today
Document channels (print, e-mail, portal, WhatsApp, phone)Live, every exchange logged
FHIR R4 connector (eligibility, approvals, claims)Built and tested against a test payer; enabled per payer once its endpoint and credentials are set; not certified against NPHIES or any national profile
Shafafiya / eClaimLink (UAE)XML file export only, no live calls
MedNet, GlobeMed, NEXtCAREPrepared connectors marked "requires agreement" until a signed agreement, specification and test credentials exist

Doctor fees and e-invoicing

Doctor fees follow percentage or fixed rules, accrue automatically when services are billed, and are paid out with withholding tax and Form 41 data. For Egyptian hospitals, Nabd produces ETA e-invoice and e-receipt documents and a submission queue; the live connection is configured with each hospital’s own ETA credentials. See e-invoicing for Egyptian hospitals.

Frequently asked questions

Can Nabd send approvals and claims directly to our insurer?

Nabd is integration-ready, and live connectors are connected per payer after an agreement. Until then, approvals go through the payer’s usual channels and claims are produced in its file layout, with every exchange recorded.

Does Nabd support NPHIES in Saudi Arabia?

Nabd has a FHIR R4 payer connector shaped like NPHIES messaging. It is not certified against NPHIES; the NPHIES profiles and the mandatory vendor certification are planned. See the Saudi Arabia page.

Can Nabd stop services that have no approval?

Yes, if you turn it on. The default only warns; the strict setting blocks orders without a valid approval, except emergency visits and bed-days, with audited overrides.

Does Nabd calculate doctors’ withholding tax?

Yes. Payouts deduct withholding tax and keep the data needed for Form 41.

Is the ETA connection live from day one?

Nabd produces the ETA documents and the submission queue. The live connection needs the hospital’s own ETA registration, point-of-sale registration and electronic signature, which we configure with you.

Follow one patient account from charge to claim

Pre-authorisation, invoice, claim, rejection and resubmission, on fictional data.