ReconciliationResponseV02

caad.006.001.02

The ReconciliationResponse message is sent by any party to any party (acquirer, agent or issuer) in response to a ReconciliationInitiation message.

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
%% ReconciliationResponseV02 recursion level 0 with max 0
ReconciliationResponseV02 *-- "1..1" Header39 : Header
ReconciliationResponseV02 *-- "1..1" ReconciliationResponse2 : Body
ReconciliationResponseV02 *-- "0..1" ContentInformationType20 : SecurityTrailer
  

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

Header building block

Information related to the management of the protocol. Set of characteristics related to the protocol.

For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Header39 recursion level 0 with max 1
class Header39{
    MessageFunction MessageFunction17Code
    ProtocolVersion IsoMax2048Text
    ExchangeIdentification IsoMax35Text
    ReTransmissionCounter IsoMax3NumericText
    CreationDateTime IsoISODateTime
}
Header39 *-- "0..1" BatchManagementInformation1 : BatchManagementInformation
Header39 *-- "1..1" GenericIdentification172 : InitiatingParty
Header39 *-- "0..1" GenericIdentification172 : RecipientParty
Header39 *-- "0..0" AdditionalData1 : TraceData
Header39 *-- "0..0" Traceability7 : Traceability
%% BatchManagementInformation1 recursion level 1 with max 1
class BatchManagementInformation1{
    CollectionIdentification IsoMax35Text
    BatchIdentification IsoMax35Text
    MessageSequenceNumber IsoMax15NumericText
    MessageChecksumInputValue IsoMax140Binary
}
%% GenericIdentification172 recursion level 1 with max 1
class GenericIdentification172{
    Identification IsoMax35Text
    Type PartyType17Code
    OtherType IsoMax35Text
    Assigner PartyType18Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% GenericIdentification172 recursion level 1 with max 1
class GenericIdentification172{
    Identification IsoMax35Text
    Type PartyType17Code
    OtherType IsoMax35Text
    Assigner PartyType18Code
    Country IsoMin2Max3AlphaText
    ShortName IsoMax35Text
}
%% AdditionalData1 recursion level 1 with max 1
class AdditionalData1{
    Type IsoMax35Text
    Value IsoMax2048Text
}
%% Traceability7 recursion level 1 with max 1
class Traceability7{
    TraceDateTimeIn IsoISODateTime
    TraceDateTimeOut IsoISODateTime
}
Traceability7 *-- "1..1" GenericIdentification172 : RelayIdentification
  

Header39 members

Body building block

Information related to the reconciliation response. Information related to the reconciliation response message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ReconciliationResponse2 recursion level 0 with max 1
ReconciliationResponse2 *-- "1..1" Environment3 : Environment
ReconciliationResponse2 *-- "0..1" Context8 : Context
ReconciliationResponse2 *-- "1..1" Transaction94 : Transaction
ReconciliationResponse2 *-- "1..1" ProcessingResult4 : ProcessingResult
ReconciliationResponse2 *-- "0..0" ProtectedData1 : ProtectedData
ReconciliationResponse2 *-- "0..0" SupplementaryData1 : SupplementaryData
%% Environment3 recursion level 1 with max 1
Environment3 *-- "0..1" PartyIdentification197 : Originator
Environment3 *-- "0..1" PartyIdentification197 : Sender
Environment3 *-- "0..1" PartyIdentification197 : Receiver
Environment3 *-- "0..1" PartyIdentification197 : Destination
%% Context8 recursion level 1 with max 1
Context8 *-- "0..1" TransactionContext5 : TransactionContext
%% Transaction94 recursion level 1 with max 1
class Transaction94{
    ReconciliationFunction ReconciliationFunction1Code
    ReconciliationType CardServiceType4Code
    OtherReconciliationType IsoMax35Text
    RequestedCurrency IsoExact3NumericText
}
Transaction94 *-- "0..1" TransactionIdentification12 : TransactionIdentification
Transaction94 *-- "0..0" TransactionTotals11 : ReconciliationTotals
Transaction94 *-- "0..0" AdditionalFee1 : AdditionalFees
Transaction94 *-- "0..0" AdditionalData1 : AdditionalData
%% ProcessingResult4 recursion level 1 with max 1
ProcessingResult4 *-- "0..1" ResultData5 : ResultData
ProcessingResult4 *-- "0..1" ResultData1 : OriginalResultData
ProcessingResult4 *-- "0..0" AdditionalInformation22 : AdditionalInformation
%% ProtectedData1 recursion level 1 with max 1
class ProtectedData1{
    ContentType ContentType3Code
}
ProtectedData1 *-- "0..1" EnvelopedData6 : EnvelopedData
ProtectedData1 *-- "0..1" EncryptedData1 : EncryptedData
%% SupplementaryData1 recursion level 1 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
  

ReconciliationResponse2 members

SecurityTrailer building block

Trailer of the message containing a MAC General cryptographic message syntax (CMS) containing encrypted data. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ContentInformationType20 recursion level 0 with max 1
class ContentInformationType20{
    MAC IsoMax8HexBinaryText
}
ContentInformationType20 *-- "1..1" MACData1 : MACData
%% MACData1 recursion level 1 with max 1
class MACData1{
    Control IsoExact1HexBinaryText
    KeySetIdentifier IsoMax8NumericText
    DerivedInformation IsoMax32HexBinaryText
    Algorithm IsoMax2NumericText
    KeyLength IsoMax4NumericText
    KeyProtection IsoMax2NumericText
    KeyIndex IsoMax5NumericText
    PaddingMethod IsoMax2NumericText
    InitialisationVector IsoMax32HexBinaryText
}
  

ContentInformationType20 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    ReconciliationResponseV02 --|> IOuterRecord : Implements
    ReconciliationResponseV02Document --|> IOuterDocument~ReconciliationResponseV02~ : Implements
    class IOuterDocument~ReconciliationResponseV02~ {
        ReconciliationResponseV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    ReconciliationResponseV02Document *-- ReconciliationResponseV02 : 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:caad.006.001.02">
    <RcncltnRspn>
        <Hdr>
            <!-- Header inner content -->
        </Hdr>
        <Body>
            <!-- Body inner content -->
        </Body>
        <SctyTrlr>
            <!-- SecurityTrailer inner content -->
        </SctyTrlr>
    </RcncltnRspn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_7OfdhVUHEeetiruPyDPo0Q"
  nextVersions="_CFmNIYv_EeuC5632vxUfGg"
  previousVersion="_A6xeEHvBEeSLmfFG0DG7zQ"
  name="ReconciliationResponseV02"
  definition="The ReconciliationResponse message is sent by any party to any party (acquirer, agent or issuer) in response to a ReconciliationInitiation message."
  registrationStatus="Registered"
  messageSet="_oFVkcKmaEeqA4rV5xCgycA"
  xmlTag="RcncltnRspn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_7OfdhlUHEeetiruPyDPo0Q"
    nextVersions="_CFmNI4v_EeuC5632vxUfGg"
    name="Header"
    definition="Information related to the management of the protocol."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Hdr"
    complexType="_4s6-AVA4EeedyPuM0kK2EQ" />
  <messageBuildingBlock
    xmi:id="_7Ofdh1UHEeetiruPyDPo0Q"
    nextVersions="_CFmNJYv_EeuC5632vxUfGg"
    name="Body"
    definition="Information related to the reconciliation response."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Body"
    complexType="_PWuXEVUIEeetiruPyDPo0Q" />
  <messageBuildingBlock
    xmi:id="_7OfdiFUHEeetiruPyDPo0Q"
    nextVersions="_CFmNJ4v_EeuC5632vxUfGg"
    name="SecurityTrailer"
    definition="Trailer of the message containing a MAC"
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SctyTrlr"
    complexType="_fP-osaQuEeeWXKXf3KjtmQ" />
  <messageDefinitionIdentifier
    businessArea="caad"
    messageFunctionality="006"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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