Wise is discussing a settlement with HM Revenue & Customs after software supplied by a third party generated incorrect tax statements for about 4,000 UK customers using the fintech’s investment products.
The errors affected statements covering 2021 through 2025 and involved income and capital-gains figures used in self-assessment tax returns, according to reports by the Financial Times and other financial publications. Wise said it has fixed the issue, issued corrected statements and is addressing potential customer liabilities.
The episode is a customer-remediation and third-party-control failure, not evidence that every recipient paid the wrong tax. Wise has said individual circumstances differ, so an incorrect statement did not necessarily produce an incorrect tax payment. The amount of any aggregate shortfall, overpayment or settlement has not been disclosed.
What Wise and the reports say happened
Finance Magnates and Scottish Financial News reported that Wise contacted affected customers after internal checks identified an error in software provided by an unnamed third-party supplier. The software had produced incorrect investment-income and capital-gains figures for customers of Wise Interest and Stocks.
Wise said in a statement carried by both publications: “Wise identified that errors in software used by a third-party provider led to incorrect tax statements for a limited number of customers using our Wise Interest and Stocks investment products. We have fixed the issue, issued corrected statements to affected customers and are proactively redressing potential liabilities, with no ongoing risk to customers.”
The company is reported to be discussing a “bulk settlement” with HMRC that could cover tax shortfalls, while customers who overpaid would be compensated. No completed agreement with HMRC has been announced in the material reviewed, and neither the supplier nor the precise software defect has been identified.
A four-year reporting problem raises control questions
The operational concern extends beyond the initial calculation error. Statements covering multiple tax years passed through the reporting process before the problem was found, leaving questions about how Wise validated supplier-generated calculations, reconciled customer records and tested tax-document changes.
Using a vendor for specialist calculations does not remove the customer-facing firm’s responsibility for output delivered under its brand. For payments and fintech operators, the practical control chain includes documented calculation rules, test cases for income and capital gains, change-management checks, exception monitoring, data lineage and reconciliations against underlying transactions. It should also include a remediation plan capable of identifying who relied on an incorrect document and whether a corrected filing, payment or refund is required.
The available reporting does not establish whether Wise’s checks failed at one stage or across several stages. It also does not show when the software defect began, when Wise first had enough information to identify it or how many of the approximately 4,000 customers submitted inaccurate returns. Those remain material unanswered questions.
Why the redress design matters
A bulk arrangement could reduce the administrative burden on customers, but its scope will matter. Customers may have different filing histories, marginal tax rates and investment activity. Some may owe additional tax, some may have overpaid, and others may have received an incorrect statement without any change to their final liability.
Effective remediation therefore requires more than reissuing a document. Wise will need to explain which tax years and products were affected, whether customers must amend returns, how interest or penalties will be handled, what evidence customers should retain and how compensation will be calculated. The reviewed reports do not provide a timetable for an HMRC agreement or completion of individual redress.
For the wider fintech sector, the case is a reminder that outsourced reporting systems can create long-lived conduct and compliance exposure even when the underlying investment or payment ledger remains available. Firms need controls that can detect bad derived data before it reaches customers—and a response process that restores customers to the position they would have occupied had the supplier output been correct.