AccountMandateMaintenanceRequestV02

acmt.017.001.02

The AccountMandateMaintenanceRequest message is sent from an organisation to a financial institution as part of the account maintenance process. It is the initial request message to update one or several accounts. Usage: this update is only about mandate information. If modification codes are not used: the organisation will specify under the “Mandate” and “Group” tags the complete information as it should be in the financial institution’s records after processing the update request. If modification codes are used (in that case, they must be used everywhere): the organisation will specify under the “Mandate” and “Group” tags which elements must be added, deleted, modified, or if they are unchanged. It is not possible to update the account characteristics or organisation information with this 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
%% AccountMandateMaintenanceRequestV02 recursion level 0 with max 0
AccountMandateMaintenanceRequestV02 *-- "1..1" References4 : References
AccountMandateMaintenanceRequestV02 *-- "0..1" OrganisationIdentification8 : From
AccountMandateMaintenanceRequestV02 *-- "0..1" AccountContract2 : ContractDates
AccountMandateMaintenanceRequestV02 *-- "0..1" ContractDocument1 : UnderlyingMasterAgreement
AccountMandateMaintenanceRequestV02 *-- "1..1" AccountForAction1 : AccountIdentification
AccountMandateMaintenanceRequestV02 *-- "1..1" BranchAndFinancialInstitutionIdentification5 : AccountServicerIdentification
AccountMandateMaintenanceRequestV02 *-- "1..1" Organisation14 : OrganisationIdentification
AccountMandateMaintenanceRequestV02 *-- "1..1" OperationMandate3 : Mandate
AccountMandateMaintenanceRequestV02 *-- "0..1" Group2 : Group
AccountMandateMaintenanceRequestV02 *-- "0..1" AdditionalInformation5 : AdditionalMessageInformation
AccountMandateMaintenanceRequestV02 *-- "0..1" PartyAndSignature2 : DigitalSignature
AccountMandateMaintenanceRequestV02 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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
%% References4 recursion level 0 with max 1
class References4{
    AttachedDocumentName IsoMax70Text
}
References4 *-- "1..1" MessageIdentification1 : MessageIdentification
References4 *-- "1..1" MessageIdentification1 : ProcessIdentification
%% 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
}
  

References4 members

Member name Description Data Type / Multiplicity
MessageIdentification Identifies a message by a unique identifier and the date and time when the message was created by the sender. MessageIdentification1 - Required 1..1
ProcessIdentification Identifies a process by a unique identifier and the date and time when the first message belonging to the process was created by the sender. The process identification remains the same in all messages belonging to the same process, from the initial request message to the final account report closing the process. MessageIdentification1 - Required 1..1
AttachedDocumentName File name of a document logically related to the request. IsoMax70Text - Unknown 0..0

From building block

Identifies the business sender of the message, if it is not the account owner or account servicing financial institution. Unique and unambiguous way to identify an organisation. For comparison, see the ISO20022 official specification

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

OrganisationIdentification8 members

Member name Description Data Type / Multiplicity
AnyBIC Code allocated to a financial institution or non financial institution by the ISO 9362 Registration Authority as described in ISO 9362 “Banking - Banking telecommunication messages - Business identifier code (BIC)”. IsoAnyBICIdentifier - Optional 0..1
Other Unique identification of an organisation, as assigned by an institution, using an identification scheme. GenericOrganisationIdentification1 - Unknown 0..0

ContractDates building block

Specifies target dates. Specifies target dates dates related to account opening and closing. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AccountContract2 recursion level 0 with max 1
class AccountContract2{
    TargetGoLiveDate IsoISODate
    TargetClosingDate IsoISODate
    UrgencyFlag IsoYesNoIndicator
}
  

AccountContract2 members

Member name Description Data Type / Multiplicity
TargetGoLiveDate Date on which the account and related basic services are expected to be operational for the account owner. IsoISODate - Optional 0..1
TargetClosingDate Date on which the account and related services are expected to cease to be operational for the account owner. IsoISODate - Optional 0..1
UrgencyFlag Indicator that the account opening/maintenance/closing process needs to be treated urgently, that is, sooner than the terms established by the service level agreed between the account holder customer and the account servicing institution. IsoYesNoIndicator - Optional 0..1

UnderlyingMasterAgreement building block

Account contract established between the organisation or the group to which the organisation belongs, and the account servicer. This contract has to be applied for the new account to be opened and maintained. Document that contains the information of the contract agreed between both parties. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ContractDocument1 recursion level 0 with max 1
class ContractDocument1{
    Reference IsoMax35Text
    SignOffDate IsoISODate
    Version IsoMax6Text
}
  

ContractDocument1 members

Member name Description Data Type / Multiplicity
Reference Account contract established between the organisation or the group to which the organisation belongs, and the account servicer. This contract has to be applied for the new account to be opened and maintained. IsoMax35Text - Required 1..1
SignOffDate Signoff date of the document. IsoISODate - Optional 0..1
Version Identification of the version of the contract. IsoMax6Text - Optional 0..1

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

Member name Description Data Type / Multiplicity
Identification Unique and unambiguous identification for the account between the account owner and the account servicer. IAccountIdentification4Choice - Required 1..1
Currency Medium of exchange of value. ActiveCurrencyCode - Required 1..1

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
%% BranchAndFinancialInstitutionIdentification5 recursion level 0 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
%% FinancialInstitutionIdentification8 recursion level 1 with max 1
class FinancialInstitutionIdentification8{
    BICFI IsoBICFIIdentifier
    Name IsoMax140Text
}
FinancialInstitutionIdentification8 *-- "0..1" ClearingSystemMemberIdentification2 : ClearingSystemMemberIdentification
FinancialInstitutionIdentification8 *-- "0..1" PostalAddress6 : PostalAddress
FinancialInstitutionIdentification8 *-- "0..1" GenericFinancialIdentification1 : Other
%% BranchData2 recursion level 1 with max 1
class BranchData2{
    Identification IsoMax35Text
    Name IsoMax140Text
}
BranchData2 *-- "0..1" PostalAddress6 : PostalAddress
  

BranchAndFinancialInstitutionIdentification5 members

Member name Description Data Type / Multiplicity
FinancialInstitutionIdentification Unique and unambiguous identification of a financial institution, as assigned under an internationally recognised or proprietary identification scheme. FinancialInstitutionIdentification8 - Required 1..1
BranchIdentification Identifies a specific branch of a financial institution.

OrganisationIdentification building block

Identification of the organisation requesting the change. Information which describes the organisation. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Organisation14 recursion level 0 with max 1
class Organisation14{
    FullLegalName IsoMax350Text
}
Organisation14 *-- "1..1" OrganisationIdentification8 : OrganisationIdentification
%% OrganisationIdentification8 recursion level 1 with max 1
class OrganisationIdentification8{
    AnyBIC IsoAnyBICIdentifier
}
OrganisationIdentification8 *-- "0..0" GenericOrganisationIdentification1 : Other
  

Organisation14 members

Member name Description Data Type / Multiplicity
FullLegalName Name by which a party is known and which is usually used to identify that party. IsoMax350Text - Optional 0..1
OrganisationIdentification Unique and unambiguous way of identifying an organisation. OrganisationIdentification8 - Required 1..1

Mandate building block

Information specifying the account mandate. Information specifying the Mandate. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% OperationMandate3 recursion level 0 with max 1
class OperationMandate3{
    ModificationCode Modification1Code
    Identification IsoMax35Text
    RequiredSignatureNumber IsoMax15PlusSignedNumericText
    SignatureOrderIndicator IsoYesNoIndicator
    StartDate IsoISODate
    EndDate IsoISODate
}
OperationMandate3 *-- "1..0" IChannel2Choice : ApplicableChannel
OperationMandate3 *-- "0..0" PartyAndAuthorisation3 : MandateHolder
OperationMandate3 *-- "1..0" BankTransactionCodeStructure4 : BankOperation
%% IChannel2Choice recursion level 1 with max 1
%% PartyAndAuthorisation3 recursion level 1 with max 1
class PartyAndAuthorisation3{
    ModificationCode Modification1Code
    SignatureOrder IsoMax15PlusSignedNumericText
}
PartyAndAuthorisation3 *-- "1..1" IPartyOrGroup1Choice : PartyOrGroup
PartyAndAuthorisation3 *-- "1..1" Authorisation2 : Authorisation
%% BankTransactionCodeStructure4 recursion level 1 with max 1
BankTransactionCodeStructure4 *-- "0..1" BankTransactionCodeStructure5 : Domain
BankTransactionCodeStructure4 *-- "0..1" ProprietaryBankTransactionCodeStructure1 : Proprietary
  

OperationMandate3 members

Member name Description Data Type / Multiplicity
ModificationCode Specifies the type of change. Modification1Code - Optional 0..1
Identification Unique and unambiguous identification of the mandate. IsoMax35Text - Required 1..1
ApplicableChannel Channel for which the operation mandate is valid. If ApplicableChannel equals Fax, this means that a bank operation instruction sent by fax will be processed according to the mandates exchanged in this message. IChannel2Choice - Unknown 1..0
RequiredSignatureNumber Number of required and necessary signatures by the mandate. IsoMax15PlusSignedNumericText - Required 1..1
SignatureOrderIndicator Indicator whether a certain order of signatures has to be respected or not. IsoYesNoIndicator - Required 1..1
MandateHolder Holder of the mandate. PartyAndAuthorisation3 - Unknown 0..0
BankOperation Bank operation allowed by a mandate. BankTransactionCodeStructure4 - Unknown 1..0
StartDate Is the date when the mandate becomes valid. IsoISODate - Optional 0..1
EndDate Is the date when the mandate stops to be valid. IsoISODate - Optional 0..1

Group building block

Definition of a group of parties. Group of parties with their related security certificate. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Group2 recursion level 0 with max 1
class Group2{
    ModificationCode Modification1Code
    GroupIdentification IsoMax4AlphaNumericText
}
Group2 *-- "1..0" PartyAndCertificate3 : Party
%% PartyAndCertificate3 recursion level 1 with max 1
class PartyAndCertificate3{
    ModificationCode Modification1Code
    Certificate IsoMax10KBinary
}
PartyAndCertificate3 *-- "1..1" PartyIdentification43 : Party
  

Group2 members

Member name Description Data Type / Multiplicity
ModificationCode Specifies the type of change. Modification1Code - Optional 0..1
GroupIdentification Specifies the identification of the group. IsoMax4AlphaNumericText - Required 1..1
Party Specifies a party and related certificate. PartyAndCertificate3 - Unknown 1..0

AdditionalMessageInformation building block

Contains additional information related to the message. Contains additional information related to the message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AdditionalInformation5 recursion level 0 with max 1
class AdditionalInformation5{
    Information IsoMax256Text
}
  

AdditionalInformation5 members

Member name Description Data Type / Multiplicity
Information Contains additional information related to the message. IsoMax256Text - Unknown 1..0

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
%% PartyAndSignature2 recursion level 0 with max 1
PartyAndSignature2 *-- "1..1" PartyIdentification43 : Party
PartyAndSignature2 *-- "1..1" ProprietaryData3 : Signature
%% PartyIdentification43 recursion level 1 with max 1
class PartyIdentification43{
    Name IsoMax140Text
    CountryOfResidence CountryCode
}
PartyIdentification43 *-- "0..1" PostalAddress6 : PostalAddress
PartyIdentification43 *-- "0..1" IParty11Choice : Identification
PartyIdentification43 *-- "0..1" ContactDetails2 : ContactDetails
%% ProprietaryData3 recursion level 1 with max 1
ProprietaryData3 *-- "1..1" SkipProcessing : Any
  

PartyAndSignature2 members

Member name Description Data Type / Multiplicity
Party Entity involved in an activity. PartyIdentification43 - Required 1..1
Signature Signature of a party. ProprietaryData3 - Required 1..1

SupplementaryData building block

Additional information that cannot be captured in the structured elements and/or any other specific block. Additional information that can not be captured in the structured fields and/or any other specific block. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SupplementaryData1 recursion level 0 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
%% IsoSupplementaryDataEnvelope1 recursion level 1 with max 1
  

SupplementaryData1 members

Member name Description Data Type / Multiplicity
PlaceAndName Unambiguous reference to the location where the supplementary data must be inserted in the message instance. In the case of XML, this is expressed by a valid XPath. IsoMax350Text - Optional 0..1
Envelope Technical element wrapping the supplementary data. IsoSupplementaryDataEnvelope1 - Required 1..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AccountMandateMaintenanceRequestV02 --|> IOuterRecord : Implements
    AccountMandateMaintenanceRequestV02Document --|> IOuterDocument~AccountMandateMaintenanceRequestV02~ : Implements
    class IOuterDocument~AccountMandateMaintenanceRequestV02~ {
        AccountMandateMaintenanceRequestV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    AccountMandateMaintenanceRequestV02Document *-- AccountMandateMaintenanceRequestV02 : 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.017.001.02">
    <AcctMndtMntncReq>
        <Refs>
            <!-- References inner content -->
        </Refs>
        <Fr>
            <!-- From inner content -->
        </Fr>
        <CtrctDts>
            <!-- ContractDates inner content -->
        </CtrctDts>
        <UndrlygMstrAgrmt>
            <!-- UnderlyingMasterAgreement inner content -->
        </UndrlygMstrAgrmt>
        <AcctId>
            <!-- AccountIdentification inner content -->
        </AcctId>
        <AcctSvcrId>
            <!-- AccountServicerIdentification inner content -->
        </AcctSvcrId>
        <OrgId>
            <!-- OrganisationIdentification inner content -->
        </OrgId>
        <Mndt>
            <!-- Mandate inner content -->
        </Mndt>
        <Grp>
            <!-- Group inner content -->
        </Grp>
        <AddtlMsgInf>
            <!-- AdditionalMessageInformation inner content -->
        </AddtlMsgInf>
        <DgtlSgntr>
            <!-- DigitalSignature inner content -->
        </DgtlSgntr>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </AcctMndtMntncReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_Yex38Q1TEeKGXqvMN6jpiw"
  nextVersions="_bf9RAW2PEei3KuUgpx7Xcw"
  previousVersion="_rkXieNE9Ed-BzquC8wXy7w_1808843508"
  name="AccountMandateMaintenanceRequestV02"
  definition="The AccountMandateMaintenanceRequest message is sent from an organisation to a financial institution as part of the account maintenance process. It is the initial request message to update one or several accounts. Usage: this update is only about mandate information. &#xD;&#xA;If modification codes are not used: the organisation will specify under the “Mandate” and “Group” tags the complete information as it should be in the financial institution’s records after processing the update request. &#xD;&#xA;If modification codes are used (in that case, they must be used everywhere): the organisation will specify under the “Mandate” and “Group” tags which elements must be added, deleted, modified, or if they are unchanged.&#xD;&#xA;It is not possible to update the account characteristics or organisation information with this message."
  registrationStatus="Registered"
  messageSet="_Q3UKwL0wEeKGooZDzppDJQ"
  xmlTag="AcctMndtMntncReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_Yex38w1TEeKGXqvMN6jpiw"
    nextVersions="_bf9RA22PEei3KuUgpx7Xcw"
    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="_Qn9899p-Ed-ak6NoX_4Aeg_-250058534" />
  <messageBuildingBlock
    xmi:id="_TABW8A1YEeKGXqvMN6jpiw"
    nextVersions="_bf9RBW2PEei3KuUgpx7Xcw"
    name="From"
    definition="Identifies the business sender of the message, if it is not the account owner or account servicing financial institution."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="Fr"
    complexType="_QPiO1Np-Ed-ak6NoX_4Aeg_1971114098" />
  <messageBuildingBlock
    xmi:id="_Yex39w1TEeKGXqvMN6jpiw"
    nextVersions="_bf9RB22PEei3KuUgpx7Xcw"
    name="ContractDates"
    definition="Specifies target dates."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="CtrctDts"
    complexType="_UkZWQtp-Ed-ak6NoX_4Aeg_-1896166238" />
  <messageBuildingBlock
    xmi:id="_Yex3-w1TEeKGXqvMN6jpiw"
    nextVersions="_bf9RCW2PEei3KuUgpx7Xcw"
    name="UnderlyingMasterAgreement"
    definition="Account contract established between the organisation or the group to which the organisation belongs, and the account servicer. This contract has to be applied for the new account to be opened and maintained."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="UndrlygMstrAgrmt"
    complexType="_UkjHQtp-Ed-ak6NoX_4Aeg_15886237" />
  <messageBuildingBlock
    xmi:id="_Yex3_w1TEeKGXqvMN6jpiw"
    nextVersions="_bf9RC22PEei3KuUgpx7Xcw"
    name="AccountIdentification"
    definition="Unique and unambiguous identification of the account between the account owner and the account servicer."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="AcctId"
    complexType="_SN5Y9Np-Ed-ak6NoX_4Aeg_1820239688" />
  <messageBuildingBlock
    xmi:id="_Yex4Aw1TEeKGXqvMN6jpiw"
    nextVersions="_bf9RDW2PEei3KuUgpx7Xcw"
    name="AccountServicerIdentification"
    definition="Unique and unambiguous identifier of a financial institution, as assigned under an internationally recognised or proprietary identification scheme."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="AcctSvcrId"
    complexType="_TFB1Qdp-Ed-ak6NoX_4Aeg_1367253312" />
  <messageBuildingBlock
    xmi:id="_Yex4Bw1TEeKGXqvMN6jpiw"
    nextVersions="_bf9RD22PEei3KuUgpx7Xcw"
    name="OrganisationIdentification"
    definition="Identification of the organisation requesting the change."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="OrgId"
    complexType="_uUtoMQ39EeKGXqvMN6jpiw" />
  <messageBuildingBlock
    xmi:id="_Yex4Cw1TEeKGXqvMN6jpiw"
    nextVersions="_bf9REW2PEei3KuUgpx7Xcw"
    name="Mandate"
    definition="Information specifying the account mandate."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="Mndt"
    complexType="_QCGs4Q4fEeK3IMoVvcTkkg" />
  <messageBuildingBlock
    xmi:id="_gEgTIA4XEeKGXqvMN6jpiw"
    nextVersions="_bf9RE22PEei3KuUgpx7Xcw"
    name="Group"
    definition="Definition of a group of parties."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="Grp"
    complexType="_wNfOoRg4EeKnW4lR85q-0A" />
  <messageBuildingBlock
    xmi:id="_Yex4Dw1TEeKGXqvMN6jpiw"
    nextVersions="_bf9RFW2PEei3KuUgpx7Xcw"
    name="AdditionalMessageInformation"
    definition="Contains additional information related to the message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="AddtlMsgInf"
    complexType="_Qoao5dp-Ed-ak6NoX_4Aeg_478592239" />
  <messageBuildingBlock
    xmi:id="_Yex4Ew1TEeKGXqvMN6jpiw"
    nextVersions="_bf9RF22PEei3KuUgpx7Xcw"
    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="_k4nFNZKuEeGnRMFvqYmPBQ" />
  <messageBuildingBlock
    xmi:id="_qNAEkA4AEeKGXqvMN6jpiw"
    nextVersions="_bf9RGW2PEei3KuUgpx7Xcw"
    name="SupplementaryData"
    definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SplmtryData"
    complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
  <messageDefinitionIdentifier
    businessArea="acmt"
    messageFunctionality="017"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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