How to Submit a Tax Return on SARS eFiling
A practical guide to submitting a tax return on SARS eFiling and how small businesses should prepare before they press submit.
- Filing on eFiling is not only a platform task. The real risk usually sits in the records and schedules behind the return.
- The right submission path depends on whether the taxpayer is filing an ITR12, ITR14, or another return type.
- Bank details, profile details, and pre-populated information should be reviewed before the final submission step.
- A cleaner eFiling process usually starts with preparation before login, not after the return opens.
Submitting a tax return on SARS eFiling is not difficult because the buttons are mysterious. It becomes difficult when the return is opened before the supporting file is ready.
Submitting a tax return on SARS eFiling sounds like a platform question, but the platform is only one part of the job. The bigger issue is whether the taxpayer is using the right return type, whether the profile is current, and whether the numbers behind the return are ready to stand up after submission.
So the best eFiling process does not start with clicking through tabs. It starts by deciding what must be reviewed before the return is opened.
Why this matters in a live SME finance cycle
Small businesses usually only become serious about eFiling when a deadline is close, a refund is expected, or a return is already sitting overdue. In that moment, people focus on the system steps and underestimate the preparation steps.
That creates a predictable pattern. The return opens, something looks incomplete, bank details or source values still need work, and the team is now solving accounting and tax issues inside a filing deadline. A stronger process separates preparation from submission so the platform work stays simple.
The sequence that usually makes eFiling cleaner
- Confirm which return type is required before logging in and assuming the system will guide the whole process for you.
- Review the profile, tax-reference details, and bank information that may affect the return or any resulting payment or refund.
- Check the source documents and schedules first so the figures going into the return already make sense before eFiling is used.
- Work through the return in eFiling only once the underlying support is in place.
- Keep the notices, assessment, and any supporting-document requests together after submission so the record stays usable.
That sequence matters because most eFiling problems are not actually user-interface problems. They are late-preparation problems that only become visible on the platform.
Step 1: Confirm the taxpayer, year, and return type
Before any figures are entered, confirm whose return is being filed and which tax year or period is open. For individuals this may be an ITR12. For companies it may be an ITR14. A sole proprietor may have business income inside the owner's personal return, while a company has a separate corporate tax return.
This sounds obvious, but it prevents a common SME mistake: trying to solve a record problem inside the wrong filing workflow. If the business structure is unclear, first compare the position with the sole proprietor tax guide or the ITR14 company tax return checklist.
Also check that the SARS profile, banking details, registered representative, and contact details are current. A clean return can still become slow if the profile information around it is wrong.
Step 2: Prepare the evidence pack before typing figures
The return should be the last place the numbers land, not the place where the business discovers the numbers. Before opening the return, gather the accounting records, tax certificates, bank statements, payroll certificates, investment certificates, medical aid certificates where relevant, and schedules for income, expenses, allowances, assets, or deductions.
For small companies, this usually means starting from reviewed accounting records and the company-tax checklist. For individuals and sole proprietors, it means separating personal information from business activity clearly enough that the ITR12 can be completed without guessing.
The evidence pack should be saved with the assessment and SARS notices after submission. That makes later verification, audit, refund, or objection work much easier.
Step 3: Submit, save the proof, and review the assessment
Once the return is complete, review the summary before submission. Check income, deductions, bank details, taxpayer details, and any declarations. After submission, save the confirmation, assessment, and any supporting-document request from SARS.
Do not treat the final click as the end of the process. The assessment must be reviewed against what the taxpayer expected. If SARS requests documents, respond from the evidence pack rather than rebuilding the file from scratch.
This is where eFiling connects to the wider tax clearance certificate guide. A business that files accurately and keeps notices under control is in a better position when it later needs compliance proof for tenders, banks, or customers.
The comparison table that keeps the filing workflow realistic
| Filing step | What strong preparation looks like | What usually creates rework |
|---|---|---|
| Return selection | The taxpayer knows which return must be filed | The wrong return type or wrong year is being chased too late |
| Profile review | Bank and registration details are already current | Important details are only checked at the end |
| Data review | Source figures and schedules have already been checked | The return is used to discover accounting gaps |
| Final submission | The taxpayer can explain the return after it is filed | Submission happens before the support pack is stable |
The table helps because it shifts attention from the screen flow to the real control points around the filing process.
Common mistakes that create avoidable rework
- Treating eFiling as if it will automatically solve wrong or incomplete source figures.
- Filing from pre-populated values without checking whether they still match the real records.
- Leaving bank-detail or profile changes too late in the process.
- Assuming that a successful submission means the return is unlikely to attract questions later.
Those mistakes usually happen because the filing task is treated like admin, not like a compliance control point.
How this connects to the service layer
This page works best when it sits next to the more specific filing resources and the live service pages that handle the work when the file is not clean.
- Tax Return Filing Services
- Online Tax Services
- ITR14 Company Tax Return Checklist
- ITR12 Personal Tax Return Checklist
That structure makes the page useful for both search and buyers. It explains the filing workflow, then points to the exact support path needed when the issue goes beyond the platform steps.
When to escalate instead of guessing
Escalate if the return depends on uncertain figures, unresolved bookkeeping issues, missing certificates, or a tax profile that still needs correction before filing. Those issues are usually cheaper to fix before submission than after SARS asks questions.
Escalation is also sensible when the return has business income, capital gains, mixed personal and business expenses, prior-year corrections, provisional-tax exposure, or a refund that is likely to trigger verification. Those items are not impossible, but they need a cleaner support trail than a basic salaried taxpayer return.
What to keep after the return is filed
After submission, create a small filing pack for the tax year. It should include the submitted return, assessment, proof of submission, SARS correspondence, payment proof or refund notes, and the source documents used to support the figures. For a company, keep the accounting reports and tax schedules that support the ITR14. For an individual, keep certificates, business schedules, deduction support, and any correspondence about verification.
This pack is useful even if SARS does not ask questions immediately. A later audit, refund review, tax-clearance request, lender request, or next-year comparison may depend on the same evidence. If the documents are scattered across inboxes and downloads, the business loses time when the pressure is higher.
For SMEs, the best habit is to save the pack before moving on to the next filing cycle. That keeps eFiling work connected to real compliance control rather than treating each return as a once-off screen task.
Name the folder by taxpayer and tax year so it is easy to find later. A simple naming habit prevents the next return, verification, or tax-clearance request from starting with another document search.
Practical FAQs
Can I submit first and fix the documents later?
That is risky. If SARS asks for support, the documents must match the submitted return. Filing before the evidence is ready often creates more work than waiting long enough to prepare properly.
What should I save after submission?
Save the submitted return, assessment, confirmation, SARS notices, payment proof if relevant, and the documents used to support the return.
Does a successful eFiling submission mean the tax is final?
Not always. SARS may still assess differently, request documents, verify bank details, or raise follow-up questions.
Practical takeaway
Submitting a return on eFiling should be the final step in a prepared process, not the moment the business discovers whether the file was ever ready to submit.

