Available to GoMedPay Clients

Ledgr turns medical-aid remittances
and bank receipts into daily cash visibility.

For South African private practices that need to know what was paid, what is unmatched, what was reversed, what remains unclassified, and what still needs follow-up.

The Gap

The money is there.
Somewhere.

Your billing system says the claim was submitted. The medical-aid remittance says part of it was paid. The bank shows a receipt with no useful description. Then a reversal or clawback arrives quietly, weeks later.

Ledgr is built for the gap between billing, remittance and bank.

🧾
Billing system

Claim submitted, awaiting payment.

ERA remittance arrives — partial, batched, coded.
📋
Medical aid remittance

Batch payment — which claims? Which amounts? Any State 14 reversals?

Bank EFT arrives — no claim reference.
🏦
Bank statement

Receipt received. But matched to which claim? R how much short-paid?

How Ledgr Works

Six steps from bank CSV
to cash certainty.

1
Configure the practice entity

GoMedPay sets up your Ledgr entity during controlled onboarding — bank format, VAT status, financial year-end, and classification rules are checked before daily use begins.

2
Import bank CSV or supported transaction data

Upload your bank statement export (FNB, Nedbank, ABSA, Standard Bank CSV formats supported during onboarding). Each import is logged with timestamp and row count.

3
Classify receipts, expenses, transfers and exceptions

Ledgr applies your entity's classification rules to each transaction. Unclassified items surface for review so nothing falls into a suspense black hole.

4
Match receipts to remittance and practice records

Where ERA remittance data is available, Ledgr flags matched, unmatched and partially matched receipts. Reversals and clawbacks are detected and surfaced separately.

5
Review exception items daily

Unmatched receipts, reversals, unclassified transactions and stale imports appear in your Ledgr dashboard every day — not discovered at month-end.

6
Produce reporting outputs where configured

Management-accounting and VAT-related reporting outputs are available for configured entities, subject to data validation and professional review where required.

Who Ledgr Is For

Built for practices where
cash clarity matters daily.

🏥
Private Specialists

Surgeons, physicians, radiologists — any specialist with medical-aid ERA remittances and bank receipts to reconcile daily.

🏢
Multi-Entity Practices

Imaging + GP + Holdings under one group. Ledgr supports multiple entities with separate reconciliation and visibility per entity.

📊
Practice Managers

Stop spending three hours on a morning reconciliation. Ledgr surfaces exceptions in minutes — what is unmatched, reversed or unclassified.

📑
Accountants & Bookkeepers

Practices already on a billing/PMS system. Ledgr bridges the gap between the billing system and the bank — where the reconciliation work actually lives.

What Ledgr Flags

Eight exception types surfaced
before they become problems.

Unmatched bank receipts — payments received but not linked to a remittance or claim.

Unclassified transactions — rows without an account or category code.

Reversals & clawbacks — State 14 and scheme-initiated reversals detected on import.

Stale bank imports — entities where no import has been processed recently.

Missing remittance matches — ERA batch paid but no matching bank EFT found.

Suspense items — transactions that do not fit existing classification rules.

VAT-sensitive classifications — transactions flagged for VAT treatment review.

Multi-entity cash gaps — inter-entity transfers and visibility gaps across group entities.

What Ledgr Outputs

Honest about what is
available now versus configured.

Available Now
  • Bank import review — CSV upload, row count, import status log
  • Transaction list with date, description, amount, type and match status
  • Unmatched receipts count and classification exception visibility
  • Reversal and clawback detection on import
  • Unclassified transaction queue
  • Last import date and entity status dashboard
Controlled Onboarding
  • Entity classification rules — keyword-to-account-code mapping
  • Bank account configuration and multi-account support
  • ERA remittance matching workflows
  • Multi-entity setup and entity-level access provisioning
CA(SA)-Reviewed / Configured
  • Management-accounting reports (Income Statement, Balance Sheet) — configured entities
  • VAT201 support — for entities with validated VAT configuration and CA(SA) review
  • AFS-related compilation workflows — subject to ISRS 4410 boundaries and professional sign-off
  • PAYE and PIS-related reporting where applicable and configured
Professional note: VAT201, management-accounting and AFS-related outputs may require data validation, onboarding configuration and professional review. GoMedPay operates under CA(SA) leadership. Andile Memela CA(SA) is the Information Officer ([email protected]).
Pricing

Transparent. Per entity.

Ledgr is available as part of GoMedPay's Tier 2 and Tier 3 engagement — or as a standalone Ledgr access subscription for existing GoMedPay clients.

Ledgr Access
R1,950
per month, per entity — excl. VAT
Daily bank import and exception visibility
Unmatched receipt and reversal detection
Classification rule engine
Multi-bank account support
GoMedPay practice portal integration
POPIA-aligned operator controls
+ Once-off setup — R4,500 (first entity)
Request Ledgr Access →

Ledgr is included in GoMedPay Tier 2 (Recovery + Ledgr) at 6% recovery + R1,950/month. Multi-entity pricing available on request.

Questions

Frequently asked about Ledgr.

No. Ledgr is a reconciliation and cash-visibility tool, not an accounting replacement. It surfaces the exceptions — unmatched receipts, reversals, unclassified transactions — so your accountant, bookkeeper or practice manager spends less time finding the problem and more time resolving it. Management-accounting and AFS outputs are produced under CA(SA) review, not as automated replacements for professional sign-off.
Yes. Ledgr is available as a standalone cash-visibility subscription for practices that only need bank reconciliation and exception reporting, without the full RCM claims-recovery engagement. Contact GoMedPay to discuss a Ledgr-only onboarding.
Ledgr imports standard bank CSV statement exports. During controlled onboarding, your bank's CSV format (FNB, Nedbank, ABSA, Standard Bank and others) is configured and validated before daily imports begin. If your bank's format is non-standard, GoMedPay will advise during the onboarding review.
Ledgr runs inside the GoMedPay platform, which operates under POPIA Act 4 of 2013 as a data Operator. Your Ledgr entity data is isolated at the row level — no other client can access your records. Access is authenticated and gated per entity. GoMedPay's Information Officer is Andile Memela CA(SA) ([email protected]). No patient PII is stored in Ledgr — only transaction-level financial data.
Ledgr supports VAT201 and management-accounting workflows for configured entities. These outputs require data validation, correct entity configuration, and professional review before use — particularly for mixed-supply practices where VAT treatment is not straightforward. GoMedPay does not produce automated VAT returns without CA(SA)-level review. Setup is discussed during onboarding.
Ledgr supports multiple entities — for example, a GP practice, an imaging entity, and a holdings company under the same group. Each entity is configured, reconciled and reported separately. Multi-entity pricing is available on request. Access to each entity is provisioned individually through GoMedPay admin.

Ready to see what actually
reached your bank?

Ledgr is available to selected GoMedPay clients through controlled onboarding. Onboarding takes 24–48 hours. Contact us to begin.

Ledgr onboarding: 24–48 hours · Multi-entity supported · POPIA-aligned operator controls · R1,950/month per entity