If your Recognition of Transfer (ROT) SARS tax return rejected message appeared on eFiling this filing season, the cause sits with your retirement fund, not with you. SARS now blocks any 2026 ITR12 that declares a lump sum transfer between retirement funds where the receiving fund never lodged a matching ROT. You must get the fund to file it, then refresh and resubmit.
SARS confirmed the change in its Changes for Filing Season 2026 notice, stating that “subsequent to the updates on the Tax Directive System on 17 April 2026, SARS introduced a new validation mechanism called the Recognition of Transfer (ROT) validation”, and in a notice dated 29 June 2026 that “from the 2026 year of assessment, SARS will reject a return if it declares a lump sum benefit for which a tax-directive application for a transfer between retirement funds was submitted to SARS, but SARS did not receive any Recognition of Transfers (ROT) from the transferee fund”. With the non-provisional deadline of 23 October 2026 seven weeks away and SARS opening selected service centres on Saturdays to clear volumes, the timing is unforgiving.
I’m Chris Herbst, Managing Director at CH Consulting. I hold the CBAP(SA) designation as a Practising Member of the Southern African Institute of Business Accountants and the GTP(SA) designation as a Practising Member of the South African Institute of Tax Professionals. Our practice spends much of each filing season reconstructing directive trails for individual taxpayers whose retirement fund transfers were reported badly, tracing directive numbers off third-party data and escalating to administrators’ directive teams on the client’s behalf.
What is a Recognition of Transfer (ROT) and why does SARS need one?
A Recognition of Transfer is the form a receiving retirement fund or long-term insurer lodges with SARS to confirm that it actually received the lump sum described on a tax directive, or used it to buy an annuity. There are two versions: the ROT01, used where a benefit was transferred to another approved fund before retirement, and the ROT02, used to acknowledge the purchase of a member-owned or beneficiary-owned pension or annuity from an insurer.
The transfer itself is meant to be tax neutral. Paragraph (e) of the definition of “gross income” in section 1(1) brings retirement fund lump sum benefits referred to in paragraph 2(1)(c) of the Second Schedule into gross income, and the offsetting Second Schedule deduction is what neutralises it. SARS’s now-withdrawn Retirement Fund Practice Note 1 of 2012 put it as the transfer being allowed as a deduction under paragraph 6 of the Second Schedule and “accordingly still a tax neutral event”. That practice note was withdrawn on 15 November 2021, so treat it as background rather than current authority.
Where does the ROT sit in the chain?
The sequence runs: transferring fund applies for a directive with the reason “Transfer before Retirement [Par 2(1)(c)]”; SARS finalises it and issues an IRP3(e); the money moves; the receiving fund lodges the ROT01 or ROT02. According to the SARS guide IT-AE-41-G03, once the directive application is finalised the system activates an indicator on the directive to show that the ROT is required.
Which transfers switch the ROT indicator on?
The indicator is set where the full lump sum or a portion of it is transferred to another fund before retirement, including a section 14(1) transfer of business, the Vested Component, the Retirement Component, and unclaimed benefits transferred to unclaimed benefit preservation funds. That is a wide net, and it captures a great many routine job changes and preservation fund moves.
Why is my Recognition of Transfer (ROT) SARS tax return rejected on eFiling?
Your return is rejected because SARS is checking its own Tax Directive System and finding the ROT indicator on your directive still set to “No”. IT-AE-41-G03 states that “if, on submission of a taxpayer’s annual return the above-mentioned ROT indicator is set as ‘No’ (not received), the taxpayer’s return will be rejected with a rejection message that the ROT is outstanding”.
Note what this means: nothing on your ITR12 caused the failure. SARS is comparing the directive it issued against the ROT it never received. The exact on-screen wording of the taxpayer-facing message is not something we can confirm word for word from SARS’s own publications, so if your message reads differently to what you have seen quoted elsewhere, that is not a sign something else is wrong.
Can I file the ROT myself?
No. SARS confirms that ROTs must only be submitted electronically through an interface agent (ISV platform) or SARS eFiling where a tax directive application was submitted after 1 July 2017. Those are fund and insurer channels. A member has no access to them.
Does this affect auto-assessed taxpayers?
It can. If you were auto-assessed between 1 and 12 July 2026 on directive data that is wrong, and you then try to file a corrected return, the ROT validation can block the correction. We deal with the mechanics of challenging an estimate in our guide to disputing a SARS auto-assessment, and the broader risk in the hidden risks of relying solely on auto-assessments.
How long do I have before SARS taxes the transfer in full?
SARS has published two different clocks, and it has not reconciled them. IT-AE-41-G03, effective 24 July 2026, says that “if the Receiving Fund / Long-term Insurer does not submit the ROT within 10 working days, SARS will regard the amount indicated on the tax directive as normal income and the amount will be taxable in full”, adding, in SARS’s own words, “This will cause hardship to the taxpayer.”
A separate, undated SARS FAQ page says something else: “SARS will issue final reminder to the taxpayer to submit ROT, failure to submit after 21 working days will lead SARS to treat the transfer as a withdrawal.” This is genuinely unsettled. The two positions differ on the number of days, on who receives the final reminder, and on the tax outcome, because “normal income taxable in full” and “treated as a withdrawal” are not the same treatment. Our advice is to work to the shorter ten working day clock and keep the FAQ wording on hand if SARS acts earlier than twenty-one days.
What are the exact steps to fix a rejected 2026 ITR12?
Work through these in order, and start today rather than in October, because the fund’s submission and SARS’s processing both take time.
- Capture the rejection. Screenshot the message on your eFiling Income Tax Work Page with the date and time visible. This is the first document in your evidence file.
- Find the certificate. On a tax-neutral transfer the fund issues an IT3(a), not an IRP5, so look for a second certificate you may have filed away. Our note on documents needed to file your 2026 return covers what to gather.
- Extract the directive number. It sits on the certificate under source code 3230, with the directive amount under code 3233. Per the SARS PAYE BRS, where lump sum codes are completed with values the directive number is mandatory and must not be zeros. That BRS version carries an April 2022 footer and a later version now applies, so whether the code numbers changed is unverified.
- Pull the underlying third-party data if the PDF does not show it. SARS’s route is the guide GEN-ENR-01-G09, “How to view submitted third party data returns or data files via eFiling”.
- Identify the transferee fund. You need its registered name as recorded with the FSCA, the fund type, whether it is an approved or public sector fund, and the FSCA registration number in the format 12/8/0000000/000000. For a long-term insurer, the number format is 10/10/1/ followed by four digits.
- Contact the receiving fund, not the transferring fund. SARS’s stated remedy is that the taxpayer must contact the receiving fund and request that the ROT is submitted to SARS.
- Ask for the directive team by name. Member services cannot lodge an ROT. Ask for the tax directives or retirement benefits operations team.
- Name the two eFiling functions. Since 17 April 2026 administrators have an “Enquire ROT reminder” function to review details of reminders received from SARS, and an “Enquire ROT cancellation status” function on the “Manage ROT” tab. Naming these forecloses the “we have no record” answer.
- Get written confirmation with a submission reference. Ask for the date of submission and the reference, in writing.
- Wait, then refresh. SARS instructs the taxpayer to refresh the data on eFiling and submit the return. Allow several days for processing first.
- If it still blocks, regenerate. Close the return and generate a fresh ITR12 rather than resubmitting the cached one.
Does “Refresh Data” actually refresh the ROT?
Unclear, and worth saying plainly. The Refresh Data screen offers tick-boxes for IRP5 data, medical data, retirement annuity data, investment income and tax-free investment. There is no ROT or directive option. Whether the indicator refreshes as part of the IRP5 pull is unverified. Refresh anyway, then wait and regenerate if needed.
What does SARS already hold, and how does a mismatch show up?
SARS holds the directive it issued, which is the entire basis of the validation. It knows the transferring fund, the reason code, the amount, the date of accrual, the nominated receiving fund and its FSCA number, and the current state of the ROT indicator. This is SARS checking its own records against itself, which is why nothing you change on the return will clear the block.
It also holds the certificate the fund submitted through the reconciliation process, carrying the lump sum under a 39xx code, the directive number at 3230, the directive amount at 3233, tax at 4115 where any was withheld, and code 4150 reason “04” where nothing was withheld. Per the PAYE BRS V23.0.0, reason 04 covers “non-taxable earnings, including: nil directives and income protection annuities from 1 March 2015”, and may only be used where the certificate type is IT3(a).
What about the FSCA database?
SARS validates fund and insurer identity against the FSCA registration database. From mid-September 2022, all directive applications are rejected where the information does not match the FSCA data, and SARS notes this validation is necessary to ensure the successful submission of the ROT. For a freestanding fund or a retirement annuity fund, the last six digits of the FSCA number must be zeroes and the participating employer name must be blank.
How does the failure appear on assessment?
In the blocked case there is no assessment at all, because the return never enters SARS’s systems. If the ten working day rule runs its course, the guide’s stated outcome is that the amount on the directive is regarded as normal income and taxed in full. That is the same shape as the 2025 defect SARS acknowledged, where “the tax calculation was incorrect as the amounts transferred from one retirement fund to another were incorrectly regarded as taxable on assessment”.
Where does the ROT validation go wrong most often?
The failures cluster into a handful of causes, most of which originate at directive stage rather than at ROT stage.
The taxpayer never knew a directive existed
Members who instruct a transfer receive a benefit statement, not a directive. The ROT indicator is set silently at finalisation, so the eFiling rejection is often the first anyone hears of it.
The tax reference number does not match
SARS rejects the ROT with the message “Tax reference number on the ROT01 must match the original transfer directive application” where the number does not correspond with its records. This catches people who were assigned a tax number after the transfer, or who had duplicate numbers merged.
The FSCA details were captured wrongly before September 2022
SARS’s fix here is counter-intuitive: if the FSCA name and number format were captured incorrectly on the directive before September 2022, the same incorrect information must be reflected on the ROT to avoid rejection. The administrator has to reproduce the error deliberately.
Umbrella versus freestanding format confusion
Umbrella fund transfers need the participating employer segment populated; freestanding and retirement annuity funds need trailing zeroes and a blank employer name. Reverse the two and the ROT bounces.
The wrong directive reason was selected
SARS’s lump sum directive guide is clear that a member cannot transfer a portion or the two-thirds of the benefit to a retirement annuity fund if the reason “Retirement” is selected; the correct reason is “Transfer before Retirement [Par 2(1)(c)]”. A wrong reason poisons everything downstream.
Section 14 bulk transfers fail as a group
Where an entire employer’s membership moves under a section 14(1) transfer of business and the receiving administrator’s ROT file fails, every member is blocked at once, and none of them will have been handed a directive number. SARS has published nothing on bulk remediation.
What if the directive itself is wrong and the ROT has to be cancelled?
Cancellation is slow, one-way, and requires the money to physically move back. SARS states that once the ROT has been cancelled it cannot be reinstated, and the only way to “reinstate” one is for the receiving fund to submit a fresh ROT electronically.
The sequence is: the receiving fund confirms non-receipt; the ROT is cancelled; only once the eFiling status reflects “Cancelled” can the transferring fund request a refund into its own bank account; only then can the transferring fund cancel the directive; then a new directive and a new ROT follow. SARS also notes the directive should only be cancelled if the receiving fund indicated that the amount was not received. Started in October, this will not fit inside the 23 October window.
How do the timing and penalty scenarios compare?
The table below sets out the positions side by side. The middle column is what SARS has actually published; the right-hand column is our read on how settled it is.
- ROT received before you file: SARS position: Return accepted, transfer neutral; Status: Clean
- ROT outstanding at submission: SARS position: Return rejected outright; Status: Confirmed in IT-AE-41-G03
- Fund misses 10 working days: SARS position: Amount taxed in full as normal income; Status: Guide position
- Fund misses 21 working days: SARS position: Transfer treated as a withdrawal; Status: Conflicting FAQ
- Blocked past 23 October 2026: SARS position: No published concession; Status: Admin penalty exposure
- Pre-2023 orphaned directive: SARS position: Not addressed; Status: No SARS guidance
Am I liable for admin penalties if the fund’s delay pushes me past 23 October?
SARS has published no position on whether a validation-rejected return counts as a filed return for penalty purposes, so this remains unsettled and you should plan for the worse reading. The strict view is that a rejected return never entered SARS’s systems, which makes you a non-submitter after the deadline.
The penalty regime is the fixed-amount administrative penalty under section 210 of the Tax Administration Act. SARS states the penalty “can range from R250 up to R16 000 a month for each month that the non-compliance continues”, based on taxable income, and that from 4 May 2026 SARS will issue a penalty assessment notice (AP34). Commentary on sections 210 and 211 notes the penalties “continue to accrue for each month that the non-compliance persists, up to a maximum of 35 months”.
What is the best evidence for a remission request?
Paper the file now. The rejection screenshot with its timestamp, the dated email to the receiving fund, the fund’s dated acknowledgement and any ROT submission reference together form your remission application. SARS’s own concession in IT-AE-41-G03 that “this will cause hardship to the taxpayer” is the strongest single line available to you. There is no published SARS concession, so nobody can promise you remission. Our note on what to do if you miss the tax deadline covers the wider process.
Can I object against a rejection?
A rejected return produces no ITA34, so there is no assessment to object against. One view is that your only live routes are the SARS Complaints Management Office and, where service is the issue, the Office of the Tax Ombud, although the Ombud’s jurisdiction over this specific validation is unverified. Another view is to let the ten working day rule run, allow SARS to assess the transfer in full, and object against that assessment, accepting the “pay now, argue later” cash-flow risk. Neither route is documented by SARS.
Does the ROT validation apply to old returns and old transfers?
This is one of the genuine open questions, and SARS has not answered it. The Updated Guides notice frames the change as applying “from the 2026 year of assessment”, while the Changes notice frames it as a system validation introduced after 17 April 2026. Those are different things: a validation built into the submission engine would fire on any return submitted after that date, including a late 2022 or 2023 ITR12.
What about the pre-2023 cut-off?
SARS states that the ROT indicator is set to “No” on all directive applications submitted on or after 1 March 2023 even where accrual predates 28 February 2023, and that all outstanding ROTs up to 28 February 2023 will no longer be required, with no reminders sent. Whether an indicator still sitting at “No” on an older directive will block a 2026 ITR12 is not addressed.
And pre-1 July 2017 directives?
Here the same SARS guide contains two sentences that do not sit together. One says a manual ROT must be signed and submitted where the directive was finalised before 1 July 2017, regardless of accrual date. The other says manual ROT submissions are no longer accepted by SARS. On the face of the guide, an orphaned 2015 transfer has no channel through which its ROT can now be filed. SARS has not reconciled this.
Does a retirement transfer force me to file a return at all?
Yes, in many cases, because the filing exemption excludes retirement lump sums. The exemption for 2026 is expressed as “remuneration (other than retirement lump sums) not exceeding R500 000 from a single source and employees’ tax has been withheld for that remuneration”, which drags a retiree who did nothing but move a pot into the filing population, and then straight into the ROT block.
Other 2026 conditions requiring a return include capital gains or losses exceeding R40 000 for residents, foreign currency or offshore assets worth more than R250 000 at any stage during the year, and interest above R23 800 for a person under 65 or R34 500 for a person 65 or older. If you also hold crypto assets, the same return carries those disposals, and our guide to calculating crypto capital gains sets out the working.
How does this interact with two-pot transfers?
SARS introduced directive reasons “Two Pot-Transfer Prior to Retirement: All Components (Inter-Fund Transfer)” and “Two Pot-Divorce Transfer: All Components (Inter-Fund Transfer)”, and updated the ROT01 to accommodate them, as reported by SAICA in its Legal and Policy update of 5 September 2024. Whether a wrong-reason directive from 2025 that produced a phantom lump sum will now also produce an ROT block is unaddressed. Our article on two-pot tax owed on your 2026 assessment covers the related assessment problem.
Do You Need Help With a Recognition of Transfer (ROT) Rejection?
If your ITR12 is sitting blocked and the fund is not moving, we can take it off your hands: identify the directive from the third-party data, establish which fund is the transferee, escalate to the administrator’s directive team with the correct FSCA identifiers, and refile once the indicator flips. Book a call to talk through your own circumstances, or email info@chconsulting.co.za with the rejection message and your certificates attached and we will tell you what we think it will take.
