Integration and migration-enabling software

Arx Engineering builds adapters for integrations and migrations between core financial systems and external networks: banks for payments, exchange channels for e-invoicing. Facilitate your integration or migration using a canonical data model and let the adapter handle format-specific rules.

All adapters run 100% on-premises.

ISO 20022 · Payments

i22-MBA: ISO 20022 Multi-Bank Adapter

On-premises software for Sweden's migration from legacy Bankgirot to bank-specific ISO 20022 XML. Built-in data scrambler and audit trail.

  • Multi-profiles
  • Dual-run Migration
  • Audit Trail
Explore i22-MBA →
EN 16931 · E-invoicing

e31-MFA: EN 16931 Multi-Format Adapter

Validate and generate PINT-files in national XML-variants before exchange channel handoff. EN 16931-aligned canonical model.

  • PINT / EN 16931
  • Self-billing
  • Credit Notes
Explore e31-MFA →
i22-MBAe31-MFA
StandardISO 20022EN 16931 / PINT
ProfilesDebit banksCountry-specific e-invoice formats
Canonical TypesPaymentBatch, StatementInvoice, CreditNote
MarketsSwedenUAE, Oman, Japan, EU
Software Version0.2.50.1.0

The practical security and deployment model for i22-MBA (ISO 20022) and e31-MFA (EN 16931 / PINT).

Deployment model

On-premises by design
The adapters run on customer-controlled infrastructure. No invoice or payment files are sent to a vendor cloud.

Operating environment
Current releases run as Node.js software (Windows / Linux), used either as a CLI/batch component or embedded as a library depending on your integration model.

Data boundary

Payments (i22-MBA)
All conversion and validation occurs on your infrastructure; payment data is not transmitted to any external systems.

E-invoicing (e31-MFA)
Invoice data stays inside your environment; e31-MFA validates, parses, and generates structured XML locally before your exchange-channel handoff.

Connectivity & responsibilities

No transmission layer
i22-MBA and e31-MFA produce and read files; they do not transmit files to banks or exchange channels and do not store transfer credentials.

Separation of responsibilities
Transport, participant registration, access-point / ASP responsibilities, and reporting remain with your existing providers and agreements.

Licensing

Offline licensing
Signed licenses control permitted profiles and optional modules (e.g., bank profiles for i22-MBA and format packs for e31-MFA) without requiring phone-home validation.

Support model & sample handling

Keep sensitive data inside
When diagnostic samples are required for testing or support, i22-MBA supports local anonymization workflows so real payment information does not have to leave your environment.

Deterministic diagnostics
Both product lines are designed to return stable, operator-friendly diagnostics (validation codes / profiles) to shorten the remediation loop.

Planning a payment or e-invoicing integration?

Tell us about your banks, formats, systems, and timeline.

Reach Out