acmt.018.001.01
Scope The AccountMandateMaintenanceAmendmentRequest message is sent from an organisation to a financial institution as part of the account maintenance process. It is sent in response to a request from the financial institution to send additional information. This update is only about mandate information. Usage This message should only be sent in response to a request from the financial institution. This update is only about mandate information. The organisation will specify under the Mandate tag the complete information as it should be in the financial institutions records after processing the update request. It is not possible to update the account characteristics or organisation information with this message. It is possible to request to update the mandate information of several accounts, if these accounts must have exactly the same mandates. This message could be sent together with other related documents.
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
%% AccountMandateMaintenanceAmendmentRequestV01 recursion level 0 with max 0
AccountMandateMaintenanceAmendmentRequestV01 *-- "1..1" References4 : References
AccountMandateMaintenanceAmendmentRequestV01 *-- "0..1" AccountContract2 : ContractDates
AccountMandateMaintenanceAmendmentRequestV01 *-- "0..1" ContractDocument1 : UnderlyingMasterAgreement
AccountMandateMaintenanceAmendmentRequestV01 *-- "1..1" AccountForAction1 : AccountIdentification
AccountMandateMaintenanceAmendmentRequestV01 *-- "1..1" BranchAndFinancialInstitutionIdentification4 : AccountServicerIdentification
AccountMandateMaintenanceAmendmentRequestV01 *-- "1..1" OrganisationIdentification6 : OrganisationIdentification
AccountMandateMaintenanceAmendmentRequestV01 *-- "0..1" OperationMandate1 : Mandate
AccountMandateMaintenanceAmendmentRequestV01 *-- "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
%% 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 |
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
%% 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
| 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. | FinancialInstitutionIdentification7 - Required 1..1 |
| BranchIdentification | Identifies a specific branch of a financial institution. |
OrganisationIdentification building block
Identification of the organisation requesting the change. 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
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| BIC | Code allocated to organisations by the ISO 9362 Registration Authority, under an international identification scheme, as described in the latest version of the standard ISO 9362 Banking (Banking telecommunication messages, Business Identifier Codes). | IsoAnyBICIdentifier - Optional 0..1 |
| Other | Unique identification of an organisation, as assigned by an institution, using an identification scheme. | GenericOrganisationIdentification1 - Unknown 0..0 |
Mandate building block
Information specifying the account mandate. Information specifying the Mandate. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% OperationMandate1 recursion level 0 with max 1
class OperationMandate1{
Identification IsoMax35Text
RequiredSignatureNumber IsoMax15PlusSignedNumericText
SignatureOrderIndicator IsoYesNoIndicator
StartDate IsoISODate
EndDate IsoISODate
}
OperationMandate1 *-- "0..0" PartyAndCertificate1 : MandateHolder
OperationMandate1 *-- "1..0" BankTransactionCodeStructure4 : BankOperation
%% PartyAndCertificate1 recursion level 1 with max 1
class PartyAndCertificate1{
Certificate IsoMax10KBinary
SignatureOrder IsoMax15PlusSignedNumericText
}
PartyAndCertificate1 *-- "1..1" PartyIdentification41 : Party
PartyAndCertificate1 *-- "1..1" Authorisation1 : Authorisation
%% BankTransactionCodeStructure4 recursion level 1 with max 1
BankTransactionCodeStructure4 *-- "0..1" BankTransactionCodeStructure5 : Domain
BankTransactionCodeStructure4 *-- "0..1" ProprietaryBankTransactionCodeStructure1 : Proprietary
OperationMandate1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | Unique and unambiguous identification of the mandate. | IsoMax35Text - Required 1..1 |
| 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. | PartyAndCertificate1 - 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 |
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
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Party | Entity involved in an activity. | PartyIdentification41 - Required 1..1 |
| Signature | Signature of a party. | ProprietaryData3 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the AccountMandateMaintenanceAmendmentRequestV01 implementation follows a specific implementaiton pattern. First of all, AccountMandateMaintenanceAmendmentRequestV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AccountMandateMaintenanceAmendmentRequestV01Document implements IOuterDocument. Because AccountMandateMaintenanceAmendmentRequestV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AccountMandateMaintenanceAmendmentRequestV01.
classDiagram
class IOuterRecord
AccountMandateMaintenanceAmendmentRequestV01 --|> IOuterRecord : Implements
AccountMandateMaintenanceAmendmentRequestV01Document --|> IOuterDocument~AccountMandateMaintenanceAmendmentRequestV01~ : Implements
class IOuterDocument~AccountMandateMaintenanceAmendmentRequestV01~ {
AccountMandateMaintenanceAmendmentRequestV01 Message
}
Document wrapper for serialization
The only real purpose AccountMandateMaintenanceAmendmentRequestV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:acmt.018.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AccountMandateMaintenanceAmendmentRequestV01.ToDocument() method. The returned AccountMandateMaintenanceAmendmentRequestV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram
AccountMandateMaintenanceAmendmentRequestV01Document *-- AccountMandateMaintenanceAmendmentRequestV01 : 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.018.001.01">
<AcctMndtMntncAmdmntReq>
<Refs>
<!-- References inner content -->
</Refs>
<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>
<DgtlSgntr>
<!-- DigitalSignature inner content -->
</DgtlSgntr>
</AcctMndtMntncAmdmntReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_rHdkCNE9Ed-BzquC8wXy7w_-266920575"
nextVersions="_XYvc8Q1TEeKGXqvMN6jpiw"
name="AccountMandateMaintenanceAmendmentRequestV01"
definition="Scope
The AccountMandateMaintenanceAmendmentRequest message is sent from an organisation to a financial institution as part of the account maintenance process. It is sent in response to a request from the financial institution to send additional information. This update is only about mandate information.
Usage
This message should only be sent in response to a request from the financial institution. This update is only about mandate information. The organisation will specify under the Mandate tag the complete information as it should be in the financial institutions records after processing the update request. It is not possible to update the account characteristics or organisation information with this message.
It is possible to request to update the mandate information of several accounts, if these accounts must have exactly the same mandates.
This message could be sent together with other related documents."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="AcctMndtMntncAmdmntReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_rHdkCdE9Ed-BzquC8wXy7w_-1650659865"
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="_rHnVANE9Ed-BzquC8wXy7w_1663722693"
name="ContractDates"
definition="Specifies target dates."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="CtrctDts"
complexType="_UkZWQtp-Ed-ak6NoX_4Aeg_-1896166238" />
<messageBuildingBlock
xmi:id="_rHnVAdE9Ed-BzquC8wXy7w_1467666004"
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="_rHnVAtE9Ed-BzquC8wXy7w_604759008"
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="_rHnVA9E9Ed-BzquC8wXy7w_-391901204"
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="_TFB1RNp-Ed-ak6NoX_4Aeg_-736060150" />
<messageBuildingBlock
xmi:id="_rHnVBNE9Ed-BzquC8wXy7w_142996449"
name="OrganisationIdentification"
definition="Identification of the organisation requesting the change."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="OrgId"
complexType="_QPrYxtp-Ed-ak6NoX_4Aeg_434657677" />
<messageBuildingBlock
xmi:id="_rHnVBdE9Ed-BzquC8wXy7w_-1737493661"
name="Mandate"
definition="Information specifying the account mandate."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="Mndt"
complexType="_PU0TCNp-Ed-ak6NoX_4Aeg_882485355" />
<messageBuildingBlock
xmi:id="_rHnVBtE9Ed-BzquC8wXy7w_629134464"
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="018"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.