Struct MT191 

pub struct MT191 {
    pub field_20: Field20,
    pub field_21: Field21NoOption,
    pub field_32b: Field32B,
    pub field_52: Option<Field52OrderingInstitution>,
    pub field_57: Option<Field57AccountWithInstitution>,
    pub field_71b: Field71B,
    pub field_72: Option<Field72>,
}

MT191: Request for Payment of Charges, Interest and Other Expenses

Purpose

Used to request payment of charges, interest and other expenses from another financial institution. This message enables banks to claim reimbursement for costs incurred on behalf of another institution, ensuring proper cost recovery and transparent inter-bank expense management.

Scope

This message is:

• Sent between financial institutions to request expense reimbursement
• Used to claim charges, interest, and other costs incurred
• Applied to various types of inter-bank expenses and fee recovery
• Essential for correspondent banking cost management
• Part of the comprehensive inter-bank settlement process

Key Features

• Expense Request: Formal request for payment of incurred expenses
• Detailed Charges: Comprehensive breakdown of charges being claimed
• Currency Specification: Clear identification of currency and amount
• Reference Tracking: Links to related transactions or services
• Institution Identification: Clear identification of parties involved
• Settlement Instructions: Optional routing for payment settlement

Common Use Cases

• Correspondent banking charge recovery
• Interest payment requests on nostro accounts
• Service fee reimbursement requests
• Transaction processing cost recovery
• Foreign exchange handling charges
• Investigation and inquiry fee recovery
• Amendment processing charge requests
• Compliance and regulatory cost recovery

Message Structure

• Field 20: Transaction Reference Number (mandatory) - Unique reference for this request
• Field 21: Related Reference (mandatory) - Reference to related transaction or period
• Field 32B: Currency Code, Amount (mandatory) - Amount being requested
• Field 52a: Ordering Institution (optional) - Institution initiating request (A or D)
• Field 57a: Account With Institution (optional) - Settlement account details (A, B, or D)
• Field 71B: Details of Charges (mandatory) - Detailed breakdown of expenses
• Field 72: Sender to Receiver Information (optional) - Additional information

Network Validation Rules

• Reference Format: Transaction references must follow SWIFT standards
• Amount Validation: Requested amounts must be properly formatted
• Institution Validation: BIC codes must be valid SWIFT participants
• Charge Details: Field 71B must contain meaningful expense information
• Currency Validation: Currency codes must be valid ISO 4217 codes

Processing Context

Request Processing Workflow

1. Expenses incurred and documented
2. MT191 request prepared with details
3. Message sent to responsible institution
4. Receiving institution validates claim
5. Payment processed via appropriate channel

Expense Management

• Cost tracking and allocation
• Inter-bank billing processes
• Service level agreements
• Reconciliation support

SRG2025 Status

• No Structural Changes: MT191 format remains stable
• Enhanced Processing: Improved integration with expense management systems
• Validation Updates: Enhanced validation rules for expense claims
• Real-time Capability: Support for immediate expense notifications

Integration Considerations

• Correspondent Banking: Core component of correspondent relationships
• Expense Systems: Integration with bank expense management platforms
• Settlement Networks: Links to payment and settlement systems
• Reporting: Essential for inter-bank cost reporting

Relationship to Other Messages

• May trigger: MT103/MT202 for actual payment
• Related to: MT192 for payment request cancellation
• Complements: MT199 for free format messages
• Alternative: MT291 for cancellation of this request

Best Practices

• Provide detailed charge breakdown in Field 71B
• Include clear reference to services or transactions
• Specify preferred settlement instructions when applicable
• Ensure timely submission of expense claims
• Maintain supporting documentation for all charges

Fields

field_20: Field20

field_21: Field21NoOption

field_32b: Field32B

field_52: Option<Field52OrderingInstitution>

field_57: Option<Field57AccountWithInstitution>

field_71b: Field71B

field_72: Option<Field72>

Implementations

impl MT191

pub fn validate() -> &'static str

Get validation rules for this message type

Trait Implementations

impl Clone for MT191

fn clone(&self) -> MT191

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for MT191

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for MT191

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for MT191

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

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 MT191

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 MT191