GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
PAYMENTSSIGNAL

The interactive academy for the standards, messages, and rails that move money.

PROGRESS
camt.026ISO 20022

camt.026 — Unable to Apply

Opens an investigation when a received payment instruction or account entry cannot be executed or reconciled because information is missing, incorrect, inconsistent or possibly duplicated. It asks for repair; it does not move value.

DIRECTION: Sent by the party unable to apply the payment or entry to the party expected to clarify or correct it, directly or through the applicable investigation service.

Version + profile: camt.026 is a message-family identifier, not a complete version. The numeric .001.xx definition and field rules depend on the scheme, service, usage guideline, and implementation version named in each context; sample namespaces show only the illustrated version.

Contributor Shubham Mathure

DOMAIN + EDITORIAL AUDITAudited 2026-07-18 for payment logic, source scope, technical writing, and Payments Signal voice — see the method.

EVIDENCE AT ARM'S REACH

IMPLEMENTATION RESOURCES

Start with the exact message version, then apply the scheme or network profile that governs your implementation.

An XSD checks XML structure. A usage guideline adds profile rules, conditional fields, code restrictions, and business controls. XSD-valid does not mean scheme-compliant.

Field matrixBase ISO 20022current

camt.026 field matrix

Curated field requirements, contexts, operational meaning, and implementation cautions.

Owner
Payments Signal
Checked
2026-07-19
Integrity
crc32:347020d4
Access
Payments Signal download · Original, source-backed teaching asset; no login required.
DOWNLOAD

WHO IS INVOLVED

  • Case creator / assignerIdentifies the original item and states exactly what prevents application or reconciliation.
  • Case assigneeLocates the source record, supplies or corrects the information, or explains why the request cannot be satisfied.

KEY FIELDS

Curated conceptual subset. camt.026 is part of the classic ISO exceptions-and-investigations message set; production availability, exact version and migration treatment depend on the service profile in force.

Key fields of camt.026
FIELDNAMEPRESENCEWHAT IT MEANS
Assgnmt/IdAssignment identificationMANDATORYReference for this assignment of the investigation.
Assgnmt/AssgnrAssignerMANDATORYParty sending the unable-to-apply case.
Assgnmt/AssgneAssigneeMANDATORYParty expected to investigate or provide the repair.
Case/IdCase identificationCONDITIONALStable reference for the investigation case where a case block is used.
Undrlyg/TxInf/OrgnlUETROriginal UETRCONDITIONALNetwork reference used to locate the payment that cannot be applied.
Justfn/MssngOrIncrrctInfMissing or incorrect informationCONDITIONALStructured description of the data that is absent or wrong.
PssblDplctInstrPossible duplicate instructionMANDATORYIndicates whether the unresolved item might duplicate an earlier instruction or entry.

COMMON ERRORS

  • Sending a vague narrative without identifying the missing field.Consequence: The assignee cannot repair the payment and the case loops through manual correspondence.Avoid it: Quote the original references and state the missing or incorrect data precisely.
  • Calling an unable-to-apply case a payment rejection after settlement.Consequence: Operations loses the distinction between held funds, returned funds and rejected instructions.Avoid it: Record settlement, suspense posting, case status and any later return as separate events.

USAGE CONTEXTS

  • Missing or inconsistent payment dataThe receiver holds the item in a controlled exception state and asks for the specific information needed to apply it.
  • Migration to Case ManagementDo not assume camt.026 and camt.110 are interchangeable on every service; current reachability and orchestration rules decide the supported dialogue.

SEE IT IN A PLAYABLE FLOW

LEARN THE CONTEXT

Sources for this reference3
  1. Official requirement

    ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · camt.026 UnableToApply message definition

    Defines the current versions of all ISO 20022 message definitions, including the pain, pacs, and camt messages taught on this site. · Checked 2026-07-12

    Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.

  2. Scheme-specific rule

    ISO 20022 Standards (Swift ISO 20022 adoption programme) ↗ — Swift · Exceptions-and-investigations migration roadmap

    Describes current CBPR+ adoption, the 22 November 2025 end of coexistence for in-scope FI-to-FI payment instructions, later migration work and the November 2026 structured-address milestone. · Checked 2026-07-18

    Do not generalise the payment-instruction deadline to every FIN message. Swift publishes differentiated NAK, contingency-conversion, reporting, initiation and exceptions-and-investigations treatment.

  3. Simplified educational illustration

    Payments Signal editorial teaching models — Payments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    What this simplifies: A compact field subset and one payment-repair use case; version-specific conditions are omitted.

    Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.

COMMUNITY SIGNAL

Discuss this learning page

Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.

NEXT QUESTION REVIEWMonday, 27 Jul, 8:00 amMonday answer runs use source-supported educational material. Some questions may need owner review.
WHAT ARE YOU SHARING?

Publish only lawful, relevant content. Never include confidential payment or personal data.

Public discussion

LOADING

Loading the discussion…