Concept and mechanism
Correct mapping preserves meaning rather than merely characters. Distinguish account owner, servicing agent, and any party on whose behalf the transaction occurs. An agent bank should not automatically replace Debtor; product names do not identify Ultimate Parties. If the source does not capture required data, the project has a capture and quality dependency that middleware cannot resolve by inventing values. Amount and currency are also related information: retaining 2500 without currency can change the obligation interpreted by the destination. Overly generic text or numeric types can carry formally acceptable but semantically incorrect values.
Guided application
Translation into legacy formats can lose information through insufficient length or missing equivalent fields. Testing only that a converter completed does not establish fidelity. Build synthetic examples with long names, multiple references, relevant characters, and boundary values. Compare source, intermediate representation, and the result used by each consumer. Identify losses affecting reconciliation, reporting, or functional control and who can accept temporary mitigation. Preserving the original under appropriate controls helps investigate and reconstruct input but does not automatically make consumers use missing data. Quality indicators should measure availability of required information where the process actually uses it.
Example: three invoice references become one truncated line. Payment value can remain correct while invoice matching fails; acceptance needs to cover both outcomes.
Common pitfalls
Populated field treated as correct data; value without currency; translation OK treated as losslessness; archived original treated as repaired consumer.
Related topics: Semantics and contract documentation · Messages, headers, and states · Layered validation
Demonstrate data meaning and fidelity through to the final consumer.
Reference: ISO20022 to MT translation · DR ISO20022 fundamentals professional assessment2026.10