MX to MX Conversions

Why convert MX to MX

Most conversions change family, MT to MX or the reverse. A few problems sit entirely inside ISO 20022 (MX): a bank sends an account report (camt.052) where your ERP expects a statement (camt.053), a bank's camt.053 fails your importer's schema check, or a statement arrives in the old .001.02 version. For those, transmute offers a short, fixed list of same-family pairs:

No other MX to MX pair and no MT to MT pair is supported. camt.053 → camt.052, camt.054 → camt.053 and pacs.008 → pacs.008 are deliberately absent: each would change what the message claims. Asking for one is a unsupported-conversion 422.

Report to statement (camt.052 → camt.053)

curl -sS -X POST "https://api.transmute.403fin.io/v1/convert?to=camt.053" \
  -H "Authorization: Bearer $TRANSMUTE_KEY" \
  -H "Content-Type: application/xml" \
  --data-binary @report.camt052.xml
# "meta": {"detectedType": "camt.052", "detectedVersion": "camt.052.001.08",
#          "targetType": "camt.053.001.08", ...}

An account report is an intraday or interim view; a statement is the end-of-period record. Two gaps between them are reported, never papered over:

[
  { "code": "STATEMENT_BALANCE_ABSENT", "severity": "warning",
    "sourceField": "Rpt[0]/Bal", "targetField": "Stmt[0]/Bal",
    "detail": "account report carries no CLBD closing booked balance; balances carried verbatim by type, none retyped to CLBD" },
  { "code": "LEGAL_SEQUENCE_ABSENT", "severity": "info",
    "sourceField": "Rpt[0]/LglSeqNb", "targetField": "Stmt[0]/LglSeqNb",
    "detail": "account report carries no legal sequence number; none synthesized (element is optional)" }
]

A report that does carry a CLBD balance and a legal sequence number converts with neither warning.

Re-render (camt.053 → camt.053, camt.052 → camt.052)

A re-render parses the document and writes it again. It is not a byte-for-byte copy:

• Version upgrade. .001.02 input comes out as .001.08, with the elements renamed in .08 (such as BIC to BICFI) moved to their new names. To go the other way, add toVersion=camt.053.001.02; see Message Versions.
• Schema-valid output. The sequence numbers ElctrncSeqNb and LglSeqNb must be at most 18 digits. A value that is longer or not a plain number is dropped, never shortened (a shortened sequence number would be a wrong one), with FIELD_OVERSIZED (lossy). Both elements are optional, so the output stays valid.
• Content with no place in the model is dropped with a warning. Elements transmute does not model surface as DROP_FIELD warnings. Re-rendering promises clean, schema-valid, version-normalized output with a warning trail, not losslessness.

curl -sS -X POST "https://api.transmute.403fin.io/v1/convert?to=camt.052" \
  -H "Authorization: Bearer $TRANSMUTE_KEY" \
  -H "Content-Type: application/xml" \
  --data-binary @report.camt052.xml

{ "code": "FIELD_OVERSIZED", "severity": "lossy",
  "sourceField": "statement[0].statementNumber", "targetField": "Rpt[0]/ElctrncSeqNb",
  "detail": "ElctrncSeqNb value of length 22 exceeds 18 digits (schema type Number, max 18 digits); element dropped, never truncated" }

The same sequence-number check applies on every conversion that writes camt.052 or camt.053, for example from MT942.

Cancellation request (camt.055 → camt.056)

A camt.055 is a customer asking its bank to cancel a payment it initiated. Once the payment has left the bank, the bank forwards the request to the next bank as a camt.056. transmute converts in that one direction only.

• The original payment-information id (OrgnlPmtInfId) has no place in the interbank message and is dropped with DROP_FIELD (lossy).
• The instructed amount and requested execution date are copied into the original interbank settlement amount and date. They are copied, never computed.
• camt.056 elements the request does not supply, such as the assignee, are defaulted with MISSING_REQUIRED_DEFAULTED (info).

camt.055 also converts to mt192 and mt292.

Account reports and statements to MT942

camt.052, camt.053 and camt.054 also convert to MT942, the MT interim transaction report:

curl -sS -X POST "https://api.transmute.403fin.io/v1/convert?to=mt942" \
  -H "Authorization: Bearer $TRANSMUTE_KEY" \
  -H "Content-Type: application/xml" \
  --data-binary @report.camt052.xml

For a report built from the quickstart MT940 sample, result is:

:20:STMT0001
:25:DE89370400440532013000
:28C:00042/001
:34F:EUR0,
:13D:2610081057+0000
:61:2606020602C250,00NTRFNONREF//BANKREF1
:86:INVOICE 4711

MT942 has two mandatory fields an ISO 20022 report does not supply directly:

Other behaviour:

• Balances (opening, closing, available, forward) and the reporting period have no MT942 field and are dropped with DROP_FIELD (info).
• :90D: and :90C: (number and sum of debit and credit entries) are written only when the source states a transaction summary, copied as stated. They are never computed from the entries.
• field86Profile shapes :86: exactly as for MT940.
• MT942 is not split into pages. An oversize report is written whole, with a warning.

All warning codes on this page are listed in the warning registry.