auth.003.001.01
This message is sent by the authorities (police, customs, tax authorities, enforcement authorities) to a financial institution to inform the financial institution that the confidentiality status of the investigation has changed.
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 %% InformationRequestStatusChangeNotificationV01 recursion level 0 with max 0 class InformationRequestStatusChangeNotificationV01{ OriginalBusinessQuery IsoMax35Text ConfidentialityStatus IsoYesNoIndicator } InformationRequestStatusChangeNotificationV01 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
OriginalBusinessQuery building block
Reference of the information request opening message that this message is an update of. Specifies a character string with a maximum length of 35 characters. For comparison, see the ISO20022 official specification This message is declared as Max35Text in the ISO specification. In our implementation, it is represented in source code as IsoMax35Text. Due to global using directives, it is treated as a System.String by the compiler and runtime.
ConfidentialityStatus building block
Specifies the confidentiality status of the investigation. Indicates a “Yes” or “No” type of answer for an element. For comparison, see the ISO20022 official specification This message is declared as YesNoIndicator in the ISO specification. In our implementation, it is represented in source code as IsoYesNoIndicator. Due to global using directives, it is treated as a System.String by the compiler and runtime.
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
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 InformationRequestStatusChangeNotificationV01 implementation follows a specific implementaiton pattern. First of all, InformationRequestStatusChangeNotificationV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, InformationRequestStatusChangeNotificationV01Document implements IOuterDocument. Because InformationRequestStatusChangeNotificationV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type InformationRequestStatusChangeNotificationV01.
classDiagram class IOuterRecord InformationRequestStatusChangeNotificationV01 --|> IOuterRecord : Implements InformationRequestStatusChangeNotificationV01Document --|> IOuterDocument~InformationRequestStatusChangeNotificationV01~ : Implements class IOuterDocument~InformationRequestStatusChangeNotificationV01~ { InformationRequestStatusChangeNotificationV01 Message }
Document wrapper for serialization
The only real purpose InformationRequestStatusChangeNotificationV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:auth.003.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using InformationRequestStatusChangeNotificationV01.ToDocument() method. The returned InformationRequestStatusChangeNotificationV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram InformationRequestStatusChangeNotificationV01Document *-- InformationRequestStatusChangeNotificationV01 : 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.003.001.01">
<InfReqStsChngNtfctn>
<OrgnlBizQry>
<!-- OriginalBusinessQuery inner content -->
</OrgnlBizQry>
<CnfdtltySts>
<!-- ConfidentialityStatus inner content -->
</CnfdtltySts>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</InfReqStsChngNtfctn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_fQEyMzz1EeGl7N0Cd54dlw"
name="InformationRequestStatusChangeNotificationV01"
definition="This message is sent by the authorities (police, customs, tax authorities, enforcement authorities) to a financial institution to inform the financial institution that the confidentiality status of the investigation has changed."
registrationStatus="Registered"
messageSet="_8zxLQz2SEeGG64_ngBNdUg"
xmlTag="InfReqStsChngNtfctn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_tqPSWz2QEeGG64_ngBNdUg"
name="OriginalBusinessQuery"
definition="Reference of the information request opening message that this message is an update of."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="OrgnlBizQry"
simpleType="_YW1tKdp-Ed-ak6NoX_4Aeg_1913463446" />
<messageBuildingBlock
xmi:id="_0ikcBT2QEeGG64_ngBNdUg"
name="ConfidentialityStatus"
definition="Specifies the confidentiality status of the investigation."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="CnfdtltySts"
simpleType="_YXbjA9p-Ed-ak6NoX_4Aeg_-2040117978" />
<messageBuildingBlock
xmi:id="_2tmJOz2QEeGG64_ngBNdUg"
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="003"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.