AccountRequestAcknowledgementV01

acmt.010.001.01

Scope The AccountRequestAcknowledgement message is sent from a financial institution to an organisation. This message is sent in response to a request message from the organisation. It is sent after the request has been validated from an authentication and authorization point of view. The business content has not yet been validated at this stage. Usage This message should only be sent after the request has been validated from an authentication and authorization point of view.

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
%% AccountRequestAcknowledgementV01 recursion level 0 with max 0
AccountRequestAcknowledgementV01 *-- "1..1" References5 : References
AccountRequestAcknowledgementV01 *-- "0..1" AccountForAction1 : AccountIdentification
AccountRequestAcknowledgementV01 *-- "1..1" OrganisationIdentification6 : OrganisationIdentification
AccountRequestAcknowledgementV01 *-- "1..1" BranchAndFinancialInstitutionIdentification4 : AccountServicerIdentification
AccountRequestAcknowledgementV01 *-- "0..1" PartyAndSignature1 : DigitalSignature
  

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

References building block

Set of elements for the identification of the message and related references. Set of elements for the identification of the message and related references. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% References5 recursion level 0 with max 1
class References5{
    RequestType UseCases1Code
    Status IsoMax35Text
    AttachedDocumentName IsoMax70Text
}
References5 *-- "1..1" MessageIdentification1 : MessageIdentification
References5 *-- "1..1" MessageIdentification1 : ProcessIdentification
References5 *-- "0..0" MessageIdentification1 : AcknowledgedMessageIdentification
%% MessageIdentification1 recursion level 1 with max 1
class MessageIdentification1{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
%% MessageIdentification1 recursion level 1 with max 1
class MessageIdentification1{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
%% MessageIdentification1 recursion level 1 with max 1
class MessageIdentification1{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
  

References5 members

AccountIdentification building block

Unique and unambiguous identification of the account between the account owner and the account servicer. Account to or from which a cash entry is made. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AccountForAction1 recursion level 0 with max 1
class AccountForAction1{
    Currency ActiveCurrencyCode
}
AccountForAction1 *-- "1..1" IAccountIdentification4Choice : Identification
%% IAccountIdentification4Choice recursion level 1 with max 1
  

AccountForAction1 members

OrganisationIdentification building block

Identifier for an organisation. Unique and unambiguous way to identify an organisation. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% OrganisationIdentification6 recursion level 0 with max 1
class OrganisationIdentification6{
    BIC IsoAnyBICIdentifier
}
OrganisationIdentification6 *-- "0..0" GenericOrganisationIdentification1 : Other
%% GenericOrganisationIdentification1 recursion level 1 with max 1
class GenericOrganisationIdentification1{
    Identification IsoMax35Text
    Issuer IsoMax35Text
}
GenericOrganisationIdentification1 *-- "0..1" IOrganisationIdentificationSchemeName1Choice : SchemeName
  

OrganisationIdentification6 members

AccountServicerIdentification building block

Unique and unambiguous identifier of a financial institution, as assigned under an internationally recognised or proprietary identification scheme. . Set of elements used to uniquely and unambiguously identify a financial institution or a branch of a financial institution. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% BranchAndFinancialInstitutionIdentification4 recursion level 0 with max 1
BranchAndFinancialInstitutionIdentification4 *-- "1..1" FinancialInstitutionIdentification7 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification4 *-- "0..1" BranchData2 : BranchIdentification
%% FinancialInstitutionIdentification7 recursion level 1 with max 1
class FinancialInstitutionIdentification7{
    BIC IsoBICIdentifier
    Name IsoMax140Text
}
FinancialInstitutionIdentification7 *-- "0..1" ClearingSystemMemberIdentification2 : ClearingSystemMemberIdentification
FinancialInstitutionIdentification7 *-- "0..1" PostalAddress6 : PostalAddress
FinancialInstitutionIdentification7 *-- "0..1" GenericFinancialIdentification1 : Other
%% BranchData2 recursion level 1 with max 1
class BranchData2{
    Identification IsoMax35Text
    Name IsoMax140Text
}
BranchData2 *-- "0..1" PostalAddress6 : PostalAddress
  

BranchAndFinancialInstitutionIdentification4 members

DigitalSignature building block

Contains the signature with its components, namely signed info, signature value, key info and the object. Entity involved in an activity. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PartyAndSignature1 recursion level 0 with max 1
PartyAndSignature1 *-- "1..1" PartyIdentification41 : Party
PartyAndSignature1 *-- "1..1" ProprietaryData3 : Signature
%% PartyIdentification41 recursion level 1 with max 1
class PartyIdentification41{
    Name IsoMax140Text
    CountryOfResidence CountryCode
}
PartyIdentification41 *-- "0..1" PostalAddress6 : PostalAddress
PartyIdentification41 *-- "0..1" IParty8Choice : Identification
PartyIdentification41 *-- "0..1" ContactDetails2 : ContactDetails
%% ProprietaryData3 recursion level 1 with max 1
ProprietaryData3 *-- "1..1" SkipProcessing : Any
  

PartyAndSignature1 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AccountRequestAcknowledgementV01 --|> IOuterRecord : Implements
    AccountRequestAcknowledgementV01Document --|> IOuterDocument~AccountRequestAcknowledgementV01~ : Implements
    class IOuterDocument~AccountRequestAcknowledgementV01~ {
        AccountRequestAcknowledgementV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    AccountRequestAcknowledgementV01Document *-- AccountRequestAcknowledgementV01 : 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:acmt.010.001.01">
    <AcctReqAck>
        <Refs>
            <!-- References inner content -->
        </Refs>
        <AcctId>
            <!-- AccountIdentification inner content -->
        </AcctId>
        <OrgId>
            <!-- OrganisationIdentification inner content -->
        </OrgId>
        <AcctSvcrId>
            <!-- AccountServicerIdentification inner content -->
        </AcctSvcrId>
        <DgtlSgntr>
            <!-- DigitalSignature inner content -->
        </DgtlSgntr>
    </AcctReqAck>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_wMT98tE9Ed-BzquC8wXy7w_-1760678511"
  nextVersions="_gDPu8Q1TEeKGXqvMN6jpiw"
  name="AccountRequestAcknowledgementV01"
  definition="Scope&#xD;&#xA;The AccountRequestAcknowledgement message is sent from a financial institution to an organisation. This message is sent in response to a request message from the organisation. It is sent after the request has been validated from an authentication and authorization point of view. The business content has not yet been validated at this stage.&#xD;&#xA;Usage&#xD;&#xA;This message should only be sent after the request has been validated from an authentication and authorization point of view."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="AcctReqAck"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_wMT989E9Ed-BzquC8wXy7w_1295593479"
    name="References"
    definition="Set of elements for the identification of the message and related references."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Refs"
    complexType="_QoQ359p-Ed-ak6NoX_4Aeg_823875605" />
  <messageBuildingBlock
    xmi:id="_wMT99NE9Ed-BzquC8wXy7w_-800492608"
    name="AccountIdentification"
    definition="Unique and unambiguous identification of the account between the account owner and the account servicer."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="AcctId"
    complexType="_SN5Y9Np-Ed-ak6NoX_4Aeg_1820239688" />
  <messageBuildingBlock
    xmi:id="_wMT99dE9Ed-BzquC8wXy7w_297553784"
    name="OrganisationIdentification"
    definition="Identifier for an organisation."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="OrgId"
    complexType="_QPrYxtp-Ed-ak6NoX_4Aeg_434657677" />
  <messageBuildingBlock
    xmi:id="_wMT99tE9Ed-BzquC8wXy7w_1393402158"
    name="AccountServicerIdentification"
    definition="Unique and unambiguous identifier of a financial institution, as assigned under an internationally recognised or proprietary identification scheme. &#xA;."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="AcctSvcrId"
    complexType="_TFB1RNp-Ed-ak6NoX_4Aeg_-736060150" />
  <messageBuildingBlock
    xmi:id="_wMT999E9Ed-BzquC8wXy7w_1931364103"
    name="DigitalSignature"
    definition="Contains the signature with its components, namely signed info, signature value, key info and the object."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="DgtlSgntr"
    complexType="_PW59tdp-Ed-ak6NoX_4Aeg_-515475026" />
  <messageDefinitionIdentifier
    businessArea="acmt"
    messageFunctionality="010"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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