RUN A BIGGER BOOKWITHOUT A BIGGERADMIN LOAD.
OptiTax is built for the volume side of practice: many clients, many documents, one review queue that keeps you looking at what actually needs a decision.
Less chasing, more reviewing
The work does not disappear. It moves from finding documents to deciding on them.
One inbox per client, not per channel
WhatsApp messages, uploaded files and emailed documents all land against the same client file, so nothing has to be manually filed later.
The pile gets sorted before you see it
Statements, slips and certificates are read and matched to SARS codes and known expense categories before they reach a human queue.
You work the exceptions
A review queue surfaces missing evidence, unclear line items and anything the engine flagged rather than guessed at.
Your sign-off, your name, every time
OptiTax does not change who is accountable for a return. It changes how much of the file you have to touch before you sign it off.
You still review
Every flagged item and every claim is presented for your decision, not filed automatically on your behalf.
You still sign
Submission is completed by a registered SARS tax practitioner. The engine never files on its own.
Your team, your assignments
Clients are assigned to specific accountants inside the practice. Each person sees the book they are responsible for.
A record of every step
Messages, uploads, flags and sign-offs are logged against the client and the staff member who acted.
Tools for the parts of practice work that repeat
PDF to CSV
Bank statements convert to Sage- or Xero-ready CSV files, so reconciliation does not start with manual retyping.
Year on year compare
A client's current year sits next to their prior year, so unusual movements are visible before you file, not after a query.
Commission tracking
Where a package includes a commission arrangement, what is owed and what has been paid is tracked in one place.
ⓘA practice signs up with its SARS tax practitioner number and recognised controlling body, as section 240 of the Tax Administration Act requires. The practice is created pending and reviewed by a person before it goes live, usually the same working day.
Your whole book, on six counts
The console opens on six figures, each one a live count across every client return the practice holds. They are what a practitioner needs before deciding where the day goes.
OUTSTANDING
What is still missing, grouped by the kind of thing it is rather than by client. Three clients owing the same document collapse into one line, so one reminder clears all three instead of three separate chases.
Clients
Every client file loaded into the practice.
Sending
Clients actively sending evidence in.
Scan queue
Expense lines still marked pending that did not come from a manual upload: the ones the engine read and wants a human to confirm before they become a claim.
Documents
Every document held across the practice's returns.
Filed
Returns that have reached the filed stage or past it.
Every file sits on one of five rungs
The same ladder the client sees on their own dashboard, so a practitioner and a client are never describing the same file with two different vocabularies.
Collecting
Their paper arrives. Covers lead, paid, engaging, awaiting access and collecting.
Checking
The engine reads and matches it. This is the reconciling stage.
Preparing
The return is worked out. This is the computing stage.
Your say
The client approves the figures. Covers awaiting approval and awaiting sign-off.
Filed
Lodged with SARS. Covers ready to file, filed, assessed and closed.
WALK THROUGH ITAGAINST A REAL CLIENT
Bring the kind of client file you deal with every week and we will show the workflow against it.