auth.024.001.02
The PaymentRegulatoryInformationNotification message is sent by the reporting party to the registration agent to provide details on the transaction, when a payment has to be recorded against the registered currency control contract.
In some cases, the registration agent may also sent this message to the reporting party.
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
%% PaymentRegulatoryInformationNotificationV02 recursion level 0 with max 0
PaymentRegulatoryInformationNotificationV02 *-- "1..1" CurrencyControlHeader5 : GroupHeader
PaymentRegulatoryInformationNotificationV02 *-- "1..1" RegulatoryReportingNotification2 : TransactionNotification
PaymentRegulatoryInformationNotificationV02 *-- "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
%% CurrencyControlHeader5 recursion level 0 with max 1
class CurrencyControlHeader5{
MessageIdentification IsoMax35Text
CreationDateTime IsoISODateTime
NumberOfItems IsoMax15NumericText
}
CurrencyControlHeader5 *-- "1..1" IParty40Choice : InitiatingParty
CurrencyControlHeader5 *-- "0..1" BranchAndFinancialInstitutionIdentification6 : ForwardingAgent
%% IParty40Choice recursion level 1 with max 1
%% BranchAndFinancialInstitutionIdentification6 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification6 *-- "1..1" FinancialInstitutionIdentification18 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification6 *-- "0..1" BranchData3 : BranchIdentification
CurrencyControlHeader5 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. | IParty40Choice - Required 1..1 |
| ForwardingAgent | Agent which forwards the message. | BranchAndFinancialInstitutionIdentification6 - Optional 0..1 |
TransactionNotification building block
Notification of information related to a regulatory reporting on a payment. Provides details on the regulatory notification. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% RegulatoryReportingNotification2 recursion level 0 with max 1
class RegulatoryReportingNotification2{
TransactionNotificationIdentification IsoMax35Text
}
RegulatoryReportingNotification2 *-- "1..1" PartyIdentification135 : AccountOwner
RegulatoryReportingNotification2 *-- "1..1" BranchAndFinancialInstitutionIdentification6 : AccountServicer
RegulatoryReportingNotification2 *-- "1..0" TransactionCertificate3 : TransactionCertificate
%% PartyIdentification135 recursion level 1 with max 1
class PartyIdentification135{
Name IsoMax140Text
CountryOfResidence CountryCode
}
PartyIdentification135 *-- "0..1" PostalAddress24 : PostalAddress
PartyIdentification135 *-- "0..1" IParty38Choice : Identification
PartyIdentification135 *-- "0..1" Contact4 : ContactDetails
%% BranchAndFinancialInstitutionIdentification6 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification6 *-- "1..1" FinancialInstitutionIdentification18 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification6 *-- "0..1" BranchData3 : BranchIdentification
%% TransactionCertificate3 recursion level 1 with max 1
class TransactionCertificate3{
TransactionIdentification IsoMax35Text
BankAccountDomiciliationCountry CountryCode
}
TransactionCertificate3 *-- "1..1" DocumentIdentification28 : Certificate
TransactionCertificate3 *-- "0..1" CashAccount38 : Account
TransactionCertificate3 *-- "0..1" DocumentAmendment1 : Amendment
TransactionCertificate3 *-- "1..0" TransactionCertificateRecord1 : CertificateRecord
TransactionCertificate3 *-- "0..0" SupplementaryData1 : SupplementaryData
RegulatoryReportingNotification2 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| TransactionNotificationIdentification | Unique and unambiguous identification of the transaction notification. | IsoMax35Text - Required 1..1 |
| AccountOwner | Party that legally owns the cash account. | PartyIdentification135 - Required 1..1 |
| AccountServicer | Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account. | BranchAndFinancialInstitutionIdentification6 - Required 1..1 |
| TransactionCertificate | Certificate against which all currency control transactions are registered. | TransactionCertificate3 - Unknown 1..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 PaymentRegulatoryInformationNotificationV02 implementation follows a specific implementaiton pattern. First of all, PaymentRegulatoryInformationNotificationV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, PaymentRegulatoryInformationNotificationV02Document implements IOuterDocument. Because PaymentRegulatoryInformationNotificationV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type PaymentRegulatoryInformationNotificationV02.
classDiagram
class IOuterRecord
PaymentRegulatoryInformationNotificationV02 --|> IOuterRecord : Implements
PaymentRegulatoryInformationNotificationV02Document --|> IOuterDocument~PaymentRegulatoryInformationNotificationV02~ : Implements
class IOuterDocument~PaymentRegulatoryInformationNotificationV02~ {
PaymentRegulatoryInformationNotificationV02 Message
}
Document wrapper for serialization
The only real purpose PaymentRegulatoryInformationNotificationV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:auth.024.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using PaymentRegulatoryInformationNotificationV02.ToDocument() method. The returned PaymentRegulatoryInformationNotificationV02Document value will serialize correctly according to ISO 20022 standards.
classDiagram
PaymentRegulatoryInformationNotificationV02Document *-- PaymentRegulatoryInformationNotificationV02 : 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.024.001.02">
<PmtRgltryInfNtfctn>
<GrpHdr>
<!-- GroupHeader inner content -->
</GrpHdr>
<TxNtfctn>
<!-- TransactionNotification inner content -->
</TxNtfctn>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</PmtRgltryInfNtfctn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_bf9R622PEei3KuUgpx7Xcw"
nextVersions="_Nz8a0R3pEeuiRvbpCaJe6A"
previousVersion="_1xNvwNLgEeSdq5yU2aaSNw"
name="PaymentRegulatoryInformationNotificationV02"
definition="The PaymentRegulatoryInformationNotification message is sent by the reporting party to the registration agent to provide details on the transaction, when a payment has to be recorded against the registered currency control contract. 

In some cases, the registration agent may also sent this message to the reporting party."
registrationStatus="Registered"
messageSet="__ju0gDh7Eeqhm8z1jMmfeA"
xmlTag="PmtRgltryInfNtfctn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_bf9R7W2PEei3KuUgpx7Xcw"
nextVersions="_Nz8a0x3pEeuiRvbpCaJe6A"
previousVersion="_ChRFYNLiEeSdq5yU2aaSNw"
name="GroupHeader"
definition="Characteristics shared by all individual items included in the message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="GrpHdr"
complexType="_9DQf9W48EeiU9cctagi5ow" />
<messageBuildingBlock
xmi:id="_bf9R722PEei3KuUgpx7Xcw"
nextVersions="_Nz8a1R3pEeuiRvbpCaJe6A"
previousVersion="_GWJFMNLiEeSdq5yU2aaSNw"
name="TransactionNotification"
definition="Notification of information related to a regulatory reporting on a payment."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="TxNtfctn"
complexType="_NcmF5249EeiU9cctagi5ow" />
<messageBuildingBlock
xmi:id="_bf9R8W2PEei3KuUgpx7Xcw"
nextVersions="_Nz8a1x3pEeuiRvbpCaJe6A"
previousVersion="_HTtxodLrEeSDLevdaFPXHw"
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="024"
flavour="001"
version="02" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.