Struct MT950 

pub struct MT950 {
    pub field_20: Field20,
    pub field_25: Field25NoOption,
    pub field_28c: Field28C,
    pub field_60: Field60,
    pub field_61: Option<Vec<Field61>>,
    pub field_62: Field62,
    pub field_64: Option<Field64>,
}

MT950: Statement Message

Purpose

Used to transmit account statement information with a simplified structure focusing on balance information and essential transaction data. This message provides streamlined account reporting for efficient processing and communication.

Scope

This message is:

• Sent by account servicing institutions for streamlined statement delivery
• Used for simplified account reporting with essential information
• Applied when detailed narrative information is not required
• Essential for automated processing and high-volume account reporting
• Part of efficient account management and customer communication systems

Key Features

• Simplified Structure: Streamlined format for efficient processing
• Essential Information: Focus on key balance and transaction data
• Multiple Transactions: Support for multiple statement line entries
• Balance Information: Opening and closing balance with currency consistency
• Available Balance: Optional available balance information
• Automated Processing: Optimized for automated statement processing systems

Common Use Cases

• High-volume account statement processing
• Automated statement delivery systems
• Simplified account reporting for operational accounts
• Batch processing of multiple account statements
• System-to-system account information exchange
• Streamlined cash management reporting
• Efficient correspondent banking statement delivery
• Simplified regulatory reporting requirements

Field Structure

• 20: Transaction Reference (mandatory) - Unique statement reference
• 25: Account Identification (mandatory) - Account being reported
• 28C: Statement Number/Sequence (mandatory) - Statement numbering
• 60: Opening Balance (mandatory) - Starting balance for statement period
• 61: Statement Line (mandatory, repetitive) - Individual transaction entries
• 62: Closing Balance (mandatory) - Ending balance for statement period
• 64: Available Balance (optional) - Available balance information

Field Details

Field 61 - Statement Line

Multiple statement lines can be included, each containing:

• Value Date: Date when transaction becomes effective
• Entry Date: Date when transaction was posted (optional)
• Credit/Debit Mark: C (Credit) or D (Debit) entry
• Amount: Transaction amount
• Transaction Type: SWIFT transaction type identification
• Reference: Transaction reference number

Network Validation Rules

• Currency Consistency: Opening and closing balances must use the same currency
• Available Balance Currency: Available balances must use same currency as main balances
• Reference Format: Transaction references must follow SWIFT formatting standards
• Required Fields: All mandatory fields must be present and properly formatted
• Balance Logic: Closing balance should reflect opening balance plus/minus transactions
• Date Validation: All dates must be valid and properly sequenced

Processing Context

Simplified Statement Generation

1. Account activity summarized for statement period
2. Essential transactions selected for reporting
3. Opening balance carried forward from previous period
4. MT950 generated with streamlined transaction detail
5. Closing balance calculated and validated

Automated Processing

• High-volume statement batch processing
• Automated account reconciliation
• System integration and data exchange
• Efficient customer communication
• Streamlined compliance reporting

SRG2025 Status

• Structural Changes: None - MT950 format remains unchanged in SRG2025
• Validation Updates: Additional validation for statement accuracy and completeness
• Processing Improvements: Improved support for digital banking integration
• Compliance Notes: Enhanced support for high-volume automated processing

Integration Considerations

• Banking Systems: Efficient integration with core banking platforms and statement processing
• Customer Systems: Streamlined input for customer financial management systems
• API Integration: Optimized for modern API-based banking services and digital platforms
• Compliance Integration: Simplified compliance and audit trail maintenance requirements

Relationship to Other Messages

• Triggers: Often triggered by MT920 (Request Message) for streamlined statement delivery
• Responses: Provides simplified alternative to MT940 when detailed information is not required
• Related: Works with other cash management and account reporting messages
• Alternatives: MT940 for detailed transaction information when comprehensive reporting is needed
• Status Updates: Supports efficient account management and customer communication workflows

Fields

field_20: Field20

field_25: Field25NoOption

field_28c: Field28C

field_60: Field60

field_61: Option<Vec<Field61>>

field_62: Field62

field_64: Option<Field64>

Implementations

impl MT950

pub fn validate() -> &'static str

Get validation rules for this message type

Trait Implementations

impl Clone for MT950

fn clone(&self) -> MT950

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for MT950

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for MT950

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for MT950

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

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 MT950

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 MT950