On-premises software that sits between your ERP-systems and your settlement banks during Sweden's shift from legacy Bankgirot formats to bank-specific ISO 20022 XML under Transformationsprogrammet.
Describe payments and statements once in a neutral JSON format and use i22-MBA to Convert to and from any bank's format of your choice.
Optional add-on modules include an integrated data scrambler so that sensitive payment information never has to leave your environment for testing or support.
Swedish organizations are moving from Bankgirot's legacy file formats to ISO 20022. Every bank implements ISO 20022 slightly differently using its own flavor of ISO 20022, with its own message versions, field rules, and validation requirements.
i22-MBA removes that complexity. You integrate once against a stable, bank-neutral data model, and the adapter generates the correct bank-specific ISO 20022 XML and parses supported banks' responses back into the same neutral JSON format.
Turn legacy or neutral payment data into a correct bank-specific pain.001 XML, then parse the returned pain.002 response for a complete payment-status view.
Check inbound camt.053 and camt.054c CRBG statements against semantic rules for inbound settlement, or generate your own statements from legacy BGMax files.
Compare both legacy BGMax and pain.001 against new camt.054d NSAL flows for outbound settlement with semantic reports that help de-risk cutover.
All conversion happens on your own infrastructure, and payment data is never sent to a vendor cloud. When samples need to leave the building, the scrambler add-on anonymizes Personal Identifiable Information (PII) in legacy, canonical, and ISO 20022 XML files locally.
i22-MBA does not transmit files to banks or hold bank credentials. It produces and reads the files. Your existing transfer channels and agreements remain unchanged.
Cryptographically signed offline licenses control which debit bank profiles and optional modules (scrambler, cross-border, cancellation, money order) are permitted.
Embed as a TypeScript library or run as CLI for batch jobs.
ERP / payroll / treasury teams preparing for Sweden’s ISO 20022 migration who need fast, concrete feedback on bank-profile fit before migration cutover.
i22‑MBA has been run on‑premises at a customer site as a pre‑flight/pilot during an ISO 20022 integration between an ERP and a settlement bank. In that deployment, the adapter flagged multiple bank‑profile issues early and provided fast, actionable remediation feedback.
Twelve licensed debit bank profiles with message-type coverage for pain.001 outbound payments, pain.002 status, and camt receivables. Cross-border, money order, and payment cancellation features require optional add-on modules on your Order Form.
| Bank profile | pain.001 | pain.002 | Receivables | Cancellation | Notes |
|---|---|---|---|---|---|
| Citibank | 001.03 | — | — | — | PIUID payment methods (license for SEPA) |
| Danske Bank | 001.03 | 001.03 | camt.052–054 | Yes (license) | SE/DK/NO/FI + SEPA/URGP; payout-day |
| DNB | 001.03 or 001.09 (draft) | 001.03/001.10 | camt.053/054 | Yes (license) | — |
| Ekobanken | 001.09 | Partial | camt.053 Partial | — | — |
| Handelsbanken | 001.03 | 001.03 | camt.052–054; BGMax dual-run | — | Payout-day execution |
| ICA Banken | 001.03 | — | camt.054 Partial | — | — |
| Länsförsäkringar Bank | 001.09 | 001.10 | camt.053/054; BGMax dual-run | — | Pilot-validated; settlement dual-run |
| Nordea | 001.03 or 001.09 | 001.03/001.10 | camt.052–054 | Yes (license) | Dual MIG track |
| SEB | 001.03 or 001.09 | 001.03/001.10 | camt.053/054 | — | Personnummer; SEPA/Nordic corridors (license) |
| Sparbanken Syd | 001.09 | Partial | camt.053 Partial | — | Cross-border/SEPA (license); internetbank only |
| Swedbank | 001.03 | 001.03 | camt.054 (053 fwd-compat) | — | CHK money order (license); MIG 1.0 profile |
| Ålandsbanken | 001.03 | 001.02 Partial | — | — | — |
Partial — implemented with known gaps. — — not applicable for this profile. (license) — requires add-on module on Order Form (cross-border-outbound, money-order-outbound, cancellation-outbound / cancellation-inbound).
Profile support is not a single binary state. Depending on the bank corridor and message set, a profile can be validated at different depths:
Let's discuss how i22-MBA fits your banks, your systems, and your timeline.
Reach Out