Mediswitch and Medical Aid Claim Switching in South Africa: A Practical Guide

If you bill medical aids in South Africa, your claims almost certainly pass through a claims switch. Switching is why a claim submitted at 09:15 can come back with a response before your patient reaches the car park.

This is a neutral explainer. We build practice software, but nothing here depends on which system you run.

What a claims switch actually is

A switch is a clearing house sitting between thousands of practices and dozens of medical schemes and administrators. Instead of every practice building a connection to every scheme, everyone connects once to the switch, and the switch handles the translation, routing and responses.

In practice it does four things:

1. Validates the claim structure — member number, dependant code, practice number, ICD-10 codes, tariff codes.
2. Routes the claim to the correct scheme or administrator.
3. Returns a response — accepted, rejected, or accepted with reductions — usually in near real time.
4. Delivers remittance data later, when the scheme actually pays.

Mediswitch is one example; other switches and bureau services operate the same way. Your practice software either talks to a switch directly or hands claims to a billing bureau that does.

How a claim actually travels

Consult → clinical note → codes (ICD-10 + tariff) → claim built in your PMS
      → claims switch → scheme / administrator → response (seconds)
      → payment run → remittance advice → reconciliation in your PMS

Two points in that chain cause most of the pain. The first is coding — a note that does not carry the right diagnosis and procedure codes produces a claim that gets rejected or reduced. The second is reconciliation — the remittance rarely matches the claim line for line, and someone has to work out why.

Accurate billing starts in the consult room. HeroMed Core AI includes an AI Scribe that drafts the consultation note while you consult. For South African practices, adding the AI Invoicing Hero unlocks RocketSwitch EDI, so the claim is built from the signed note and switched from the same platform. Start a 14-day free trial.

Why claims get rejected

The recurring causes are boringly consistent:

• Membership lapsed, suspended, or dependant code wrong
• Benefit exhausted, or the service falls outside the plan option
• ICD-10 code missing, invalid, or not supported by the procedure billed
• Tariff code not valid for your discipline or practice number
• Duplicate claim, or claim submitted outside the scheme's time limit
• PMB or authorisation requirements not met

None of these are exotic. Almost all of them are catchable before submission if your software validates at capture instead of at month-end.

Real-time responses versus payment

A crucial distinction practitioners lose money on: an accepted claim is not a paid claim. Acceptance means the claim was structurally valid and reached the scheme. Payment happens on the scheme's cycle, and the remittance may reduce lines, apply co-payments, or shift amounts to patient liability.

If your process stops at "accepted", you will discover shortfalls weeks later. That is why chasing patient-liability balances promptly matters more to cash flow than almost anything else — see our cash flow guide for the 30-day version.

What to check in your practice software

1. Is switching included, or an add-on with per-claim fees? Get the per-claim cost in writing.
2. Does it validate before submission — member status, ICD-10 and tariff validity?
3. Are rejections shown as a worklist, or buried in a report someone must open?
4. Is remittance reconciliation automatic, partial, or fully manual?
5. Does it track patient-liability balances separately after remittance?
6. Can codes be generated from the clinical note, or does someone retype them?

That last question is where AI-native systems differ most. In HeroMed, the invoice and codes come from the signed clinical note, and RocketSwitch EDI (unlocked by the AI Invoicing Hero) submits the claim and reconciles the remittance — which removes the retyping step rather than reorganising it.

If you are changing switch, software, or both

Read medical aid claims switching in South Africa for the practical change checklist, and the 2026 South African buyer's guide if the software itself is under review. The single most important rule: never cut over mid-month. Finish a billing cycle, reconcile it, then switch.

RocketSwitch EDI: built-in South African scheme switching

RocketSwitch EDI is HeroMed's built-in claims switching for South African practices, unlocked by the AI Invoicing Hero. It sits inside the same platform as the diary, the AI Scribe note and the invoice, so claiming is part of the consult rather than a separate step.

• Pre-flight checks before submission. Medical aid details, member and dependant details, billed lines and tariff validity are checked before the claim leaves, and anything missing is flagged so it can be fixed first.
• Eligibility and family checks. Confirm membership and the right dependant before you bill.
• Consult to claim in one click. The claim is built from the signed AI Scribe note and invoice, with nothing retyped.
• Real-time responses where the scheme supports them. Outcomes come back line by line — accepted in full, part paid with patient liability, or rejected with the reason in plain language.
• Amend and resubmit immediately. Fix the flagged item and resubmit on the spot instead of waiting for month-end.
• Reversals where the scheme allows. Reverse a claim, correct it and resubmit from the same screen.
• RocketSwitch pipeline and bulk switching. Track every claim from invoiced to awaiting response, accepted, part paid or rejected, and switch a batch of claims in one go.
• ERAs built in. Electronic remittance advices are matched back against the original claim lines, and patient-liability balances are tracked so your front desk knows what to collect.

Less retyping, fewer rejections going back to schemes, and a clear view of what is actually owed to the practice.

Rejection reasons and what to do about each

Most rejection messages fall into a handful of buckets. The fix is usually procedural, not technical:

A practice that works rejections daily normally clears most of them within 48 hours. A practice that works them monthly writes some of them off.

Timing: what happens when

• Seconds: structural validation and the scheme response (accepted, rejected, or accepted with reductions).
• Same day: rejections should be worked and resubmitted — this is the single biggest lever on days in debtors.
• Scheme payment cycle: payment runs, typically weekly or fortnightly depending on the scheme.
• After payment: the electronic remittance advice arrives and needs reconciling against the original claim lines, with any shortfall moved to patient liability.

Switching versus direct submission

Some schemes can be billed directly, and some practices submit through a billing bureau instead. In short:

• Through a switch: one connection reaches most schemes and responses are near real time. Best default for most practices.
• Direct to a scheme: can make sense where a single scheme dominates your patient mix, but you carry a separate connection and process for each.
• Through a bureau: the bureau handles submission and follow-up for a fee or a percentage. Good if you have no admin capacity; less good for visibility, because the worklist lives outside your practice.

Whichever route you use, the questions are the same: is validation done before submission, are rejections a worklist, and is remittance reconciliation automatic?

A short claim-hygiene checklist

1. Verify membership and dependant code at check-in, not at month-end.
2. Code from the clinical note, not from memory.
3. Submit daily — never batch a week of claims.
4. Work the rejection worklist every morning.
5. Reconcile every remittance against claim lines, not just totals.
6. Invoice patient-liability balances the same week they appear.

Related reading

• Medical Practice Software in South Africa: 2026 Buyer's Guide
• Medical Billing Software in South Africa: What to Check Before You Commit
• HeroMed Core AI pricing

Related references

• Medical aid claim rejections and how to fix them
• Practice numbers and BHF verification
• ICD-10 coding for South African practices

How practice software handles this

Most of the work above only becomes manageable when your practice software does it in the background. When you compare platforms, ask specifically how each one handles switching claims and reading remittances: whether the codes are maintained for you, whether the system flags a problem before the claim is submitted rather than after it is rejected, and whether the outcome is reconciled back against the invoice automatically.

HeroMed handles this inside the same platform that holds the diary, the clinical note, the invoice and the claim, so nothing is re-typed between systems. The Core AI plan includes an AI Scribe that drafts the clinical note for the practitioner to review and sign; for South African practices, the AI Invoicing Hero adds RocketSwitch EDI for claims, and booking, reception, messaging and marketing are available as further optional AI Hero modules. If you are still comparing platforms, our buyer's guide to South African practice software sets out the questions to ask each vendor.