auth.026.001.01
The CurrencyControlRequestOrLetter message is sent by the reporting party (respectively the registration agent) to the registration agent (respectively the reporting party) to send a currency control related letter or to request for supporting documents.
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
%% CurrencyControlRequestOrLetterV01 recursion level 0 with max 0
CurrencyControlRequestOrLetterV01 *-- "1..1" CurrencyControlHeader3 : GroupHeader
CurrencyControlRequestOrLetterV01 *-- "1..1" SupportingDocumentRequestOrLetter1 : RequestOrLetter
CurrencyControlRequestOrLetterV01 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
GroupHeader building block
Characteristics shared by all individual items included in the message. Characteristics shared by all individual items included in the currency control message. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% CurrencyControlHeader3 recursion level 0 with max 1
class CurrencyControlHeader3{
MessageIdentification IsoMax35Text
CreationDateTime IsoISODateTime
NumberOfItems IsoMax15NumericText
}
CurrencyControlHeader3 *-- "1..1" IParty28Choice : InitiatingParty
CurrencyControlHeader3 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : ForwardingAgent
%% IParty28Choice recursion level 1 with max 1
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
CurrencyControlHeader3 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MessageIdentification | Point to point reference, as assigned by the instructing party, and sent to the next party in the chain to unambiguously identify the message. | Usage: The instructing party has to make sure that MessageIdentification is unique per instructed party for a pre-agreed period. |
| CreationDateTime | Date and time at which the message was created. | IsoISODateTime - Required 1..1 |
| NumberOfItems | Number of individual items contained in the message. | IsoMax15NumericText - Required 1..1 |
| InitiatingParty | Party that initiates the instruction. | IParty28Choice - Required 1..1 |
| ForwardingAgent | Agent which forwards the message. | BranchAndFinancialInstitutionIdentification5 - Optional 0..1 |
RequestOrLetter building block
Supporting document request or letter details. Currency control related document or letter supporting the contract registration. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% SupportingDocumentRequestOrLetter1 recursion level 0 with max 1
class SupportingDocumentRequestOrLetter1{
RequestOrLetterIdentification IsoMax35Text
Date IsoISODate
Subject IsoMax140Text
Type SupportDocumentType1Code
Description IsoMax1025Text
ResponseRequired IsoTrueFalseIndicator
DueDate IsoISODate
}
SupportingDocumentRequestOrLetter1 *-- "0..1" IParty28Choice : Sender
SupportingDocumentRequestOrLetter1 *-- "0..1" IParty28Choice : Receiver
SupportingDocumentRequestOrLetter1 *-- "0..0" OriginalMessage2 : OriginalReferences
SupportingDocumentRequestOrLetter1 *-- "0..0" DocumentGeneralInformation3 : Attachment
SupportingDocumentRequestOrLetter1 *-- "0..0" SupplementaryData1 : SupplementaryData
%% IParty28Choice recursion level 1 with max 1
%% IParty28Choice recursion level 1 with max 1
%% OriginalMessage2 recursion level 1 with max 1
class OriginalMessage2{
OriginalMessageIdentification IsoMax35Text
OriginalMessageNameIdentification IsoMax35Text
OriginalCreationDateTime IsoISODateTime
OriginalPackageIdentification IsoMax35Text
OriginalRecordIdentification IsoMax35Text
}
OriginalMessage2 *-- "0..1" IParty28Choice : OriginalSender
%% DocumentGeneralInformation3 recursion level 1 with max 1
class DocumentGeneralInformation3{
DocumentType ExternalDocumentType1Code
DocumentNumber IsoMax35Text
SenderReceiverSequenceIdentification IsoMax140Text
IssueDate IsoISODate
URL IsoMax256Text
}
DocumentGeneralInformation3 *-- "0..1" IsoSignatureEnvelopeReference : LinkFileHash
DocumentGeneralInformation3 *-- "1..1" BinaryFile1 : AttachedBinaryFile
%% SupplementaryData1 recursion level 1 with max 1
class SupplementaryData1{
PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
SupportingDocumentRequestOrLetter1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| RequestOrLetterIdentification | Unique and unambiguous identification of the supporting document request or the letter. | IsoMax35Text - Required 1..1 |
| Date | Date of the supporting document request or the letter. | IsoISODate - Optional 0..1 |
| Sender | Sender of the request or letter. | IParty28Choice - Optional 0..1 |
| Receiver | Receiver of the request or letter. | IParty28Choice - Optional 0..1 |
| OriginalReferences | Provides the references of the original underlying message(s) for which supporting documents are requested or for which the letter is sent. | OriginalMessage2 - Unknown 0..0 |
| Subject | Subject of the letter or supporting document. | IsoMax140Text - Required 1..1 |
| Type | Provides the type of supporting document requested. | SupportDocumentType1Code - Required 1..1 |
| Description | Further free format description of the request. | IsoMax1025Text - Optional 0..1 |
| ResponseRequired | Flag to indicate whether a response is required or not. Usage: when the request is used to send a letter, there is no response required. | IsoTrueFalseIndicator - Required 1..1 |
| DueDate | Date by which the response to the request is expected. | IsoISODate - Optional 0..1 |
| Attachment | Documents provided as attachments to the supporting document request or letter. | DocumentGeneralInformation3 - Unknown 0..0 |
| SupplementaryData | Additional information that cannot be captured in the structured elements and/or any other specific block. | SupplementaryData1 - Unknown 0..0 |
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 CurrencyControlRequestOrLetterV01 implementation follows a specific implementaiton pattern. First of all, CurrencyControlRequestOrLetterV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, CurrencyControlRequestOrLetterV01Document implements IOuterDocument. Because CurrencyControlRequestOrLetterV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type CurrencyControlRequestOrLetterV01.
classDiagram
class IOuterRecord
CurrencyControlRequestOrLetterV01 --|> IOuterRecord : Implements
CurrencyControlRequestOrLetterV01Document --|> IOuterDocument~CurrencyControlRequestOrLetterV01~ : Implements
class IOuterDocument~CurrencyControlRequestOrLetterV01~ {
CurrencyControlRequestOrLetterV01 Message
}
Document wrapper for serialization
The only real purpose CurrencyControlRequestOrLetterV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:auth.026.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using CurrencyControlRequestOrLetterV01.ToDocument() method. The returned CurrencyControlRequestOrLetterV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram
CurrencyControlRequestOrLetterV01Document *-- CurrencyControlRequestOrLetterV01 : 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.026.001.01">
<CcyCtrlReqOrLttr>
<GrpHdr>
<!-- GroupHeader inner content -->
</GrpHdr>
<ReqOrLttr>
<!-- RequestOrLetter inner content -->
</ReqOrLttr>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</CcyCtrlReqOrLttr>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_c5_V8NnPEeS--7IJLPC9lw"
nextVersions="_bf9R-22PEei3KuUgpx7Xcw"
name="CurrencyControlRequestOrLetterV01"
definition="The CurrencyControlRequestOrLetter message is sent by the reporting party (respectively the registration agent) to the registration agent (respectively the reporting party) to send a currency control related letter or to request for supporting documents."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="CcyCtrlReqOrLttr"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_RN_MYdnQEeS--7IJLPC9lw"
nextVersions="_bf9R_W2PEei3KuUgpx7Xcw"
name="GroupHeader"
definition="Characteristics shared by all individual items included in the message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="GrpHdr"
complexType="_7l1ydjm6EeWDb47rJ6ki4Q" />
<messageBuildingBlock
xmi:id="_ioRR9dnQEeS--7IJLPC9lw"
nextVersions="_bf9R_22PEei3KuUgpx7Xcw"
name="RequestOrLetter"
definition="Supporting document request or letter details."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="ReqOrLttr"
complexType="_qW0AENnSEeS--7IJLPC9lw" />
<messageBuildingBlock
xmi:id="_rp31UdnQEeS--7IJLPC9lw"
nextVersions="_bf9SAW2PEei3KuUgpx7Xcw"
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="auth"
messageFunctionality="026"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.