Message mapping assistance
Help teams interpret unfamiliar fields, compare schemas and prepare candidate mappings for technical review.
A useful output: a mapping proposal with source evidence, assumptions and unresolved fields.
Applied AI · Development direction
We are exploring how AI can help teams interpret messages, structure information and investigate integration problems. Each proposed use begins with a defined task and a way to check the result.
Where AI could help
Help teams interpret unfamiliar fields, compare schemas and prepare candidate mappings for technical review.
A useful output: a mapping proposal with source evidence, assumptions and unresolved fields.
Explore extracting agreed fields from documents, with missing, conflicting or ambiguous values flagged for review.
A useful output: structured draft data linked to the source passages that support it.
Help technical teams navigate schema documentation, explain validation failures and prepare troubleshooting notes.
A useful output: a suggested explanation supported by documentation and checks a team can reproduce.
Synthetic worked example
Consider a source system sending an amount, a currency and an internal recipient reference. The question is which values can safely be mapped, and which conclusions the available information does not support.
{
"instruction_id": "AI-DEMO-001",
"amount": "125.00",
"currency": "GBP",
"party_ref": "TEST-R17"
}All values are synthetic. The reference identifies a test recipient inside the source system.
An assistant might suggest mapping the amount and currency directly. It might also mistake the internal recipient reference for a bank account, or infer the recipient’s country from the currency.
Those suggestions need different review outcomes. A convincing explanation cannot replace source evidence.
Retain the supplied values in a draft, subject to the agreed target schema and business-rule checks.
Reject this mapping. The message supplies an internal reference, not a verified account identifier. Keep it as a reference and request the required account information separately.
Reject this inference. Currency does not establish the recipient’s country. Leave the country unresolved if the target requires it.
{
"payment": {
"reference": "AI-DEMO-001",
"amount": {
"value": "125.00",
"currency": "GBP"
},
"recipient_reference": "TEST-R17"
}
}The draft retains the supplied information without converting an internal reference into an account or inventing a country.
It still needs the receiving system’s schema and acceptance rules. It is not a complete payment instruction, an ISO 20022 message, or output from a live AI service.
AI assurance
An AI engagement should agree how the task will be evaluated and who is responsible for reviewing its outputs. These are proposed engagement requirements, not a claim that a particular implementation already provides them.
Agree which data may be used, where processing occurs, which providers are involved, and the permitted access and retention. Begin with synthetic data where possible.
Define representative test cases, failure cases and acceptance criteria. Check structured outputs against explicit schemas and rules.
Record source evidence, assumptions and versions. Identify the reviewer, the rejection pathway and what happens when a result is uncertain or incomplete.
Relationship to the translator
Candidate mappings can inform technical design. A production transformation still requires an agreed specification, validation and operational acceptance.
Explore translator developmentDescribe the information you have, the output you need and how your team would determine whether the result is correct. We can discuss the scope of a feasibility assessment.
Discuss an AI assessment