pain.012.001.01
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
%% MandateAcceptanceReportV01 recursion level 0 with max 0
MandateAcceptanceReportV01 *-- "1..1" GroupHeader31 : GroupHeader
MandateAcceptanceReportV01 *-- "1..1" MandateAcceptance1 : UnderlyingAcceptanceDetails
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
%% GroupHeader31 recursion level 0 with max 1
class GroupHeader31{
MessageIdentification IsoMax35Text
CreationDateTime IsoISODateTime
}
GroupHeader31 *-- "0..2" IAuthorisation1Choice : Authorisation
GroupHeader31 *-- "0..1" PartyIdentification32 : InitiatingParty
GroupHeader31 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : InstructingAgent
GroupHeader31 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : InstructedAgent
%% IAuthorisation1Choice recursion level 1 with max 1
%% PartyIdentification32 recursion level 1 with max 1
class PartyIdentification32{
Name IsoMax140Text
CountryOfResidence CountryCode
}
PartyIdentification32 *-- "0..1" PostalAddress6 : PostalAddress
PartyIdentification32 *-- "0..1" IParty6Choice : Identification
PartyIdentification32 *-- "0..1" ContactDetails2 : ContactDetails
%% BranchAndFinancialInstitutionIdentification4 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification4 *-- "1..1" FinancialInstitutionIdentification7 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification4 *-- "0..1" BranchData2 : BranchIdentification
%% BranchAndFinancialInstitutionIdentification4 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification4 *-- "1..1" FinancialInstitutionIdentification7 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification4 *-- "0..1" BranchData2 : BranchIdentification
GroupHeader31 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. | PartyIdentification32 - 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
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
%% MandateAcceptance1 recursion level 0 with max 1
MandateAcceptance1 *-- "0..1" OriginalMessageInformation1 : OriginalMessageInformation
MandateAcceptance1 *-- "1..1" AcceptanceResult6 : AcceptanceResult
MandateAcceptance1 *-- "1..1" IOriginalMandate1Choice : 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
%% IOriginalMandate1Choice recursion level 1 with max 1
MandateAcceptance1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| OriginalMessageInformation | Set of elements used to provide information on the original messsage. | OriginalMessageInformation1 - Optional 0..1 |
| AcceptanceResult | Set of elements used to provide detailed information on the acceptance result. | AcceptanceResult6 - Required 1..1 |
| OriginalMandate | Set of elements used to provide the original mandate data. | IOriginalMandate1Choice - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the MandateAcceptanceReportV01 implementation follows a specific implementaiton pattern. First of all, MandateAcceptanceReportV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MandateAcceptanceReportV01Document implements IOuterDocument. Because MandateAcceptanceReportV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MandateAcceptanceReportV01.
classDiagram
class IOuterRecord
MandateAcceptanceReportV01 --|> IOuterRecord : Implements
MandateAcceptanceReportV01Document --|> IOuterDocument~MandateAcceptanceReportV01~ : Implements
class IOuterDocument~MandateAcceptanceReportV01~ {
MandateAcceptanceReportV01 Message
}
Document wrapper for serialization
The only real purpose MandateAcceptanceReportV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:pain.012.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MandateAcceptanceReportV01.ToDocument() method. The returned MandateAcceptanceReportV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram
MandateAcceptanceReportV01Document *-- MandateAcceptanceReportV01 : 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.01">
<MndtAccptncRpt>
<GrpHdr>
<!-- GroupHeader inner content -->
</GrpHdr>
<UndrlygAccptncDtls>
<!-- UnderlyingAcceptanceDetails inner content -->
</UndrlygAccptncDtls>
</MndtAccptncRpt>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_GX7CUtEvEd-BzquC8wXy7w_2092980503"
nextVersions="_rwGZYFkyEeGeoaLUQk__nA_1820631680"
name="MandateAcceptanceReportV01"
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 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."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="MndtAccptncRpt"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_GX7CU9EvEd-BzquC8wXy7w_-1730068754"
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="_PrK9iNp-Ed-ak6NoX_4Aeg_-727218247" />
<messageBuildingBlock
xmi:id="_GX7CVNEvEd-BzquC8wXy7w_1787356156"
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="_RBmk9tp-Ed-ak6NoX_4Aeg_-1832843790" />
<messageDefinitionIdentifier
businessArea="pain"
messageFunctionality="012"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.