pub struct MT296 {
pub field_20: GenericReferenceField,
pub field_21: GenericReferenceField,
pub field_76: GenericMultiLine6x35,
pub field_77a: Option<GenericMultiLine20x35>,
pub field_11a: Option<GenericTextField>,
pub field_79: Option<GenericMultiLine6x35>,
pub field_32a: Option<Field32A>,
pub field_58a: Option<GenericBicField>,
pub field_52a: Option<GenericBicField>,
pub field_53a: Option<GenericBicField>,
pub field_56a: Option<GenericBicField>,
pub field_57a: Option<GenericBicField>,
}Expand description
§MT296: Answers (Treasury Messages)
This message is sent by a financial institution to provide answers, confirmations, or status information in response to queries or requests related to treasury messages. MT296 is used for answering treasury transfer queries and other institutional inquiries.
§Key Features
- Treasury answer provision: Official responses to treasury message queries
- Reference tracking: Links to the original message through reference fields
- Conditional structure: Either narrative (field 79) or copy of original message fields
- Answer codes: Standardized answer codes with supplementary data
- Narrative support: Additional narrative description capability
§Field Structure
The message follows a conditional structure where either field 79 (narrative description) or a copy of the mandatory fields from the original message may be present, but not both. This structure is identical to MT196 but used for treasury/institutional contexts.
§Answer Process
Used when a treasury department or institutional receiver needs to provide answers, confirmations, or status updates regarding previously received treasury messages, including confirmations of institutional transfers, cover payments, or responses to treasury queries.
Fields§
§field_20: GenericReferenceFieldTransaction Reference Number - Field 20
Unique reference assigned by the sender for this treasury answer message. This reference is used throughout the answer lifecycle for tracking, acknowledgment, and audit purposes. Must be unique within sender’s system per business day.
field_21: GenericReferenceFieldRelated Reference - Field 21
Contains the reference from field 20 of the treasury message being answered. This creates a direct link between the answer and the original treasury message, enabling complete audit trails and transaction tracking.
field_76: GenericMultiLine6x35Answers - Field 76
Contains response codes, narratives, and supplementary data. Includes confirmation codes (1-33), cancellation codes (CNCL, PDCR, RJCR), and reason codes with optional supplementary details in parentheses.
field_77a: Option<GenericMultiLine20x35>Narrative - Field 77A (Optional)
Free-form narrative description that supplements the answer codes in field 76. Used for providing additional context, explanations, or details about the treasury answers.
field_11a: Option<GenericTextField>MT and Date of the Original Message - Field 11a (Optional)
Specifies the message type and date of the original treasury message being answered. Can be in Option R format (with session/ISN) or Option S format (date only).
field_79: Option<GenericMultiLine6x35>Narrative Description of Original Message - Field 79 (Conditional)
Contains narrative description of the original treasury message being answered. Must be present if copy of original message fields is not included. Cannot be used together with copy of original message fields.
field_32a: Option<Field32A>Copy of Mandatory Fields from Original Message - Multiple Fields (Conditional)
When present, contains a copy of at least the mandatory fields from the original treasury message. This helps identify the exact treasury transaction being answered. Cannot be used together with field 79 according to conditional rule C1.
For treasury messages:
- MT202: Would include fields 32A, 53, 58
- MT205: Would include fields 32A, 53, 56, 57, 58
- MT210: Would include fields 32A, 53
field_58a: Option<GenericBicField>§field_52a: Option<GenericBicField>§field_53a: Option<GenericBicField>§field_56a: Option<GenericBicField>§field_57a: Option<GenericBicField>