1 reviews | Active since Mar 2023
10x still can't get the numbers right
Last year, I identified that 10X was recording my contributions incorrectly. Upon raising the matter with them, I was assured that the error would not affect my IRP5 as it would be rectified on their backend systems.
Despite this assurance, this year I encountered a serious issue wherein 10X issued me with an incorrect IRP5, contrary to their prior undertaking. Following protracted and challenging engagement with 10X, a corrected IRP5 was eventually issued.
Recently, I discovered that 10X is once again committing the same recording error. When I contacted them, they repeated the same explanation provided last year, which I expressly rejected. I subsequently escalated the matter to their complaints department, where I was assured that the statement would be corrected. However, one week later, the statement remains in its incorrect form.
This raises serious concern as to how a financial services provider of 10X's standing can fail to effect a simple correction to an inaccurate statement, particularly in light of previous assurances and the recurrence of the same issue.
The 10X Team
The 10X Team
We acknowledge your continued frustration regarding the recording of your contributions on your benefit statement and sincerely apologise for the delay in resolving this matter.
As communicated previously, the issue does not affect the accuracy of your contributions on our administration system or the information reported to SARS. The error lies specifically in the statement output, where lump-sum EFT contributions are currently being displayed as “transfers in” instead of “contributions.”
To correct this, the matter has been escalated to our third-party software provider who maintains and develops the statement generation system. This requires their technical team to rewrite the script that produces the benefit statement to ensure contributions are reflected under the correct heading. Unfortunately, this is not a simple manual correction on our side, but a system-level adjustment that needs careful testing to prevent further errors.
We understand that this is taking longer than either you or we would like, and we agree that accurate statements are a basic obligation. Please rest assured that we are actively engaging with the software team to prioritise this fix and we will keep you updated on the progress.
Once the revised script is deployed, we will immediately issue you with a corrected statement.
We appreciate your patience while this technical matter is being resolved and again apologise for the inconvenience caused.
Kind regards,
The 10X Team
We acknowledge your continued frustration regarding the recording of your contributions on your benefit statement and sincerely apologise for the delay in resolving this matter.
As communicated previously, the issue does not affect the accuracy of your contributions on our administration system or the information reported to SARS. The error lies specifically in the statement output, where lump-sum EFT contributions are currently being displayed as “transfers in” instead of “contributions.”
To correct this, the matter has been escalated to our third-party software provider who maintains and develops the statement generation system. This requires their technical team to rewrite the script that produces the benefit statement to ensure contributions are reflected under the correct heading. Unfortunately, this is not a simple manual correction on our side, but a system-level adjustment that needs careful testing to prevent further errors.
We understand that this is taking longer than either you or we would like, and we agree that accurate statements are a basic obligation. Please rest assured that we are actively engaging with the software team to prioritise this fix and we will keep you updated on the progress.
Once the revised script is deployed, we will immediately issue you with a corrected statement.
We appreciate your patience while this technical matter is being resolved and again apologise for the inconvenience caused.
Kind regards,
The 10X Team
cracked the code of enlightenment - turns out fixing incorrect statements requires rewriting the script that generates the benefit statement. Groundbreaking discovery, right? They've framed it as some kind of "system-level adjustment," like we're talking about rewiring NASA's launch sequence. Newsflash: it's called programming. Teenagers do it between rounds of Fortnite. Stop blowing smoke about the "complexity" and either fix it with the resources you already have, or should I hire a programmer myself and let you guys pick up the tab?
cracked the code of enlightenment - turns out fixing incorrect statements requires rewriting the script that generates the benefit statement. Groundbreaking discovery, right? They've framed it as some kind of "system-level adjustment," like we're talking about rewiring NASA's launch sequence. Newsflash: it's called programming. Teenagers do it between rounds of Fortnite. Stop blowing smoke about the "complexity" and either fix it with the resources you already have, or should I hire a programmer myself and let you guys pick up the tab?
The 10x team, hard at work… or at least that’s what their silence suggests. Maybe they’re still in a top-secret boardroom, debating whether “fixing incorrect statements” requires divine intervention. At this rate, I’m half expecting them to launch a committee to investigate if code is, in fact, written by humans or conjured by AI. Stay tuned — progress is just one more excuse away.
The 10x team, hard at work… or at least that’s what their silence suggests. Maybe they’re still in a top-secret boardroom, debating whether “fixing incorrect statements” requires divine intervention. At this rate, I’m half expecting them to launch a committee to investigate if code is, in fact, written by humans or conjured by AI. Stay tuned — progress is just one more excuse away.
Thank you for your message. We note your concerns regarding the outstanding matter and fully acknowledge the frustration caused by the delays. Our last update to you was on 18 August, and we appreciate that the lack of further communication since then has added to your frustration.
To provide clarity: the correction process requires the rewriting of a data script that underpins how statements are generated in our investment system. This is not a simple adjustment, as the script governs how information is pulled, calculated, and displayed across all member statements. Rewriting and testing this script is therefore necessary to ensure accuracy and prevent further errors.
This work is being carried out by our third-party administrator, Ebsphere, who is the custodian of our investment application. As they manage the underlying system, we are dependent on them to implement and validate these changes before corrected statements can be released.
We are in active communication with Ebsphere and continue to prioritise this matter. While we are unable to commit to an exact completion date until their development and testing is finalised, we will ensure that you are kept updated on any material progress.
We sincerely apologise for the inconvenience and frustration this has caused, and we remain committed to resolving this as quickly as possible while ensuring the integrity of your investment records.
Kind regards,
The 10X Team
Thank you for your message. We note your concerns regarding the outstanding matter and fully acknowledge the frustration caused by the delays. Our last update to you was on 18 August, and we appreciate that the lack of further communication since then has added to your frustration.
To provide clarity: the correction process requires the rewriting of a data script that underpins how statements are generated in our investment system. This is not a simple adjustment, as the script governs how information is pulled, calculated, and displayed across all member statements. Rewriting and testing this script is therefore necessary to ensure accuracy and prevent further errors.
This work is being carried out by our third-party administrator, Ebsphere, who is the custodian of our investment application. As they manage the underlying system, we are dependent on them to implement and validate these changes before corrected statements can be released.
We are in active communication with Ebsphere and continue to prioritise this matter. While we are unable to commit to an exact completion date until their development and testing is finalised, we will ensure that you are kept updated on any material progress.
We sincerely apologise for the inconvenience and frustration this has caused, and we remain committed to resolving this as quickly as possible while ensuring the integrity of your investment records.
Kind regards,
The 10X Team
Breaking news: the 10x team has made a breakthrough - they've decided that thinking about fixing the problem is basically the same as fixing it. Genius. Why bother coding when you can just brainstorm excuses all day? Honestly, if they put half as much energy into the actual work as they do into inflating "complexity," we'd have the solution by now. But hey, let's not rush them - procrastination is clearly their core product.
Breaking news: the 10x team has made a breakthrough - they've decided that thinking about fixing the problem is basically the same as fixing it. Genius. Why bother coding when you can just brainstorm excuses all day? Honestly, if they put half as much energy into the actual work as they do into inflating "complexity," we'd have the solution by now. But hey, let's not rush them - procrastination is clearly their core product.
Fingers crossed. After all, when results are too hard to deliver, delays make a lovely consolation prize. Who knows—maybe tomorrow they’ll shock me… with something other than yet another excuse for why fixing it is a mythical impossibility.
Fingers crossed. After all, when results are too hard to deliver, delays make a lovely consolation prize. Who knows—maybe tomorrow they’ll shock me… with something other than yet another excuse for why fixing it is a mythical impossibility.
Lucky 13! Or unlucky, if you’re still waiting on the 10x team. They say patience is a virtue — but then again, so is competence. Sadly, neither seem to exist in this office. I’m starting to wonder if their strategy is to bore the problem into fixing itself. Bold approach.
Lucky 13! Or unlucky, if you’re still waiting on the 10x team. They say patience is a virtue — but then again, so is competence. Sadly, neither seem to exist in this office. I’m starting to wonder if their strategy is to bore the problem into fixing itself. Bold approach.
By Day 18, one thing’s clear — the only “benefit statement” 10x knows how to produce is: we did nothing, and called it something. Honestly, at this rate, I wouldn’t be surprised if they launch a press release celebrating their “achievement"
By Day 18, one thing’s clear — the only “benefit statement” 10x knows how to produce is: we did nothing, and called it something. Honestly, at this rate, I wouldn’t be surprised if they launch a press release celebrating their “achievement"
19 days and still counting. I think I finally get it — their strategy is to let me do all the updates while they contribute… absolutely nothing. Brilliant. If only laziness were billable, they’d be billionaires by now.
19 days and still counting. I think I finally get it — their strategy is to let me do all the updates while they contribute… absolutely nothing. Brilliant. If only laziness were billable, they’d be billionaires by now.
Three weeks in. At this point, the 10x team isn’t solving problems — they’re curating them. Keeping them alive, feeding them, nurturing them like houseplants. Except unlike plants, problems don’t grow into anything useful. But hey, at least they’ve built a legacy: the Guinness World Record for “Longest Delay Over the Simplest Task.”
Three weeks in. At this point, the 10x team isn’t solving problems — they’re curating them. Keeping them alive, feeding them, nurturing them like houseplants. Except unlike plants, problems don’t grow into anything useful. But hey, at least they’ve built a legacy: the Guinness World Record for “Longest Delay Over the Simplest Task.”
10X Team
10X Team
Day 26 and the only “progress” here is my growing collection of sarcastic updates. Meanwhile, the 10x team is proving that time travel is real — because somehow, they keep sending us back to Day 1 levels of productivity.
Day 26 and the only “progress” here is my growing collection of sarcastic updates. Meanwhile, the 10x team is proving that time travel is real — because somehow, they keep sending us back to Day 1 levels of productivity.
Four weeks. 28 days. Entire TV shows get filmed, edited, and aired in less time. But fixing one incorrect statement? Nah, that’s apparently a task for the next century. Bravo, 10x. You’ve turned procrastination into performance art.
Four weeks. 28 days. Entire TV shows get filmed, edited, and aired in less time. But fixing one incorrect statement? Nah, that’s apparently a task for the next century. Bravo, 10x. You’ve turned procrastination into performance art.
One full month. 30 days. A complete lunar cycle. In this time, crops have grown, empires have risen, children have learned to walk — but the 10x team? Still wrestling with the life-altering challenge of rewriting a script. Congratulations, 10x, you’ve achieved the impossible: turning a one-hour task into a month-long monument of incompetence. Truly historic.
One full month. 30 days. A complete lunar cycle. In this time, crops have grown, empires have risen, children have learned to walk — but the 10x team? Still wrestling with the life-altering challenge of rewriting a script. Congratulations, 10x, you’ve achieved the impossible: turning a one-hour task into a month-long monument of incompetence. Truly historic.
Today’s special guest: the intern. The intern bravely suggested, “Why don’t we just fix the code?” Don’t worry — HR quickly escorted them out for “thinking too radically.” That’ll teach them.
Today’s special guest: the intern. The intern bravely suggested, “Why don’t we just fix the code?” Don’t worry — HR quickly escorted them out for “thinking too radically.” That’ll teach them.
Guest star cameo: the imaginary programmer I keep threatening to hire. Unlike the 10x team, this fictional character actually solved the issue in 20 minutes — but apparently his work is “too efficient” to be adopted.
Guest star cameo: the imaginary programmer I keep threatening to hire. Unlike the 10x team, this fictional character actually solved the issue in 20 minutes — but apparently his work is “too efficient” to be adopted.
Thank you for your feedback and comments.
We can confirm that the error has been corrected and all contributions are reflecting under the right naming status on the statement.
Regards,
The 10X Team
Thank you for your feedback and comments.
We can confirm that the error has been corrected and all contributions are reflecting under the right naming status on the statement.
Regards,
The 10X Team
