AI for accounting firms in South Africa
What it actually does inside a practice, what it is never allowed to touch, and how to test it on five clients mid-season without changing any of your software.
AI in a South African accounting firm chases outstanding client documents, reads what arrives, files each item against the right client and the right return, and flags what is missing or looks wrong against prior periods. It works with view-only access to the software the practice already runs, it never logs into SARS eFiling, and someone at your firm approves every output before it goes anywhere.
What does AI actually do in an accounting practice?
It runs the document chase and the checking that fill filing season. Most practices run short of hands in the weeks when the IRP5s, medical aid certificates, and retirement annuity certificates are due to arrive and mostly have not, which usually means a junior retyping the same reminder for the fourth time while a senior sits with a half-ready return, waiting for one photographed certificate to land in the inbox. Research Sage commissioned from Plum Consulting puts the administrative load on a South African small business at around 202 working days a year, measured across the business as a whole rather than per person, and inside a practice the heaviest share of that is requesting, re-requesting, renaming, filing, and checking other people’s paperwork.
That is the layer it takes over. It sends and follows up document requests in the firm’s name, reads what comes back, matches every document to the right client and return in its own workspace, where nothing lands in your ledger, and raises a flag when something is missing, arrives twice, or looks wrong next to last year. Your people work from a worklist and a review screen instead of an inbox.
Judgement stays with your people: whether an estimate is defensible, what to say to SARS, and whether a return is ready to go are calls for your reviewers, and the filing itself belongs to a registered practitioner at your firm. The workflow detail is written up in why the document chase decides your filing season and AI for month-end close.
Where it fits, form by form
| Return | What AI carries | What stays with your people |
|---|---|---|
| ITR12 | Supporting-document chase and intake across the whole client list | Review, sign-off, submission |
| ITR14 | Financials and supporting-data readiness inside the 12-month window | Judgement calls and the filing |
| IRP6 | Estimate inputs gathered early, paragraph 20 threshold checked before commitment | The estimate decision and the payment |
| VAT201 | Period data readiness and exception flags ahead of the eFiling deadline | Review and submission |
| EMP201 | Payroll input checks ahead of the 7th (or the last business day before it) | Approval and payment |
Per the SARS Filing Season 2026 notice, auto-assessments run from 1 to 12 July, the season opens on 13 July, and non-provisional individuals file by 23 October, so a firm that starts its ITR12 intake in the first week of July spends October reviewing returns instead of asking clients for certificates. The season’s first call, accepting a SARS auto assessment or filing over it, has its own guide.
The provisional side is where an estimate error turns into money. Take a company client whose second estimate went in at R1,400,000 and whose assessed income lands at R2,000,000: paragraph 20 of the Fourth Schedule applies its over-R1-million test, an 80 percent benchmark of R1,600,000, the estimate misses it, and the 20 percent penalty on the R54,000 shortfall in tax, at the 27 percent company rate with provisional payments matching the estimate, comes to R10,800, with section 89quat interest running on the underpayment. That exact scenario is the worked example inside the free SARS provisional tax calculator, which runs on the same arithmetic as the engine behind C-Suite Commercial. C-Suite Individual covers the ITR12 row of the table, and Commercial runs the rest of the calendar.
Is any of this allowed in a tax practice?
Yes. Four rules make the setup defensible, and every one of them is checkable.
Filing for reward belongs to a registered tax practitioner under section 240 of the Tax Administration Act, so filing stays with your practitioner, and C-Suite’s own line sits further back: the system never logs into SARS eFiling and never submits anything, anywhere. The practice remains the responsible party under POPIA while C-Suite works as an operator, under a written operator agreement that records where every processing step runs, hosted in South Africa, and client data is never used to train a model. The professional codes, SAICA, SAIT and SAIPA alike, hold the member responsible for the work whatever tools sit underneath, so every output stops at a review screen until one of your people approves it. And because an auditor or the Information Regulator may one day want the trail, every action is written to a log your firm can export.
C-Suite builds every engagement around these four rules because they decide whether a partner can defend the setup to their professional body. The eFiling boundary in day-to-day terms is covered in AI and SARS eFiling: what it can and can’t do, and the POPIA mechanics of chasing client documents are in chasing month-end documents without breaking POPIA.
Software, or someone to run it
The licences a practice already pays for hold the client data, and the tax knowledge arrived with the partners, so the gap that decides the season is operational capacity: someone to run the chase and the checking every day while the returns move.
There are three ways to close that gap. Building in-house suits a practice with real engineering capacity and the patience to maintain what it builds, because models and APIs keep changing. Buying software adds a licence and a login, and the chasing and checking stay with the same staff who had no capacity before. The third way is the one C-Suite sells: managed tax operations. Managed tax operations means chase, intake, and exception work run as a service inside your own systems, on Xero, Sage, Pastel, GreatSoft, or CaseWare as you run them today, with view-only access, nothing written back to any ledger, and approval sitting with your people. C-Suite Individual runs it for ITR12 season, C-Suite Commercial runs the company compliance calendar, and Custom AI Systems covers the workflows that fit neither, the multi-branch intake routing and the integrations nobody has built yet.
A practice already running Dext or Hubdoc keeps them: those tools read the documents that arrive. The gap they leave is the arrival itself, the following up, and the cross-check against last year, and that gap is what consumes the season.
C-Suite is not built for individual taxpayers filing their own returns, a job SARS eFiling and TaxTim already serve well, and an in-house corporate tax team that wants a platform to drive itself will be better served by the software vendors. Anyone hoping for software that files returns automatically is in the wrong place too, because section 240 keeps filing with a registered practitioner, as it should.
How to see it on your own clients
The quickest look is the free SARS provisional tax calculator: no sign-up, and it runs the IRP6, paragraph 20, and section 89quat arithmetic in your browser on any client scenario you type in. The fuller test is a free one-week pilot: the operator agreement is signed before any client data is visible, the document chase then runs read-only on five of your slowest clients for the week, and the firm ends with the log of every message and flag for review. Setup asks about ten minutes of your team’s time. A 15-minute call goes to the founder directly, who runs every C-Suite engagement personally.
Common questions
How do South African accounting firms use AI safely?
By keeping the four rules above in place: view-only access to the software the firm already runs, no contact with SARS eFiling, a written POPIA operator agreement with hosting in South Africa, and approval from one of your own people on every output. Together they let AI run chasing and intake at a scale a practice cannot staff for in season.
Is AI allowed under the SAICA Code?
SAICA’s Code, and the SAIT and SAIPA codes with it, hold the member responsible for the work whatever tools sit underneath, and a defensible setup is designed around exactly that: every output stops at a review screen, waits for a person at the firm, and leaves an exportable record of what was done and who approved it.
Can AI post to the ledger or file on eFiling?
No. Access is view-only, so nothing can be posted, adjusted, or deleted in the accounting records, and eFiling is never touched. Preparation runs up to the review screen, a person at your practice approves the work, and a registered practitioner files.