FinancialSupervisedPartyIdentityReportV01

auth.076.001.01

This FinancialSupervisedPartyIdentityReport message is sent by the competent institution to report parties used for the purpose of the local regulation.

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
%% FinancialSupervisedPartyIdentityReportV01 recursion level 0 with max 0
FinancialSupervisedPartyIdentityReportV01 *-- "1..1" IPartyReport1Choice : PartyData
FinancialSupervisedPartyIdentityReportV01 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

PartyData building block

Provides appropriate instructions to update or cancel information about a party in the scope of the local regulation. Report of the relevant institution. The report can be either an update or a cancellation. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IPartyReport1Choice recursion level 0 with max 1
  

PartyReport1Choice members

SupplementaryData building block

Additional information that can not be captured in the structured fields 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

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    FinancialSupervisedPartyIdentityReportV01 --|> IOuterRecord : Implements
    FinancialSupervisedPartyIdentityReportV01Document --|> IOuterDocument~FinancialSupervisedPartyIdentityReportV01~ : Implements
    class IOuterDocument~FinancialSupervisedPartyIdentityReportV01~ {
        FinancialSupervisedPartyIdentityReportV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    FinancialSupervisedPartyIdentityReportV01Document *-- FinancialSupervisedPartyIdentityReportV01 : 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:auth.076.001.01">
    <FinSprvsdPtyIdntyRpt>
        <PtyData>
            <!-- PartyData inner content -->
        </PtyData>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </FinSprvsdPtyIdntyRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_EUnq8PH0Eeaz_YGUGLjP6A"
  name="FinancialSupervisedPartyIdentityReportV01"
  definition="This FinancialSupervisedPartyIdentityReport message is sent by the competent institution to report parties used for the purpose of the local regulation.&#xD;&#xA;"
  registrationStatus="Registered"
  messageSet="_v6phIPHzEeaz_YGUGLjP6A"
  xmlTag="FinSprvsdPtyIdntyRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_fA8vsIgKEeeMp7TnNqgLag"
    name="SupplementaryDataRule"
    definition="The SupplementaryData building block at message level must not be used to provide any information about a party. The SupplementaryData element at party level should be used for that purpose."
    registrationStatus="Provisionally Registered" />
  <messageBuildingBlock
    xmi:id="_DehT8fH1Eeaz_YGUGLjP6A"
    name="PartyData"
    definition="Provides appropriate instructions to update or cancel information about a party in the scope of the local regulation."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="PtyData"
    complexType="_77i8YDbtEeeYhaZ6bvG1Xg" />
  <messageBuildingBlock
    xmi:id="_nAykQTbuEeeYhaZ6bvG1Xg"
    name="SupplementaryData"
    definition="Additional information that can not be captured in the structured fields and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SplmtryData"
    complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
  <messageDefinitionIdentifier
    businessArea="auth"
    messageFunctionality="076"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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