AdditionalPaymentInformationV06

camt.028.001.06

Scope The AdditionalPaymentInformation message is sent by an account servicing institution to an account owner. This message is used to provide additional or corrected information on a payment instruction or statement entry, in order to allow reconciliation. Usage The AdditionalPaymentInformation message provides elements which are usually not reported in a statement or advice (for example full remittance information or identification of parties other than the account servicing institution and the account owner). It complements information about a payment instruction that has already been received, in the form of one or several entries of the original payment instruction. The AdditionalPaymentInformation message covers one and only one original payment instruction. If several payment instructions need further details, multiple AdditionalPaymentInformation messages must be used, one for each of the payment instructions. The AdditionalPaymentInformation message may be used as a result of two investigation processes and in a way outlined below.

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
%% AdditionalPaymentInformationV06 recursion level 0 with max 0
AdditionalPaymentInformationV06 *-- "1..1" CaseAssignment3 : Assignment
AdditionalPaymentInformationV06 *-- "1..1" Case3 : Case
AdditionalPaymentInformationV06 *-- "1..1" IUnderlyingTransaction2Choice : Underlying
AdditionalPaymentInformationV06 *-- "1..1" PaymentComplementaryInformation5 : Information
AdditionalPaymentInformationV06 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

Assignment building block

Identifies the assignment of an investigation case from an assigner to an assignee. Usage: The Assigner must be the sender of this confirmation and the Assignee must be the receiver. Represents the assignment of a case to a party. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CaseAssignment3 recursion level 0 with max 1
class CaseAssignment3{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
CaseAssignment3 *-- "1..1" IParty12Choice : Assigner
CaseAssignment3 *-- "1..1" IParty12Choice : Assignee
%% IParty12Choice recursion level 1 with max 1
%% IParty12Choice recursion level 1 with max 1
  

CaseAssignment3 members

Member name Description Data Type / Multiplicity
Identification Uniquely identifies the case assignment. IsoMax35Text - Required 1..1
Assigner Party who assigns the case. Usage: This is also the sender of the message.
Assignee Party to which the case is assigned. Usage: This is also the receiver of the message.
CreationDateTime Date and time at which the assignment was created. IsoISODateTime - Required 1..1

Case building block

Identifies the investigation case. Provides further details to identify an investigation case. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Case3 recursion level 0 with max 1
class Case3{
    Identification IsoMax35Text
    ReopenCaseIndication IsoYesNoIndicator
}
Case3 *-- "1..1" IParty12Choice : Creator
%% IParty12Choice recursion level 1 with max 1
  

Case3 members

Member name Description Data Type / Multiplicity
Identification Uniquely identifies the case. IsoMax35Text - Required 1..1
Creator Party that created the investigation case. IParty12Choice - Required 1..1
ReopenCaseIndication Indicates whether or not the case was previously closed and is now re-opened. IsoYesNoIndicator - Optional 0..1

Underlying building block

Identifies the underlying payment instruction. Specifies the details of the underlying transaction on which the investigation is processed. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IUnderlyingTransaction2Choice recursion level 0 with max 1
  

UnderlyingTransaction2Choice members

Member name Description Data Type / Multiplicity

Information building block

Additional information to the underlying payment instruction. Provides further additional details on the underlying payment instruction that cannot be transferred in a regular statement message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PaymentComplementaryInformation5 recursion level 0 with max 1
class PaymentComplementaryInformation5{
    InstructionIdentification IsoMax35Text
    EndToEndIdentification IsoMax35Text
    TransactionIdentification IsoMax35Text
    RequestedExecutionDate IsoISODate
    RequestedCollectionDate IsoISODate
    InterbankSettlementDate IsoISODate
    InterbankSettlementAmount IsoActiveOrHistoricCurrencyAndAmount
    ChargeBearer ChargeBearerType1Code
    InstructionForDebtorAgent IsoMax140Text
}
PaymentComplementaryInformation5 *-- "0..1" PaymentTypeInformation25 : PaymentTypeInformation
PaymentComplementaryInformation5 *-- "0..1" IAmountType4Choice : Amount
PaymentComplementaryInformation5 *-- "0..1" PartyIdentification43 : UltimateDebtor
PaymentComplementaryInformation5 *-- "0..1" PartyIdentification43 : Debtor
PaymentComplementaryInformation5 *-- "0..1" CashAccount24 : DebtorAccount
PaymentComplementaryInformation5 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : DebtorAgent
PaymentComplementaryInformation5 *-- "0..1" CashAccount24 : DebtorAgentAccount
PaymentComplementaryInformation5 *-- "0..1" SettlementInstruction4 : SettlementInformation
PaymentComplementaryInformation5 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : IntermediaryAgent1
PaymentComplementaryInformation5 *-- "0..1" CashAccount24 : IntermediaryAgent1Account
PaymentComplementaryInformation5 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : IntermediaryAgent2
PaymentComplementaryInformation5 *-- "0..1" CashAccount24 : IntermediaryAgent2Account
PaymentComplementaryInformation5 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : IntermediaryAgent3
PaymentComplementaryInformation5 *-- "0..1" CashAccount24 : IntermediaryAgent3Account
PaymentComplementaryInformation5 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : CreditorAgent
PaymentComplementaryInformation5 *-- "0..1" CashAccount24 : CreditorAgentAccount
PaymentComplementaryInformation5 *-- "0..1" PartyIdentification43 : Creditor
PaymentComplementaryInformation5 *-- "0..1" CashAccount24 : CreditorAccount
PaymentComplementaryInformation5 *-- "0..1" PartyIdentification43 : UltimateCreditor
PaymentComplementaryInformation5 *-- "0..1" IPurpose2Choice : Purpose
PaymentComplementaryInformation5 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : PreviousInstructingAgent
PaymentComplementaryInformation5 *-- "0..1" CashAccount24 : PreviousInstructingAgentAccount
PaymentComplementaryInformation5 *-- "0..0" InstructionForNextAgent1 : InstructionForNextAgent
PaymentComplementaryInformation5 *-- "0..0" InstructionForCreditorAgent1 : InstructionForCreditorAgent
PaymentComplementaryInformation5 *-- "0..1" RemittanceInformation11 : RemittanceInformation
%% PaymentTypeInformation25 recursion level 1 with max 1
class PaymentTypeInformation25{
    InstructionPriority Priority2Code
    ClearingChannel ClearingChannel2Code
    SequenceType SequenceType3Code
}
PaymentTypeInformation25 *-- "0..1" IServiceLevel8Choice : ServiceLevel
PaymentTypeInformation25 *-- "0..1" ILocalInstrument2Choice : LocalInstrument
PaymentTypeInformation25 *-- "0..1" ICategoryPurpose1Choice : CategoryPurpose
%% IAmountType4Choice 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
%% 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
%% CashAccount24 recursion level 1 with max 1
class CashAccount24{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount24 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount24 *-- "0..1" ICashAccountType2Choice : Type
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
%% CashAccount24 recursion level 1 with max 1
class CashAccount24{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount24 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount24 *-- "0..1" ICashAccountType2Choice : Type
%% SettlementInstruction4 recursion level 1 with max 1
class SettlementInstruction4{
    SettlementMethod SettlementMethod1Code
}
SettlementInstruction4 *-- "0..1" CashAccount24 : SettlementAccount
SettlementInstruction4 *-- "0..1" IClearingSystemIdentification3Choice : ClearingSystem
SettlementInstruction4 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : InstructingReimbursementAgent
SettlementInstruction4 *-- "0..1" CashAccount24 : InstructingReimbursementAgentAccount
SettlementInstruction4 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : InstructedReimbursementAgent
SettlementInstruction4 *-- "0..1" CashAccount24 : InstructedReimbursementAgentAccount
SettlementInstruction4 *-- "0..1" BranchAndFinancialInstitutionIdentification5 : ThirdReimbursementAgent
SettlementInstruction4 *-- "0..1" CashAccount24 : ThirdReimbursementAgentAccount
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
%% CashAccount24 recursion level 1 with max 1
class CashAccount24{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount24 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount24 *-- "0..1" ICashAccountType2Choice : Type
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
%% CashAccount24 recursion level 1 with max 1
class CashAccount24{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount24 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount24 *-- "0..1" ICashAccountType2Choice : Type
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
%% CashAccount24 recursion level 1 with max 1
class CashAccount24{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount24 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount24 *-- "0..1" ICashAccountType2Choice : Type
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
%% CashAccount24 recursion level 1 with max 1
class CashAccount24{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount24 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount24 *-- "0..1" ICashAccountType2Choice : Type
%% 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
%% CashAccount24 recursion level 1 with max 1
class CashAccount24{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount24 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount24 *-- "0..1" ICashAccountType2Choice : Type
%% 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
%% IPurpose2Choice recursion level 1 with max 1
%% BranchAndFinancialInstitutionIdentification5 recursion level 1 with max 1
BranchAndFinancialInstitutionIdentification5 *-- "1..1" FinancialInstitutionIdentification8 : FinancialInstitutionIdentification
BranchAndFinancialInstitutionIdentification5 *-- "0..1" BranchData2 : BranchIdentification
%% CashAccount24 recursion level 1 with max 1
class CashAccount24{
    Currency ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
CashAccount24 *-- "1..1" IAccountIdentification4Choice : Identification
CashAccount24 *-- "0..1" ICashAccountType2Choice : Type
%% InstructionForNextAgent1 recursion level 1 with max 1
class InstructionForNextAgent1{
    Code Instruction4Code
    InstructionInformation IsoMax140Text
}
%% InstructionForCreditorAgent1 recursion level 1 with max 1
class InstructionForCreditorAgent1{
    Code Instruction3Code
    InstructionInformation IsoMax140Text
}
%% RemittanceInformation11 recursion level 1 with max 1
class RemittanceInformation11{
    Unstructured IsoMax140Text
}
RemittanceInformation11 *-- "0..0" StructuredRemittanceInformation13 : Structured
  

PaymentComplementaryInformation5 members

Member name Description Data Type / Multiplicity
InstructionIdentification Unique identification, as assigned by an instructing party for an instructed party, to unambiguously identify the instruction.
EndToEndIdentification Unique identification, as assigned by the initiating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.
TransactionIdentification Unique identification, as assigned by the first instructing agent, to unambiguously identify the transaction that is passed on, unchanged, throughout the entire interbank chain. Usage: The transaction identification can be used for reconciliation, tracking or to link tasks relating to the transaction on the interbank level.
PaymentTypeInformation Set of elements used to further specify the type of transaction. PaymentTypeInformation25 - Optional 0..1
RequestedExecutionDate Date at which the initiating party requests the clearing agent to process the payment. Usage: This is the date on which the debtor’s account is to be debited. If payment by cheque, the date when the cheque must be generated by the bank.
RequestedCollectionDate Date and time at which the creditor requests that the amount of money is to be collected from the debtor. IsoISODate - Optional 0..1
InterbankSettlementDate Date on which the amount of money ceases to be available to the agent that owes it and when the amount of money becomes available to the agent to which it is due. IsoISODate - Optional 0..1
Amount Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. IAmountType4Choice - Optional 0..1
InterbankSettlementAmount Amount of money moved between the instructing agent and the instructed agent. IsoActiveOrHistoricCurrencyAndAmount - Optional 0..1
ChargeBearer Specifies which party/parties will bear the charges associated with the processing of the payment transaction. ChargeBearerType1Code - Optional 0..1
UltimateDebtor Ultimate party that owes an amount of money to the (ultimate) creditor. PartyIdentification43 - Optional 0..1
Debtor Party that owes an amount of money to the (ultimate) creditor. PartyIdentification43 - Optional 0..1
DebtorAccount Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction. CashAccount24 - Optional 0..1
DebtorAgent Financial institution servicing an account for the debtor. BranchAndFinancialInstitutionIdentification5 - Optional 0..1
DebtorAgentAccount Unambiguous identification of the account of the debtor agent at its servicing agent in the payment chain. CashAccount24 - Optional 0..1
SettlementInformation Instruction between two clearing agents stipulating the cash transfer characteristics between the two parties. SettlementInstruction4 - Optional 0..1
IntermediaryAgent1 Agent between the debtor’s agent and the creditor’s agent.
IntermediaryAgent1Account Unambiguous identification of the account of the intermediary agent 1 at its servicing agent in the payment chain. CashAccount24 - Optional 0..1
IntermediaryAgent2 Agent between the debtor’s agent and the creditor’s agent.
IntermediaryAgent2Account Unambiguous identification of the account of the intermediary agent 2 at its servicing agent in the payment chain. CashAccount24 - Optional 0..1
IntermediaryAgent3 Agent between the debtor’s agent and the creditor’s agent.
IntermediaryAgent3Account Unambiguous identification of the account of the intermediary agent 3 at its servicing agent in the payment chain. CashAccount24 - Optional 0..1
CreditorAgent Financial institution servicing an account for the creditor. BranchAndFinancialInstitutionIdentification5 - Optional 0..1
CreditorAgentAccount Unambiguous identification of the account of the creditor agent at its servicing agent to which a credit entry will be made as a result of the payment transaction. CashAccount24 - Optional 0..1
Creditor Party to which an amount of money is due. PartyIdentification43 - Optional 0..1
CreditorAccount Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction. CashAccount24 - Optional 0..1
UltimateCreditor Ultimate party to which an amount of money is due. PartyIdentification43 - Optional 0..1
Purpose Underlying reason for the payment transaction. Usage: Purpose is used by the end-customers, that is initiating party, (ultimate) debtor, (ultimate) creditor to provide information concerning the nature of the payment. Purpose is a content element, which is not used for processing by any of the agents involved in the payment chain.
InstructionForDebtorAgent Further information related to the processing of the payment instruction, provided by the initiating party, and intended for the debtor agent. IsoMax140Text - Optional 0..1
PreviousInstructingAgent Agent immediately prior to the instructing agent. BranchAndFinancialInstitutionIdentification5 - Optional 0..1
PreviousInstructingAgentAccount Unambiguous identification of the account of the previous instructing agent at its servicing agent in the payment chain. CashAccount24 - Optional 0..1
InstructionForNextAgent Further information related to the processing of the payment instruction that may need to be acted upon by the next agent.
InstructionForCreditorAgent Further information related to the processing of the payment instruction, provided by the initiating party, and intended for the creditor agent. InstructionForCreditorAgent1 - Unknown 0..0
RemittanceInformation Structured information that enables the matching, that is reconciliation, of a payment with the items that the payment is intended to settle, such as commercial invoices in an account receivable system. RemittanceInformation11 - Optional 0..1

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 AdditionalPaymentInformationV06 implementation follows a specific implementaiton pattern. First of all, AdditionalPaymentInformationV06 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AdditionalPaymentInformationV06Document implements IOuterDocument. Because AdditionalPaymentInformationV06 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AdditionalPaymentInformationV06.

classDiagram
    class IOuterRecord
    AdditionalPaymentInformationV06 --|> IOuterRecord : Implements
    AdditionalPaymentInformationV06Document --|> IOuterDocument~AdditionalPaymentInformationV06~ : Implements
    class IOuterDocument~AdditionalPaymentInformationV06~ {
        AdditionalPaymentInformationV06 Message
     }
  

Document wrapper for serialization

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

classDiagram
    AdditionalPaymentInformationV06Document *-- AdditionalPaymentInformationV06 : 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:camt.028.001.06">
    <AddtlPmtInf>
        <Assgnmt>
            <!-- Assignment inner content -->
        </Assgnmt>
        <Case>
            <!-- Case inner content -->
        </Case>
        <Undrlyg>
            <!-- Underlying inner content -->
        </Undrlyg>
        <Inf>
            <!-- Information inner content -->
        </Inf>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </AddtlPmtInf>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_KjcucTqxEeWZFYSPlduMhw"
  nextVersions="_xwzGIWXoEeap-P22vGV91g"
  previousVersion="_wQzacRPeEeSVo-TFVwFHvA"
  name="AdditionalPaymentInformationV06"
  definition="Scope&#xD;&#xA;The AdditionalPaymentInformation message is sent by an account servicing institution to an account owner.&#xD;&#xA;This message is used to provide additional or corrected information on a payment instruction or statement entry, in order to allow reconciliation.&#xD;&#xA;Usage&#xD;&#xA;The AdditionalPaymentInformation message provides elements which are usually not reported in a statement or advice (for example full remittance information or identification of parties other than the account servicing institution and the account owner). It complements information about a payment instruction that has already been received, in the form of one or several entries of the original payment instruction.&#xD;&#xA;The AdditionalPaymentInformation message covers one and only one original payment instruction. If several payment instructions need further details, multiple AdditionalPaymentInformation messages must be used, one for each of the payment instructions.&#xD;&#xA;The AdditionalPaymentInformation message may be used as a result of two investigation processes and in a way outlined below.&#xD;&#xA;- A ClaimNonReceipt workflow raised by the creditor or recipient of the payment: This means that the payment instruction has reached the creditor or beneficiary. The account owner needs further details or correct information for its reconciliation processes. The AdditionalPaymentInformation can be used to provide the missing information.&#xD;&#xA;- A RequestToModifyPayment workflow raised by the debtor or one of the intermediate agents upstream: When the payment instruction has reached its intended recipient and the modification does not affect the accounting at the account servicing institution, this AdditionalPaymentInformation message allows the account owner to receive further particulars or correct information about a payment instruction or an entry passed to its account.&#xD;&#xA;The AdditionalPayment Information message cannot be used to trigger a request for modification of a payment instruction activity. A RequestToModifyPayment message must be used. In other words, if a debtor or one of intermediate agent (excluding the account servicing institution of the creditor) realises the some information was missing in the original payment instruction, he should not use an AdditionalPaymentInformation but instead a RequestToModifyPayment message.&#xD;&#xA;It is assumed that when an account servicing institution sends out an AdditionalPaymentInformation message, the institution is fairly confident that this will resolve the case. Therefore it does not need to wait for a Resolution Of Investigation message. Neither does the account owner, or whoever receives the additional information, need to send back a ResolutionOfInvestigation message. Positive resolution in this case is implicit. Both parties are expected to close the case. In the event that the problem does not go away, a party can re-open the case."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="AddtlPmtInf"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_KjcuczqxEeWZFYSPlduMhw"
    nextVersions="_xwzGI2XoEeap-P22vGV91g"
    previousVersion="_wQzacxPeEeSVo-TFVwFHvA"
    name="Assignment"
    definition="Identifies the assignment of an investigation case from an assigner to an assignee.&#xA;Usage: The Assigner must be the sender of this confirmation and the Assignee must be the receiver."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Assgnmt"
    complexType="_sbKvolkyEeGeoaLUQk__nA_1583838951" />
  <messageBuildingBlock
    xmi:id="_KjcudTqxEeWZFYSPlduMhw"
    nextVersions="_xwzGJWXoEeap-P22vGV91g"
    previousVersion="_wQzadRPeEeSVo-TFVwFHvA"
    name="Case"
    definition="Identifies the investigation case."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Case"
    complexType="_tijOcFkyEeGeoaLUQk__nA_-1838378407" />
  <messageBuildingBlock
    xmi:id="_KjcudzqxEeWZFYSPlduMhw"
    nextVersions="_xwzGJ2XoEeap-P22vGV91g"
    previousVersion="_wQzadxPeEeSVo-TFVwFHvA"
    name="Underlying"
    definition="Identifies the underlying payment instruction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Undrlyg"
    complexType="_P3N9Vp9XEeGBX4a4yy-WHg_2030305441" />
  <messageBuildingBlock
    xmi:id="_KjcueTqxEeWZFYSPlduMhw"
    nextVersions="_xwzGKWXoEeap-P22vGV91g"
    previousVersion="_wQzaeRPeEeSVo-TFVwFHvA"
    name="Information"
    definition="Additional information to the underlying payment instruction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Inf"
    complexType="_ko_scTq3EeWZFYSPlduMhw" />
  <messageBuildingBlock
    xmi:id="_KjcuezqxEeWZFYSPlduMhw"
    nextVersions="_xwzGK2XoEeap-P22vGV91g"
    previousVersion="_wQzaexPeEeSVo-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="camt"
    messageFunctionality="028"
    flavour="001"
    version="06" />
</messageDefinition>

ISO Building Blocks

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