The work between your clients and your software is what costs you the most time in the season, and you want it handled without hiring.
From 13 July the IRP5s, medical-aid certificates, and rental schedules arrive in a trickle, and the most expensive people in the practice spend the season chasing them instead of reviewing returns.
Company income tax, provisional tax, VAT, and payroll each carry their own deadline and their own document chase, so the compliance calendar is different for every business on your book.
GreatSoft, CaseWare, the portal nobody logs into. The tools hold the work, and someone still moves it by hand between the email, the drive, and the client. That someone is usually a senior.
Most practices do two kinds of tax work. Individual returns (ITR12) come in a rush during filing season, 13 July to 23 October. Company tax runs all year: provisional tax, VAT201, and monthly payroll.
When the job sits outside individual or company tax, we scope and quantify a custom AI system in the proposal before you commit to anything.
A bespoke build for the work beyond individual and company tax.
Across both engines, your team approves every message and every filing before it goes out, so nothing reaches a client or SARS without your say-so. Both run read-only on the software your practice already uses (Xero, Sage, Pastel, GreatSoft, CaseWare, eFiling), so you stay the practitioner of record while the follow-ups get handled first.
The biggest fear is an outside party getting near your clients and your SARS eFiling and getting something wrong in your firm’s name. Here is how each of those risks is prevented.
We never get write access to your SARS eFiling. The permission scopes you grant show that limit. Your team files; we never do.
Nothing reaches a client and nothing is filed until a person on your team approves it. That approval is on by default and cannot be switched off.
Every action is logged, attributed, and exportable, so you have a clean answer ready for SARS or your professional-indemnity insurer whenever one is asked for.
It works on the tools you already use, in your practice’s name, so your client sees your own firm being efficient.
You remain the practitioner of record on every return. We run the operations underneath, and the professional judgement and the SARS relationship stay with your team.
Every return and every ledger entry waits on someone at your practice to approve it before it goes anywhere, so the figure you see here stays at zero until one of your people signs.
Before any work starts, we agree the single outcome we are aiming at and put it in writing. A person on your team signs off every action, nothing posts to your ledger, and your client data is never used as training data.
The first thing practices ask is whether client data is safe. C-Suite reads only, runs in South Africa, and aligns with POPIA: it never files on eFiling, it never posts to your ledger, and every client message waits for your sign-off before it sends. Read the engagement terms.
A POPIA-aligned chase is read-only, hosted in South Africa, never trains a model on client data, and runs on a written operator agreement, with your team signing off every output.
Read: Chasing month-end documents without breaking POPIAWe map where your season costs the most senior time and name the one step that fits your practice. Start with a free week on your own clients, and you speak to Ty Panaino directly on the call.
