Struct MT290 

pub struct MT290 {
    pub field_20: Field20,
    pub field_21: Field21NoOption,
    pub field_25: Field25AccountIdentification,
    pub field_32: Field32,
    pub field_52: Option<Field52OrderingInstitution>,
    pub field_71b: Field71B,
    pub field_72: Option<Field72>,
}

MT290: Advice of Charges, Interest and Other Adjustments Cancellation

Purpose

Used to cancel or reverse a previously sent MT190 advice. This message notifies the account holder that a previous adjustment advice needs to be cancelled or reversed, ensuring accurate account records and proper handling of erroneous or superseded adjustments.

Scope

This message is:

• Sent by the account servicing institution to the account holder
• Used to cancel previously advised charges, interest, or adjustments
• Applied when errors are discovered or adjustments need reversal
• Essential for maintaining accurate account records
• Part of the error correction and adjustment management process

Key Features

• Cancellation Notification: Official cancellation of previous MT190 advice
• Reference Linking: Clear reference to the original MT190 being cancelled
• Reversal Details: Complete information about the adjustment being reversed
• Account Identification: Clear identification of the affected account
• Charge Details: Detailed explanation of the cancellation reason
• Audit Trail: Maintains complete documentation of adjustments and cancellations

Common Use Cases

• Cancelling erroneously posted interest calculations
• Reversing incorrect fee charges
• Correcting misapplied account adjustments
• Cancelling duplicate charge advisories
• Reversing provisional adjustments
• Correcting calculation errors in fees
• Cancelling adjustments due to system errors
• Reversing adjustments per customer dispute resolution

Message Structure

• Field 20: Transaction Reference Number (mandatory) - Unique reference for this cancellation
• Field 21: Related Reference (mandatory) - Reference to original MT190 being cancelled
• Field 25: Account Identification (mandatory) - Account affected by cancellation
• Field 32a: Value Date, Currency Code, Amount (mandatory) - Original adjustment amount (C or D)
• Field 52a: Ordering Institution (optional) - Institution initiating cancellation (A or D)
• Field 71B: Details of Charges (mandatory) - Explanation of cancellation/reversal
• Field 72: Sender to Receiver Information (optional) - Additional cancellation details

Network Validation Rules

• Reference Matching: Field 21 must reference a valid MT190 transaction
• Amount Consistency: Amount should match the original MT190 adjustment
• Account Validation: Account must match the original MT190 account
• Cancellation Details: Field 71B must explain the cancellation reason
• Timing Rules: Cancellation typically within reasonable timeframe of original

Processing Context

Cancellation Processing Workflow

1. Error or reversal requirement identified
2. Original MT190 adjustment reversed in system
3. MT290 sent to advise cancellation
4. Account holder reverses original entry
5. Reconciliation updated accordingly

Reversal Management

• Automatic reversal posting
• Audit trail maintenance
• Balance correction
• Statement adjustment

SRG2025 Status

• No Structural Changes: MT290 format remains stable
• Enhanced Processing: Improved cancellation workflow support
• Validation Updates: Stricter reference matching validation
• Real-time Capability: Support for immediate cancellation notifications

Integration Considerations

• Banking Systems: Integrated with core banking reversal processes
• Audit Systems: Complete audit trail for compliance
• Reconciliation: Automatic reconciliation adjustment
• Reporting: Reflected in account statements and reports

Relationship to Other Messages

• Cancels: MT190 advice messages
• May trigger: New MT190 with corrected information
• Related to: MT192/292 for payment cancellations
• Supports: Error correction and adjustment management processes

Best Practices

• Send MT290 promptly upon discovering errors
• Provide clear cancellation reasons in Field 71B
• Ensure amount and account details match original MT190
• Consider sending corrected MT190 if adjustment still valid
• Maintain complete audit trail of adjustments and cancellations

Fields

field_20: Field20

field_21: Field21NoOption

field_25: Field25AccountIdentification

field_32: Field32

field_52: Option<Field52OrderingInstitution>

field_71b: Field71B

field_72: Option<Field72>

Implementations

impl MT290

pub fn validate() -> &'static str

Get validation rules for this message type

Trait Implementations

impl Clone for MT290

fn clone(&self) -> MT290

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for MT290

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for MT290

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for MT290

fn eq(&self, other: &MT290) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for MT290

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl SwiftMessageBody for MT290

fn message_type() -> &'static str

Get the message type identifier (e.g., “103”, “202”)

fn from_fields( fields: HashMap<String, Vec<(String, usize)>>, ) -> SwiftResult<Self>

Create from field map with sequential consumption tracking

fn from_fields_with_config( fields: HashMap<String, Vec<(String, usize)>>, config: &ParserConfig, ) -> Result<ParseResult<Self>, ParseError>

Create from field map with configuration for error collection

fn to_fields(&self) -> HashMap<String, Vec<String>>

Convert to field map

fn required_fields() -> Vec<&'static str>

Get required field tags for this message type

fn optional_fields() -> Vec<&'static str>

Get optional field tags for this message type

fn to_ordered_fields(&self) -> Vec<(String, String)>

Convert to ordered field list for MT serialization Returns fields in the correct sequence order for multi-sequence messages

impl StructuralPartialEq for MT290