Iso20022

BuyInRegulatoryAdviceV01

sese.041.001.01

Scope

An account owner sends a BuyInRegulatoryAdvice to an account servicer to notify the results of the buy-in transactions executed under CSDR regulatory regime.

The account owner/servicer relationship may be:

Usage

The message may also 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
%% BuyInRegulatoryAdviceV01 recursion level 0 with max 0
BuyInRegulatoryAdviceV01 *-- "0..1" PartyIdentification144 : AccountOwner
BuyInRegulatoryAdviceV01 *-- "1..1" SecuritiesAccount19 : SafekeepingAccount
BuyInRegulatoryAdviceV01 *-- "1..1" BuyInAdviceDetails1 : BuyInAttributes
BuyInRegulatoryAdviceV01 *-- "0..1" SupplementaryData1 : SupplementaryData

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

AccountOwner building block

Party that legally owns the account. Identification of a party. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PartyIdentification144 recursion level 0 with max 1
class PartyIdentification144{
    LEI IsoLEIIdentifier
}
PartyIdentification144 *-- "1..1" IPartyIdentification127Choice : Identification
%% IPartyIdentification127Choice recursion level 1 with max 1

PartyIdentification144 members

Member name Description Data Type / Multiplicity
Identification Unique identification of the party. IPartyIdentification127Choice - Required 1..1
LEI Legal entity identification as an alternate identification for a party. IsoLEIIdentifier - Optional 0..1

SafekeepingAccount building block

Account used in the original failing transaction. Account to or from which a securities entry is made. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SecuritiesAccount19 recursion level 0 with max 1
class SecuritiesAccount19{
    Identification IsoMax35Text
    Name IsoMax70Text
}
SecuritiesAccount19 *-- "0..1" GenericIdentification30 : Type
%% GenericIdentification30 recursion level 1 with max 1
class GenericIdentification30{
    Identification IsoExact4AlphaNumericText
    Issuer IsoMax35Text
    SchemeName IsoMax35Text
}

SecuritiesAccount19 members

Member name Description Data Type / Multiplicity
Identification Unambiguous identification for the account between the account owner and the account servicer. IsoMax35Text - Required 1..1
Type Specifies the type of securities account. GenericIdentification30 - Optional 0..1
Name Description of the account. IsoMax70Text - Optional 0..1

BuyInAttributes building block

Details of the buy-in. Details of a buy-in. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% BuyInAdviceDetails1 recursion level 0 with max 1
class BuyInAdviceDetails1{
    BuyInState BuyInState1Code
    BuyInDeferral BuyInDeferral1Code
}
BuyInAdviceDetails1 *-- "1..1" References23 : Reference
BuyInAdviceDetails1 *-- "0..1" SecurityIdentification19 : FinancialInstrumentIdentification
BuyInAdviceDetails1 *-- "0..1" IFinancialInstrumentQuantity1Choice : Quantity
BuyInAdviceDetails1 *-- "0..1" IRateAndAmountFormat39Choice : BuyInPrice
BuyInAdviceDetails1 *-- "0..1" AmountAndDirection102 : CashCompensationAmount
BuyInAdviceDetails1 *-- "0..1" IDateAndDateTime2Choice : BuyInSettlementDate
%% References23 recursion level 1 with max 1
class References23{
    AccountOwnerTransactionIdentification IsoMax35Text
    AccountServicerTransactionIdentification IsoMax35Text
    MarketInfrastructureTransactionIdentification IsoMax35Text
    ProcessorTransactionIdentification IsoMax35Text
    PoolIdentification IsoMax35Text
    CommonIdentification IsoMax35Text
    TradeIdentification IsoMax52Text
}
%% SecurityIdentification19 recursion level 1 with max 1
class SecurityIdentification19{
    ISIN IsoISINOct2015Identifier
    Description IsoMax140Text
}
SecurityIdentification19 *-- "0..0" OtherIdentification1 : OtherIdentification
%% IFinancialInstrumentQuantity1Choice recursion level 1 with max 1
%% IRateAndAmountFormat39Choice recursion level 1 with max 1
%% AmountAndDirection102 recursion level 1 with max 1
class AmountAndDirection102{
    Amount IsoActiveCurrencyAndAmount
    Sign IsoPlusOrMinusIndicator
}
%% IDateAndDateTime2Choice recursion level 1 with max 1

BuyInAdviceDetails1 members

Member name Description Data Type / Multiplicity
Reference References of the failing transaction. References23 - Required 1..1
BuyInState Status of the buy-in transaction. BuyInState1Code - Required 1..1
BuyInDeferral Specifies if the buy-in transaction was deferred or not. BuyInDeferral1Code - Required 1..1
FinancialInstrumentIdentification Identification of the financial instrument of the buy-in instruction. SecurityIdentification19 - Optional 0..1
Quantity Quantity of financial instrument concerned by the buy-in transaction. IFinancialInstrumentQuantity1Choice - Optional 0..1
BuyInPrice Price of the traded financial instrument in the buy-in transaction. IRateAndAmountFormat39Choice - Optional 0..1
CashCompensationAmount Amount of money that has to be paid by the failing trading party in case of an unsuccessful or partially successful buy-in transaction. AmountAndDirection102 - Optional 0..1
BuyInSettlementDate Settlement date of the buy-in. IDateAndDateTime2Choice - 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 BuyInRegulatoryAdviceV01 implementation follows a specific implementaiton pattern. First of all, BuyInRegulatoryAdviceV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, BuyInRegulatoryAdviceV01Document implements IOuterDocument. Because BuyInRegulatoryAdviceV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type BuyInRegulatoryAdviceV01.

classDiagram
    class IOuterRecord
    BuyInRegulatoryAdviceV01 --|> IOuterRecord : Implements
    BuyInRegulatoryAdviceV01Document --|> IOuterDocument~BuyInRegulatoryAdviceV01~ : Implements
    class IOuterDocument~BuyInRegulatoryAdviceV01~ {
        BuyInRegulatoryAdviceV01 Message
     }

Document wrapper for serialization

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

classDiagram
    BuyInRegulatoryAdviceV01Document *-- BuyInRegulatoryAdviceV01 : 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:sese.041.001.01">
    <BuyInRgltryAdvc>
        <AcctOwnr>
            <!-- AccountOwner inner content -->
        </AcctOwnr>
        <SfkpgAcct>
            <!-- SafekeepingAccount inner content -->
        </SfkpgAcct>
        <BuyInAttrbts>
            <!-- BuyInAttributes inner content -->
        </BuyInAttrbts>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </BuyInRgltryAdvc>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_O1mdgZwQEeqtp-LOti013g"
  name="BuyInRegulatoryAdviceV01"
  definition="Scope&#xD;&#xA;&#xA;An account owner sends a BuyInRegulatoryAdvice to an account servicer to  notify the results of the buy-in transactions executed under CSDR regulatory regime.&#xA;&#xA;&#xD;&#xA;The account owner/servicer relationship may be:&#xA;- a central securities depository participant which has an account with a central securities depository.&#xA;It could also be, if agreed in a service level agreement:&#xA;- a global custodian which has an account with its local agent (sub-custodian), or&#xA;- an investment management institution which manage a fund account opened at a custodian, or&#xA;- a broker which has an account with a custodian, or&#xA;- a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure.&#xA;The ultimate receiving party at the end of the settlement chain is a central securities depository or interational central securities depository.&#xA;&#xA;&#xD;&#xA;&#xD;&#xA;Usage&#xD;&#xA;&#xA;The message may also be used to:&#xA;- re-send a message previously sent,&#xA;- provide a third party with a copy of a message for information,&#xA;- re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.&#xA;&#xA;"
  registrationStatus="Registered"
  messageSet="_jMnLMJwWEeqtp-LOti013g"
  xmlTag="BuyInRgltryAdvc"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_O1mdg5wQEeqtp-LOti013g"
    previousVersion="_vYSqs9BmEeihG9bKfarOOA"
    name="SecuritiesMarketPracticeGroupGuideline"
    definition="The Securities Market Practice Group (SMPG) has published market practice recommendations on the use of this message.&#xD;&#xA;These market practices are available on www.smpg.info."
    registrationStatus="Provisionally Registered" />
  <messageBuildingBlock
    xmi:id="_O1mdiZwQEeqtp-LOti013g"
    previousVersion="_vYSqtdBmEeihG9bKfarOOA"
    name="AccountOwner"
    definition="Party that legally owns the account."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="AcctOwnr"
    complexType="_XnxoYdLCEeiN28wlpBQScw" />
  <messageBuildingBlock
    xmi:id="_O1mdi5wQEeqtp-LOti013g"
    previousVersion="_vYSqt9BmEeihG9bKfarOOA"
    name="SafekeepingAccount"
    definition="Account used in the original failing transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SfkpgAcct"
    complexType="_T_JUKtp-Ed-ak6NoX_4Aeg_1976638301" />
  <messageBuildingBlock
    xmi:id="_O1mdjZwQEeqtp-LOti013g"
    previousVersion="_vYSqudBmEeihG9bKfarOOA"
    name="BuyInAttributes"
    definition="Details of the buy-in."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="BuyInAttrbts"
    complexType="_fGNv0ZwREeqtp-LOti013g" />
  <messageBuildingBlock
    xmi:id="_O1mdkZwQEeqtp-LOti013g"
    previousVersion="_vYSqvdBmEeihG9bKfarOOA"
    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="sese"
    messageFunctionality="041"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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