camt.028.001.03
Scope The Additional Payment Information 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 Additional Payment Information 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 Additional Payment Information message covers one and only one original payment instruction. If several payment instructions need further details, multiple Additional Payment Information 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.
- A Claim Non Receipt 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 Additional Payment Information can be used to provide the missing information.
- A Request To Modify Payment 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 Additional Payment Information message allows the account owner to receive further particulars or correct information about a payment instruction or an entry passed to its account. The Additional Payment Information message cannot be used to trigger a request for modification of a payment instruction activity. A Request To Modify Payment 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 Additional Payment Information but instead a Request To Modify Payment message. It is assumed that when an account servicing institution sends out an Additional Payment Information 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 Resolution Of Investigation 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.
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 %% AdditionalPaymentInformationV03 recursion level 0 with max 0 AdditionalPaymentInformationV03 *-- "1..1" CaseAssignment2 : Assignment AdditionalPaymentInformationV03 *-- "1..1" Case2 : Case AdditionalPaymentInformationV03 *-- "1..1" IUnderlyingTransaction1Choice : Underlying AdditionalPaymentInformationV03 *-- "1..1" PaymentComplementaryInformation2 : Information
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. Set of elements used to represent the assignment of a case to a party. For comparison, see the ISO20022 official specification
classDiagram direction tb %% CaseAssignment2 recursion level 0 with max 1 class CaseAssignment2{ Identification IsoMax35Text CreationDateTime IsoISODateTime } CaseAssignment2 *-- "1..1" IParty7Choice : Assigner CaseAssignment2 *-- "1..1" IParty7Choice : Assignee %% IParty7Choice recursion level 1 with max 1 %% IParty7Choice recursion level 1 with max 1
CaseAssignment2 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. Set of elements used to identify a case. For comparison, see the ISO20022 official specification
classDiagram direction tb %% Case2 recursion level 0 with max 1 class Case2{ Identification IsoMax35Text ReopenCaseIndication IsoYesNoIndicator } Case2 *-- "1..1" IParty7Choice : Creator %% IParty7Choice recursion level 1 with max 1
Case2 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Identification | Uniquely identifies the case. | IsoMax35Text - Required 1..1 |
Creator | Party that created the investigation case. | IParty7Choice - 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 %% IUnderlyingTransaction1Choice recursion level 0 with max 1
UnderlyingTransaction1Choice members
Member name | Description | Data Type / Multiplicity |
---|
Information building block
Additional information to the underlying payment instruction. Set of elements used to provide additional information on the underlying payment instruction that cannot be transferred in a regular statement message. For comparison, see the ISO20022 official specification
classDiagram direction tb %% PaymentComplementaryInformation2 recursion level 0 with max 1 class PaymentComplementaryInformation2{ InstructionIdentification IsoMax35Text EndToEndIdentification IsoMax35Text TransactionIdentification IsoMax35Text RequestedExecutionDate IsoISODate RequestedCollectionDate IsoISODate InterbankSettlementDate IsoISODate InterbankSettlementAmount IsoActiveOrHistoricCurrencyAndAmount ChargeBearer ChargeBearerType1Code InstructionForDebtorAgent IsoMax140Text } PaymentComplementaryInformation2 *-- "0..1" PaymentTypeInformation22 : PaymentTypeInformation PaymentComplementaryInformation2 *-- "0..1" IAmountType3Choice : Amount PaymentComplementaryInformation2 *-- "0..1" PartyIdentification32 : UltimateDebtor PaymentComplementaryInformation2 *-- "0..1" PartyIdentification32 : Debtor PaymentComplementaryInformation2 *-- "0..1" CashAccount16 : DebtorAccount PaymentComplementaryInformation2 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : DebtorAgent PaymentComplementaryInformation2 *-- "0..1" CashAccount16 : DebtorAgentAccount PaymentComplementaryInformation2 *-- "0..1" SettlementInformation13 : SettlementInformation PaymentComplementaryInformation2 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : IntermediaryAgent1 PaymentComplementaryInformation2 *-- "0..1" CashAccount16 : IntermediaryAgent1Account PaymentComplementaryInformation2 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : IntermediaryAgent2 PaymentComplementaryInformation2 *-- "0..1" CashAccount16 : IntermediaryAgent2Account PaymentComplementaryInformation2 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : IntermediaryAgent3 PaymentComplementaryInformation2 *-- "0..1" CashAccount16 : IntermediaryAgent3Account PaymentComplementaryInformation2 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : CreditorAgent PaymentComplementaryInformation2 *-- "0..1" CashAccount16 : CreditorAgentAccount PaymentComplementaryInformation2 *-- "0..1" PartyIdentification32 : Creditor PaymentComplementaryInformation2 *-- "0..1" CashAccount16 : CreditorAccount PaymentComplementaryInformation2 *-- "0..1" PartyIdentification32 : UltimateCreditor PaymentComplementaryInformation2 *-- "0..1" IPurpose2Choice : Purpose PaymentComplementaryInformation2 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : PreviousInstructingAgent PaymentComplementaryInformation2 *-- "0..1" CashAccount16 : PreviousInstructingAgentAccount PaymentComplementaryInformation2 *-- "0..0" InstructionForNextAgent1 : InstructionForNextAgent PaymentComplementaryInformation2 *-- "0..0" InstructionForCreditorAgent1 : InstructionForCreditorAgent PaymentComplementaryInformation2 *-- "0..1" RemittanceInformation5 : RemittanceInformation %% PaymentTypeInformation22 recursion level 1 with max 1 class PaymentTypeInformation22{ InstructionPriority Priority2Code ClearingChannel ClearingChannel2Code SequenceType SequenceType1Code } PaymentTypeInformation22 *-- "0..1" IServiceLevel8Choice : ServiceLevel PaymentTypeInformation22 *-- "0..1" ILocalInstrument2Choice : LocalInstrument PaymentTypeInformation22 *-- "0..1" ICategoryPurpose1Choice : CategoryPurpose %% IAmountType3Choice 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 %% 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 %% CashAccount16 recursion level 1 with max 1 class CashAccount16{ Currency ActiveOrHistoricCurrencyCode Name IsoMax70Text } CashAccount16 *-- "1..1" IAccountIdentification4Choice : Identification CashAccount16 *-- "0..1" CashAccountType2 : Type %% BranchAndFinancialInstitutionIdentification4 recursion level 1 with max 1 BranchAndFinancialInstitutionIdentification4 *-- "1..1" FinancialInstitutionIdentification7 : FinancialInstitutionIdentification BranchAndFinancialInstitutionIdentification4 *-- "0..1" BranchData2 : BranchIdentification %% CashAccount16 recursion level 1 with max 1 class CashAccount16{ Currency ActiveOrHistoricCurrencyCode Name IsoMax70Text } CashAccount16 *-- "1..1" IAccountIdentification4Choice : Identification CashAccount16 *-- "0..1" CashAccountType2 : Type %% SettlementInformation13 recursion level 1 with max 1 class SettlementInformation13{ SettlementMethod SettlementMethod1Code } SettlementInformation13 *-- "0..1" CashAccount16 : SettlementAccount SettlementInformation13 *-- "0..1" IClearingSystemIdentification3Choice : ClearingSystem SettlementInformation13 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : InstructingReimbursementAgent SettlementInformation13 *-- "0..1" CashAccount16 : InstructingReimbursementAgentAccount SettlementInformation13 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : InstructedReimbursementAgent SettlementInformation13 *-- "0..1" CashAccount16 : InstructedReimbursementAgentAccount SettlementInformation13 *-- "0..1" BranchAndFinancialInstitutionIdentification4 : ThirdReimbursementAgent SettlementInformation13 *-- "0..1" CashAccount16 : ThirdReimbursementAgentAccount %% BranchAndFinancialInstitutionIdentification4 recursion level 1 with max 1 BranchAndFinancialInstitutionIdentification4 *-- "1..1" FinancialInstitutionIdentification7 : FinancialInstitutionIdentification BranchAndFinancialInstitutionIdentification4 *-- "0..1" BranchData2 : BranchIdentification %% CashAccount16 recursion level 1 with max 1 class CashAccount16{ Currency ActiveOrHistoricCurrencyCode Name IsoMax70Text } CashAccount16 *-- "1..1" IAccountIdentification4Choice : Identification CashAccount16 *-- "0..1" CashAccountType2 : Type %% BranchAndFinancialInstitutionIdentification4 recursion level 1 with max 1 BranchAndFinancialInstitutionIdentification4 *-- "1..1" FinancialInstitutionIdentification7 : FinancialInstitutionIdentification BranchAndFinancialInstitutionIdentification4 *-- "0..1" BranchData2 : BranchIdentification %% CashAccount16 recursion level 1 with max 1 class CashAccount16{ Currency ActiveOrHistoricCurrencyCode Name IsoMax70Text } CashAccount16 *-- "1..1" IAccountIdentification4Choice : Identification CashAccount16 *-- "0..1" CashAccountType2 : Type %% BranchAndFinancialInstitutionIdentification4 recursion level 1 with max 1 BranchAndFinancialInstitutionIdentification4 *-- "1..1" FinancialInstitutionIdentification7 : FinancialInstitutionIdentification BranchAndFinancialInstitutionIdentification4 *-- "0..1" BranchData2 : BranchIdentification %% CashAccount16 recursion level 1 with max 1 class CashAccount16{ Currency ActiveOrHistoricCurrencyCode Name IsoMax70Text } CashAccount16 *-- "1..1" IAccountIdentification4Choice : Identification CashAccount16 *-- "0..1" CashAccountType2 : Type %% BranchAndFinancialInstitutionIdentification4 recursion level 1 with max 1 BranchAndFinancialInstitutionIdentification4 *-- "1..1" FinancialInstitutionIdentification7 : FinancialInstitutionIdentification BranchAndFinancialInstitutionIdentification4 *-- "0..1" BranchData2 : BranchIdentification %% CashAccount16 recursion level 1 with max 1 class CashAccount16{ Currency ActiveOrHistoricCurrencyCode Name IsoMax70Text } CashAccount16 *-- "1..1" IAccountIdentification4Choice : Identification CashAccount16 *-- "0..1" CashAccountType2 : Type %% 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 %% CashAccount16 recursion level 1 with max 1 class CashAccount16{ Currency ActiveOrHistoricCurrencyCode Name IsoMax70Text } CashAccount16 *-- "1..1" IAccountIdentification4Choice : Identification CashAccount16 *-- "0..1" CashAccountType2 : Type %% 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 %% IPurpose2Choice recursion level 1 with max 1 %% BranchAndFinancialInstitutionIdentification4 recursion level 1 with max 1 BranchAndFinancialInstitutionIdentification4 *-- "1..1" FinancialInstitutionIdentification7 : FinancialInstitutionIdentification BranchAndFinancialInstitutionIdentification4 *-- "0..1" BranchData2 : BranchIdentification %% CashAccount16 recursion level 1 with max 1 class CashAccount16{ Currency ActiveOrHistoricCurrencyCode Name IsoMax70Text } CashAccount16 *-- "1..1" IAccountIdentification4Choice : Identification CashAccount16 *-- "0..1" CashAccountType2 : 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 } %% RemittanceInformation5 recursion level 1 with max 1 class RemittanceInformation5{ Unstructured IsoMax140Text } RemittanceInformation5 *-- "0..0" StructuredRemittanceInformation7 : Structured
PaymentComplementaryInformation2 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. | PaymentTypeInformation22 - 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. | IAmountType3Choice - 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. | PartyIdentification32 - Optional 0..1 |
Debtor | Party that owes an amount of money to the (ultimate) creditor. | PartyIdentification32 - 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. | CashAccount16 - Optional 0..1 |
DebtorAgent | Financial institution servicing an account for the debtor. | BranchAndFinancialInstitutionIdentification4 - Optional 0..1 |
DebtorAgentAccount | Unambiguous identification of the account of the debtor agent at its servicing agent in the payment chain. | CashAccount16 - Optional 0..1 |
SettlementInformation | Instruction between two clearing agents stipulating the cash transfer characteristics between the two parties. | SettlementInformation13 - 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. | CashAccount16 - 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. | CashAccount16 - 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. | CashAccount16 - Optional 0..1 |
CreditorAgent | Financial institution servicing an account for the creditor. | BranchAndFinancialInstitutionIdentification4 - 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. | CashAccount16 - Optional 0..1 |
Creditor | Party to which an amount of money is due. | PartyIdentification32 - 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. | CashAccount16 - Optional 0..1 |
UltimateCreditor | Ultimate party to which an amount of money is due. | PartyIdentification32 - 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. | BranchAndFinancialInstitutionIdentification4 - Optional 0..1 |
PreviousInstructingAgentAccount | Unambiguous identification of the account of the previous instructing agent at its servicing agent in the payment chain. | CashAccount16 - 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, ie, reconciliation, of a payment with the items that the payment is intended to settle, such as commercial invoices in an account receivable system. | RemittanceInformation5 - Optional 0..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the AdditionalPaymentInformationV03 implementation follows a specific implementaiton pattern. First of all, AdditionalPaymentInformationV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AdditionalPaymentInformationV03Document implements IOuterDocument. Because AdditionalPaymentInformationV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AdditionalPaymentInformationV03.
classDiagram class IOuterRecord AdditionalPaymentInformationV03 --|> IOuterRecord : Implements AdditionalPaymentInformationV03Document --|> IOuterDocument~AdditionalPaymentInformationV03~ : Implements class IOuterDocument~AdditionalPaymentInformationV03~ { AdditionalPaymentInformationV03 Message }
Document wrapper for serialization
The only real purpose AdditionalPaymentInformationV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:camt.028.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AdditionalPaymentInformationV03.ToDocument() method. The returned AdditionalPaymentInformationV03Document value will serialize correctly according to ISO 20022 standards.
classDiagram AdditionalPaymentInformationV03Document *-- AdditionalPaymentInformationV03 : 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.03">
<AddtlPmtInf>
<Assgnmt>
<!-- Assignment inner content -->
</Assgnmt>
<Case>
<!-- Case inner content -->
</Case>
<Undrlyg>
<!-- Underlying inner content -->
</Undrlyg>
<Inf>
<!-- Information inner content -->
</Inf>
</AddtlPmtInf>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_GN9QONE-Ed-BzquC8wXy7w_-434015417"
nextVersions="_sYCjIVkyEeGeoaLUQk__nA_-1513426724"
name="AdditionalPaymentInformationV03"
definition="Scope
The Additional Payment Information 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 Additional Payment Information 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 Additional Payment Information message covers one and only one original payment instruction. If several payment instructions need further details, multiple Additional Payment Information 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.
- A Claim Non Receipt 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 Additional Payment Information can be used to provide the missing information.
- A Request To Modify Payment 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 Additional Payment Information message allows the account owner to receive further particulars or correct information about a payment instruction or an entry passed to its account.
The Additional Payment Information message cannot be used to trigger a request for modification of a payment instruction activity. A Request To Modify Payment 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 Additional Payment Information but instead a Request To Modify Payment message.
It is assumed that when an account servicing institution sends out an Additional Payment Information 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 Resolution Of Investigation 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="_GOHBMNE-Ed-BzquC8wXy7w_-1248371085"
name="Assignment"
definition="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."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Assgnmt"
complexType="_T9Nac9p-Ed-ak6NoX_4Aeg_-1609381277" />
<messageBuildingBlock
xmi:id="_GOHBMdE-Ed-BzquC8wXy7w_-1248371146"
name="Case"
definition="Identifies the investigation case."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Case"
complexType="_SpAnptp-Ed-ak6NoX_4Aeg_-1565053133" />
<messageBuildingBlock
xmi:id="_GOHBMtE-Ed-BzquC8wXy7w_-1248371024"
name="Underlying"
definition="Identifies the underlying payment instruction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Undrlyg"
complexType="_P9DXuNp-Ed-ak6NoX_4Aeg_-2030379979" />
<messageBuildingBlock
xmi:id="_GOHBM9E-Ed-BzquC8wXy7w_-434015294"
name="Information"
definition="Additional information to the underlying payment instruction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Inf"
complexType="_P7RPCtp-Ed-ak6NoX_4Aeg_-1461213451" />
<messageDefinitionIdentifier
businessArea="camt"
messageFunctionality="028"
flavour="001"
version="03" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.