acmt.032.001.01
The AccountSwitchBalanceTransferAcknowledgement message is sent by the previous account servicer to the new account servicer in response to the AccountSwitchRequestBalanceTransfer message. It confirms the status of the old account and the balance of the account on closure. In the case of a negative closing balance, the old account servicer provides details of the nominated account to which payment should be made from the new account servicer.
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
%% AccountSwitchBalanceTransferAcknowledgementV01 recursion level 0 with max 0
AccountSwitchBalanceTransferAcknowledgementV01 *-- "1..1" MessageIdentification1 : MessageIdentification
AccountSwitchBalanceTransferAcknowledgementV01 *-- "1..1" AccountSwitchDetails1 : AccountSwitchDetails
AccountSwitchBalanceTransferAcknowledgementV01 *-- "1..1" CashAccount36 : OldAccount
AccountSwitchBalanceTransferAcknowledgementV01 *-- "1..1" AmountAndDirection5 : OldAccountBalance
AccountSwitchBalanceTransferAcknowledgementV01 *-- "0..1" BalanceTransfer1 : BalanceTransfer
AccountSwitchBalanceTransferAcknowledgementV01 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
MessageIdentification building block
Unique identification for the 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 |
AccountSwitchDetails building block
Contains information about the details of the account switch. Details of the account switch, including its status and any response codes. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% AccountSwitchDetails1 recursion level 0 with max 1
class AccountSwitchDetails1{
UniqueReferenceNumber IsoMax35Text
RoutingUniqueReferenceNumber IsoMax35Text
SwitchReceivedDateTime IsoISODateTime
SwitchDate IsoISODate
SwitchType SwitchType1Code
SwitchStatus SwitchStatus1Code
BalanceTransferWindow BalanceTransferWindow1Code
}
AccountSwitchDetails1 *-- "0..0" ResponseDetails1 : Response
%% ResponseDetails1 recursion level 1 with max 1
class ResponseDetails1{
ResponseCode IsoMax35Text
AdditionalDetails IsoMax350Text
}
AccountSwitchDetails1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| UniqueReferenceNumber | Unique number that provides unique and unambiguous identification of the account switch. | IsoMax35Text - Required 1..1 |
| RoutingUniqueReferenceNumber | Unique number that provides unique and unambiguous identification of the account switch. Usage: Where one or more account switches have taken place since the original account switch this field contains the unique number that relates to the switch that transferred the account to the latest new account servicer. | IsoMax35Text - Required 1..1 |
| SwitchReceivedDateTime | Date and time that the request was received by the central switch service, populated by the central switch service only. | IsoISODateTime - Optional 0..1 |
| SwitchDate | Date on which the account switch is expected to have completed. The value is the same as the targeted switch date if the switch completes in the expected timeline. | IsoISODate - Optional 0..1 |
| SwitchType | Indicates whether the account switch is a full switch or a partial switch. Usage: A full switch indicates the transfer of the full balance of the account and associated payment mandates. A partial switch indicates the transfer of certain payment mandates to a new account. | SwitchType1Code - Required 1..1 |
| SwitchStatus | State of the account switch at the time the message is sent. | SwitchStatus1Code - Optional 0..1 |
| BalanceTransferWindow | Identifies the processing window in which the balance transfer will be processed on the day of the account switch. | BalanceTransferWindow1Code - Optional 0..1 |
| Response | Response code and additional information. | ResponseDetails1 - Unknown 0..0 |
OldAccount building block
Account held at the old Account Servicer being switched to the new Account Servicer. Provides the details to identify an account. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% CashAccount36 recursion level 0 with max 1
class CashAccount36{
Currency ActiveOrHistoricCurrencyCode
Name IsoMax70Text
}
CashAccount36 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount36 *-- "0..1" ICashAccountType2Choice : Type
CashAccount36 *-- "0..1" PartyIdentification125 : Owner
CashAccount36 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : Servicer
%% IAccountIdentification4Choice recursion level 1 with max 1
%% ICashAccountType2Choice recursion level 1 with max 1
%% PartyIdentification125 recursion level 1 with max 1
class PartyIdentification125{
Name IsoMax140Text
CountryOfResidence CountryCode
}
PartyIdentification125 *-- "0..1" PostalAddress6 : PostalAddress
PartyIdentification125 *-- "0..1" IParty34Choice : Identification
PartyIdentification125 *-- "0..1" ContactDetails2 : ContactDetails
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
CashAccount36 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 |
| Type | Specifies the nature, or use of the account. | ICashAccountType2Choice - Optional 0..1 |
| Currency | Identification of the currency in which the account is held. | ActiveOrHistoricCurrencyCode - Optional 0..1 |
| Name | Name of the account, as assigned by the account servicing institution, in agreement with the account owner in order to provide an additional means of identification of the account. | |
| Owner | Party that legally owns the account. | PartyIdentification125 - Optional 0..1 |
| Servicer | Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account. | BranchAndFinancialInstitutionIdentification5 - Optional 0..1 |
OldAccountBalance building block
Balance of the old account. Amount of money debited or credited on the books of an account servicer. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% AmountAndDirection5 recursion level 0 with max 1
class AmountAndDirection5{
Amount IsoActiveCurrencyAndAmount
CreditDebit CreditDebitCode
}
AmountAndDirection5 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Amount | Amount of money that is debited or credited. | IsoActiveCurrencyAndAmount - Required 1..1 |
| CreditDebit | Indicates if the amount is a debited or a credited. | CreditDebitCode - Optional 0..1 |
BalanceTransfer building block
Information that enables any payments made in connection with the fulfilment of an account switch to be reconciled by the relevant account servicer with the associated request.
Usage: In the case of a negative closing balance of the old account, and where the old account servicer wishes any payment from the new account servicer to be addressed to an alternate account, this will be specified here. Information that enables any payments made in connection with the fulfilment of an account switch to be reconciled by the relevant account servicer with the associated request. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% BalanceTransfer1 recursion level 0 with max 1
BalanceTransfer1 *-- "0..1" BalanceTransferReference1 : BalanceTransferReference
BalanceTransfer1 *-- "0..1" ISettlementMethod1Choice : BalanceTransferMethod
BalanceTransfer1 *-- "0..1" BalanceTransferFundingLimit1 : BalanceTransferFundingLimit
%% BalanceTransferReference1 recursion level 1 with max 1
class BalanceTransferReference1{
BalanceTransferReference IsoMax35Text
}
%% ISettlementMethod1Choice recursion level 1 with max 1
%% BalanceTransferFundingLimit1 recursion level 1 with max 1
class BalanceTransferFundingLimit1{
CurrencyAmount IsoActiveCurrencyAndAmount
}
BalanceTransfer1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| BalanceTransferReference | Reference that enables the creditor to reconcile a payment received through a different payment channel with the payment request. | BalanceTransferReference1 - Optional 0..1 |
| BalanceTransferMethod | Contains details of the clearance and settlement method chosen to make the appropriate payment from account servicer to account servicer in order to transfer the positive or negative closing balance of the old account to the new account. | ISettlementMethod1Choice - Optional 0..1 |
| BalanceTransferFundingLimit | Maximum value that the new account servicer will pay to the old account servicer when the closing balance on the old account is negative. | BalanceTransferFundingLimit1 - Optional 0..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 AccountSwitchBalanceTransferAcknowledgementV01 implementation follows a specific implementaiton pattern. First of all, AccountSwitchBalanceTransferAcknowledgementV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AccountSwitchBalanceTransferAcknowledgementV01Document implements IOuterDocument. Because AccountSwitchBalanceTransferAcknowledgementV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AccountSwitchBalanceTransferAcknowledgementV01.
classDiagram
class IOuterRecord
AccountSwitchBalanceTransferAcknowledgementV01 --|> IOuterRecord : Implements
AccountSwitchBalanceTransferAcknowledgementV01Document --|> IOuterDocument~AccountSwitchBalanceTransferAcknowledgementV01~ : Implements
class IOuterDocument~AccountSwitchBalanceTransferAcknowledgementV01~ {
AccountSwitchBalanceTransferAcknowledgementV01 Message
}
Document wrapper for serialization
The only real purpose AccountSwitchBalanceTransferAcknowledgementV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:acmt.032.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AccountSwitchBalanceTransferAcknowledgementV01.ToDocument() method. The returned AccountSwitchBalanceTransferAcknowledgementV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram
AccountSwitchBalanceTransferAcknowledgementV01Document *-- AccountSwitchBalanceTransferAcknowledgementV01 : 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.032.001.01">
<AcctSwtchBalTrfAck>
<MsgId>
<!-- MessageIdentification inner content -->
</MsgId>
<AcctSwtchDtls>
<!-- AccountSwitchDetails inner content -->
</AcctSwtchDtls>
<OdAcct>
<!-- OldAccount inner content -->
</OdAcct>
<OdAcctBal>
<!-- OldAccountBalance inner content -->
</OdAcctBal>
<BalTrf>
<!-- BalanceTransfer inner content -->
</BalTrf>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</AcctSwtchBalTrfAck>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_ohwbQBMGEeSTk5fcu7tr9w"
nextVersions="_7HK1cW42EeiU9cctagi5ow"
name="AccountSwitchBalanceTransferAcknowledgementV01"
definition="The AccountSwitchBalanceTransferAcknowledgement message is sent by the previous account servicer to the new account servicer in response to the AccountSwitchRequestBalanceTransfer message. It confirms the status of the old account and the balance of the account on closure. In the case of a negative closing balance, the old account servicer provides details of the nominated account to which payment should be made from the new account servicer."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="AcctSwtchBalTrfAck"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_5evuIa5fEee17eDA_q0a9g"
nextVersions="_7HK1c242EeiU9cctagi5ow"
name="MessageIdentification"
definition="Unique identification for the message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MsgId"
complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
<messageBuildingBlock
xmi:id="_6zD1sa5fEee17eDA_q0a9g"
nextVersions="_7HK1dW42EeiU9cctagi5ow"
name="AccountSwitchDetails"
definition="Contains information about the details of the account switch."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="AcctSwtchDtls"
complexType="_8m2xcQ2ZEeSNWNtJlXOAhg" />
<messageBuildingBlock
xmi:id="_xv5JUBMHEeSTk5fcu7tr9w"
nextVersions="_7HK1d242EeiU9cctagi5ow"
name="OldAccount"
definition="Account held at the old Account Servicer being switched to the new Account Servicer."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="OdAcct"
complexType="_jez1wa9UEeeJJK1oRb-jTw" />
<messageBuildingBlock
xmi:id="_olEYgBMHEeSTk5fcu7tr9w"
nextVersions="_7HK1eW42EeiU9cctagi5ow"
name="OldAccountBalance"
definition="Balance of the old account."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="OdAcctBal"
complexType="_T2Wkhdp-Ed-ak6NoX_4Aeg_-2124038249" />
<messageBuildingBlock
xmi:id="_GupTkA_TEeejZrQVdmNFGg"
nextVersions="_7HK1e242EeiU9cctagi5ow"
name="BalanceTransfer"
definition="Information that enables any payments made in connection with the fulfilment of an account switch to be reconciled by the relevant account servicer with the associated request.

Usage: In the case of a negative closing balance of the old account, and where the old account servicer wishes any payment from the new account servicer to be addressed to an alternate account, this will be specified here."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="BalTrf"
complexType="_5yEaVA_QEeejZrQVdmNFGg" />
<messageBuildingBlock
xmi:id="_wAy5IA8CEeeJ4ZumUkzG4Q"
nextVersions="_7HK1fW42EeiU9cctagi5ow"
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="032"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.