com.prowidesoftware.swift.model.mx.dic.Camt02800102 Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of pw-iso20022 Show documentation
Show all versions of pw-iso20022 Show documentation
Prowide Library for ISO 20022 messages
The newest version!
package com.prowidesoftware.swift.model.mx.dic;
import jakarta.xml.bind.annotation.XmlAccessType;
import jakarta.xml.bind.annotation.XmlAccessorType;
import jakarta.xml.bind.annotation.XmlElement;
import jakarta.xml.bind.annotation.XmlType;
import org.apache.commons.lang3.builder.EqualsBuilder;
import org.apache.commons.lang3.builder.HashCodeBuilder;
import org.apache.commons.lang3.builder.ToStringBuilder;
import org.apache.commons.lang3.builder.ToStringStyle;
/**
* 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 (such as 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.
*
*
*
*/
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "camt.028.001.02", propOrder = {
"assgnmt",
"_case",
"undrlyg",
"inf"
})
public class Camt02800102 {
@XmlElement(name = "Assgnmt", required = true)
protected CaseAssignment assgnmt;
@XmlElement(name = "Case", required = true)
protected Case _case;
@XmlElement(name = "Undrlyg", required = true)
protected PaymentInstructionExtract2 undrlyg;
@XmlElement(name = "Inf", required = true)
protected PaymentComplementaryInformation inf;
/**
* Gets the value of the assgnmt property.
*
* @return
* possible object is
* {@link CaseAssignment }
*
*/
public CaseAssignment getAssgnmt() {
return assgnmt;
}
/**
* Sets the value of the assgnmt property.
*
* @param value
* allowed object is
* {@link CaseAssignment }
*
*/
public Camt02800102 setAssgnmt(CaseAssignment value) {
this.assgnmt = value;
return this;
}
/**
* Gets the value of the case property.
*
* @return
* possible object is
* {@link Case }
*
*/
public Case getCase() {
return _case;
}
/**
* Sets the value of the case property.
*
* @param value
* allowed object is
* {@link Case }
*
*/
public Camt02800102 setCase(Case value) {
this._case = value;
return this;
}
/**
* Gets the value of the undrlyg property.
*
* @return
* possible object is
* {@link PaymentInstructionExtract2 }
*
*/
public PaymentInstructionExtract2 getUndrlyg() {
return undrlyg;
}
/**
* Sets the value of the undrlyg property.
*
* @param value
* allowed object is
* {@link PaymentInstructionExtract2 }
*
*/
public Camt02800102 setUndrlyg(PaymentInstructionExtract2 value) {
this.undrlyg = value;
return this;
}
/**
* Gets the value of the inf property.
*
* @return
* possible object is
* {@link PaymentComplementaryInformation }
*
*/
public PaymentComplementaryInformation getInf() {
return inf;
}
/**
* Sets the value of the inf property.
*
* @param value
* allowed object is
* {@link PaymentComplementaryInformation }
*
*/
public Camt02800102 setInf(PaymentComplementaryInformation value) {
this.inf = value;
return this;
}
@Override
public String toString() {
return ToStringBuilder.reflectionToString(this, ToStringStyle.MULTI_LINE_STYLE);
}
@Override
public boolean equals(Object that) {
return EqualsBuilder.reflectionEquals(this, that);
}
@Override
public int hashCode() {
return HashCodeBuilder.reflectionHashCode(this);
}
}
© 2015 - 2025 Weber Informatics LLC | Privacy Policy