Struct MT935 

pub struct MT935 {
    pub field_20: Field20,
    pub rate_changes: Vec<MT935RateChange>,
    pub field_72: Option<Field72>,
}

MT935: Rate Change Advice

Purpose

Used to advise changes in interest rates, exchange rates, or other financial rates that affect existing agreements, accounts, or financial instruments. This message provides formal notification of rate changes with effective dates and detailed rate information.

Scope

This message is:

• Sent by financial institutions to notify customers or correspondents of rate changes
• Used for interest rate changes on deposits, loans, and credit facilities
• Applied to foreign exchange rate notifications and updates
• Essential for pricing transparency and regulatory compliance
• Part of relationship management and customer communication processes

Key Features

• Rate Change Notification: Formal advice of rate modifications
• Multiple Rate Changes: Support for up to 10 rate changes in a single message
• Effective Dating: Precise effective dates for each rate change
• Flexible Identification: Either function code (field 23) or account (field 25) identification
• Detailed Rate Information: Comprehensive rate details using field 37H
• Additional Information: Optional narrative for context and explanations

Common Use Cases

• Interest rate changes on deposit accounts
• Loan and credit facility rate adjustments
• Foreign exchange rate updates for currency accounts
• Investment product rate notifications
• Central bank rate change implementations
• Correspondent banking rate adjustments
• Treasury and money market rate updates
• Regulatory rate change compliance notifications

Message Structure

Header Section

• 20: Transaction Reference (mandatory) - Unique reference for this rate change advice
• Rate Changes: Repetitive sequence (1-10 occurrences) of rate change details
• 72: Sender to Receiver Information (optional) - Additional context and explanations

Rate Change Sequence (MT935RateChange)

Each rate change sequence contains:

• 23: Function Code (optional) - Type of rate change or product code
• 25: Account Identification (optional) - Specific account affected by rate change
• 30: Effective Date (mandatory) - Date when new rate becomes effective
• 37H: New Rate (mandatory, repetitive) - Detailed rate information

Network Validation Rules

• C1 Rule: Rate change sequences must occur 1-10 times
• C2 Rule: Either field 23 (Function Code) or field 25 (Account) must be present, but not both
• Reference Format: Transaction references must follow SWIFT formatting standards
• Required Fields: All mandatory fields must be present and properly formatted
• Date Validation: Effective dates must be valid and properly formatted
• Rate Validation: Rate information must be complete and valid

Field 23 - Function Codes

When used, field 23 may contain codes such as:

• DEPOSIT: Interest rates for deposit products
• LOAN: Interest rates for lending products
• FX: Foreign exchange rates
• CREDIT: Credit facility rates
• INVEST: Investment product rates
• MONEY: Money market rates

Field 37H - Rate Information

Provides detailed rate information including:

• Rate type and classification
• Percentage rates or basis point changes
• Spread information over reference rates
• Tier-based or graduated rate structures
• Minimum and maximum rate constraints

Processing Context

Rate Change Implementation

1. Rate change decision made by institution
2. MT935 prepared with effective date and rate details
3. Message sent to affected customers/correspondents
4. Recipients update systems and communicate changes
5. New rates become effective on specified date

Regulatory Compliance

• Documentation of rate change notifications
• Audit trail for regulatory review
• Customer communication requirements
• Transparency and disclosure obligations

SRG2025 Status

• No Structural Changes: MT935 format remains unchanged in SRG2025
• Enhanced Validation: Additional validation for rate accuracy and completeness
• Digital Integration: Improved support for automated rate change processing
• Regulatory Compliance: Enhanced support for regulatory reporting requirements

Integration Considerations

• Banking Systems: Direct integration with rate management and pricing systems
• Customer Systems: Input for customer treasury and financial management systems
• Compliance Systems: Essential for regulatory reporting and audit trail maintenance
• Communication Platforms: Integration with multi-channel customer notification systems

Relationship to Other Messages

• Supports: Rate-sensitive account management and transaction processing
• Complements: Statement messages (MT940, MT950) that reflect rate changes
• Integrates with: Customer communication and relationship management processes
• Documentation: Provides formal record of rate change notifications for compliance

Fields

field_20: Field20

rate_changes: Vec<MT935RateChange>

field_72: Option<Field72>

Implementations

impl MT935

pub fn validate() -> &'static str

Get validation rules for this message type

Trait Implementations

impl Clone for MT935

fn clone(&self) -> MT935

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for MT935

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for MT935

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for MT935

fn eq(&self, other: &MT935) -> 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 MT935

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 MT935

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 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

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

impl StructuralPartialEq for MT935