MandateAcceptanceReportV02

pain.012.001.02

Scope The MandateAcceptanceReport message is sent from the agent of the receiver (debtor or creditor) of the MandateRequest message (initiation, amendment or cancellation) to the agent of the initiator of the MandateRequest message (debtor or creditor). A MandateAcceptanceReport message is used to confirm the acceptance or rejection of a MandateRequest message. Where acceptance is part of the full process flow, a MandateRequest message only becomes valid after a confirmation of acceptance is received through a MandateAcceptanceReport message from the agent of the receiver. Usage The MandateAcceptanceReport message can contain only one confirmation of acceptance of rejection of one specific MandateRequest message. The messages can be exchanged between debtor agent and creditor agent and between debtor agent and debtor and creditor agent and creditor. The MandateAcceptanceReport message can be used in domestic and cross-border scenarios.

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
%% MandateAcceptanceReportV02 recursion level 0 with max 0
MandateAcceptanceReportV02 *-- "1..1" GroupHeader47 : GroupHeader
MandateAcceptanceReportV02 *-- "1..1" MandateAcceptance2 : UnderlyingAcceptanceDetails
MandateAcceptanceReportV02 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

GroupHeader building block

Set of characteristics to identify the message and parties playing a role in the mandate acceptance, but which are not part of the mandate. Set of characteristics shared by all individual transactions included in the message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% GroupHeader47 recursion level 0 with max 1
class GroupHeader47{
    MessageIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
}
GroupHeader47 *-- "0..2" IAuthorisation1Choice : Authorisation
GroupHeader47 *-- "0..1" PartyIdentification43 : InitiatingParty
GroupHeader47 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : InstructingAgent
GroupHeader47 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : InstructedAgent
%% IAuthorisation1Choice recursion level 1 with max 1
%% PartyIdentification43 recursion level 1 with max 1
class PartyIdentification43{
    Name IsoMax140Text
    CountryOfResidence CountryCode
}
PartyIdentification43 *-- "0..1" PostalAddress6 : PostalAddress
PartyIdentification43 *-- "0..1" IParty11Choice : Identification
PartyIdentification43 *-- "0..1" ContactDetails2 : ContactDetails
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
  

GroupHeader47 members

UnderlyingAcceptanceDetails building block

Set of elements used to provide information on the acception or rejection of the mandate request. Identifies the mandate, which is being accepted. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MandateAcceptance2 recursion level 0 with max 1
MandateAcceptance2 *-- "0..1" OriginalMessageInformation1 : OriginalMessageInformation
MandateAcceptance2 *-- "1..1" AcceptanceResult6 : AcceptanceResult
MandateAcceptance2 *-- "1..1" IOriginalMandate2Choice : OriginalMandate
%% OriginalMessageInformation1 recursion level 1 with max 1
class OriginalMessageInformation1{
    MessageIdentification IsoMax35Text
    MessageNameIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
}
%% AcceptanceResult6 recursion level 1 with max 1
class AcceptanceResult6{
    Accepted IsoYesNoIndicator
    AdditionalRejectReasonInformation IsoMax105Text
}
AcceptanceResult6 *-- "0..1" IMandateReason1Choice : RejectReason
%% IOriginalMandate2Choice recursion level 1 with max 1
  

MandateAcceptance2 members

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

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    MandateAcceptanceReportV02 --|> IOuterRecord : Implements
    MandateAcceptanceReportV02Document --|> IOuterDocument~MandateAcceptanceReportV02~ : Implements
    class IOuterDocument~MandateAcceptanceReportV02~ {
        MandateAcceptanceReportV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    MandateAcceptanceReportV02Document *-- MandateAcceptanceReportV02 : 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:pain.012.001.02">
    <MndtAccptncRpt>
        <GrpHdr>
            <!-- GroupHeader inner content -->
        </GrpHdr>
        <UndrlygAccptncDtls>
            <!-- UnderlyingAcceptanceDetails inner content -->
        </UndrlygAccptncDtls>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </MndtAccptncRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_rwGZYFkyEeGeoaLUQk__nA_1820631680"
  nextVersions="_CAyuQSGnEeKjd4jizyIDGA"
  previousVersion="_GX7CUtEvEd-BzquC8wXy7w_2092980503"
  name="MandateAcceptanceReportV02"
  definition="Scope&#xD;&#xA;The MandateAcceptanceReport message is sent from the agent of the receiver (debtor or creditor) of the MandateRequest message (initiation, amendment or cancellation) to the agent of the initiator of the MandateRequest message (debtor or creditor).&#xD;&#xA;A MandateAcceptanceReport message is used to confirm the acceptance or rejection of a MandateRequest message. Where acceptance is part of the full process flow, a MandateRequest message only becomes valid after a confirmation of acceptance is received through a MandateAcceptanceReport message from the agent of the receiver.&#xD;&#xA;Usage&#xD;&#xA;The MandateAcceptanceReport message can contain only one confirmation of acceptance of rejection of one specific MandateRequest message.&#xD;&#xA;The messages can be exchanged between debtor agent and creditor agent and between debtor agent and debtor and creditor agent and creditor.&#xD;&#xA;The MandateAcceptanceReport message can be used in domestic and cross-border scenarios."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="MndtAccptncRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_rwZUUFkyEeGeoaLUQk__nA_136321228"
    name="GroupHeader"
    definition="Set of characteristics to identify the message and parties playing a role in the mandate acceptance, but which are not part of the mandate."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="GrpHdr"
    complexType="_s3oCIFkyEeGeoaLUQk__nA_-839305610" />
  <messageBuildingBlock
    xmi:id="_rwjFUFkyEeGeoaLUQk__nA_-746912059"
    name="UnderlyingAcceptanceDetails"
    definition="Set of elements used to provide information on the acception or rejection of the mandate request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="UndrlygAccptncDtls"
    complexType="_tlE-AFkyEeGeoaLUQk__nA_1609524877" />
  <messageBuildingBlock
    xmi:id="_rwjFUVkyEeGeoaLUQk__nA_-467468330"
    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="pain"
    messageFunctionality="012"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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