On-premises software that sits between your own systems - payroll, ERP, or receivables - and your 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 internal format, and i22-MBA handles the conversion to and from each bank's format. It also includes a built-in scrambler that anonymizes sample data locally, so real payment information never has to leave your environment for testing or support.
Tell us how i22-MBA can help your migration→Swedish organizations are moving from Bankgirot's legacy file formats to ISO 20022. The catch: every bank implements ISO 20022 slightly differently, 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 XML - and parses each bank's responses back into the same neutral format.
Turn neutral payment data into the correct profile-specific pain.001 XML, then read each bank's pain.002 response back into a clear payment-status view.
Parse BGMax files or camt statement XML into a single canonical Statement format your systems can consume consistently.
Compare legacy BGMax against new camt feeds with a semantic difference tool, so you can confirm parity before switching off the old format.
Produce bank-ready payment files, or validate pain.001 your ERP already generates against the bank's schema.
Convert pain.002 responses into a clear, structured payment-status view for reconciliation and audit.
Normalize BGMax and camt.052/053/054 into one canonical Statement model.
Read and write Leverantörsbetalningar (LB) and SALA salary files alongside the new ISO formats during transition.
Dual-run reports for both receivables (BGMax vs camt) and status (LB status vs pain.002) to de-risk cutover.
Anonymize sample data locally, so real payment information never has to leave your environment for testing or support.
All conversion happens on your own infrastructure, and payment data is never sent to a vendor cloud. When samples do need to leave the building - for a support ticket or a test fixture - the built-in scrambler anonymizes the personal data in legacy Bankgirot and canonical files first, locally and irreversibly.
i22-MBA does not transmit files to banks or hold bank credentials. It produces and reads the files; your existing transfer channels and agreements stay exactly as they are.
Cryptographically signed license files control which bank profiles and deployments are permitted - verified offline, with no phone-home.
Use it as a TypeScript library embedded in your ERP or validation service, or as a command-line tool for batch jobs.
Across these profiles, i22-MBA works with the ISO 20022 messages - pain.001 for payments, pain.002 for status, and camt.052/053/054 for statements - alongside legacy Bankgirot BGMax, Leverantörsbetalningar (LB), and SALA salary files.
Each bank is supported through a licensed profile that captures its specific ISO 20022 rules.
Let's discuss how i22-MBA fits your banks, your systems, and your timeline.
Get in touch