Iso20022

IntraBalanceMovementModificationRequestV01

camt.072.001.01

The IntraBalanceMovementModificationRequest message is sent from an account owner/requestor to a settlement infrastructure to request the modification of a processing indicator on a previously sent IntraBalanceMovementInstruction message.

Usage: The message may be used to:

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
%% IntraBalanceMovementModificationRequestV01 recursion level 0 with max 0
IntraBalanceMovementModificationRequestV01 *-- "0..1" DocumentIdentification51 : Identification
IntraBalanceMovementModificationRequestV01 *-- "1..1" CashAccount38 : CashAccount
IntraBalanceMovementModificationRequestV01 *-- "0..1" SystemPartyIdentification8 : CashAccountOwner
IntraBalanceMovementModificationRequestV01 *-- "0..1" BranchAndFinancialInstitutionIdentification6 : CashAccountServicer
IntraBalanceMovementModificationRequestV01 *-- "1..1" RequestDetails22 : RequestDetails
IntraBalanceMovementModificationRequestV01 *-- "0..1" IntraBalance5 : UnderlyingIntraBalance
IntraBalanceMovementModificationRequestV01 *-- "0..1" SupplementaryData1 : SupplementaryData

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

Identification building block

Unambiguous identification of the message as known by the account owner (or the instructing party acting on its behalf). Identification and creation date of a document. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% DocumentIdentification51 recursion level 0 with max 1
class DocumentIdentification51{
    Identification IsoMax35Text
    CopyDuplicate CopyDuplicate1Code
}
DocumentIdentification51 *-- "0..1" IDateAndDateTime2Choice : CreationDateTime
DocumentIdentification51 *-- "0..1" PartyIdentification136 : MessageOriginator
DocumentIdentification51 *-- "0..1" PartyIdentification136 : MessageRecipient
%% IDateAndDateTime2Choice recursion level 1 with max 1
%% PartyIdentification136 recursion level 1 with max 1
class PartyIdentification136{
    LEI IsoLEIIdentifier
}
PartyIdentification136 *-- "1..1" IPartyIdentification120Choice : Identification
%% PartyIdentification136 recursion level 1 with max 1
class PartyIdentification136{
    LEI IsoLEIIdentifier
}
PartyIdentification136 *-- "1..1" IPartyIdentification120Choice : Identification

DocumentIdentification51 members

Member name Description Data Type / Multiplicity
Identification Unique identifier of the document (message) assigned by the sender of the document. IsoMax35Text - Required 1..1
CreationDateTime Date and time at which the document (message) was created by the sender. IDateAndDateTime2Choice - Optional 0..1
CopyDuplicate Specifies if this document is a copy, a duplicate, or a duplicate of a copy. CopyDuplicate1Code - Optional 0..1
MessageOriginator Party that originated the message, if other than the sender. PartyIdentification136 - Optional 0..1
MessageRecipient Party that is the final destination of the message, if other than the receiver. PartyIdentification136 - Optional 0..1

CashAccount building block

Account to or from which an entry is made. Provides the details to identify an account. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CashAccount38 recursion level 0 with max 1
class CashAccount38{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount38 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount38 *-- "0..1" ICashAccountType2Choice : Type
CashAccount38 *-- "0..1" ProxyAccountIdentification1 : Proxy
%% IAccountIdentification4Choice recursion level 1 with max 1
%% ICashAccountType2Choice recursion level 1 with max 1
%% ProxyAccountIdentification1 recursion level 1 with max 1
class ProxyAccountIdentification1{
    Identification IsoMax2048Text
}
ProxyAccountIdentification1 *-- "0..1" IProxyAccountType1Choice : Type

CashAccount38 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.
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.
Proxy Specifies an alternate assumed name for the identification of the account. ProxyAccountIdentification1 - Optional 0..1

CashAccountOwner building block

Party that legally owns the cash account. Unique and unambiguous identification of a party within a system. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SystemPartyIdentification8 recursion level 0 with max 1
SystemPartyIdentification8 *-- "1..1" PartyIdentification136 : Identification
SystemPartyIdentification8 *-- "0..1" PartyIdentification136 : ResponsiblePartyIdentification
%% PartyIdentification136 recursion level 1 with max 1
class PartyIdentification136{
    LEI IsoLEIIdentifier
}
PartyIdentification136 *-- "1..1" IPartyIdentification120Choice : Identification
%% PartyIdentification136 recursion level 1 with max 1
class PartyIdentification136{
    LEI IsoLEIIdentifier
}
PartyIdentification136 *-- "1..1" IPartyIdentification120Choice : Identification

SystemPartyIdentification8 members

Member name Description Data Type / Multiplicity
Identification Unique identification to unambiguously identify the party within the system. PartyIdentification136 - Required 1..1
ResponsiblePartyIdentification Unique identification of the party responsible for the maintenance of the party reference data. PartyIdentification136 - Optional 0..1

CashAccountServicer building block

Party that manages the cash 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. Unique and unambiguous identification of a financial institution or a branch of a financial institution. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% BranchAndFinancialInstitutionIdentification6 recursion level 0 with max 1
BranchAndFinancialInstitutionIdentification6 *-- "1..1" FinancialInstitutionIdentification18 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification6 *-- "0..1" BranchData3 : BranchIdentification
%% FinancialInstitutionIdentification18 recursion level 1 with max 1
class FinancialInstitutionIdentification18{
    BICFI IsoBICFIDec2014Identifier
    LEI IsoLEIIdentifier
    Name IsoMax140Text
}
FinancialInstitutionIdentification18 *-- "0..1" ClearingSystemMemberIdentification2 : ClearingSystemMemberIdentification
FinancialInstitutionIdentification18 *-- "0..1" PostalAddress24 : PostalAddress
FinancialInstitutionIdentification18 *-- "0..1" GenericFinancialIdentification1 : Other
%% BranchData3 recursion level 1 with max 1
class BranchData3{
    Identification IsoMax35Text
    LEI IsoLEIIdentifier
    Name IsoMax140Text
}
BranchData3 *-- "0..1" PostalAddress24 : PostalAddress

BranchAndFinancialInstitutionIdentification6 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. FinancialInstitutionIdentification18 - Required 1..1
BranchIdentification Identifies a specific branch of a financial institution.

RequestDetails building block

Details of the request providing the changes and references of the instruction for which the modification is requested. Details of the request providing the changes and references of the instruction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% RequestDetails22 recursion level 0 with max 1
class RequestDetails22{
    PartialSettlementIndicator IsoYesNoIndicator
    ClearingChannel ClearingChannel2Code
}
RequestDetails22 *-- "1..1" References14 : Reference
RequestDetails22 *-- "0..1" ILinkageType3Choice : Linkage
RequestDetails22 *-- "0..1" IPriorityNumeric4Choice : Priority
RequestDetails22 *-- "0..0" GenericIdentification30 : OtherProcessing
RequestDetails22 *-- "0..0" Linkages57 : Linkages
%% References14 recursion level 1 with max 1
class References14{
    AccountOwnerTransactionIdentification IsoMax35Text
    AccountServicerTransactionIdentification IsoMax35Text
    MarketInfrastructureTransactionIdentification IsoMax35Text
    ProcessorTransactionIdentification IsoMax35Text
    PoolIdentification IsoMax35Text
}
%% ILinkageType3Choice recursion level 1 with max 1
%% IPriorityNumeric4Choice recursion level 1 with max 1
%% GenericIdentification30 recursion level 1 with max 1
class GenericIdentification30{
    Identification IsoExact4AlphaNumericText
    Issuer IsoMax35Text
    SchemeName IsoMax35Text
}
%% Linkages57 recursion level 1 with max 1
Linkages57 *-- "0..1" IProcessingPosition7Choice : ProcessingPosition
Linkages57 *-- "0..1" IDocumentNumber5Choice : MessageNumber
Linkages57 *-- "1..1" IReferences34Choice : Reference
Linkages57 *-- "0..1" IPartyIdentification127Choice : ReferenceOwner

RequestDetails22 members

Member name Description Data Type / Multiplicity
Reference References of the transaction for which the intra-balance modification is requested. References14 - Required 1..1
Linkage Specifies the type of linkage requested. ILinkageType3Choice - Optional 0..1
Priority Specifies whether the transaction is to be executed with a high priority. IPriorityNumeric4Choice - Optional 0..1
OtherProcessing Specifies another type of processing change request. GenericIdentification30 - Unknown 0..0
PartialSettlementIndicator Specifies whether partial settlement is allowed. IsoYesNoIndicator - Optional 0..1
ClearingChannel Specifies the clearing channel to be used to process the payment instruction. ClearingChannel2Code - Optional 0..1
Linkages Information regarding the linkage requested. Linkages57 - Unknown 0..0

UnderlyingIntraBalance building block

Original intra-balance movement transaction details. Details of the intra-balance movement. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IntraBalance5 recursion level 0 with max 1
class IntraBalance5{
    InstructionProcessingAdditionalDetails IsoMax350Text
}
IntraBalance5 *-- "1..1" IAmount2Choice : SettlementAmount
IntraBalance5 *-- "1..1" IDateAndDateTime2Choice : SettlementDate
IntraBalance5 *-- "1..1" CashSubBalanceTypeAndQuantityBreakdown3 : BalanceFrom
IntraBalance5 *-- "1..1" CashSubBalanceTypeAndQuantityBreakdown3 : BalanceTo
IntraBalance5 *-- "0..1" GenericIdentification37 : CashSubBalanceIdentification
IntraBalance5 *-- "0..1" IPriorityNumeric4Choice : Priority
%% IAmount2Choice recursion level 1 with max 1
%% IDateAndDateTime2Choice recursion level 1 with max 1
%% CashSubBalanceTypeAndQuantityBreakdown3 recursion level 1 with max 1
CashSubBalanceTypeAndQuantityBreakdown3 *-- "1..1" ICashBalanceType3Choice : Type
CashSubBalanceTypeAndQuantityBreakdown3 *-- "0..0" AmountAndQuantityBreakdown1 : QuantityBreakdown
%% CashSubBalanceTypeAndQuantityBreakdown3 recursion level 1 with max 1
CashSubBalanceTypeAndQuantityBreakdown3 *-- "1..1" ICashBalanceType3Choice : Type
CashSubBalanceTypeAndQuantityBreakdown3 *-- "0..0" AmountAndQuantityBreakdown1 : QuantityBreakdown
%% GenericIdentification37 recursion level 1 with max 1
class GenericIdentification37{
    Identification IsoMax35Text
    Issuer IsoMax35Text
}
%% IPriorityNumeric4Choice recursion level 1 with max 1

IntraBalance5 members

Member name Description Data Type / Multiplicity
SettlementAmount Total amount of money to be settled. IAmount2Choice - Required 1..1
SettlementDate Date and time at which the amount of money is to be moved. IDateAndDateTime2Choice - Required 1..1
BalanceFrom Balance from which the amount of money is moved. CashSubBalanceTypeAndQuantityBreakdown3 - Required 1..1
BalanceTo Balance to which the amount of money is moved. CashSubBalanceTypeAndQuantityBreakdown3 - Required 1..1
CashSubBalanceIdentification Number identifying a lot constituting the sub-balance. GenericIdentification37 - Optional 0..1
Priority Specifies whether the transaction is to be executed with a high priority. IPriorityNumeric4Choice - Optional 0..1
InstructionProcessingAdditionalDetails Provides additional settlement processing information which can not be included within the structured fields of the message. IsoMax350Text - 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 IntraBalanceMovementModificationRequestV01 implementation follows a specific implementaiton pattern. First of all, IntraBalanceMovementModificationRequestV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, IntraBalanceMovementModificationRequestV01Document implements IOuterDocument. Because IntraBalanceMovementModificationRequestV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type IntraBalanceMovementModificationRequestV01.

classDiagram
    class IOuterRecord
    IntraBalanceMovementModificationRequestV01 --|> IOuterRecord : Implements
    IntraBalanceMovementModificationRequestV01Document --|> IOuterDocument~IntraBalanceMovementModificationRequestV01~ : Implements
    class IOuterDocument~IntraBalanceMovementModificationRequestV01~ {
        IntraBalanceMovementModificationRequestV01 Message
     }

Document wrapper for serialization

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

classDiagram
    IntraBalanceMovementModificationRequestV01Document *-- IntraBalanceMovementModificationRequestV01 : 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:camt.072.001.01">
    <IntraBalMvmntModReq>
        <Id>
            <!-- Identification inner content -->
        </Id>
        <CshAcct>
            <!-- CashAccount inner content -->
        </CshAcct>
        <CshAcctOwnr>
            <!-- CashAccountOwner inner content -->
        </CshAcctOwnr>
        <CshAcctSvcr>
            <!-- CashAccountServicer inner content -->
        </CshAcctSvcr>
        <ReqDtls>
            <!-- RequestDetails inner content -->
        </ReqDtls>
        <UndrlygIntraBal>
            <!-- UnderlyingIntraBalance inner content -->
        </UndrlygIntraBal>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </IntraBalMvmntModReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_DLtLCTncEem7JZMuWtwtsg"
  name="IntraBalanceMovementModificationRequestV01"
  definition="The IntraBalanceMovementModificationRequest message is sent from an account owner/requestor to a settlement infrastructure to request the modification of a processing indicator on a previously sent IntraBalanceMovementInstruction message.&#xD;&#xA;&#xD;&#xA;Usage: &#xD;&#xA;The message may be used to:&#xD;&#xA;- re-send a message previously sent (the sub-function of the message is &quot;Duplicate&quot;)&#xD;&#xA;- provide a third party with a copy of a message for information (the sub-function of the message is &quot;Copy&quot;)&#xD;&#xA;- re-send to a third party a copy of a message for information (the sub-function of the message is &quot;CopyDuplicate&quot;)."
  registrationStatus="Registered"
  messageSet="_Fl3iMBHREeqzEaNIFJIN-g"
  xmlTag="IntraBalMvmntModReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_DLtLETncEem7JZMuWtwtsg"
    name="Identification"
    definition="Unambiguous identification of the message as known by the account owner (or the instructing party acting on its behalf)."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="Id"
    complexType="_BsblMTp6EemwKdP955WBJQ" />
  <messageBuildingBlock
    xmi:id="_DLtLEzncEem7JZMuWtwtsg"
    name="CashAccount"
    definition="Account to or from which an entry is made."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="CshAcct"
    complexType="_TnJx8Xh1EeidzqjNEfehPg" />
  <messageBuildingBlock
    xmi:id="_EHK3Yjp8EemwKdP955WBJQ"
    name="CashAccountOwner"
    definition="Party that legally owns the cash account."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="CshAcctOwnr"
    complexType="_7KrUEVhLEeih3fUfzR38Ig" />
  <messageBuildingBlock
    xmi:id="_EHK3Yzp8EemwKdP955WBJQ"
    name="CashAccountServicer"
    definition="Party that manages the cash 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."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="CshAcctSvcr"
    complexType="_8nO10W49EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_DLtLFTncEem7JZMuWtwtsg"
    name="RequestDetails"
    definition="Details of the request providing the changes and references of the instruction for which the modification is requested."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="ReqDtls"
    complexType="_ZCu2lzneEem7JZMuWtwtsg" />
  <messageBuildingBlock
    xmi:id="_DLtLFzncEem7JZMuWtwtsg"
    name="UnderlyingIntraBalance"
    definition="Original intra-balance movement transaction details."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="UndrlygIntraBal"
    complexType="_pqQzoTnfEem7JZMuWtwtsg" />
  <messageBuildingBlock
    xmi:id="_DLtLGTncEem7JZMuWtwtsg"
    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="camt"
    messageFunctionality="072"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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