RedemptionOrderConfirmationV04

setr.006.001.04

Scope The RedemptionOrderConfirmation message is sent by an executing party, for example, a transfer agent, to the instructing party, for example, an investment manager or its authorised representative, to confirm the details of execution for a previously received RedemptionOrder message. Usage The RedemptionOrderConfirmation message is used to confirm the execution of one or more individual orders. A RedemptionOrder message containing more than one individual order may be responded to by more than one RedemptionOrderConfirmation message, as the valuation cycle of the financial instruments in each individual order may be different. When a RedemptionOrderConfirmation message contains fewer confirmations that originally instructed in the original RedemptionOrder message, there is no specification indication in the confirmation for this. Reconciliation must be based on the references. Each individual order confirmation specified is identified in DealReference. The reference of the original individual order is specified in OrderReference. The message identification of the RedemptionOrder message in which the individual order was conveyed may also be quoted in RelatedReference but this is not recommended. A RedemptionOrder must in all cases be responded to by a RedemptionOrderConfirmation message and in no circumstances by a RedemptionBulkOrderConfirmation message. If the executing party needs to confirm one or more redemption orders for the same financial instrument then a RedemptionBulkOrderConfirmation message must be used. When the message is used to convey a confirmation amendment/s, the AmendmentIndicator must be present with the value ‘true’ or ‘1’. When this is the case, the message must only contain a confirmation amendment/s and not contain both a confirmation amendment/s and a ‘new’ confirmation/s.

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
%% RedemptionOrderConfirmationV04 recursion level 0 with max 0
RedemptionOrderConfirmationV04 *-- "1..1" MessageIdentification1 : MessageIdentification
RedemptionOrderConfirmationV04 *-- "0..1" AdditionalReference9 : PoolReference
RedemptionOrderConfirmationV04 *-- "0..1" AdditionalReference8 : PreviousReference
RedemptionOrderConfirmationV04 *-- "0..1" AdditionalReference8 : RelatedReference
RedemptionOrderConfirmationV04 *-- "1..1" RedemptionMultipleExecution5 : MultipleExecutionDetails
RedemptionOrderConfirmationV04 *-- "0..1" CopyInformation4 : CopyDetails
RedemptionOrderConfirmationV04 *-- "0..1" Extension1 : Extension
  

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

MessageIdentification building block

Reference that uniquely identifies the message from a business application standpoint. 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

PoolReference building block

Collective reference identifying a set of messages. References a related message or provides another reference, such as a pool reference, linking a set of messages. The party which issued the related reference may be the Sender of the referenced message or a party other than the Sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AdditionalReference9 recursion level 0 with max 1
class AdditionalReference9{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference9 *-- "0..1" PartyIdentification113 : ReferenceIssuer
%% PartyIdentification113 recursion level 1 with max 1
class PartyIdentification113{
    LEI IsoLEIIdentifier
}
PartyIdentification113 *-- "1..1" IPartyIdentification90Choice : Party
  

AdditionalReference9 members

PreviousReference building block

Reference to a linked message that was previously sent. References a related message or provides another reference, such as a pool reference, linking a set of messages. The party which issued the related reference may be the Sender of the referenced message or a party other than the Sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AdditionalReference8 recursion level 0 with max 1
class AdditionalReference8{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference8 *-- "0..1" PartyIdentification113 : ReferenceIssuer
%% PartyIdentification113 recursion level 1 with max 1
class PartyIdentification113{
    LEI IsoLEIIdentifier
}
PartyIdentification113 *-- "1..1" IPartyIdentification90Choice : Party
  

AdditionalReference8 members

RelatedReference building block

Reference to a linked message that was previously received. References a related message or provides another reference, such as a pool reference, linking a set of messages. The party which issued the related reference may be the Sender of the referenced message or a party other than the Sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AdditionalReference8 recursion level 0 with max 1
class AdditionalReference8{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference8 *-- "0..1" PartyIdentification113 : ReferenceIssuer
%% PartyIdentification113 recursion level 1 with max 1
class PartyIdentification113{
    LEI IsoLEIIdentifier
}
PartyIdentification113 *-- "1..1" IPartyIdentification90Choice : Party
  

AdditionalReference8 members

MultipleExecutionDetails building block

General information related to the execution of investment fund orders. Execution of a redemption order. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% RedemptionMultipleExecution5 recursion level 0 with max 1
class RedemptionMultipleExecution5{
    AmendmentIndicator IsoYesNoIndicator
    MasterReference IsoMax35Text
    OrderDateTime IsoISODateTime
    ReceivedDateTime IsoISODateTime
    RequestedFutureTradeDate IsoISODate
    TotalSettlementAmount IsoActiveCurrencyAndAmount
}
RedemptionMultipleExecution5 *-- "0..1" IPlaceOfTradeIdentification1Choice : PlaceOfTrade
RedemptionMultipleExecution5 *-- "0..1" ICancellationRight1Choice : CancellationRight
RedemptionMultipleExecution5 *-- "1..1" InvestmentAccount58 : InvestmentAccountDetails
RedemptionMultipleExecution5 *-- "0..0" IndividualPerson32 : BeneficiaryDetails
RedemptionMultipleExecution5 *-- "1..0" RedemptionExecution15 : IndividualExecutionDetails
RedemptionMultipleExecution5 *-- "0..1" PaymentTransaction72 : BulkCashSettlementDetails
%% IPlaceOfTradeIdentification1Choice recursion level 1 with max 1
%% ICancellationRight1Choice recursion level 1 with max 1
%% InvestmentAccount58 recursion level 1 with max 1
class InvestmentAccount58{
    AccountIdentification IsoMax35Text
    AccountName IsoMax35Text
    AccountDesignation IsoMax35Text
    OrderOriginatorEligibility OrderOriginatorEligibility1Code
}
InvestmentAccount58 *-- "0..0" PartyIdentification113 : OwnerIdentification
InvestmentAccount58 *-- "0..1" PartyIdentification113 : AccountServicer
InvestmentAccount58 *-- "0..1" SubAccount6 : SubAccountDetails
%% IndividualPerson32 recursion level 1 with max 1
class IndividualPerson32{
    Name IsoMax350Text
    BirthDate IsoISODate
}
IndividualPerson32 *-- "0..1" CountryAndResidentialStatusType2 : CountryAndResidentialStatus
IndividualPerson32 *-- "0..0" GenericIdentification164 : OtherIdentification
%% RedemptionExecution15 recursion level 1 with max 1
class RedemptionExecution15{
    OrderReference IsoMax35Text
    ClientReference IsoMax35Text
    DealReference IsoMax35Text
    UnitsNumber IsoDecimalNumber
    Rounding RoundingDirection2Code
    NetAmount IsoActiveCurrencyAndAmount
    GrossAmount IsoActiveCurrencyAndAmount
    HoldingsRedemptionRate IsoPercentageRate
    SettlementAmount IsoActiveCurrencyAndAmount
    CashSettlementDate IsoISODate
    SettlementMethod DeliveryReceiptType2Code
    PartiallyExecutedIndicator IsoYesNoIndicator
    BestExecution BestExecution1Code
    CumDividendIndicator IsoYesNoIndicator
    IncomePreference IncomePreference1Code
    Group1Or2Units UKTaxGroupUnit1Code
    PhysicalDeliveryIndicator IsoYesNoIndicator
    RequestedSettlementCurrency ActiveCurrencyCode
    RequestedNAVCurrency ActiveOrHistoricCurrencyCode
    NonStandardSettlementInformation IsoMax350Text
    PartialSettlementOfUnits IsoPercentageRate
    PartialSettlementOfCash IsoPercentageRate
    PartialRedemptionWithholdingAmount IsoActiveCurrencyAndAmount
    FinancialAdvice FinancialAdvice1Code
    NegotiatedTrade NegotiatedTrade1Code
    LateReport LateReport1Code
}
RedemptionExecution15 *-- "0..10" IFundOrderType4Choice : OrderType
RedemptionExecution15 *-- "1..1" FinancialInstrument57 : FinancialInstrumentDetails
RedemptionExecution15 *-- "0..1" SubAccount6 : SubAccountForHolding
RedemptionExecution15 *-- "1..1" IDateAndDateTimeChoice : TradeDateTime
RedemptionExecution15 *-- "1..1" UnitPrice22 : DealingPriceDetails
RedemptionExecution15 *-- "0..2" UnitPrice22 : InformativePriceDetails
RedemptionExecution15 *-- "0..1" IProfitAndLoss2Choice : InterimProfitAmount
RedemptionExecution15 *-- "0..0" ForeignExchangeTerms33 : ForeignExchangeDetails
RedemptionExecution15 *-- "0..1" TotalFeesAndTaxes40 : TransactionOverhead
RedemptionExecution15 *-- "0..1" InformativeTax1 : InformativeTaxDetails
RedemptionExecution15 *-- "0..1" FundSettlementParameters11 : SettlementAndCustodyDetails
RedemptionExecution15 *-- "0..1" DeliveryParameters3 : PhysicalDeliveryDetails
RedemptionExecution15 *-- "0..1" PaymentTransaction72 : CashSettlementDetails
RedemptionExecution15 *-- "0..4" InvestmentFundsOrderBreakdown2 : StaffClientBreakdown
RedemptionExecution15 *-- "0..10" Intermediary39 : RelatedPartyDetails
RedemptionExecution15 *-- "0..1" Equalisation1 : Equalisation
RedemptionExecution15 *-- "0..1" ICustomerConductClassification1Choice : CustomerConductClassification
RedemptionExecution15 *-- "0..1" ITransactionChannelType1Choice : TransactionChannelType
RedemptionExecution15 *-- "0..1" ISignatureType1Choice : SignatureType
RedemptionExecution15 *-- "0..1" OrderWaiver1 : OrderWaiverDetails
RedemptionExecution15 *-- "0..1" HoldBackInformation2 : GatingOrHoldBackDetails
%% PaymentTransaction72 recursion level 1 with max 1
PaymentTransaction72 *-- "1..1" IPaymentInstrument21Choice : PaymentInstrument
  

RedemptionMultipleExecution5 members

CopyDetails building block

Information provided when the message is a copy of a previous message. Information provided when the message is a copy of a previous message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CopyInformation4 recursion level 0 with max 1
class CopyInformation4{
    CopyIndicator IsoYesNoIndicator
    OriginalReceiver IsoAnyBICIdentifier
}
  

CopyInformation4 members

Extension 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
%% Extension1 recursion level 0 with max 1
class Extension1{
    PlaceAndName IsoMax350Text
    Text IsoMax350Text
}
  

Extension1 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    RedemptionOrderConfirmationV04 --|> IOuterRecord : Implements
    RedemptionOrderConfirmationV04Document --|> IOuterDocument~RedemptionOrderConfirmationV04~ : Implements
    class IOuterDocument~RedemptionOrderConfirmationV04~ {
        RedemptionOrderConfirmationV04 Message
     }
  

Document wrapper for serialization

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

classDiagram
    RedemptionOrderConfirmationV04Document *-- RedemptionOrderConfirmationV04 : 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:setr.006.001.04">
    <RedOrdrConf>
        <MsgId>
            <!-- MessageIdentification inner content -->
        </MsgId>
        <PoolRef>
            <!-- PoolReference inner content -->
        </PoolRef>
        <PrvsRef>
            <!-- PreviousReference inner content -->
        </PrvsRef>
        <RltdRef>
            <!-- RelatedReference inner content -->
        </RltdRef>
        <MltplExctnDtls>
            <!-- MultipleExecutionDetails inner content -->
        </MltplExctnDtls>
        <CpyDtls>
            <!-- CopyDetails inner content -->
        </CpyDtls>
        <Xtnsn>
            <!-- Extension inner content -->
        </Xtnsn>
    </RedOrdrConf>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_Aab6QzbLEead9bDRE_1DAQ"
  previousVersion="_utoEWNE7Ed-BzquC8wXy7w_1346008013"
  name="RedemptionOrderConfirmationV04"
  definition="Scope&#xD;&#xA;The RedemptionOrderConfirmation message is sent by an executing party, for example, a transfer agent, to the instructing party, for example, an investment manager or its authorised representative, to confirm the details of execution for a previously received RedemptionOrder message.&#xD;&#xA;Usage&#xD;&#xA;The RedemptionOrderConfirmation message is used to confirm the execution of one or more individual orders.&#xD;&#xA;A RedemptionOrder message containing more than one individual order may be responded to by more than one RedemptionOrderConfirmation message, as the valuation cycle of the financial instruments in each individual order may be different. When a RedemptionOrderConfirmation message contains fewer confirmations that originally instructed in the original RedemptionOrder message, there is no specification indication in the confirmation for this. Reconciliation must be based on the references.&#xD;&#xA;Each individual order confirmation specified is identified in DealReference. The reference of the original individual order is specified in OrderReference. The message identification of the RedemptionOrder message in which the individual order was conveyed may also be quoted in RelatedReference but this is not recommended.&#xD;&#xA;A RedemptionOrder must in all cases be responded to by a RedemptionOrderConfirmation message and in no circumstances by a RedemptionBulkOrderConfirmation message.&#xD;&#xA;If the executing party needs to confirm one or more redemption orders for the same financial instrument then a RedemptionBulkOrderConfirmation message must be used.&#xD;&#xA;When the message is used to convey a confirmation amendment/s, the AmendmentIndicator must be present with the value ‘true’ or ‘1’. When this is the case, the message must only contain a confirmation amendment/s and not contain both a confirmation amendment/s and a ‘new’ confirmation/s."
  registrationStatus="Registered"
  messageSet="_hijK0WiLEeOuqdLlpUIWBw _qCumkAFwEeu2__1EbNXzuA"
  xmlTag="RedOrdrConf"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_Aab6RTbLEead9bDRE_1DAQ"
    previousVersion="_ut6_QNE7Ed-BzquC8wXy7w_1718187321"
    name="AccountIdentificationRule"
    definition="If this message is linked to an account opening request and the account identification is not yet known then the value of the AccountIdentification element in MultipleExecutionDetails/InvestmentAccountDetails must be UNKNOWN."
    registrationStatus="Provisionally Registered" />
  <constraint
    xmi:id="_Aab6RzbLEead9bDRE_1DAQ"
    previousVersion="_ut6_Q9E7Ed-BzquC8wXy7w_-1532899470"
    name="OrderReferenceRule"
    definition="If this message is not solicited by the receiver, then the value of the OrderReference element in every occurrence of MultipleExecutionDetails/IndividualExecutionDetails must be UNSOLICITED."
    registrationStatus="Provisionally Registered" />
  <messageBuildingBlock
    xmi:id="_Aab6TTbLEead9bDRE_1DAQ"
    previousVersion="_utxOQNE7Ed-BzquC8wXy7w_-1539573830"
    name="MessageIdentification"
    definition="Reference that uniquely identifies the message from a business application standpoint."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MsgId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_Aab6TzbLEead9bDRE_1DAQ"
    previousVersion="_utxOQdE7Ed-BzquC8wXy7w_-412970353"
    name="PoolReference"
    definition="Collective reference identifying a set of messages."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="PoolRef"
    complexType="_N4g3EXETEea2e4bzJ8TyEw" />
  <messageBuildingBlock
    xmi:id="_Aab6UTbLEead9bDRE_1DAQ"
    previousVersion="_utxOQtE7Ed-BzquC8wXy7w_-411121699"
    name="PreviousReference"
    definition="Reference to a linked message that was previously sent."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="PrvsRef"
    complexType="_udnPoTbsEead9bDRE_1DAQ" />
  <messageBuildingBlock
    xmi:id="_Aab6UzbLEead9bDRE_1DAQ"
    previousVersion="_utxOQ9E7Ed-BzquC8wXy7w_-400964997"
    name="RelatedReference"
    definition="Reference to a linked message that was previously received."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="RltdRef"
    complexType="_udnPoTbsEead9bDRE_1DAQ" />
  <messageBuildingBlock
    xmi:id="_Aab6VTbLEead9bDRE_1DAQ"
    previousVersion="_utxORNE7Ed-BzquC8wXy7w_1763770658"
    name="MultipleExecutionDetails"
    definition="General information related to the execution of investment fund orders."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MltplExctnDtls"
    complexType="_GKGTHzbtEead9bDRE_1DAQ" />
  <messageBuildingBlock
    xmi:id="_Aab6WTbLEead9bDRE_1DAQ"
    previousVersion="_utxORtE7Ed-BzquC8wXy7w_647232459"
    name="CopyDetails"
    definition="Information provided when the message is a copy of a previous message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="CpyDtls"
    complexType="_7VUJ8degEeSA_uUacqhl1Q" />
  <messageBuildingBlock
    xmi:id="_Aab6WzbLEead9bDRE_1DAQ"
    previousVersion="_utxOR9E7Ed-BzquC8wXy7w_649080424"
    name="Extension"
    definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="Xtnsn"
    complexType="_Q6vvCNp-Ed-ak6NoX_4Aeg_1503007069" />
  <messageDefinitionIdentifier
    businessArea="setr"
    messageFunctionality="006"
    flavour="001"
    version="04" />
</messageDefinition>

ISO Building Blocks

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