Both read the ledger exports and mailbox your practice already runs, so the paperwork is in and the gaps flagged before your reviewer opens the file.
Next 90 days
1 December 2026 to 28 February 2027
| Due | Return | What it covers |
|---|---|---|
| 7 Dec 2026 | EMP201 | November payroll: PAYE, UIF and SDL, return and payment by the 7th. |
| 31 Dec 2026 | VAT201 | October to November period, Category A, filed on eFiling by the last business day of the month. |
| 7 Jan 2027 | EMP201 | December payroll, return and payment. |
| 5 Feb 2027 | EMP201 | January payroll, brought forward because the 7th is a Sunday. |
| 26 Feb 2027 | VAT201 | December to January period, last business day of February. |
| 26 Feb 2027 | IRP6 second | Second provisional payment for the year to 28 February 2027, twelve months in; the 28th is a Sunday. |
| 26 Feb 2027 | ITR14 | Return for the year ended 28 February 2026, due twelve months after year end, so it moves back to the Friday as well. |
The first IRP6 payment for this year fell due on 31 August 2026, six months into the year, and is already in. The EMP501 annual reconciliation for the year opens on 1 April 2027 and closes on 31 May 2027.
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 the work runs the same way. The chase goes out in your firm voice with the missing documents named, whatever comes back is read and filed against the right client and the right return or period, and the gaps surface for your reviewer while there is still time to fix them, all of it working from the ledger exports your team already runs out of Xero, Sage, Pastel, GreatSoft, or CaseWare and drops into a watched folder.
The biggest fear is an outside party getting near your clients and your SARS eFiling and getting something wrong in your firm’s name.
The only credential C-Suite holds is a read-only scope on your firm mailbox and drive, which you grant and can revoke, since it has no connection to your SARS eFiling and no login to your ledger, and a named person on your team approves every message before it sends.
The mailbox and drive scope is granted by your practice, covers reading the documents clients send and the threads the chase runs in, and can be withdrawn at any time by the person who granted it. Client data stays in infrastructure hosted in South Africa and is never used to train a model.
The approval step is built in with no setting that turns it off, so a message nobody at your practice has approved waits until someone does, and the reviewer who clears it is the name the log records against it.
Every action is logged with the person who approved it, the time, and the message or document it touched, and the log exports as a file, 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.
| Scope | What it allows | What it cannot do |
|---|---|---|
| SARS eFiling | Nothing, because no connection exists and none is requested | Read, file, or amend a return, which stays with your practitioner logging in as today |
| Xero, Sage, Pastel, GreatSoft, CaseWare | Reads the general ledger data your practice exports to a watched folder | Log in, post an entry, or change a figure inside the package |
| Firm mailbox and drive | Reads the documents clients send and drafts the chase, under a read-only scope your practice grants and can revoke | Send a message before a named person on your team has approved it |
Zero is the number of entries C-Suite can post to a client ledger or file with SARS, because it holds no login to either.
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.
Client data is hosted in South Africa under a POPIA operator agreement signed before any of it is visible, processing is logged per matter, and deletion on request happens inside seven days. Read the engagement terms.
A POPIA-aligned chase runs on a written operator agreement, keeps client data hosted in South Africa, logs processing per matter, and deletes on request inside seven days, so the paper trail exists before a client or the Regulator asks for it.
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.