camt: Cash Management
camt.026 Unable To Apply
Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked
camt.026 is the ISO 20022 UnableToApply message in the Cash Management business area (camt). The latest version is camt.026.001.10, and 10 versions are in the repository.
- Message
- UnableToApply
- Latest version
- camt.026.001.10
- Submitting organisation
- Swift
- MT equivalent
- None listed
In use: published in the current ISO 20022 catalogue.
What camt.026 is for
The UnableToApply message is sent by a case creator or a case assigner to a case assignee. This message is used to initiate an investigation of a payment instruction that cannot be executed or reconciled.
The Unable To Apply case occurs in two situations:
- an agent cannot execute the payment instruction due to missing or incorrect information;
- a creditor cannot reconcile the payment entry as it is received unexpectedly, or missing or incorrect information prevents reconciliation.
The UnableToApply message:
- always follows the reverse route of the original payment instruction;
- must be forwarded to the preceding agents in the payment processing chain, where appropriate;
- covers one and only one payment instruction (or payment entry) at a time; if several payment instructions cannot be executed or several payment entries cannot be reconciled, then multiple UnableToApply messages must be sent.
Depending on what stage the payment is and what has been done to it, for example incorrect routing, errors/omissions when processing the instruction or even the absence of any error, the unable to apply case may lead to a:
- AdditionalPaymentInformation message, sent to the case creator/case assigner, if a truncation or omission in a payment instruction prevented reconciliation;
camt.026 versions
Every version published in the e-Repository, newest first. A message keeps its business purpose across versions; each new version is a separate schema with its own namespace.
| Version | Registration status | Published in |
|---|---|---|
| camt.026.001.10latest | Registered | Latest version set |
| camt.026.001.09 | Registered | Previous version set |
| camt.026.001.08 | Registered | Archive |
| camt.026.001.07 | Registered | Archive |
| camt.026.001.06 | Registered | Archive |
| camt.026.001.05 | Registered | Archive |
| camt.026.001.04 | Registered | Archive |
| camt.026.001.03 | Registered | Archive |
| camt.026.001.02 | Provisionally Registered | Archive |
| camt.026.001.01 | Registered | Archive |
camt.026 message structure
The building blocks of camt.026.001.10 to three levels, with multiplicity ([0..1] optional, [1..1] mandatory, * any number) and the data type or component. Element names and definitions are from the ISO 20022 repository; usage guidelines such as CBPR+ or a market infrastructure's rules can restrict them further.
Document[1..1]UblToApplyUnableToApply [1..1]AssgnmtAssignment [1..1]CaseAssignment6Identifies the assignment of an investigation case from an assigner to an assignee.
IdIdentification [1..1]Max35TextUniquely identifies the case assignment.
AssgnrAssigner [1..1]Party50Choice (choice)Party who assigns the case.
PtyParty [1..1]PartyIdentification272AgtAgent [1..1]BranchAndFinancialInstitutionIdentification8
AssgneAssignee [1..1]Party50Choice (choice)Party to which the case is assigned.
PtyParty [1..1]PartyIdentification272AgtAgent [1..1]BranchAndFinancialInstitutionIdentification8
CreDtTmCreation Date Time [1..1]ISODateTimeDate and time at which the assignment was created.
CaseCase [0..1]Case6Identifies the investigation case.
IdIdentification [1..1]Max35TextUniquely identifies the case.
CretrCreator [1..1]Party50Choice (choice)Party that created the investigation case.
PtyParty [1..1]PartyIdentification272AgtAgent [1..1]BranchAndFinancialInstitutionIdentification8
ReopCaseIndctnReopen Case Indication [0..1]YesNoIndicatorIndicates whether or not the case was previously closed and is now re-opened.
UndrlygUnderlying [1..1]UnderlyingTransaction8Choice (choice)References the payment instruction or statement entry that a party is unable to execute or unable to reconcile.
InitnInitiation [1..1]UnderlyingPaymentInstruction9Set of elements used to reference the details of the original payment initiation.
OrgnlGrpInfOriginal Group Information [0..1]UnderlyingGroupInformation1OrgnlPmtInfIdOriginal Payment Information Identification [0..1]Max35TextOrgnlInstrIdOriginal Instruction Identification [0..1]Max35TextOrgnlEndToEndIdOriginal End To End Identification [0..1]Max35TextOrgnlUETROriginal UETR [0..1]UUIDv4IdentifierOrgnlInstdAmtOriginal Instructed Amount [0..1]ActiveOrHistoricCurrencyAndAmountReqdExctnDtRequested Execution Date [0..1]DateAndDateTime2Choice (choice)ReqdColltnDtRequested Collection Date [0..1]ISODateOrgnlTxRefOriginal Transaction Reference [0..1]OriginalTransactionReference42OrgnlSvcLvlOriginal Service Level [0..1]ServiceLevel8Choice (choice)
IntrBkInterbank [1..1]UnderlyingPaymentTransaction8Set of elements used to reference the details of the original interbank payment transaction.
OrgnlGrpInfOriginal Group Information [0..1]UnderlyingGroupInformation1OrgnlInstrIdOriginal Instruction Identification [0..1]Max35TextOrgnlEndToEndIdOriginal End To End Identification [0..1]Max35TextOrgnlTxIdOriginal Transaction Identification [0..1]Max35TextOrgnlUETROriginal UETR [0..1]UUIDv4IdentifierOrgnlIntrBkSttlmAmtOriginal Interbank Settlement Amount [0..1]ActiveOrHistoricCurrencyAndAmountOrgnlIntrBkSttlmDtOriginal Interbank Settlement Date [0..1]ISODateOrgnlTxRefOriginal Transaction Reference [0..1]OriginalTransactionReference42OrgnlSvcLvlOriginal Service Level [0..1]ServiceLevel8Choice (choice)
StmtNtryStatement Entry [1..1]UnderlyingStatementEntry3Reference details on the underlying statement cash entry.
OrgnlGrpInfOriginal Group Information [0..1]OriginalGroupInformation29OrgnlStmtIdOriginal Statement Identification [0..1]Max35TextOrgnlNtryIdOriginal Entry Identification [0..1]Max35TextOrgnlUETROriginal UETR [0..1]UUIDv4Identifier
JustfnJustification [1..1]UnableToApplyJustification4Choice (choice)Explains the reason why the case creator is unable to apply the instruction.
AnyInfAny Information [1..1]YesNoIndicatorIndicates whether or not all available information on the underlying payment instruction is requested.
MssngOrIncrrctInfMissing Or Incorrect Information [1..1]MissingOrIncorrectData1Set of elements used to indicate which information is missing or incorrect.
AMLReqAnti Money Laundering Request [0..1]AMLIndicatorMssngInfMissing Information [0..10]UnableToApplyMissing2IncrrctInfIncorrect Information [0..10]UnableToApplyIncorrect2
PssblDplctInstrPossible Duplicate Instruction [1..1]TrueFalseIndicatorIndicates whether or not the referred item is a possible duplicate of a previous instruction or entry.
SplmtryDataSupplementary Data [0..*]SupplementaryData1Additional information that cannot be captured in the structured elements and/or any other specific block.
PlcAndNmPlace And Name [0..1]Max350TextUnambiguous reference to the location where the supplementary data must be inserted in the message instance.
EnvlpEnvelope [1..1]SupplementaryDataEnvelope1Technical element wrapping the supplementary data.
Have a camt.026 message? Paste it into the parser to see every element with its name and definition, and format checks on BICs, IBANs, dates and amounts.
External code sets used in camt.026
These elements take their values from ISO 20022 external code sets, which are published separately and updated every quarter without a new message version.
- ExternalAccountIdentification1Code4 codes
- ExternalCashAccountType1Code28 codes
- ExternalCashClearingSystem1Code145 codes
- ExternalCategoryPurpose1Code49 codes
- ExternalClearingSystemIdentification1Code172 codes
- ExternalCreditorReferenceType1Code7 codes
- ExternalDateType1Code5 codes
- ExternalDocumentAmountType1Code27 codes
- ExternalDocumentLineType1Code19 codes
- ExternalDocumentType1Code23 codes
- ExternalFinancialInstitutionIdentification1Code0 codes
- ExternalGarnishmentType1Code3 codes
- ExternalLocalInstrument1Code114 codes
- ExternalMandateSetupReason1Code0 codes
- ExternalOrganisationIdentification1Code15 codes
- ExternalPersonIdentification1Code11 codes
- ExternalProxyAccountType1Code22 codes
- ExternalPurpose1Code366 codes
- ExternalServiceLevel1Code29 codes
- ExternalUnableToApplyIncorrectData1Code41 codes
- ExternalUnableToApplyMissingData1Code19 codes
camt.026 questions
- What is the latest version of camt.026?
- The latest version in the ISO 20022 e-Repository release of 24 April 2025 is camt.026.001.10.
- What is the root element of camt.026?
- The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:camt.026.001.10, and its message element is UblToApply (UnableToApply).
- Is there an MT equivalent of camt.026?
- No Swift MT message is listed as its direct equivalent on this site. Many ISO 20022 messages have no MT counterpart.
All ISO 20022 messages · ISO 20022 code sets · MT messages
The ISO 20022 message definitions, element names and definitions on this page are reproduced from material published at iso20022.org under the ISO 20022 Intellectual Property Rights policy. This is not the official source: the up-to-date ISO 20022 standards and repository material are published only at iso20022.org. Explanations in our own words are by ZagTrader. ZagTrader is not affiliated with or endorsed by ISO or Swift.