In an era where global finance is increasingly defined by digital agility, a quiet but profound transformation is rippling through corporate treasury departments. The mandate: transition to the ISO 20022 messaging standard. While the shift promises a more streamlined, data-rich future for international payments, it has exposed a significant vulnerability in the modern corporate technology stack. Many organizations running sophisticated ERP systems like IFS Cloud and NetSuite are discovering that their legacy data structures are fundamentally incompatible with the new, rigorous demands of global banking regulators.
To address this, Nordic ERP services firm Addovation has forged a strategic partnership with payments connectivity specialist Cobase. The collaboration aims to bridge the gap between static ERP records and the dynamic, structured requirements now being enforced by banks across Europe and beyond. As payment messages face increasing rejection rates due to "unstructured" address data, this joint venture positions itself as a critical lifeline for corporate finance teams struggling to maintain liquidity in an era of tightening technical compliance.
The Regulatory Driver: The Shift to ISO 20022
At the heart of this challenge is the decommissioning of unstructured data fields in financial messaging. Historically, international and SEPA (Single Euro Payments Area) payments allowed for "free-text" blocks for address information. However, organizations such as SWIFT and the European Payments Council (EPC) have spearheaded a move toward full structural compliance.
Under the evolving ISO 20022 standard, payment messages must contain specific, dedicated fields for town and country, rather than relying on loosely formatted text. The intent is clear: to enhance automated processing, reduce fraud, and improve the speed of cross-border settlements. However, the path to implementation has been fraught with ambiguity. While the initial deadline for global compliance was slated for November 2026, both SWIFT and the EPC have introduced postponements.
Despite these delays, the regulatory momentum remains irreversible. As of July 2026, data from SWIFT indicated that approximately 60 percent of global payment messages were still failing to meet the new structured address requirements. This represents a staggering compliance backlog that threatens to disrupt the operations of countless multinational corporations.
Chronology of Compliance: A Moving Target
The regulatory timeline has proven to be a double-edged sword for the corporate sector. While delays in the formal global deadline have provided some breathing room, they have also fostered a false sense of security.
- The Initial Vision: Regulators set an ambitious goal for universal ISO 20022 adoption, aiming to harmonize financial messaging across the globe.
- The Reality Check: As 2025 progressed, it became clear that the corporate sector was not prepared for the granular data requirements of the new standard.
- The Shift in Deadlines: Recognizing the widespread lack of readiness, major bodies like SWIFT and the EPC signaled delays to the 2026 deadline. However, these are not blanket extensions.
- The "De Facto" Deadlines: Crucially, many individual banks and national jurisdictions have opted to accelerate their own enforcement. Some institutions are already rejecting or queuing payments that lack structured data, regardless of the official global timeline.
- The Verification of Payee (VoP) Layer: Adding further pressure, euro-area banks began mandating the verification of payee names against account numbers in October 2025. This added a second layer of complexity, forcing treasury departments to ensure their master data is not just structured, but also impeccably accurate.
Supporting Data: Why ERPs Are Struggling
The compliance burden has landed squarely on the shoulders of the corporate treasury and finance functions. The primary issue is that the data required for these payment messages originates in the supplier and customer master records stored deep within the ERP system.
For years, these systems were configured to prioritize operational flexibility over rigid data structures. Changing this requires a fundamental re-architecting of how customer and vendor information is captured, validated, and stored. For a mid-market company with thousands of international suppliers, manually remediating address records to fit ISO 20022 standards is an insurmountable task.
The data suggests that the problem is not merely a lack of effort, but a fundamental mismatch between legacy ERP configurations and the modern digital banking landscape. With 60% of messages still non-compliant as of mid-2026, the reliance on manual intervention or "workarounds" is becoming a significant operational risk, increasing the cost of processing and the likelihood of failed payments.
The Product Architecture: A Three-Layer Solution
Addovation’s partnership with Cobase introduces a pragmatic solution designed to minimize disruption to the client’s core operations. The architecture is built on a three-tier model:
- The Core ERP (IFS Cloud or NetSuite): The existing ERP system remains the single source of truth for financial data. By keeping the core untouched, Addovation ensures that companies do not need to undergo a painful and costly re-implementation of their entire enterprise software suite.
- The Connectivity Layer (Cobase): Cobase acts as the sophisticated middleware between the ERP and the banking ecosystem. It normalizes outgoing payment files and incoming bank statements into the specific formats required by each of the client’s 300+ supported banks across 90 countries. This removes the need for companies to maintain individual host-to-host connections with every bank they partner with.
- The Managed Service (Addovation Engage): Addovation provides the glue that binds the system together. Through their "Addovation Engage" service, they handle the technical implementation and the ongoing management of the integration, ensuring that as bank requirements change, the system adapts without requiring client intervention.
Official Perspectives: Aligning Technology with Regulation
The partnership is rooted in the philosophy that "one platform cannot do everything." Fredrik Wingren, Chief Revenue Officer at Addovation, emphasizes that the modern treasury function requires a modular approach.
"Banks expect more from the payment data your ERP sends them, and the rules keep changing," says Wingren. "We don’t think one platform should try to do everything. The ERP system stays at the core, Cobase handles the connection to your banks, and we make sure it all works together, from implementation through daily operation."
This perspective highlights a shift in the ERP services market. Rather than pushing for a monolithic, all-encompassing system, service providers are increasingly opting for specialized, interoperable components. By focusing on the "integration layer," Addovation allows finance teams to achieve compliance without losing the functionality of the ERP systems they have spent years optimizing.
Implications for the Corporate Treasury
The implications of this shift are profound. For Chief Financial Officers and Treasury Managers, the era of "set and forget" for payment processes is officially over.
1. Compliance as a Data Problem
The most critical realization for the sector is that ISO 20022 is not just a connectivity issue; it is a master data management issue. If the data in the ERP is dirty, incomplete, or unstructured, no middleware provider can magically resolve it. Companies must now audit their supplier records with the same rigor they apply to their financial reporting.
2. The Competitive Landscape
The market for ERP-to-bank connectivity is rapidly becoming a battleground. Established Treasury Management System (TMS) vendors, direct bank-to-host providers, and specialist middleware firms like TIS (Treasury Intelligence Solutions) are all vying for the same corporate budgets. Addovation and Cobase are looking to differentiate themselves by focusing on the mid-market segment—specifically those running IFS and NetSuite—and by providing a low-friction entry point through their "readiness assessment."
3. The Shift to "Readiness-First" Consulting
Addovation is currently leading its engagement strategy with a 30-minute structured-address readiness assessment. This move acknowledges that many organizations are paralyzed by the sheer scope of the compliance task. By identifying specific gaps in master records and mapping them against the specific deadlines of a client’s banking partners, they are turning a complex regulatory burden into a manageable project.
Conclusion: The Future of Payment Connectivity
As we move toward the finalization of global ISO 20022 adoption, the gap between the compliant and the non-compliant will widen. Companies that view this as a purely technical, IT-driven problem are likely to face significant operational headwinds as their payments continue to face rejection. Conversely, those that treat this as an opportunity to modernize their data architecture—leveraging specialized integration partners like Addovation and Cobase—will find themselves with a more robust, transparent, and efficient treasury function.
The uncertainty of deadlines may have bought the industry some time, but it has not altered the trajectory. The future of global finance is structured, digital, and data-driven. For the mid-market firms running IFS Cloud or NetSuite, the time to address these structural weaknesses is not when the final deadline passes, but while there is still a window to act with precision and intent. The partnership between Addovation and Cobase serves as a timely reminder that in the complex ecosystem of modern finance, the most successful firms will be those that build bridges between their legacy data and the future of global payments.
