On your machine
The bot is installed where the work happens, so it can reach the systems that never got an API.
Prepares every return on the calendar, files it on eFiling once a human has signed it off, and keeps the proof.
VAT201, EMP201, provisional tax and CIPC 27 systems From R6 500 / month Up to 25 client companies included
Hire a Tax & Compliance ClerkThe whole job, in the order it happens — not a feature list.
Holds every client's dates — VAT201 by the last business day on eFiling, EMP201 by the 7th, provisional tax, the EMP501 reconciliation, and the CIPC annual return on the anniversary of incorporation.
Extracts the VAT and payroll figures from the ledger and the payroll package, and reconciles the control accounts before it prepares anything at all.
Flags input VAT with no valid tax invoice behind it, VAT numbers that fail validation, and any return that moves more than your tolerance against the prior period.
Completes the return on eFiling — and stops. The submit button waits for a person.
You review the prepared return against the working paper and sign off. It submits, then captures the acknowledgement, the reference number and the assessment.
Every submission, acknowledgement and payment reference filed against the client alongside the working paper that produced it — so a query two years from now takes a minute, not an afternoon.
Nothing is ever submitted to SARS or CIPC without a named human signing it off. That is a permanent design decision, not a limitation of the first version — you carry the liability for what is filed, so you press the button.
A digital worker you cannot measure is one you cannot trust. Every run is logged, and the numbers below are reported without being asked for.
27 pre-built connections, ready on day one. Where a system publishes an API, the digital worker uses it directly from the cloud.
SARS eFiling and CIPC screens where no API covers the step — the bot works the portal on your machine, signed in under your own practitioner profile.
This is the part a cloud-only tool cannot do. The Automize bot runs on your own machine, so anything a person can open, it can work in — the desktop accounting package, the bank portal, the supplier site with no integration.
The bot is installed where the work happens, so it can reach the systems that never got an API.
Passwords live in your operating system's own keychain and never sync to us. We hold the steps, not the secrets.
Client financial data is processed locally. Servers are in AWS Ireland and hold process definitions and execution logs.
Step-by-step logs, screenshots and timestamps for every run — and a record of who approved what.
The work that turns the 7th and the 25th of every month into a crisis, for every client at once.