The document-chasing side of tax season, taken off your team.
Every season, the same grind: clients slow to send their paperwork, seniors chasing documents instead of reviewing, exceptions that only surface late with a SARS deadline approaching. C-Suite automates that legwork on the software you already use, with AI doing the reading and the drafting, and your people stay the reviewers. It reads only, it never files on its own, and every client message waits for your sign-off.
How does the document chase automation work, step by step?
Watches the mailbox and document folders
From the start of the season, C-Suite tracks what each client still owes you: the IRP5s, the certificates, the schedules, the supporting documents. It knows what has arrived and what is still outstanding, so nobody on your team holds that list in their head.
Chases the clients who are slow to send paperwork
For every client running late, C-Suite drafts the follow-up in your firm voice, with the specific documents named. The message waits in a queue for a person on your team to read and approve, and sends only after they do.
Reads and sorts what comes back
As documents arrive, C-Suite reads them, matches them to the client and the period, and files them where your seniors expect to find them. An inbox of loose attachments becomes a sorted set ready for the work.
Flags the exceptions before your reviewer sees them
C-Suite picks up the missing certificate, the mismatch, the return with a document still outstanding, and the gaps that would otherwise surface late, and raises them early. Your reviewer opens a short list of things that genuinely need a person, instead of hunting for them.
Holds every outbound for your sign-off
Nothing reaches a client until your team approves it. Your firm controls every word that leaves the building, and the audit trail shows who approved what and when.
Reads only, and never files or posts on its own
C-Suite runs on the software you already use, with read access only. Your seniors stay the reviewers and the ones who file. It takes the legwork and nothing else, and the ledger stays exactly as your people left it.
Two guides go deeper on this flow: why the chase decides the rest of the season, in document chasing decides your filing season, and how to run it on client data without breaching POPIA, in chasing month-end documents without breaking POPIA.
Where do you start, and what is agreed first?
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.
Custom AI Systems
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.
The firm stays in control, and the outcome is agreed before any work starts.
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.
We agree the outcome in writing before any work starts, then keep refining the setup against your real client base until that outcome is met and you are satisfied it works. The once-off setup is a non-refundable commitment to getting you there.
Everything runs on the software you already use. C-Suite is hosted in South Africa and POPIA-aligned, it has read access only, and your client data is never used to train a model.
We tell you plainly which product fits the firm in front of us
Most practices start with one product, not both. The discovery call names the one that actually fits, and says so when the free estimator is the only thing worth doing right now. You leave with a clear read either way.