Forge Json
Get Started
import

Convert Bank XML to JSON

Normalize legacy banking XML into schema-validated downstream JSON

  • Parses ISO 20022 and legacy bank XML
  • Extracts canonical account + transactions
  • Validates downstream contract
  • Runs locally in your browser

Paste a bank statement XML — instant preview, runs locally in your browser, no upload.

Continue

Why this package exists

Common problems

  • Banks, payment processors, and reconciliation systems still emit XML — ISO 20022, camt.053, MT940 wrappers, and gateway-specific formats. Downstream services expect normalized JSON.
  • Attribute-shaped values (`<Amount currency="EUR">500.00</Amount>`) need a deterministic JSON shape so reconciliation, analytics, and AI tooling can consume them without per-source adapters.
  • XML’s singular-vs-array ambiguity (one transaction parses as an object, two as an array) makes downstream pipelines brittle without explicit array stabilization.

When to use

Use this when upstream banking or payment systems emit XML and you need a normalized, schema-validated JSON shape before forwarding to reconciliation pipelines, analytics warehouses, or AI tooling.

Expected outcome

A normalized JSON tree with the canonical account, statement period, balance entries, and transaction list — paired with a validation report so downstream services can safely consume the payload.

Automatically detects

  • Bank statements
  • ISO 20022 wrappers
  • Transaction lines
  • Balance entries
  • Currency attributes
  • Reconciliation feeds

What the wizard asks

3 steps

Each step shows your input, the question, and a preview of the output.

  1. 1

    Parse the bank statement XML into JSON?

    Convert the raw XML statement into a JSON tree so every downstream utility (pick fields, validate, normalize) can operate on it natively.

  2. 2

    Which fields should reach downstream systems?

    Strip vendor-specific noise. Keep the canonical account, statement period, balances, and transaction list reconciliation systems require.

  3. 3

    Validate the statement matches your downstream contract?

    Confirm the parsed statement has the required account fields, balance entries, and transaction list before forwarding downstream.