Explains the ISO 20022 credit transfer message
Group header, payment identification (InstrId, EndToEndId), parties (Dbtr, UltmtDbtr, Cdtr, UltmtCdtr), agents, amounts, charge bearer, purpose and remittance; external code sets; returns echoing the original ids.
Can AI do this?
AI does this well Most of the tested AI models master this. 4 of 4 models in the current benchmark master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 100% | Mastered |
| gemini-3.5-flash-lite | Low cost | 100% | Mastered |
| gpt-6-luna | Low cost | 100% | Mastered |
| claude-haiku-5-5 | Low cost | 100% | Mastered |
Mastered means a probability of at least 90% that the model has this knobit, estimated from its graded answers. “Not shown” means the answers do not settle it either way. How the models are tested.
What it looks like in practice
Expected result: Group header, payment identification (InstrId, EndToEndId), parties (Dbtr, UltmtDbtr, Cdtr, UltmtCdtr), agents, amounts, charge bearer, purpose and remittance; external code sets; returns echoing the original ids.
How it is assessed: Answers a written question on the ISO 20022 pacs.008 correctly
Related knobits
Needed for
- N-401 Recognises a field in the wrong ISO 20022 element
- N-403 Recognises a mandatory message element missing
- N-404 Recognises a message version not stated or mixed
- N-405 Recognises a code outside the external code set
- N-409 Recognises an end-to-end id not carried to the return
- N-431 Places parties in debtor and ultimate debtor by their role
All 15 knobits of Specify data exchanges.
Source: Practice the stage 4 reference and review checklist rest on