Medical aid claims switching in South Africa: a practice guide

South African practices carry an admin burden that practices in most other markets simply do not: nearly every consultation ends with a claim to a medical scheme, and that claim has to travel through a switch, satisfy a specific administrator's rules and come back with a response before anyone knows what the patient actually owes.

If you have ever heard a colleague say "the switch rejected it" as though it were a fact of nature, this guide unpacks the plumbing — and where the money leaks.

The three parties in every claim

1. Your practice software — where the note, the codes and the invoice are created.
2. The claims switch — the intermediary that translates and delivers the claim electronically to the scheme administrator, and carries the response back. Switches exist so that you connect once instead of separately to every administrator.
3. The scheme administrator — who adjudicates against the member's plan, benefits and network rules and tells you what is payable.

Everything that goes wrong in medical aid billing goes wrong at one of those three handovers.

Real-time vs batch: why it matters at the front desk

Real-time submission sends the claim while the patient is still standing at reception and returns an accepted or rejected response within seconds. That single fact changes your cash cycle, because you learn the patient portion before they walk out — instead of posting a statement three weeks later and hoping.

Batch submission groups claims and sends them together. It is efficient for volume, but responses arrive after the fact, so every correction becomes a phone call to a patient who has already left and mentally closed the visit.

If you are choosing or reviewing software, this is the question to ask first: when do I find out what the patient owes?

Where rejections actually come from

For most South African practices, the overwhelming majority of rejections are administrative, not clinical:

• Membership and dependant mismatches — the member number is right but the dependant code, initials or date of birth no longer match the scheme's records.
• Benefits — exhausted day-to-day benefits, or a service the plan does not cover at all.
• Missing referral or authorisation — common in physiotherapy, occupational therapy and anything following a hospital event.
• Provider or practice number mismatch — the treating provider does not match the number the claim was submitted under.
• Coding — a code that is not valid for that scheme, that discipline or that date of service.
• Duplicates — the same service submitted twice because nobody could see the first submission's status.

None of these require clinical judgement to fix. They require the information to be correct at capture, and the rejection to land with someone whose job it is to correct it.

Networks and tariffs

Many plans are network-based: the scheme has agreed tariffs and referral pathways with a defined group of providers. Treating a network patient outside that network does not usually make the claim invalid — it changes who pays what, and the patient is the one who gets the surprise.

The practical fix is boring and effective: verify plan, benefit and network status at booking, not at billing. A patient who is told the likely portion when they book almost never disputes it afterwards.

Bureau, in-house, or a bit of both

There are three honest models in South Africa:

• Billing bureau — you send the work out; someone else submits, follows up and chases. Good when volume is high and you have no appetite for claims admin.
• In-house with a switch connection — your team submits and follows up inside your own software.
• Hybrid — routine claims in-house, hard rejections escalated.

There is no universally right answer. The wrong answer is a fourth model many practices end up in by accident: claims in one system, notes in another, invoices in a third, and reconciliation in a spreadsheet nobody trusts.

What to fix this month

1. Verify cover and network status at booking, and record the expected patient portion.
2. Submit on the day of service — same-day submission is the single biggest lever on days-to-payment.
3. Give rejections a named owner per provider, with a deadline. Shared worklists are where rejections go to die.
4. Track your top three rejection reasons for one month. You will almost certainly find one capture-field fix that removes a third of them.
5. Reconcile remittances against invoices weekly, not at month-end.

Where HeroMed fits

HeroMed comes in two products, and this is exactly the line between them. HeroMed Core AI handles the clinical and operational side — AI-assisted notes, bookings, reminders, invoicing and reconciliation. HeroMed Prime is our South African product, built for practices whose day runs on medical scheme claims and tariffs, priced in rand.

The design intent in both is the same: the note, the codes, the invoice and the payment status live in one place, so nobody has to reconcile three systems by hand to answer "did we get paid for that?"

If you are comparing us against an established claims specialist, the HeroMed vs Healthbridge comparison sets out where each is genuinely stronger. And if cash flow is the real problem behind the claims problem, start with our practice cash flow guide.