Struct MT104 

pub struct MT104 {

    pub field_20: Field20,
    pub field_21r: Option<Field21R>,
    pub field_23e: Option<Field23E>,
    pub field_21e: Option<Field21E>,
    pub field_30: Field30,
    pub field_51a: Option<Field51A>,
    pub field_50_instructing: Option<Field50InstructingParty>,
    pub field_50_creditor: Option<Field50Creditor>,
    pub field_52: Option<Field52CreditorBank>,
    pub field_26t: Option<Field26T>,
    pub field_77b: Option<Field77B>,
    pub field_71a: Option<Field71A>,
    pub field_72: Option<Field72>,
    pub transactions: Vec<MT104Transaction>,
    pub field_32b: Option<Field32B>,
    pub field_19: Option<Field19>,
    pub field_71f: Option<Field71F>,
    pub field_71g: Option<Field71G>,
    pub field_53: Option<Field53SenderCorrespondent>,
}

MT104: Direct Debit and Request for Debit Transfer Message

Purpose

Used for customer direct debit instructions between financial institutions, allowing creditors to request debiting of debtor accounts through the banking network. This message enables efficient collection of payments through authorized direct debit arrangements.

Scope

This message is:

• Sent by corporate entities to their financial institutions for payment collection
• Used to request direct debit of debtor accounts with proper authorization
• Applicable for both domestic and international direct debit scenarios
• Compatible with bulk processing of multiple direct debit transactions
• Subject to strict authorization and regulatory compliance requirements
• Used in conjunction with direct debit mandates and agreements

Key Features

• Multi-Transaction Support: Single message can contain multiple direct debit requests
• Three-Sequence Architecture: General info, transaction details, and settlement information
• Authorization Framework: Built-in support for direct debit mandates and agreements
• Currency Flexibility: Supports different currencies and exchange rate conversions
• Charge Allocation Options: Configurable charge handling (OUR/SHA/BEN)
• Regulatory Compliance: Comprehensive fields for regulatory reporting requirements

Common Use Cases

• Utility companies collecting monthly bills from customer accounts
• Insurance companies collecting premium payments via direct debit
• Subscription service providers collecting recurring fees
• Loan servicing companies collecting installment payments
• Government agencies collecting taxes and fees
• Corporate collection of accounts receivable from customers
• Automated clearing house (ACH) equivalent processing

Message Structure

Sequence A (General Information - Mandatory, Single)

• Field 20: Sender’s Reference (mandatory) - Unique message identifier
• Field 21R: Customer Specified Reference (optional) - Creditor’s batch reference
• Field 28D: Message Index/Total (mandatory) - For chained messages
• Field 30: Requested Execution Date (mandatory) - When debits should be executed
• Field 25: Account Identification (optional) - Creditor’s account for credits
• Field 50: Instructing Party (optional) - Party authorizing the direct debits

Sequence B (Transaction Details - Mandatory, Repetitive)

• Field 21: Transaction Reference (mandatory) - Unique transaction identifier
• Field 32B: Currency/Amount (mandatory) - Amount to be debited
• Field 50: Ordering Customer/Debtor (mandatory) - Account to be debited
• Field 52: Account Servicing Institution (optional) - Debtor’s bank
• Field 57: Account With Institution (optional) - Intermediary institution
• Field 59: Beneficiary/Creditor (mandatory) - Account to be credited
• Field 70: Remittance Information (optional) - Payment purpose and details
• Field 77B: Regulatory Reporting (optional) - Compliance information
• Field 71A: Details of Charges (mandatory) - Charge allocation instructions

Sequence C (Settlement Information - Optional, Single)

• Field 32A: Value Date/Currency/Total Amount (optional) - Settlement summary
• Field 19: Sum of Amounts (optional) - Total amount of all transactions
• Field 71F: Sender’s Charges (optional) - Total charges claimed
• Field 71G: Receiver’s Charges (optional) - Total charges to be deducted

Network Validation Rules

• Authorization Validation: Proper direct debit mandate verification required
• Transaction Limits: Individual and batch transaction limit enforcement
• Currency Consistency: Currency validation across sequences (Note: C11 requires custom implementation due to JSONLogic limitations)
• Charge Allocation: Consistent charge handling across all transactions
• Settlement Totals: Sequence C totals must match sum of Sequence B amounts
• Reference Uniqueness: Transaction references must be unique within batch

SRG2025 Status

• Structural Changes: None - MT104 format remains unchanged
• Enhanced Validation: Strengthened authorization and mandate validation
• Regulatory Compliance: Enhanced field 77B validation for reporting
• Processing Improvements: Better support for modern direct debit frameworks

Integration Considerations

• Banking Systems: Compatible with core banking and payment processing systems
• Authorization Systems: Integration with direct debit mandate management systems
• API Integration: RESTful API support for modern payment platforms
• Processing Requirements: Supports batch processing with settlement coordination

Relationship to Other Messages

• Triggers: Often triggered by recurring payment schedules or collection processes
• Responses: May generate MT103 (credit transfers) for creditor account credits
• Related: Works with MT202 for settlement and MT940/MT950 for account reporting
• Alternatives: MT101 for credit transfers, MT103 for individual payments
• Authorization: Requires underlying direct debit mandates and agreements

Fields

field_20: Field20

field_21r: Option<Field21R>

field_23e: Option<Field23E>

field_21e: Option<Field21E>

field_30: Field30

field_51a: Option<Field51A>

field_50_instructing: Option<Field50InstructingParty>

field_50_creditor: Option<Field50Creditor>

field_52: Option<Field52CreditorBank>

field_26t: Option<Field26T>

field_77b: Option<Field77B>

field_71a: Option<Field71A>

field_72: Option<Field72>

transactions: Vec<MT104Transaction>

field_32b: Option<Field32B>

field_19: Option<Field19>

field_71f: Option<Field71F>

field_71g: Option<Field71G>

field_53: Option<Field53SenderCorrespondent>

Implementations

impl MT104

pub fn validate() -> &'static str

Get validation rules for this message type

Trait Implementations

impl Clone for MT104

fn clone(&self) -> MT104

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for MT104

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for MT104

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for MT104

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

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 MT104

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 MT104