CreditorPaymentActivationRequestStatusReportV05

pain.014.001.05

The CreditorPaymentActivationRequestStatusReport message is sent by a party to the next party in the creditor payment activation request chain. It is used to inform the latter about the positive or negative status of a creditor payment activation request (either single or file).

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
%% CreditorPaymentActivationRequestStatusReportV05 recursion level 0 with max 0
CreditorPaymentActivationRequestStatusReportV05 *-- "1..1" GroupHeader46 : GroupHeader
CreditorPaymentActivationRequestStatusReportV05 *-- "1..1" OriginalGroupInformation25 : OriginalGroupInformationAndStatus
CreditorPaymentActivationRequestStatusReportV05 *-- "0..1" OriginalPaymentInstruction19 : OriginalPaymentInformationAndStatus
CreditorPaymentActivationRequestStatusReportV05 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

GroupHeader building block

Set of characteristics shared by all individual transactions included in the message. Set of characteristics shared by all individual transactions included in the message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% GroupHeader46 recursion level 0 with max 1
class GroupHeader46{
    MessageIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
}
GroupHeader46 *-- "1..1" PartyIdentification43 : InitiatingParty
GroupHeader46 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : DebtorAgent
GroupHeader46 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : CreditorAgent
%% 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
  

GroupHeader46 members

Member name Description Data Type / Multiplicity
MessageIdentification Point to point reference assigned by the instructing party and sent to the next party in the chain to unambiguously identify the message.
CreationDateTime Date and time at which the status report was created by the instructing party. IsoISODateTime - Required 1..1
InitiatingParty Party initiating the creditor payment activation request. This can either be the creditor himself or the party that initiates the request on behalf of the creditor. PartyIdentification43 - Required 1..1
DebtorAgent Financial institution servicing an account for the debtor. BranchAndFinancialInstitutionIdentification5 - Optional 0..1
CreditorAgent Financial institution servicing an account for the creditor. BranchAndFinancialInstitutionIdentification5 - Optional 0..1

OriginalGroupInformationAndStatus building block

Original group information concerning the group of transactions, to which the status report message refers to. Set of elements used to provide information on the original group, to which the message refers. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% OriginalGroupInformation25 recursion level 0 with max 1
class OriginalGroupInformation25{
    OriginalMessageIdentification IsoMax35Text
    OriginalMessageNameIdentification IsoMax35Text
    OriginalCreationDateTime IsoISODateTime
    OriginalNumberOfTransactions IsoMax15NumericText
    OriginalControlSum IsoDecimalNumber
    GroupStatus TransactionGroupStatus3Code
}
OriginalGroupInformation25 *-- "0..0" StatusReasonInformation9 : StatusReasonInformation
OriginalGroupInformation25 *-- "0..0" NumberOfTransactionsPerStatus3 : NumberOfTransactionsPerStatus
%% StatusReasonInformation9 recursion level 1 with max 1
class StatusReasonInformation9{
    AdditionalInformation IsoMax105Text
}
StatusReasonInformation9 *-- "0..1" PartyIdentification43 : Originator
StatusReasonInformation9 *-- "0..1" IStatusReason6Choice : Reason
%% NumberOfTransactionsPerStatus3 recursion level 1 with max 1
class NumberOfTransactionsPerStatus3{
    DetailedNumberOfTransactions IsoMax15NumericText
    DetailedStatus TransactionIndividualStatus3Code
    DetailedControlSum IsoDecimalNumber
}
  

OriginalGroupInformation25 members

Member name Description Data Type / Multiplicity
OriginalMessageIdentification Point to point reference, as assigned by the original instructing party, to unambiguously identify the original message. IsoMax35Text - Required 1..1
OriginalMessageNameIdentification Specifies the original message name identifier to which the message refers. IsoMax35Text - Required 1..1
OriginalCreationDateTime Date and time at which the original message was created. IsoISODateTime - Optional 0..1
OriginalNumberOfTransactions Number of individual transactions contained in the original message. IsoMax15NumericText - Optional 0..1
OriginalControlSum Total of all individual amounts included in the original message, irrespective of currencies. IsoDecimalNumber - Optional 0..1
GroupStatus Specifies the status of a group of transactions. TransactionGroupStatus3Code - Optional 0..1
StatusReasonInformation Set of elements used to provide detailed information on the status reason. StatusReasonInformation9 - Unknown 0..0
NumberOfTransactionsPerStatus Detailed information on the number of transactions for each identical transaction status. NumberOfTransactionsPerStatus3 - Unknown 0..0

OriginalPaymentInformationAndStatus building block

Information concerning the original payment information, to which the status report message refers. Provides details on the original transactions, to which the status report message refers. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% OriginalPaymentInstruction19 recursion level 0 with max 1
class OriginalPaymentInstruction19{
    OriginalPaymentInformationIdentification IsoMax35Text
    OriginalNumberOfTransactions IsoMax15NumericText
    OriginalControlSum IsoDecimalNumber
    PaymentInformationStatus TransactionGroupStatus3Code
}
OriginalPaymentInstruction19 *-- "0..0" StatusReasonInformation9 : StatusReasonInformation
OriginalPaymentInstruction19 *-- "0..0" NumberOfTransactionsPerStatus3 : NumberOfTransactionsPerStatus
OriginalPaymentInstruction19 *-- "0..0" PaymentTransaction69 : TransactionInformationAndStatus
%% StatusReasonInformation9 recursion level 1 with max 1
class StatusReasonInformation9{
    AdditionalInformation IsoMax105Text
}
StatusReasonInformation9 *-- "0..1" PartyIdentification43 : Originator
StatusReasonInformation9 *-- "0..1" IStatusReason6Choice : Reason
%% NumberOfTransactionsPerStatus3 recursion level 1 with max 1
class NumberOfTransactionsPerStatus3{
    DetailedNumberOfTransactions IsoMax15NumericText
    DetailedStatus TransactionIndividualStatus3Code
    DetailedControlSum IsoDecimalNumber
}
%% PaymentTransaction69 recursion level 1 with max 1
class PaymentTransaction69{
    StatusIdentification IsoMax35Text
    OriginalInstructionIdentification IsoMax35Text
    OriginalEndToEndIdentification IsoMax35Text
    TransactionStatus TransactionIndividualStatus3Code
    AcceptanceDateTime IsoISODateTime
    AccountServicerReference IsoMax35Text
    ClearingSystemReference IsoMax35Text
}
PaymentTransaction69 *-- "0..0" StatusReasonInformation9 : StatusReasonInformation
PaymentTransaction69 *-- "0..0" Charges2 : ChargesInformation
PaymentTransaction69 *-- "0..1" OriginalTransactionReference23 : OriginalTransactionReference
PaymentTransaction69 *-- "0..0" SupplementaryData1 : SupplementaryData
  

OriginalPaymentInstruction19 members

Member name Description Data Type / Multiplicity
OriginalPaymentInformationIdentification Unique identification, as assigned by the original sending party, to unambiguously identify the original payment information group. IsoMax35Text - Required 1..1
OriginalNumberOfTransactions Number of individual transactions contained in the original payment information group. IsoMax15NumericText - Optional 0..1
OriginalControlSum Total of all individual amounts included in the original payment information group, irrespective of currencies. IsoDecimalNumber - Optional 0..1
PaymentInformationStatus Specifies the status of the payment information group. TransactionGroupStatus3Code - Optional 0..1
StatusReasonInformation Provides detailed information on the status reason. StatusReasonInformation9 - Unknown 0..0
NumberOfTransactionsPerStatus Detailed information on the number of transactions for each identical transaction status. NumberOfTransactionsPerStatus3 - Unknown 0..0
TransactionInformationAndStatus Provides information on the original transactions to which the status report message refers. PaymentTransaction69 - 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 CreditorPaymentActivationRequestStatusReportV05 implementation follows a specific implementaiton pattern. First of all, CreditorPaymentActivationRequestStatusReportV05 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, CreditorPaymentActivationRequestStatusReportV05Document implements IOuterDocument. Because CreditorPaymentActivationRequestStatusReportV05 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type CreditorPaymentActivationRequestStatusReportV05.

classDiagram
    class IOuterRecord
    CreditorPaymentActivationRequestStatusReportV05 --|> IOuterRecord : Implements
    CreditorPaymentActivationRequestStatusReportV05Document --|> IOuterDocument~CreditorPaymentActivationRequestStatusReportV05~ : Implements
    class IOuterDocument~CreditorPaymentActivationRequestStatusReportV05~ {
        CreditorPaymentActivationRequestStatusReportV05 Message
     }
  

Document wrapper for serialization

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

classDiagram
    CreditorPaymentActivationRequestStatusReportV05Document *-- CreditorPaymentActivationRequestStatusReportV05 : 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.014.001.05">
    <CdtrPmtActvtnReqStsRpt>
        <GrpHdr>
            <!-- GroupHeader inner content -->
        </GrpHdr>
        <OrgnlGrpInfAndSts>
            <!-- OriginalGroupInformationAndStatus inner content -->
        </OrgnlGrpInfAndSts>
        <OrgnlPmtInfAndSts>
            <!-- OriginalPaymentInformationAndStatus inner content -->
        </OrgnlPmtInfAndSts>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </CdtrPmtActvtnReqStsRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_gO7AUYIWEeWs6fzahhkJjg"
  nextVersions="_8mXpEZRtEeazAtAtDSg0Nw"
  previousVersion="__PZbAU_GEeSNduMozFyRUg"
  name="CreditorPaymentActivationRequestStatusReportV05"
  definition="The CreditorPaymentActivationRequestStatusReport message is sent by a party to the next party in the creditor payment activation request chain. It is used to inform the latter about the positive or negative status of a creditor payment activation request (either single or file)."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="CdtrPmtActvtnReqStsRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_gO7AU4IWEeWs6fzahhkJjg"
    nextVersions="_8mXpE5RtEeazAtAtDSg0Nw"
    previousVersion="__PZbA0_GEeSNduMozFyRUg"
    name="GroupAndTransactionStatus1Rule"
    definition="If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to ACTC, ACCP, ACSP or ACSC, ACCR or ACWC, then TransactionInformationAndStatus/TransactionStatus must be different from RJCT."
    registrationStatus="Provisionally Registered" />
  <constraint
    xmi:id="_gO7AVYIWEeWs6fzahhkJjg"
    nextVersions="_8mXpFZRtEeazAtAtDSg0Nw"
    previousVersion="__PZbBU_GEeSNduMozFyRUg"
    name="GroupAndTransactionStatus2Rule"
    definition="If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to PDNG, then TransactionInformationAndStatus/TransactionStatus must be different from RJCT."
    registrationStatus="Provisionally Registered" />
  <constraint
    xmi:id="_gO7AV4IWEeWs6fzahhkJjg"
    nextVersions="_8mXpF5RtEeazAtAtDSg0Nw"
    previousVersion="__PZbB0_GEeSNduMozFyRUg"
    name="GroupAndTransactionStatus3Rule"
    definition="If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to RJCT, then TransactionInformationAndStatus/TransactionStatus must be different from ACTC, ACCP, ACSP, ACSC, ACCR, ACWC or PDNG."
    registrationStatus="Provisionally Registered" />
  <constraint
    xmi:id="_gO7AWYIWEeWs6fzahhkJjg"
    nextVersions="_8mXpGZRtEeazAtAtDSg0Nw"
    previousVersion="__PZbCU_GEeSNduMozFyRUg"
    name="GroupAndTransactionStatus4Rule"
    definition="If OriginalGroupInformationAndStatus/GroupStatus is present and is equal to RCVD, then TransactionInformationAndStatus/TransactionStatus is not allowed."
    registrationStatus="Provisionally Registered" />
  <constraint
    xmi:id="_gO7AW4IWEeWs6fzahhkJjg"
    nextVersions="_8mXpG5RtEeazAtAtDSg0Nw"
    previousVersion="__PZbC0_GEeSNduMozFyRUg"
    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="_gO7AXYIWEeWs6fzahhkJjg"
    nextVersions="_8mXpHZRtEeazAtAtDSg0Nw"
    previousVersion="__PZbDU_GEeSNduMozFyRUg"
    name="GroupHeader"
    definition="Set of characteristics shared by all individual transactions included in the message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="GrpHdr"
    complexType="_UQlCcdp-Ed-ak6NoX_4Aeg_-1988631022" />
  <messageBuildingBlock
    xmi:id="_gO7AX4IWEeWs6fzahhkJjg"
    nextVersions="_8mXpH5RtEeazAtAtDSg0Nw"
    previousVersion="__PZbD0_GEeSNduMozFyRUg"
    name="OriginalGroupInformationAndStatus"
    definition="Original group information concerning the group of transactions, to which the status report message refers to."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="OrgnlGrpInfAndSts"
    complexType="_Pe9Ge9p-Ed-ak6NoX_4Aeg_-379878312" />
  <messageBuildingBlock
    xmi:id="_gO7AYYIWEeWs6fzahhkJjg"
    nextVersions="_8mXpIZRtEeazAtAtDSg0Nw"
    previousVersion="__PZbEU_GEeSNduMozFyRUg"
    name="OriginalPaymentInformationAndStatus"
    definition="Information concerning the original payment information, to which the status report message refers."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="OrgnlPmtInfAndSts"
    complexType="_wWBmwYIWEeWs6fzahhkJjg" />
  <messageBuildingBlock
    xmi:id="_gO7AY4IWEeWs6fzahhkJjg"
    nextVersions="_8mXpI5RtEeazAtAtDSg0Nw"
    previousVersion="__PZbE0_GEeSNduMozFyRUg"
    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="014"
    flavour="001"
    version="05" />
</messageDefinition>

ISO Building Blocks

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