pain.012.001.05
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 one or more confirmation(s) of acceptance or rejection of a specific Mandate Request. 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
%% MandateAcceptanceReportV05 recursion level 0 with max 0
MandateAcceptanceReportV05 *-- "1..1" GroupHeader47 : GroupHeader
MandateAcceptanceReportV05 *-- "1..1" MandateAcceptance5 : UnderlyingAcceptanceDetails
MandateAcceptanceReportV05 *-- "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
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MessageIdentification | Point to point reference, as assigned by the instructing party, and sent to the instructed party, 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 |
| Authorisation | User identification or any user key to be used to check the authority of the initiating party. | |
| InitiatingParty | Party that initiates the mandate message. | PartyIdentification43 - Optional 0..1 |
| InstructingAgent | Agent that instructs the next party in the chain to carry out an instruction. | |
| InstructedAgent | Agent that is instructed by the previous party in the chain to carry out an instruction. |
UnderlyingAcceptanceDetails building block
Provides information on the acceptance or rejection of the mandate request. Identifies the mandate, which is being accepted. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MandateAcceptance5 recursion level 0 with max 1
MandateAcceptance5 *-- "0..1" OriginalMessageInformation1 : OriginalMessageInformation
MandateAcceptance5 *-- "1..1" AcceptanceResult6 : AcceptanceResult
MandateAcceptance5 *-- "0..1" IOriginalMandate5Choice : OriginalMandate
MandateAcceptance5 *-- "0..0" SupplementaryData1 : SupplementaryData
%% 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
%% IOriginalMandate5Choice recursion level 1 with max 1
%% SupplementaryData1 recursion level 1 with max 1
class SupplementaryData1{
PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
MandateAcceptance5 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| OriginalMessageInformation | Provides information on the original message. | OriginalMessageInformation1 - Optional 0..1 |
| AcceptanceResult | Provides detailed information on the acceptance result. | AcceptanceResult6 - Required 1..1 |
| OriginalMandate | Provides the original mandate data. | IOriginalMandate5Choice - Optional 0..1 |
| 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 MandateAcceptanceReportV05 implementation follows a specific implementaiton pattern. First of all, MandateAcceptanceReportV05 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MandateAcceptanceReportV05Document implements IOuterDocument. Because MandateAcceptanceReportV05 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MandateAcceptanceReportV05.
classDiagram
class IOuterRecord
MandateAcceptanceReportV05 --|> IOuterRecord : Implements
MandateAcceptanceReportV05Document --|> IOuterDocument~MandateAcceptanceReportV05~ : Implements
class IOuterDocument~MandateAcceptanceReportV05~ {
MandateAcceptanceReportV05 Message
}
Document wrapper for serialization
The only real purpose MandateAcceptanceReportV05Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:pain.012.001.05’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MandateAcceptanceReportV05.ToDocument() method. The returned MandateAcceptanceReportV05Document value will serialize correctly according to ISO 20022 standards.
classDiagram
MandateAcceptanceReportV05Document *-- MandateAcceptanceReportV05 : 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.05">
<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="_as1iAUjuEeaVLL5QKJ4f-A"
nextVersions="_bf9SMW2PEei3KuUgpx7Xcw"
previousVersion="_Ie2IQRPeEeSVo-TFVwFHvA"
name="MandateAcceptanceReportV05"
definition="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 one or more confirmation(s) of acceptance or rejection of a specific Mandate Request.
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."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="MndtAccptncRpt"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<constraint
xmi:id="_as1iA0juEeaVLL5QKJ4f-A"
nextVersions="_bf9SM22PEei3KuUgpx7Xcw"
previousVersion="_Ie2IQxPeEeSVo-TFVwFHvA"
name="SupplementaryDataRule"
definition="The SupplementaryData building block at message level must not be used to provide additional information about a transaction. The SupplementaryData element at transaction level should be used for that purpose."
registrationStatus="Provisionally Registered" />
<messageBuildingBlock
xmi:id="_as1iBUjuEeaVLL5QKJ4f-A"
nextVersions="_bf9SNW2PEei3KuUgpx7Xcw"
previousVersion="_Ie2IRRPeEeSVo-TFVwFHvA"
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="_as1iB0juEeaVLL5QKJ4f-A"
nextVersions="_bf9SN22PEei3KuUgpx7Xcw"
previousVersion="_Ie2IRxPeEeSVo-TFVwFHvA"
name="UnderlyingAcceptanceDetails"
definition="Provides information on the acceptance or rejection of the mandate request."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="UndrlygAccptncDtls"
complexType="_dJ36S0jwEeaVLL5QKJ4f-A" />
<messageBuildingBlock
xmi:id="_as1iCUjuEeaVLL5QKJ4f-A"
nextVersions="_bf9SOW2PEei3KuUgpx7Xcw"
previousVersion="_Ie2ISRPeEeSVo-TFVwFHvA"
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="05" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.