Billing Systems Are Complex —
You're Not Alone
Every year, South African clinicians are handed a complicated market and expected to make confident procurement decisions without a proper map. Here's the map.
If you've ever walked out of a vendor demo feeling more confused than when you walked in — welcome. You're in good company. And more importantly: the confusion you felt is not a reflection of your ability. It's a reflection of how this market works.
Medical billing vendors in South Africa sell more than software. They often sell the impression of a solved problem. Practice management platforms, EMR systems, EDI switching networks, billing portals, bureau services — sometimes packaged together, sometimes split across separate invoices that add up to more than anyone agreed to in writing.
Labels shift depending on who's in the room. Pricing models change by practice size. And demos are typically scripted for the happy path — failure scenarios rarely feature.
The problem is not that doctors choose badly. The problem is that they're handed an incomplete map and expected to navigate anyway.
This article is about understanding why the confusion exists — because once you understand the structure, the decisions become a lot clearer. Articles 2, 3 and 4 in this series take you from understanding to action: evaluating systems, migrating safely, and comparing what's actually available in South Africa right now.
Medical billing isn't software. It's a chain.
A single patient consultation doesn't go directly from your examination room to your bank account. It travels through a series of hand-offs — and each one is a potential failure point.
Most clinicians see two ends of this chain clearly: the booking at the front, and the bank statement at the back. Everything in the middle is managed by staff, software and third parties — and when any link breaks, cash doesn't disappear loudly. It leaks quietly, until your accounts receivable report starts telling you last month's truth about a problem that started three months ago.
The core procurement mistake
Most practices buy billing software. What they actually need is a billing architecture. A polished interface can still leave claim responses, ERA allocation, patient balances and rejection follow-up completely exposed. The software is only one layer of the chain.
The 8 layers most doctors don't know they're building
South Africa's private healthcare environment is structurally complex. Medical schemes each have distinct adjudication rules, tariff interpretations, benefit structures and authorisation protocols. A claim that passes one scheme's rules can fail another's — for reasons that often only become visible after follow-up time has already been lost.
When you buy "billing software," you're actually assembling — knowingly or not — a stack of distinct functions. Here's what that stack actually looks like:
| Billing layer | Core function | Who typically owns it |
|---|---|---|
| PMS / PMA | Patient records, scheduling, invoicing, debtor tracking | Practice / software vendor |
| EMR | Clinical notes, prescriptions, procedure records | Clinician / software vendor |
| Switcher / EDI | Electronic claim transmission to schemes; response delivery back | Switching network (e.g. Healthbridge, Jnx, SwitchOn) |
| Benefit checks | Pre-encounter membership and benefit verification | Practice / PMS vendor |
| ICD-10 & tariff validation | Rules engine that catches avoidable rejections before submission | PMS vendor / billing bureau |
| ERA reconciliation | Matching scheme remittances to individual claims, rand for rand | Billing bureau / practice |
| Patient payment tools | Co-payments, shortfalls, self-pay balance management | Practice / payment platform |
| Billing bureau | Outsourced submission, rejection follow-up, debtor management | Bureau (if used) |
The PMS showed a claim as "submitted." But the switcher response was sitting in a separate queue nobody checked daily. By the time the practice caught it, R18,400 across Discovery and Bonitas claims had moved from current work to 60-day A/R. Nothing broke loudly. It just leaked.
Payment timing obligations and valid account requirements make proof-of-submission, response monitoring and follow-up discipline commercially significant. A claim marked "submitted" inside your PMS does not automatically prove the scheme received a valid account for payment processing.
The five hidden costs — and what your monthly invoice doesn't show you
The invoice from your billing vendor shows what you agreed to pay. It doesn't show everything you're paying. A billing stack in South Africa often expands into five distinct cost lines — and many practices only discover the full picture when they go to switch.
| Cost centre | Where the leakage hides |
|---|---|
| PMS licence fees | Base system cost — often per user, per site, or per activated module |
| Switching / EDI fees | Per-claim, bundled or percentage-based — scales as your volume grows |
| Benefit check fees | Frequently excluded from base pricing and charged separately per query |
| Patient payment & SMS tools | Per-message costs, payment portal fees, and collection commissions |
| Billing bureau fees | Fixed retainer, per-claim rate, or percentage of collections — sometimes all three |
A headline PMS quote of R800 per month became R12,460 once 2,000 claims at R0.45, 600 benefit checks at R12, and SMS/payment add-ons were counted. The cheapest quote was not the cheapest architecture. By about R11,600 a month.
Panacea publicly discloses its pricing: R4.60 per claim for switching, or 0.5% for specialists / 0.8% for GPs. This is among the most transparently disclosed pricing models publicly available in the SA market. Before accepting a quote, model it against Panacea's published rates at your practice volume. Ask vendors to justify their rates against this baseline — in writing.
Why clinicians choose the wrong system — and why it isn't their fault
Here's the thing about the choices clinicians make: they're not irrational. They're understandable responses to a market that was never designed for transparency. The problem isn't the doctor. It's the information environment.
| How the choice gets made | What the market doesn't tell you |
|---|---|
| A colleague recommended it | Their practice profile, billing model and staff capability may make the comparison meaningless for yours |
| The demo looked polished | Demos show the happy path. They rarely cover high rejection rates, ERA failures or ageing A/R |
| It looked cheaper | Low licence fees can live alongside high per-claim leakage elsewhere in the stack |
| The bureau promised "full support" | "Full support" has no contractual definition. It often means nobody is accountable for anything specific |
| Staff used it before | Familiarity isn't suitability. The same system performs very differently across practice types |
| "It's fully integrated" | Integration only protects cash if it covers the full revenue cycle — not just the scheduling front-end |
If a vendor cannot show you how rejections, ERAs and patient balances move from exception to resolution — with named owners and SLA timelines — pause the procurement. A polished demo may not reveal gaps in revenue controls.
The better question to ask
Most clinicians ask: Which billing system is best?
The better question — the one that actually leads somewhere useful — is sharper than that:
Which billing architecture matches my practice type, claim complexity, billing volume, staff capability and cash-flow risk profile?
The answers are different for every specialty. A radiology group billing R4 million a month needs something structurally different from a solo GP seeing 25 patients a day. Choosing from the same vendor shortlist without accounting for that difference is how practices end up paying for systems that solve the wrong problem.
| Practice type | Where cash most often leaks |
|---|---|
| Solo GP | Same-day billing gaps, benefit check failures, patient co-payment non-collection |
| Radiology (group) | Authorisation management, ERA allocation failures, modality-code accuracy |
| Ob/Gyn | Maternity episode billing, PMB compliance, ICD-10 coding accuracy, patient shortfalls |
| Interventional radiology | Multi-site charge capture, technical vs professional component separation, hospital authorisations |
| Mental health / psychiatry | PMB chronic mental health benefit compliance, session tracking, F-code accuracy |
| Allied health | Session limit tracking, treatment plan continuity, lower-value patient balance recovery |
| Foetal medicine | Specialist scan coding, scheme-specific rule compliance, high-value claim exceptions |
| Dermatology | Separating aesthetic from medical billing, procedure-code accuracy, scheme-specific exclusions |
Map your own practice before evaluating anything
The first practical step is not to open a vendor website. The first step is to identify which stages of your billing chain have a named owner — and which stages are silently failing with no one accountable.
| Revenue cycle stage | Named owner today | How you verify it's working |
|---|---|---|
| Patient billing details captured at booking | Named person | Daily booking completeness report |
| Benefit check completed before encounter | Named person | Benefit check exception list |
| Claim captured and submitted same day | Named person | Same-day submission report |
| Claim responses monitored daily | Named person | Switcher response queue report |
| Rejections identified and corrected | Named person | Reason-code ageing report |
| ERAs reconciled to individual claims | Named person | Line-item ERA allocation report |
| Patient portions followed up | Named person | Patient balance recovery report |
Under the Protection of Personal Information Act, patient data cannot become a hostage in a vendor relationship. Your practice remains the responsible party — even when a software vendor or bureau performs parts of the workflow. This matters especially when you're considering a system change. Article 3 covers the POPIA data-export requirements in detail.
A useful test
If your practice cannot answer — with precision — what was billed, submitted, rejected, paid, short-paid, allocated and still stuck as of today, the problem is bigger than software. It's a control problem wearing a software costume.
What to do this week
- Map your billing chain. Name the owner of each stage above. Any stage with no named owner is your first finding.
- Pull your rejection report. Identify the top three rejection reason codes from the last 30 days.
- Request itemised invoices. Ask your PMS vendor, switcher and bureau to break down every cost line for the last three months.
- Quantify leakage in rands. Compare billed value, paid value, patient portions collected, write-offs, and unresolved A/R.
- Read Article 2. Once you know where your practice is losing money, the evaluation framework in Article 2 tells you what to look for in a new architecture — and what questions to ask any vendor.
If the numbers above feel difficult to pull together — or if you want independent eyes on what they mean before committing to any change — the Revenue Leakage Review at GoMedPay is designed exactly for this moment: before you sign anything new.
References
- Medical Schemes Act 131 of 1998 — including Section 59 provisions
- Council for Medical Schemes: Medical Schemes Act Regulations, Regulation 6 and PMB provisions
- Protection of Personal Information Act 4 of 2013
- HPCSA Booklet 9: Guidelines on the Keeping of Patient Records
- Panacea Medical Software — Pricing
Free Template
Get the Pre-Expiry Claims Register
Track every claim nearing the 120-day Regulation 6 deadline.
Does this apply to your practice?
GoMedPay's 9-Checkpoint System addresses these issues directly. An Unpaid Claims Review shows the exact rand exposure — no obligation to proceed.
Book an Unpaid Claims Review