camt: Cash Management
camt.030 Notification Of Case Assignment
Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked
camt.030 is the ISO 20022 NotificationOfCaseAssignment message in the Cash Management business area (camt). The latest version is camt.030.001.06, and 6 versions are in the repository.
- Message
- NotificationOfCaseAssignment
- Latest version
- camt.030.001.06
- Submitting organisation
- Swift
- MT equivalent
- None listed
In use: published in the current ISO 20022 catalogue.
What camt.030 is for
The NotificationOfCaseAssignment message is sent by a case assignee to a case creator/case assigner.
This message is used to inform the case assigner that:
- the assignee is reassigning the case to the next agent in the transaction processing chain for further action
- the assignee will work on the case himself, without re-assigning it to another party, and therefore indicating that the re-assignment has reached its end-point
The NotificationOfCaseAssignment message is used to notify the case creator or case assigner of further action undertaken by the case assignee in a:
- request to cancel payment case;
- request to modify payment case;
- unable to apply case;
- claim non receipt case.
The NotificationOfCaseAssignment message:
- covers one and only one case at a time. If the case assignee needs to inform a case creator or case assigner about several cases, then multiple Notification Of Case Assignment messages must be sent;
- except in the case where it is used to indicate that an agent is doing the correction himself, this message must be forwarded by all subsequent case assigner(s) until it reaches the case creator;
- must not be used in place of a Resolution Of Investigation or a Case Status Report message.
When the assignee does not reassign the case to another party (that is responding with a NotificationOfCaseAssignment message with notification MINE - The case is processed by the assignee), the case assignment should contain the case assignment elements as received in the original query.
camt.030 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.030.001.06latest | Registered | Latest version set |
| camt.030.001.05 | Registered | Previous version set |
| camt.030.001.04 | Registered | Archive |
| camt.030.001.03 | Registered | Archive |
| camt.030.001.02 | Provisionally Registered | Archive |
| camt.030.001.01 | Provisionally Registered | Archive |
camt.030 message structure
The building blocks of camt.030.001.06 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]NtfctnOfCaseAssgnmtNotificationOfCaseAssignment [1..1]HdrHeader [1..1]ReportHeader7Specifies generic information about the notification.
IdIdentification [1..1]Max35TextPoint to point reference as assigned by the case assigner to unambiguously identify the case status report.
FrFrom [1..1]Party50Choice (choice)Party reporting the status of the investigation case.
PtyParty [1..1]PartyIdentification272AgtAgent [1..1]BranchAndFinancialInstitutionIdentification8
ToTo [1..1]Party50Choice (choice)Party to which the status of the case is reported.
PtyParty [1..1]PartyIdentification272AgtAgent [1..1]BranchAndFinancialInstitutionIdentification8
CreDtTmCreation Date Time [1..1]ISODateTimeDate and time at which the message was created.
CaseCase [1..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.
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.
NtfctnNotification [1..1]CaseForwardingNotification3Information about the type of action taken.
JustfnJustification [1..1]CaseForwardingNotification3CodeJustification for the forward action.
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.030 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.030
These elements take their values from ISO 20022 external code sets, which are published separately and updated every quarter without a new message version.
camt.030 questions
- What is the latest version of camt.030?
- The latest version in the ISO 20022 e-Repository release of 24 April 2025 is camt.030.001.06.
- What is the root element of camt.030?
- The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:camt.030.001.06, and its message element is NtfctnOfCaseAssgnmt (NotificationOfCaseAssignment).
- Is there an MT equivalent of camt.030?
- 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.