Trust Accounting Software in South Africa: LPC Rules, POPIA, Audits and What to Budget
Choosing trust accounting software in South Africa means fitting the LPC accounting rules, the annual trust audit and POPIA. Here's what to demand from vendors, what it typically costs in ZAR and USD, and when to switch.
What Section 86 and the LPC Accounting Rules Demand of the System
If your firm holds client money, your trust accounting software is the evidence your auditor, the Legal Practice Council (LPC) and the Legal Practitioners' Fidelity Fund will rely on. Recording transactions isn't enough. On any given day, the system must show that every rand in the trust bank account belongs to a named client and that no client is overdrawn. Most firms find the gaps only when a monthly reconciliation won't balance or an auditor qualifies the report.
The legal framework has two layers. The Legal Practice Act 28 of 2014 sets the obligations. Under the Section 86 trust account provisions, a firm that receives money for clients must keep a trust banking account. It may invest surplus trust money in interest-bearing trust investment accounts, and it may invest money for a specific client on that client's instruction, with the interest going to that client. The Legal Practice Council trust account rules then set out the records, reconciliations and audit reporting that prove compliance. Rule numbers and wording have been amended before, so confirm current references with your auditor rather than relying on a vendor's brochure.
In software terms, the system must reliably do the following:
- Separate trust and business ledgers, with the trust creditors' ledger tied to the trust bank account and investment accounts. Moving money from trust to business (fees transferred against an issued invoice, for example) should happen only through a controlled, documented entry.
- Prevent or flag debit balances on any trust creditor's ledger. A client ledger in debit means you've paid out another client's money. Good systems block the payment. Weaker ones only warn you.
- Track Section 86 investments separately, by type: surplus-fund investments where the interest goes to the Fund, and client-instructed investments where the interest goes to the client. Interest should be allocated correctly and reported per investment.
- Produce a monthly reconciliation of trust bank balances, trust investments and the trust creditors' list, with differences explained and the reconciliation kept as a record.
- Keep an audit trail. Entries are reversed, not deleted. Every record shows the user and a timestamp, and closed periods are locked.
- Retain records for the prescribed period, in a form that can be printed or exported for inspection.
Treat these as minimum requirements, not a wish list. Ask each vendor which version of the LPC Rules its reports are built to, and how quickly it shipped changes after the last amendment. Have your auditor or a practice-management adviser confirm how the current rules apply to your firm.
The Annual Trust Audit: Reports Your Auditor Will Pull From the System
Every firm that runs a trust account must have its trust records audited each year by a registered auditor, and the report goes to the LPC within a prescribed period after financial year-end. Check the current deadline with your auditor. Your Fidelity Fund certificate for the next period depends partly on a clean, on-time filing. So the real test of a system is whether your auditor can get what they need without your bookkeeper spending a fortnight rebuilding spreadsheets.
Before signing, ask the vendor to show you each of these as a live report, not a screenshot:
- Twelve monthly trust reconciliations for the year, each showing the bank statement balance, outstanding deposits and payments, investment balances and the trust creditors' total.
- Trust creditors' list at any historical date, not just today. Auditors test balances at year-end and at other dates.
- Debit balance exception report showing any client ledger that went into debit during the year, when it happened and how it was fixed.
- Section 86 investment schedule listing each investment, its client or Fund designation, interest earned and interest paid out.
- Trust-to-business transfer report linking each transfer to an invoice or written authority.
- User activity and reversal log for the period.
Easy to miss: the auditor should have read-only access. Cloud platforms often offer an auditor or accountant role. If yours doesn't, you'll export to Excel, which brings back the manual errors the software was meant to remove.
Red flag: a vendor that says its reports are "customisable to whatever your auditor wants" but can't name South African audit firms that already accept its standard output. For a 5- to 30-practitioner firm, standard LPC-format reports that auditors already recognise will save more audit hours than any custom configuration.
Attorneys are also accountable institutions under the Financial Intelligence Centre Act (FICA). Trust accounting and FICA compliance needn't live in the same product, but your client-onboarding and risk-rating records should tie to the matters that hold trust money. Find out whether the system connects them or leaves them in silos.
POPIA for Law Firms: Hosting, Operators and Cross-Border Data
Trust records hold some of the most sensitive personal information a firm keeps: bank details, ID numbers, property transactions, estate assets. POPIA for law firms applies directly. You are the responsible party. Your software vendor and its hosting provider are operators under the Protection of Personal Information Act.
Three provisions matter most when choosing a vendor. First, you need a written contract with each operator requiring confidentiality and appropriate security measures. Second, operators must notify you of a suspected breach so that you can notify the Information Regulator and affected clients as soon as reasonably possible. Third, transfers of personal information outside South Africa are restricted. They're generally allowed where the recipient is bound by a law, binding corporate rules or an agreement providing adequate protection, or where another statutory ground applies, such as consent.
Hosting location matters, but it isn't a dealbreaker. Microsoft Azure, AWS and Google Cloud all operate in South Africa, and many local legal vendors host there. An international vendor hosting in the EU, UK or elsewhere can still be lawful, but you must document the transfer basis, and the paperwork has to hold up if a client or the Regulator asks.
Questions to put to every vendor in writing
- Where is primary data stored, and where are backups and disaster-recovery copies kept? These are often in different countries.
- Which sub-processors (hosting, email, support desk, analytics) can access client data, and in which countries?
- Will you sign an operator agreement that meets POPIA's requirements, or only your standard global data processing addendum?
- What is your breach notification commitment in hours, and who at the firm is notified?
- Is data encrypted at rest and in transit, and is multi-factor authentication enforced for every user, including support staff?
- How do we get a full export, including the audit trail, if we leave, and in what format?
Your information officer should sign off on the answers. Firms with cross-border clients or offices may also fall under the GDPR, the UK GDPR or other regimes at the same time. A data protection lawyer can map those overlaps before you commit to a hosting region.
Local Versus International Vendors
The South African market splits roughly in two. On one side are local legal accounting specialists such as LegalSuite, AJS and GhostPractice, built around LPC trust rules, Section 86 investments and South African banking. On the other are international practice management platforms such as Clio, which offer strong matter management, client portals and integrations, but designed their trust features around other jurisdictions' rules. Confirm each vendor's current capabilities directly, since products change.
For most South African firms holding meaningful trust balances, a local specialist is the safer core system. LPC-format reports, local bank statement imports and auditor familiarity are already there. International platforms make sense mainly for firms with little trust activity, such as advisory or litigation boutiques that rarely hold client funds, or for firms already running them across several countries and willing to pair them with a locally compliant trust ledger.
| Criterion | Local legal accounting specialist | International practice platform |
|---|---|---|
| LPC-format reconciliations and audit reports | Usually standard | Often need custom reports or a separate trust ledger |
| Section 86 investment tracking | Typically built in | Rarely native; check carefully |
| South African bank statement import | Common for major local banks | Varies; may rely on manual CSV import |
| Data hosting in South Africa | Often available | Often EU, UK or US; needs a POPIA transfer basis |
| Matter management, portals, integrations | Adequate to good | Often stronger |
| Auditor familiarity | High | Low to moderate |
| Support hours | South African business hours | May be offshore or follow-the-sun |
Red flags on either side: trust features a firm administrator can switch off, no period locking, bank feeds that post straight to client ledgers without review, or a vendor that can't give you two or three South African reference firms of similar size.
Many firms also run a general ledger such as Sage or Xero for business accounts. That's fine as long as trust stays in the legal system and the integration carries only business-side entries. If you're comparing law firm accounting software South Africa options, count that integration as part of the evaluation.
What to Budget in ZAR and USD
The figures below are typical 2026 market ranges for South African firms, converted at roughly R18 to the US dollar. Actual pricing varies with contract length, user count, modules and negotiation, so get written quotes. International vendors may bill in USD, GBP or EUR, which adds exchange-rate risk to every renewal.
| Cost item | Indicative ZAR range | Indicative USD range | What drives it |
|---|---|---|---|
| Cloud subscription, per user per month | R600 to R1,800 | $35 to $100 | Modules (trust, billing, conveyancing, FICA), user type, contract term |
| On-premise licence (where still offered), per user once-off | R8,000 to R25,000 | $450 to $1,400 | Plus annual maintenance, often a meaningful percentage of licence value |
| Implementation and configuration | R15,000 to R80,000 | $850 to $4,500 | Number of trust accounts, branches, investment accounts, report setup |
| Data migration from the old system | R10,000 to R120,000 | $550 to $6,700 | Years of history migrated, data quality, number of open matters |
| Training | R5,000 to R40,000 | $280 to $2,200 | On-site versus remote, number of bookkeepers and fee earners |
| Parallel-run staff time and extra audit work in year one | R10,000 to R60,000 | $550 to $3,300 | Length of parallel run, auditor's review of migrated balances |
Worked example (hypothetical)
Take a 12-person Johannesburg firm with eight system users, one trust banking account and about 40 Section 86 investments. On a local cloud platform at R1,100 per user per month, the subscription comes to about R105,600 a year (around $5,900). Add R35,000 for implementation, R40,000 for migrating three years of history, R12,000 for training and R25,000 for parallel-run time and extra audit hours. Year-one cost is roughly R218,000 (about $12,100). From year two, expect mainly the subscription plus annual escalation, which contracts often link to inflation or set at a fixed percentage.
Firms most often forget two costs: migrating history they never use, and staff overtime when go-live lands in the middle of the audit. The timeline below controls both.
A Switch-Over Timeline Built Around Your Financial Year
The cleanest cut-over date is the first day of a new financial year. If your firm's year ends in February, that means 1 March. Your old system then covers one complete audited year, and the new one starts with opening trust balances the auditor can tie straight to the closing trust creditors' list. If a year-start date isn't possible, pick a quarter-end after a reconciliation that balances. Never go live with an unreconciled difference you plan to sort out later.
| When (year-end = month 0) | Milestone | Owner |
|---|---|---|
| Month -6 to -5 | Shortlist two or three vendors; run scripted demos using your own reconciliation and Section 86 scenarios | Managing partner, bookkeeper |
| Month -5 to -4 | Send the POPIA questionnaire; ask your auditor to review sample reports; check references | Information officer, auditor |
| Month -4 | Sign contract and operator agreement; agree the migration scope (balances only versus full history) | Managing partner |
| Month -3 to -2 | Map chart of accounts, clients, matters and investments; complete a trial migration | Vendor, bookkeeper |
| Month -2 to -1 | Train users; run one full month in parallel and compare reconciliations line by line | Bookkeeper, fee earners |
| Month 0 | Close the old year and extract the final trust creditors' list and investment schedule | Bookkeeper |
| Month +1 (day 1) | Go live with verified opening balances; set the old system to read-only | Vendor, bookkeeper |
| Month +1 to +2 | Complete the first live reconciliation; have the auditor sign off the opening balances | Auditor |
| Month +1 to +6 | Run the prior-year audit from the read-only legacy system; file with the LPC on time | Auditor, managing partner |
Two rules keep this on track. First, keep the legacy system, or a complete certified export, available for the full record-retention period. Cancelling the old licence before the prior-year audit is filed is an expensive mistake. Second, migrate balances and open matters in full, but bring across only as much history as your auditor and retention obligations require. Keep older history in the read-only archive.
Decision rule: if your firm holds trust money in more than a handful of matters a month, shortlist only vendors that can produce LPC-format reconciliations and a Section 86 investment schedule live in the demo. Then let your auditor's review of sample reports, not the feature list, decide between them. Pick a go-live date at the start of a financial year and work back six months from it.
Quick answers
Does the Legal Practice Council approve or certify trust accounting software?
Generally no. The LPC requires that your records, reconciliations and audit reports meet its accounting rules, whatever system produces them. Be careful with any vendor claiming to be "LPC approved" and ask it to explain exactly what that means.
Can we use Clio or another international platform for trust accounting in South Africa?
You can, but check whether it produces LPC-format reconciliations, tracks Section 86 investments and imports statements from South African banks. Many firms that prefer an international platform for matter management keep trust in a local legal accounting system alongside it. Ask your auditor to review sample output before you commit.
Is it a POPIA breach to host trust data outside South Africa?
Not automatically. POPIA allows cross-border transfers where the recipient is bound by adequate protections, such as a law, binding corporate rules or a contract, or where another statutory ground applies. You must document that basis and have a compliant operator agreement in place. A data protection lawyer can confirm your position.
How long does it take to switch trust accounting software?
For a small-to-mid-sized firm, plan on about four to six months from shortlisting to go-live, including at least one month of parallel running. The safest go-live date is the first day of a new financial year. Allow extra time for many years of history or several trust accounts.
How much history should we migrate from the old system?
Migrate verified opening balances, open matters and active Section 86 investments in full. Older closed history can usually stay in a read-only copy of the legacy system or a certified export, as long as it remains accessible for the retention period. Confirm the cut-off with your auditor.
Will new software reduce our annual audit fee?
It can, if the auditor can pull standard reconciliations and exception reports directly instead of rebuilding them from spreadsheets. Expect the first audit after a switch to cost about the same or slightly more, because the auditor has to verify the migrated opening balances. Savings, if any, usually show up from the second year.
Written by the Juris Tflow Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.