StatusChangeRequestAcceptanceV02

tsmt.027.001.02

Scope The StatusChangeRequestAcceptance message is sent by the party requested to accept or reject the request of a change in the status of a transaction to the matching application. This message is used to inform about the acceptance of a request to change the status of a transaction. Usage The StatusChangeRequestAcceptance message can be sent by the party requested to accept or reject a request to change the status of a transaction to inform that it accepts the request. The message can be sent in response to a StatusChangeRequestNotification message. The rejection of a request to change the status of a transaction can be achieved by sending a StatusChangeRequestRejection 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
%% StatusChangeRequestAcceptanceV02 recursion level 0 with max 0
StatusChangeRequestAcceptanceV02 *-- "1..1" MessageIdentification1 : AcceptanceIdentification
StatusChangeRequestAcceptanceV02 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification
StatusChangeRequestAcceptanceV02 *-- "0..1" SimpleIdentificationInformation : SubmitterTransactionReference
StatusChangeRequestAcceptanceV02 *-- "1..1" TransactionStatus3 : AcceptedStatus
  

Now, we will zero-in one-by-one on each of these building blocks.

AcceptanceIdentification building block

Identifies the acceptance 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

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

SubmitterTransactionReference building block

Reference to the transaction for the requesting financial institution. 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

AcceptedStatus building block

Specifies the status accepted. Identifies the status of the transaction by means of a code. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TransactionStatus3 recursion level 0 with max 1
class TransactionStatus3{
    Status BaselineStatus2Code
}
  

TransactionStatus3 members

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the StatusChangeRequestAcceptanceV02 implementation follows a specific implementaiton pattern. First of all, StatusChangeRequestAcceptanceV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, StatusChangeRequestAcceptanceV02Document implements IOuterDocument. Because StatusChangeRequestAcceptanceV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type StatusChangeRequestAcceptanceV02.

classDiagram
    class IOuterRecord
    StatusChangeRequestAcceptanceV02 --|> IOuterRecord : Implements
    StatusChangeRequestAcceptanceV02Document --|> IOuterDocument~StatusChangeRequestAcceptanceV02~ : Implements
    class IOuterDocument~StatusChangeRequestAcceptanceV02~ {
        StatusChangeRequestAcceptanceV02 Message
     }
  

Document wrapper for serialization

The only real purpose StatusChangeRequestAcceptanceV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:tsmt.027.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using StatusChangeRequestAcceptanceV02.ToDocument() method. The returned StatusChangeRequestAcceptanceV02Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    StatusChangeRequestAcceptanceV02Document *-- StatusChangeRequestAcceptanceV02 : 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.027.001.02">
    <StsChngReqAccptnc>
        <AccptncId>
            <!-- AcceptanceIdentification inner content -->
        </AccptncId>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <SubmitrTxRef>
            <!-- SubmitterTransactionReference inner content -->
        </SubmitrTxRef>
        <AccptdSts>
            <!-- AcceptedStatus inner content -->
        </AccptdSts>
    </StsChngReqAccptnc>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_v33NZ9E8Ed-BzquC8wXy7w_-1262525653"
  name="StatusChangeRequestAcceptanceV02"
  definition="Scope&#xD;&#xA;The StatusChangeRequestAcceptance message is sent by the party requested to accept or reject the request of a change in the status of a transaction to the matching application.&#xD;&#xA;This message is used to inform about the acceptance of a request to change the status of a transaction.&#xD;&#xA;Usage&#xD;&#xA;The StatusChangeRequestAcceptance message can be sent by the party requested to accept or reject a request to change the status of a transaction to inform that it accepts the request.&#xD;&#xA;The message can be sent in response to a StatusChangeRequestNotification message.&#xD;&#xA;The rejection of a request to change the status of a transaction can be achieved by sending a StatusChangeRequestRejection message."
  registrationStatus="Registered"
  messageSet="_wRx2yk2rEeG_I4xRYCA_7g _1a374FXOEeOkkLyrDUP66g"
  xmlTag="StsChngReqAccptnc"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_v33NaNE8Ed-BzquC8wXy7w_-1262525650"
    name="AcceptanceIdentification"
    definition="Identifies the acceptance message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="AccptncId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_v33NadE8Ed-BzquC8wXy7w_-1262525622"
    name="TransactionIdentification"
    definition="Unique identification assigned by the matching application to the transaction.&#xA;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="_v33NatE8Ed-BzquC8wXy7w_-1262525591"
    name="SubmitterTransactionReference"
    definition="Reference to the transaction for the requesting financial institution."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SubmitrTxRef"
    complexType="_P-ile9p-Ed-ak6NoX_4Aeg_745508310" />
  <messageBuildingBlock
    xmi:id="_v33Na9E8Ed-BzquC8wXy7w_-1262525560"
    name="AcceptedStatus"
    definition="Specifies the status accepted."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="AccptdSts"
    complexType="_RKFyk9p-Ed-ak6NoX_4Aeg_-489445133" />
  <messageDefinitionIdentifier
    businessArea="tsmt"
    messageFunctionality="027"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.