Struct MT110 

pub struct MT110 {
    pub field_20: Field20,
    pub field_53a: Option<Field53SenderCorrespondent>,
    pub field_54a: Option<Field54ReceiverCorrespondent>,
    pub field_72: Option<Field72>,
    pub cheques: Vec<MT110Cheque>,
}

MT110: Advice of Cheque(s)

Purpose

Used to advise the receipt of cheque(s) for collection or deposit between financial institutions. This message provides detailed information about each cheque including amounts, dates, and processing instructions to facilitate efficient cheque clearing and collection processes.

Scope

This message is:

• Used for cheque collection advice between financial institutions
• Applicable for bulk cheque processing with individual cheque identification
• Designed for correspondent banking relationships in cheque clearing
• Compatible with domestic and cross-border cheque collection schemes
• Subject to cheque validation rules for proper clearing procedures
• Integrated with traditional paper-based and electronic cheque processing systems

Key Features

• Comprehensive Cheque Details: Individual cheque information with amounts, dates, and references
• Correspondent Banking Support: Fields for sender/receiver correspondents (53A/54A)
• Collection Processing Framework: Structured information for cheque collection and clearing
• Bulk Operations Support: Multiple cheques can be advised in a single message
• Reference Tracking: Unique identification for each cheque in the collection
• Currency Validation: Ensures all cheques in a message use the same currency

Common Use Cases

• Bank-to-bank cheque collection advice for deposited cheques
• Correspondent banking cheque clearing operations
• Cross-border cheque collection for foreign currency cheques
• Bulk cheque deposit processing for corporate customers
• Cheque truncation and electronic presentment advice
• Collection of returned or dishonored cheques
• High-value cheque collection requiring special handling

Message Structure

Message Header

• Field 20: Sender’s Reference (mandatory) - Unique message identifier
• Field 53A: Sender’s Correspondent (optional) - Sender’s correspondent bank
• Field 54A: Receiver’s Correspondent (optional) - Receiver’s correspondent bank
• Field 72: Sender to Receiver Information (optional) - Additional processing instructions

Cheque Details (Repetitive Sequence)

• Field 21: Cheque Reference (mandatory) - Unique reference for each cheque
• Field 30: Date of Issue (mandatory) - Date when cheque was issued (YYMMDD)
• Field 32: Currency/Amount (mandatory) - Cheque amount and currency code
• Field 50: Ordering Customer (optional) - Drawer/issuer of the cheque
• Field 52: Drawer Bank (optional) - Bank on which cheque is drawn
• Field 59: Beneficiary Customer (mandatory) - Payee of the cheque

Network Validation Rules

• Cheque Quantity Limits: Maximum 10 cheques per message for processing efficiency
• Currency Consistency: All cheques must have the same currency within a single message
• Reference Uniqueness: Each cheque reference must be unique within the message
• Date Validation: Date of issue must be in valid YYMMDD format
• Reference Format: Cheque references must not contain ‘/’ or ‘//’ characters
• Minimum Requirements: At least one cheque required per advice message
• Correspondent Validation: Proper BIC validation for correspondent bank fields

SRG2025 Status

• Structural Changes: None - MT110 format remains stable for cheque processing
• Validation Updates: Enhanced validation rules for electronic cheque processing
• Processing Improvements: Improved handling of cheque truncation scenarios
• Compliance Notes: Maintained compatibility with traditional cheque clearing systems

Integration Considerations

• Banking Systems: Compatible with cheque processing systems and clearing houses
• API Integration: RESTful API support for modern cheque collection platforms
• Processing Requirements: Supports both batch and real-time cheque collection processing
• Compliance Integration: Built-in validation for regulatory cheque processing requirements

Relationship to Other Messages

• Triggers: Often triggered by cheque deposit systems or collection processing
• Responses: May generate status messages or collection confirmation messages
• Related: Works with cheque clearing messages and account reporting systems
• Alternatives: Electronic payment messages for digital payment alternatives
• Status Updates: May receive notifications about cheque clearing success or failure

Fields

field_20: Field20

field_53a: Option<Field53SenderCorrespondent>

field_54a: Option<Field54ReceiverCorrespondent>

field_72: Option<Field72>

cheques: Vec<MT110Cheque>

Implementations

impl MT110

pub fn validate() -> &'static str

Get validation rules for this message type

Trait Implementations

impl Clone for MT110

fn clone(&self) -> MT110

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for MT110

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for MT110

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for MT110

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

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 MT110

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 MT110