Your Practice, Your Rules —
How to Choose a Billing Stack That Actually Fits
The right billing system isn't the most popular one, or the one your colleague uses. It's the one that matches exactly how your practice earns money. Here's how to find it without getting sold a demo.
In Article 1, we walked through why medical billing is confusing by design — and why the confusion isn't your fault. This article is different. This is the practical part: how to evaluate systems the right way, ask the questions that matter most, and arrive at a decision you can defend.
The best billing system isn't the one with the largest marketing presence. It's the one that matches how your practice earns money — and closes the gap where it currently loses it.
We'll walk through eight steps. Some take an afternoon. Some require a conversation with a vendor. All of them matter.
Know your practice risk profile before opening a single proposal
Different specialties lose cash at different points in the revenue cycle. A billing architecture that works for a high-volume radiology group is structurally misaligned with an Ob/Gyn practice managing maternity episodes. 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 | What to prioritise first |
|---|---|---|
| Solo GP | Same-day billing gaps, benefit check failures, patient co-payment non-collection | Automated front-desk benefit checks; integrated patient payment tools at check-out |
| Radiology (group) | Authorisation lapses, ERA allocation failures, modality-code mismatches | ERA automation; real-time switcher response visibility; authorisation tracking |
| Ob/Gyn | Maternity global-fee complexity, PMB non-compliance, ICD-10 coding accuracy | PMB coding validation; multi-episode tracking; pre-authorisation management |
| Interventional radiology | Multi-site procedure leakage, technical vs professional component separation | Multi-site charge capture; component billing templates; authorisation audit trails |
| Mental health / psychiatry | PMB chronic benefit compliance, session tracking, F-code accuracy | PMB mental health pathway coding; session-limit tracking per scheme |
| Allied health | Session limit breaches, treatment-plan continuity, patient balance accumulation | Session billing workflows; automated patient payment reminders |
| Foetal medicine | Specialist scan coding, scheme-specific variation limits, high-value claim exceptions | Scheme-specific coding rules; exception reporting on high-value claims |
Use this as a diagnostic prompt. The goal is to identify where your practice is most exposed — so vendor evaluation is targeted, not generic.
Run a 30-day leakage diagnostic before shortlisting vendors
Before speaking to a single vendor, extract these six reports from your current system. If you can't extract them — that is itself a finding worth writing down.
| Report | What it tells you |
|---|---|
| Same-day submission rate | Whether your cash cycle starts on the day of service or days later |
| Rejection rate by reason code | Whether you have a systemic coding, membership or authorisation problem |
| ERA allocation report | Whether payments received have been matched to individual claims, rand by rand |
| A/R ageing (30/60/90/120 days) | How much money is stuck, and in which age bucket |
| Patient balance report | The size and age of your patient-side debtor population |
| Write-off history (12 months) | Cash that was earned but abandoned — the permanent cost of unmanaged exceptions |
ERA reconciliation is a common — and often underestimated — leakage point in SA private practice. Many practices have a rough sense of what they should earn. Very few can confirm — with precision — what was actually paid, short-paid, or allocated to the wrong account. If your current stack doesn't support ERA reconciliation, or nobody has configured it: fix that before you look at anything new.
Once you have the diagnostic, you have a number: monthly cash leakage in rands. That figure becomes your evaluation benchmark. Any new architecture has to demonstrably beat it.
Separate the three roles — and demand accountability for each
Many practices treat PMS, switcher, and bureau as one vague "billing arrangement." This is where accountability goes to disappear quietly. When something goes wrong — and it will — a blurred boundary between three different vendors means everyone can point sideways.
| Role | What it means in practice | The accountability test |
|---|---|---|
| PMS / PMA | Workflow, patient records, invoicing, debtor tracking | Who owns data export? Who owns ERA import? |
| Switcher / EDI | Transmits claims to schemes; returns scheme responses | Who owns proof-of-submission? What's the response-latency SLA? |
| Billing bureau | Outsourced submission, rejection follow-up, debtor management | Who owns rejection-correction turnaround? Who owns A/R ageing? |
Before signing anything, you should be able to answer these three questions without hesitation:
Who corrects it — and by when? That person's name should be in the contract.
Who resolves it — and how? "The system handles it" is not an answer.
Who follows up — and on what cadence? Write-offs start here.
Who owns your data, in what format, at what cost? This is a POPIA question.
The seven non-negotiables in any vendor demonstration
Vendor demos are scripted for the happy path: a clean claim submitted to a cooperative scheme, paid immediately, allocated perfectly. That is not your daily reality. When you sit with a vendor, ask for live demonstrations of the failure scenarios — that is where your money actually lives.
| What to request live | What you're actually testing |
|---|---|
| Real-time claim submission | Does the claim leave with a timestamped proof-of-submission — or does it enter a queue? |
| Scheme response linked to patient record | Is the scheme response visible inside the patient record within seconds — or does it appear as a separate batch later? |
| In-system rejection correction | Can a staff member correct a rejection and resubmit without leaving the system? |
| Automated ERA import and allocation | Does the system auto-match remittances to claims at line-item level — or does someone trigger it manually? |
| Daily exception report | Are rejected and unallocated claims surfaced automatically each morning — or buried in a queue? |
| Coding validation before submission | Does the system flag invalid ICD-10 combinations, missing authorisations, scheme-specific code conflicts — before the claim leaves? |
| Data export right now | Can you export full claims history, patient records and ERA files in a usable format — today, at what cost? |
If a vendor cannot demonstrate these scenarios, treat the proposal as higher risk. Require written mitigations before proceeding — not verbal assurances.
ICD-10 and tariff validation — don't accept a generic library
South Africa uses WHO ICD-10 classification, but each medical scheme applies its own adjudication rules, PMB definitions and tariff interpretations. A clinically accurate claim can be rejected if it doesn't comply with scheme-specific coding logic. This is not an edge case — it's the daily reality of specialist billing.
Ask every prospective vendor these questions directly:
- Does your ICD-10 library include scheme-specific adjudication rules, or is it a generic WHO mapping?
- Does the system validate tariff code combinations before submission — to prevent avoidable short-payments?
- Does it support PMB coding pathways for maternity, chronic conditions and prescribed benefit claims?
- Does it flag common rejection risks for my specialty specifically — before the claim leaves the practice?
If your staff currently validate codes in a separate reference tool or spreadsheet before entering them into the PMS, you are paying a daily efficiency tax on a workflow gap. That gap needs to close with the new architecture — not survive it.
Model the total cost of ownership — not the headline price
The PMS licence is almost never the complete picture. Low entry-point pricing often conceals per-claim switching fees, benefit check charges, ERA tool subscriptions and bureau commissions that compound as volume scales.
Request a written, itemised quote for every cost layer — then model it over 12 months:
| Cost item | What to confirm in writing |
|---|---|
| PMS licence | Monthly cost; included modules; annual escalation clause |
| Per-user fees | Number of included users; additional user cost |
| Switching / EDI fees | Per-claim rate; percentage model; bundled option; any caps |
| Benefit check fees | Included or separately charged; volume caps |
| ERA tools and reporting | Included in base or subscription add-on |
| Patient payment / SMS tools | Per-use or bundled |
| Implementation and setup | Once-off fee; scope definition |
| Bureau fees (if applicable) | Fixed retainer; per-claim rate; percentage of collections — get all three options in writing |
| Data export on exit | Format; timeline; cost — this is the POPIA clause most doctors skip |
Panacea publicly discloses: R4.60 per claim for switching, or 0.5% for specialists / 0.8% for GPs. This is among the most transparently disclosed pricing models in the SA market. Before accepting a quote from any vendor, model it against Panacea's published rates at your actual claim volume. Ask vendors to justify their model against this baseline — in writing.
Under the Protection of Personal Information Act 4 of 2013, your practice is the responsible party for patient data. A vendor that restricts, delays or charges punitive fees for your own data export after cancellation may be treating patient records as a commercial retention mechanism. That clause deserves scrutiny before you sign. Get the data export terms in writing — not after.
Require bureau performance evidence — not bureau promises
A good billing bureau adds genuine, measurable value. But "we'll handle your billing" is not accountability. Value must be demonstrated with historical data from a comparable client — before you commit.
| KPI to request | What it proves | Minimum contractual requirement |
|---|---|---|
| Same-day submission rate | Claims enter the revenue cycle on the day of service | Named KPI target with defined consequences for breach |
| Rejection rate by reason code | Submission quality is improving — or at least not stagnating | Monthly reason-code breakdown, provided automatically |
| Rejection-to-correction turnaround | The bureau follows up quickly — not at month-end | SLA with named turnaround times |
| ERA allocation accuracy | Received payments are correctly matched to claims | Accuracy target with your right to audit |
| Patient portion recovery rate | Patient balances are actively managed — not written off | Recovery rate target and reporting cadence |
| A/R ageing movement | Overdue balances are reducing — not accumulating | Ageing-band targets at 30/60/90/120 days |
If a bureau can't produce this for a comparable client, you may be outsourcing work without outsourcing accountability. That is a costly arrangement — you pay for the bureau, and you still carry the risk.
Make the decision by fit — not by familiarity
At the end of the evaluation, score each vendor against a weighted framework built around your practice's specific risk profile. Here's a defensible starting point:
| Criterion | Suggested weight |
|---|---|
| Match to your practice type and specialty workflows | 30% |
| ERA reconciliation capability | 25% |
| Submission and response visibility | 15% |
| Bureau performance evidence (KPIs) | 15% |
| Total cost of ownership over 12 months | 15% |
Adjust the weights for your practice. A radiology group may weight ERA reconciliation at 35%. A solo GP may weight patient payment tools more heavily. The point is: score by what matters to your revenue cycle — not by the vendor's pitch order.
The final principle
The winning vendor isn't the one with the most features, the most familiar brand, or the best-presented proposal. It's the one that closes your highest-value leakage point — demonstrably, in writing, with named accountability for every gap in the architecture.
If a vendor's proposal can't tell you where coding validation lives, where member and benefit checks live, and how ERAs reconcile back to banked cash — the stack is not end-to-end, regardless of how the brochure reads.
Before you shortlist anyone — this week
- Run the 30-day diagnostic. Extract same-day submission rate, rejection reason codes, ERA allocation and A/R ageing. Quantify leakage in rands.
- Score by specialty fit. Use the practice risk matrix above to identify which architecture layers your practice needs most urgently.
- Request a 12-month TCO model. Ask every shortlisted vendor for full cost breakdown — switching fees, benefit checks, bureau charges and data-export terms, all in writing.
- Run the live demo test. Use the seven-point checklist. Reject scripted presentations. Require your specialty's actual rejection scenarios.
- Insert contractual protections. Data export format and timeline; ERA SLA; named accountable owner for each role; KPI-linked bureau fees for the first six months.
If you'd like help interpreting the diagnostic numbers — or want a second opinion on a vendor proposal before signing — GoMedPay provides independent Revenue Leakage Reviews for SA specialist and general practices. Not a sales pitch. A diagnostic.