Tax and SARS knowledge base
Retirement-transfer return rejected: missing ROT
Why can a retirement transfer return be rejected where SARS has no recognition-of-transfer record?
Last reviewed:
Direct answer
From the 2026 year of assessment, SARS says it will reject a return that declares a lump-sum benefit where a tax-directive application for a transfer between retirement funds was submitted, but SARS did not receive a Recognition of Transfer, or ROT, from the transferee fund. The affected member cannot create the ROT. The receiving fund must confirm the transfer data and submit the required ROT information to SARS.
This is not a generic explanation for every retirement-return error. The administrator should first preserve the exact eFiling error, directive number, transfer dates and fund details. It should then reconcile those records before resubmitting data or telling the member to retry a return.
What this means in practice
The ROT process exists to identify a qualifying transfer correctly in SARS records. A member may have a transfer instruction, statement and tax directive, while the matching ROT submission is still absent, rejected or linked to incorrect details. That mismatch can interrupt the member's ITR12 process even where the commercial transfer has completed.
SARS's ROT guide places the relevant submission role with the receiving fund. Fund administrators should therefore avoid giving members a task they cannot complete. Instead, provide a clear escalation path that identifies the receiving fund team, the directive reference, the originating and receiving fund, transfer reason and the status that must be confirmed.
Operational discipline matters. A successful payment instruction is not proof that the ROT has been accepted. Record the submission confirmation and the data used. If a correction is required, keep the original evidence and explain the reason for the correction, rather than overwriting the case history.
Step-by-step
- Capture the exact rejection.
Save the eFiling message or member screenshot and record the ITR12 year, lump-sum benefit, directive number, transfer-between-funds reason and return status. Confirm that the error actually refers to the stated 2026 validation and a missing matching ROT from the transferee fund.
- Reconcile the transfer file.
Compare the member's name, tax number, old and receiving fund, transfer date, amount, transfer reason and directive reference across the instruction, fund records and SARS-facing data. Investigate any mismatch before submitting.
- Confirm receiving-fund responsibility.
Identify which fund is the receiving fund for the transaction. Route the case to the authorised administrator who can submit or correct ROT information. Do not direct the member to submit the ROT themselves.
- Submit and retain proof.
Follow the current SARS ROT guide for the submission or correction. Retain the submission confirmation, supporting documents and any SARS response. Update the case log with the date, owner and expected follow-up.
- Give the member a factual update.
Explain that the administrator has addressed the ROT record and that the member should refresh eFiling only after confirmation. Do not promise an immediate return acceptance, refund or tax outcome.
- Close the control loop.
Where possible, confirm that the corrected information matches the transfer records and that the member can proceed. Record recurring data-quality causes so that future transfer files are checked before a directive or tax certificate is issued.
Documents and records to keep
Keep the transfer instruction, directive, fund statements, member identification details, ROT data and submission confirmation, eFiling error evidence, fund correspondence and correction log. The file should identify the originating and receiving fund, dates and people responsible for each action.
Important limits and exceptions
This guide concerns the stated 2026 validation only: a declared lump-sum benefit, a tax-directive application for a transfer between retirement funds, and no ROT received from the transferee fund. An ITR12 may be rejected for many other reasons, and a retirement transfer may have separate tax and administrative requirements. The member should not be told that a missing ROT proves a tax liability or that every transfer is tax-free.
SARS guidance also requires the receiving fund to confirm receipt electronically through the applicable ROT process.
When to get tailored advice
Escalate where funds disagree about receiving-fund status, the directive data does not match the transfer, a two-pot transaction is involved, the transfer has been treated as a cash withdrawal or the member has a material assessment. TaxProof can help organise the case chronology. We cannot submit fund data or decide the tax effect of a transfer.