OasisPro · ISOWorks · ISO 20022 Middleware · CBPR+ · Any ERP
ISO 20022 middleware
for any ERP. Any bank.
ISO 20022 middleware is no longer optional for any business making cross-border payments. ISOWorks by OasisPro is the most affordable, most reliable ISO 20022 connector in the market, built to plug into any ERP and translate payment data into the structured CBPR+ format your bank now requires. No enterprise software licence. No lengthy integration project. One connector, any ERP, every bank.
The Swift coexistence period ended in November 2025. Cross-border payment messages now move almost entirely in ISO 20022 MX format, and the next major deadline lands in November 2026.
From that date, fully unstructured postal addresses are removed from CBPR+ messages entirely. Payments without structured town and country data will be rejected outright, not delayed and retried. For businesses running payments out of an ERP that was never built with ISO 20022 in mind, that is a direct operational risk landing on a fixed date.
One connector. Any ERP. Every bank ISO 20022 ready.
ISOWorks sits between your ERP and your banking partners, converting payment instructions and reporting messages into fully structured ISO 20022 MX format. Your ERP keeps producing payment data the way it always has. ISOWorks handles the translation, validation, and routing so every payment clears without rejection.
November 2026: the ISO 20022 deadline that catches ERPs out
The end of the MT coexistence period in November 2025 was the headline event. The deadline that matters most for ERP-driven payments is the one that follows it.
From November 2026, fully unstructured postal addresses are no longer permitted in Swift CBPR+ messages. Payments must carry, at minimum, structured town name and country fields for both debtor and creditor. Swift has confirmed this is a community-driven standards change agreed through formal governance, not a temporary measure subject to further delay.
After November 2026, payments with unstructured addresses are rejected. Not delayed. Rejected.
This requirement applies to all CBPR+ cross-border payments and urgent domestic RTGS transactions. If your ERP cannot produce structured town and country data in the correct ISO 20022 fields, those payments fail outright and require resubmission. For businesses running high payment volumes, that is not a minor inconvenience. It is a direct threat to payment runs, supplier relationships, and payroll.
Most ERPs were not built with ISO 20022 structured messaging as a native requirement. Many still generate payment files in legacy formats that banks have historically translated on the business's behalf.
Swift's own guidance confirms that in-flow translation and contingency processing now carry additional charges from January 2026 onward, and those workarounds do not solve the structured address requirement landing in November. ISOWorks closes that gap directly at the ERP level, before the payment ever reaches your bank.
What ISOWorks does between your ERP and your bank
ISOWorks is ISO 20022 middleware. It is not a banking platform and it does not replace your ERP. It sits in the middle, taking the payment and reporting data your ERP already produces and converting it into fully compliant ISO 20022 MX messages before transmission to your banking partners.
Format conversion
Payment data from your ERP is converted automatically into the correct ISO 20022 message type for the transaction: pain.001 for initiation, pacs.008 or pacs.009 for credit transfers, camt for reporting and cancellations.
Structured address generation
ISOWorks generates fully structured or hybrid postal addresses to CBPR+ specification, meeting the November 2026 requirement so payments are never rejected for missing structured town and country data.
Real-time validation
Every message is validated against current CBPR+ usage guidelines before transmission. Errors are caught and flagged at the middleware layer, not discovered as a rejection from your bank days later.
Multi-bank routing
One ISOWorks connection routes payments correctly across every banking partner your business uses, regardless of which bank, country, or payment network each transaction needs to reach.
Status tracking and reporting
Full visibility into every payment instruction from submission through to settlement. Track status, investigate exceptions, and reconcile against camt.053 and camt.054 reporting without manual file handling.
Full audit trail
Every message logged, timestamped, and retained for compliance and reconciliation. Complete traceability for finance teams, auditors, and treasury operations across every payment processed.
CBPR+ message types ISOWorks handles
ISOWorks covers the core CBPR+ message set businesses actually use in day-to-day payment operations, from initiation through to reporting and exception handling.
The most affordable ISO 20022 middleware without compromising reliability
The ISO 20022 middleware market is dominated by large banking technology vendors charging enterprise software licensing rates. For mid-market businesses and growing ERP environments, those costs are difficult to justify against the actual payment volumes being processed.
OasisPro built ISOWorks to remove that cost barrier without cutting corners on reliability. Payment infrastructure is not a place to compromise. ISOWorks is priced for accessibility while maintaining the validation, uptime, and audit standards that mission-critical payment processing demands.
What large ISO 20022 vendors charge for
- Enterprise software licensing fees
- Per-bank-connection setup charges
- Lengthy implementation projects
- Annual maintenance contracts on top of licence cost
- Minimum volume commitments
- Dedicated infrastructure overhead passed to the customer
What you actually pay for with ISOWorks
- Affordable pricing scaled to your business
- One connection covers all your banking partners
- Fast deployment, no lengthy project required
- Transparent pricing with no hidden maintenance fees
- No minimum volume requirements
- Enterprise-grade reliability at mid-market pricing
ISOWorks pricing models
ISOWorks is available on flexible pricing structures so the cost reflects your actual payment volume, not a fixed enterprise licence regardless of usage.
Pay only for the payments you process. Ideal for businesses with variable payment volumes or starting their ISO 20022 migration.
- ✓ No monthly commitment
- ✓ All message types included
- ✓ Scale up or down freely
Predictable monthly cost with a set transaction allowance. Best for businesses with consistent payment volumes across multiple banks.
- ✓ Predictable cost
- ✓ Priority support included
- ✓ Volume discounts available
Annual commitment with maximum savings. Best for high-volume businesses with established multi-bank payment operations.
- ✓ Lowest per-transaction cost
- ✓ Dedicated account manager
- ✓ SLA and uptime guarantees
Why ERP-agnostic matters for ISO 20022 middleware
Many businesses run payments out of more than one system, or plan to migrate ERPs in the coming years. Middleware tied to a single ERP vendor creates a second migration project the moment your underlying ERP changes.
ISOWorks is built to be ERP-agnostic from the ground up. The connection point is the payment data itself, not the ERP producing it. That means the middleware investment survives ERP changes, multi-entity environments running different systems, and finance teams that need one consistent payment process regardless of what sits underneath it.
Why reliability cannot be an afterthought in payment middleware
Payment infrastructure failures are not abstract risks. A rejected payment run means missed supplier payments, delayed payroll, or a failed cross-border settlement with real financial and reputational consequences.
ISOWorks is built specifically for payment-critical environments. Every message is validated before it leaves the middleware layer, every transmission is logged and tracked, and exception handling is built in rather than bolted on. The platform is designed around the assumption that payment failures are unacceptable, not an occasional inconvenience to be tolerated.
Validated before transmission. Tracked after submission. Logged for every transaction.
ISOWorks does not send a payment instruction and hope it clears. Every message is validated against current CBPR+ usage guidelines before it leaves your environment, and full status tracking means your finance team always knows exactly where every payment stands.
ISO 20022 middleware: what to check before you commit
Not every ISO 20022 connector in the market is built the same way. Before committing to any provider, these are the questions that determine whether the middleware will hold up under real payment volume.
| Question to ask | Typical enterprise vendor | ISOWorks |
|---|---|---|
| Is the middleware tied to a specific ERP? | Often yes, requiring a separate migration if you change ERPs. | ERP-agnostic. Any ERP connects. |
| Are structured addresses generated automatically for CBPR+? | Varies. Often requires manual data cleansing first. | Generated automatically to spec. |
| What is the pricing model? | Enterprise licence plus per-connection and maintenance fees. | Transparent, scaled to volume. |
| Is message validation done before or after transmission? | Often after, meaning rejections are discovered late. | Before transmission, every time. |
| How long does implementation take? | Months, with a structured enterprise project. | Fast deployment, days to weeks. |
Why OasisPro built ISOWorks
OasisPro builds ERP and finance compliance middleware as a specialism, not a side project. ISOWorks sits alongside the OasisPro eInvoicing Gateway and CrystalWorks as part of a connected suite addressing the compliance and infrastructure gaps that ERP vendors leave open.
- Most affordable in the market: ISOWorks removes the enterprise licensing overhead that makes ISO 20022 middleware unaffordable for mid-market businesses, without compromising on reliability.
- ERP-agnostic by design: One connector works with any ERP. Your middleware investment survives ERP migrations and multi-entity environments running different systems.
- CBPR+ structured addresses handled automatically: The November 2026 deadline is covered from day one. No manual data cleansing project required before go-live.
- Built for reliability, not just compliance: Validation before transmission, full status tracking, and complete audit logging. Payment infrastructure that holds up under real volume.
- Fast deployment: ISOWorks can be deployed in weeks, not the months typical of enterprise ISO 20022 implementation projects.
- Part of a connected compliance suite: OasisPro also delivers the EU eInvoicing Gateway and CrystalWorks, giving businesses one specialist partner across payments, invoicing, and IFS Cloud reporting compliance.
November 2026 is closer than your payment run schedule.
Talk to OasisPro about ISOWorks. We will review your ERP, your banking partners, and your current payment data structure, then confirm exactly what ISOWorks needs to have you CBPR+ ready before the deadline.
Frequently asked questions about ISO 20022 middleware and ISOWorks
What is ISO 20022 middleware and why do I need it?
ISO 20022 middleware sits between your ERP and your banks, converting payment instructions and reporting messages into the structured ISO 20022 MX format that Swift CBPR+ and most banks now require. Without it, payments built on legacy data structures risk rejection, delay, or extra translation charges from your bank, particularly after the November 2026 structured address deadline.
Does ISOWorks work with any ERP?
Yes. ISOWorks is built as ERP-agnostic middleware. It connects to SAP, Oracle, Microsoft Dynamics, Odoo, IFS Cloud, NetSuite, Infor, and any other ERP capable of producing payment data, converting and routing it to your banking partners in ISO 20022 format. The connection point is the payment data itself, not a specific ERP vendor's architecture.
Is ISOWorks ready for the November 2026 structured address deadline?
Yes. From November 2026, fully unstructured postal addresses are no longer accepted in Swift CBPR+ messages and non-compliant payments will be rejected outright. ISOWorks generates fully structured and hybrid addresses to CBPR+ specification automatically, so payments clear without delay and without requiring a manual data cleansing project beforehand.
How does ISOWorks compare on price to other ISO 20022 middleware providers?
ISOWorks is positioned as the most affordable ISO 20022 middleware in the market without compromising on reliability. Large banking technology vendors charge enterprise software licensing rates, per-connection setup fees, and ongoing maintenance contracts. OasisPro removes that overhead and prices ISOWorks to be accessible to businesses of any size, with per-transaction, monthly, and annual options available.
What message types does ISOWorks support?
ISOWorks supports the core CBPR+ message set including pain.001 payment initiation, pacs.008 and pacs.009 credit transfers, camt.052, camt.053 and camt.054 account reporting, camt.029 and camt.056 case management and cancellation messages, and pacs.004 returns. Coverage is maintained as Swift releases new CBPR+ guidelines.
How reliable is ISOWorks for mission-critical payment processing?
ISOWorks is built specifically for payment-critical environments where failed or delayed messages have direct financial consequences. It includes message validation before transmission, full delivery tracking, and complete audit logging, so businesses always know the status of every payment instruction rather than discovering a rejection after the fact.
ISO 20022 middleware that works with any ERP. Built for the deadline that's actually coming.
The end of MT coexistence in November 2025 was the headline moment. November 2026 is the deadline that catches ERPs and payment teams unprepared, because structured address data is not something most ERPs were built to produce natively.
ISOWorks closes that gap directly, for any ERP, at a price that does not require an enterprise software budget to justify. One connector, every bank, every CBPR+ requirement covered before the deadline lands.
OasisPro are ERP and finance compliance specialists building ISOWorks, the EU eInvoicing Gateway, and CrystalWorks for businesses across the UK and Europe. · info@oasispro.co.uk · 01865 538071 · oasispro.co.uk