tsmt.024.001.03
Scope The ActionReminder message is sent by the matching application to a party involved in a transaction that it is expecting to take an action. This message is used to remind a party of an action that it is expected to take. Usage The ActionReminder message can be sent by the matching application to remind a party that it is waiting for
- the submission of a transaction initiation message (BaselineReSubmission message), or
- the acceptance or rejection of mis-matched data sets (MisMatchAcceptance or MisMatchRejection message), or
- the acceptance or rejection of an amendment request (AmendmentAcceptance or AmendmentRejection message), or
- the acceptance or rejection of a status change request (StatusChangeRequestAcceptance or StatusChangeRequestRejection message), or
- the acceptance or rejection of a status extension request (StatusExtensionAcceptance or StatusExtensionRejection message).
- or
- the acceptance or rejection of a request to accept role and baseline (RoleAndBaselineAcceptance or RoleAndBaselineRejection message).
Message Construction
Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification
classDiagram
direction LR
%% ActionReminderV03 recursion level 0 with max 0
ActionReminderV03 *-- "1..1" MessageIdentification1 : ReminderIdentification
ActionReminderV03 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification
ActionReminderV03 *-- "0..1" DocumentIdentification3 : EstablishedBaselineIdentification
ActionReminderV03 *-- "1..1" TransactionStatus4 : TransactionStatus
ActionReminderV03 *-- "0..2" DocumentIdentification5 : UserTransactionReference
ActionReminderV03 *-- "1..1" MessageIdentification1 : MessageRequiringAction
ActionReminderV03 *-- "1..1" PendingActivity2 : PendingRequestForAction
Now, we will zero-in one-by-one on each of these building blocks.
ReminderIdentification building block
Identifies the reminder message. Identifies a message by a unique identifier and the date and time when the message was created by the sender. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MessageIdentification1 recursion level 0 with max 1
class MessageIdentification1{
Identification IsoMax35Text
CreationDateTime IsoISODateTime
}
MessageIdentification1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | Identification of the message. | IsoMax35Text - Required 1..1 |
| CreationDateTime | Date of creation of the message. | IsoISODateTime - Required 1..1 |
TransactionIdentification building block
Unique identification assigned by the matching application to the transaction. This identification is to be used in any communication between the parties. Information related to an identification, eg, party identification or account identification. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% SimpleIdentificationInformation recursion level 0 with max 1
class SimpleIdentificationInformation{
Identification IsoMax35Text
}
SimpleIdentificationInformation members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | Name or number assigned by an entity to enable recognition of that entity, eg, account identifier. | IsoMax35Text - Required 1..1 |
EstablishedBaselineIdentification building block
Unique identification assigned by the matching application to the baseline when it is established. Identifies a document by a unique identification and a version. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% DocumentIdentification3 recursion level 0 with max 1
class DocumentIdentification3{
Identification IsoMax35Text
Version IsoNumber
}
DocumentIdentification3 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | Identification of a set of data. | IsoMax35Text - Required 1..1 |
| Version | Unambiguous identification of the version of a set of data. Example: Version 1. | IsoNumber - Required 1..1 |
TransactionStatus building block
Identifies the status of the transaction by means of a code. Identifies the status of the transaction by means of a code. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% TransactionStatus4 recursion level 0 with max 1
class TransactionStatus4{
Status BaselineStatus3Code
}
TransactionStatus4 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Status | Identifies the status of the transaction by means of a code. | BaselineStatus3Code - Required 1..1 |
UserTransactionReference building block
Reference to the transaction for each financial institution which is a party to the transaction. Identifies a document by a unique identification and its issuer. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% DocumentIdentification5 recursion level 0 with max 1
class DocumentIdentification5{
Identification IsoMax35Text
}
DocumentIdentification5 *-- "1..1" BICIdentification1 : IdentificationIssuer
%% BICIdentification1 recursion level 1 with max 1
class BICIdentification1{
BIC IsoBICIdentifier
}
DocumentIdentification5 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | Identification of a set of data. | IsoMax35Text - Required 1..1 |
| IdentificationIssuer | Uniquely identifies the financial institution which has issued the identification of the set of data by using a BIC. | BICIdentification1 - Required 1..1 |
MessageRequiringAction building block
Identifies the message for which an action is required. Identifies a message by a unique identifier and the date and time when the message was created by the sender. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MessageIdentification1 recursion level 0 with max 1
class MessageIdentification1{
Identification IsoMax35Text
CreationDateTime IsoISODateTime
}
MessageIdentification1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | Identification of the message. | IsoMax35Text - Required 1..1 |
| CreationDateTime | Date of creation of the message. | IsoISODateTime - Required 1..1 |
PendingRequestForAction building block
Next processing step required. Specifies the event that require an action from one of the parties to the trade transaction. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% PendingActivity2 recursion level 0 with max 1
class PendingActivity2{
Type Action2Code
Description IsoMax140Text
}
PendingActivity2 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Type | Code which specifies the next course of action that the receiver of the message must take. | Action2Code - Required 1..1 |
| Description | Further information on the course of action that the receiver of the message must take. | IsoMax140Text - Optional 0..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the ActionReminderV03 implementation follows a specific implementaiton pattern. First of all, ActionReminderV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, ActionReminderV03Document implements IOuterDocument. Because ActionReminderV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type ActionReminderV03.
classDiagram
class IOuterRecord
ActionReminderV03 --|> IOuterRecord : Implements
ActionReminderV03Document --|> IOuterDocument~ActionReminderV03~ : Implements
class IOuterDocument~ActionReminderV03~ {
ActionReminderV03 Message
}
Document wrapper for serialization
The only real purpose ActionReminderV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:tsmt.024.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using ActionReminderV03.ToDocument() method. The returned ActionReminderV03Document value will serialize correctly according to ISO 20022 standards.
classDiagram
ActionReminderV03Document *-- ActionReminderV03 : Document
Sample of message format
This is an abbreviated version of what the message should look like.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:tsmt.024.001.03">
<ActnRmndr>
<RmndrId>
<!-- ReminderIdentification inner content -->
</RmndrId>
<TxId>
<!-- TransactionIdentification inner content -->
</TxId>
<EstblishdBaselnId>
<!-- EstablishedBaselineIdentification inner content -->
</EstblishdBaselnId>
<TxSts>
<!-- TransactionStatus inner content -->
</TxSts>
<UsrTxRef>
<!-- UserTransactionReference inner content -->
</UsrTxRef>
<MsgReqrngActn>
<!-- MessageRequiringAction inner content -->
</MsgReqrngActn>
<PdgReqForActn>
<!-- PendingRequestForAction inner content -->
</PdgReqForActn>
</ActnRmndr>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_hnA9-NE8Ed-BzquC8wXy7w_-2083336927"
name="ActionReminderV03"
definition="Scope
The ActionReminder message is sent by the matching application to a party involved in a transaction that it is expecting to take an action.
This message is used to remind a party of an action that it is expected to take.
Usage
The ActionReminder message can be sent by the matching application to remind a party that it is waiting for
- the submission of a transaction initiation message (BaselineReSubmission message),
or
- the acceptance or rejection of mis-matched data sets (MisMatchAcceptance or MisMatchRejection message),
or
- the acceptance or rejection of an amendment request (AmendmentAcceptance or AmendmentRejection message),
or
- the acceptance or rejection of a status change request (StatusChangeRequestAcceptance or StatusChangeRequestRejection message),
or
- the acceptance or rejection of a status extension request (StatusExtensionAcceptance or StatusExtensionRejection message).
- or
- the acceptance or rejection of a request to accept role and baseline (RoleAndBaselineAcceptance or RoleAndBaselineRejection message)."
registrationStatus="Registered"
messageSet="_wRx2yk2rEeG_I4xRYCA_7g _1a374FXOEeOkkLyrDUP66g"
xmlTag="ActnRmndr"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_hnA9-dE8Ed-BzquC8wXy7w_-2083336503"
name="ReminderIdentification"
definition="Identifies the reminder message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="RmndrId"
complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
<messageBuildingBlock
xmi:id="_hnA9-tE8Ed-BzquC8wXy7w_-2083336866"
name="TransactionIdentification"
definition="Unique identification assigned by the matching application to the transaction.
This identification is to be used in any communication between the parties."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="TxId"
complexType="_P-ile9p-Ed-ak6NoX_4Aeg_745508310" />
<messageBuildingBlock
xmi:id="_hnA9-9E8Ed-BzquC8wXy7w_-2083336924"
name="EstablishedBaselineIdentification"
definition="Unique identification assigned by the matching application to the baseline when it is established."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="EstblishdBaselnId"
complexType="_RJNBwdp-Ed-ak6NoX_4Aeg_-1127047102" />
<messageBuildingBlock
xmi:id="_hnA9_NE8Ed-BzquC8wXy7w_-2083336556"
name="TransactionStatus"
definition="Identifies the status of the transaction by means of a code."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="TxSts"
complexType="_RbFb-Np-Ed-ak6NoX_4Aeg_1598523783" />
<messageBuildingBlock
xmi:id="_hnKu8NE8Ed-BzquC8wXy7w_-2083336587"
name="UserTransactionReference"
definition="Reference to the transaction for each financial institution which is a party to the transaction."
registrationStatus="Provisionally Registered"
maxOccurs="2"
minOccurs="0"
xmlTag="UsrTxRef"
complexType="_RJWLsdp-Ed-ak6NoX_4Aeg_-86119846" />
<messageBuildingBlock
xmi:id="_hnKu8dE8Ed-BzquC8wXy7w_-2083336525"
name="MessageRequiringAction"
definition="Identifies the message for which an action is required."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MsgReqrngActn"
complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
<messageBuildingBlock
xmi:id="_hnKu8tE8Ed-BzquC8wXy7w_-2083336834"
name="PendingRequestForAction"
definition="Next processing step required."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="PdgReqForActn"
complexType="_RaowBtp-Ed-ak6NoX_4Aeg_-888447978" />
<messageDefinitionIdentifier
businessArea="tsmt"
messageFunctionality="024"
flavour="001"
version="03" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.