swift_mt_message/fields/
field76.rs

1use serde::{Deserialize, Serialize};
2use swift_mt_message_macros::SwiftField;
3
4///   **Field 76: Answers**
5///
6/// ## Purpose
7/// Specifies answer information in Swift MT message query/response workflows. This field
8/// contains structured responses to queries submitted through Field 75, providing
9/// clarifications, status updates, and additional information regarding original transactions.
10/// Essential component completing the Swift query/answer ecosystem for systematic
11/// information exchange between financial institutions.
12///
13/// ## Format Specification
14/// - **Swift Format**: `6*35x`
15/// - **Structure**: Up to 6 lines of 35 characters each
16/// - **Content**: Structured answer information with codes and descriptive responses
17/// - **Character Set**: Standard SWIFT character set with narrative formatting
18///
19/// ## Business Context Applications
20/// - **Answer Messages**: Core component of MT n96 series answer messages
21/// - **Query Responses**: Providing responses to Field 75 queries
22/// - **Status Updates**: Delivering status information on requested transactions
23/// - **Clarification Delivery**: Providing requested clarifications and details
24///
25/// ## Message Type Integration
26/// ### Answer Message Types (MT n96 Series)
27/// - **MT 196**: Customer payment answers (Category 1)
28/// - **MT 296**: Treasury answers (Category 2)
29/// - **MT 396**: Foreign exchange answers (Category 3)
30/// - **MT 496**: Securities answers (Category 4)
31/// - **MT 596**: Securities lending answers (Category 5)
32/// - **MT 696**: Commodity answers (Category 6)
33/// - **MT 796**: Documentary credits answers (Category 7)
34/// - **MT 896**: Traveler's checks answers (Category 8)
35/// - **MT 996**: Cash management answers (Category 9)
36///
37/// ## Network Validation Requirements
38/// - **Line Length**: Maximum 6 lines of 35 characters each
39/// - **Character Set**: Must use valid SWIFT character set
40/// - **Answer Structure**: Should follow structured answer format
41/// - **Reference Consistency**: Must correspond to original query references
42/// - **Response Completeness**: Must address all points raised in original query
43///
44/// ## Answer Types and Response Codes
45/// ### Common Answer Categories
46/// - **Status Responses**: Current transaction processing status
47/// - **Clarification Responses**: Detailed explanations of transaction elements
48/// - **Amendment Confirmations**: Confirmations of transaction modifications
49/// - **Settlement Information**: Settlement status and timing details
50/// - **Documentation Responses**: Provision of requested documentation
51///
52/// ### Common Response Codes (from MT 292 implementation)
53/// - **AGNT**: Agent/Intermediary related response
54/// - **AM09**: Wrong amount clarification
55/// - **COVR**: Cover payment information
56/// - **CURR**: Currency-related response
57/// - **CUST**: Customer-related information
58/// - **CUTA**: Cut-off time information
59/// - **DUPL**: Duplicate transaction response
60/// - **FRAD**: Fraudulent transaction information
61/// - **TECH**: Technical problem resolution
62/// - **UPAY**: Unpaid transaction status
63///
64/// ## Query/Answer Relationship
65/// ### Direct Correspondence
66/// - **Field 75 Query**: Original query information and codes
67/// - **Field 76 Answer**: Direct response to specific query points
68/// - **Reference Linkage**: Common transaction references maintain connection
69/// - **Complete Resolution**: Answers should address all query elements
70///
71/// ### Response Structure
72/// ```logic
73/// :76:ANSWER TYPE: [Response]
74/// Detailed answer information
75/// Status or clarification details
76/// Additional relevant information
77/// ```
78///
79/// ## Answer Processing Workflow
80/// ### Answer Preparation
81/// - **Query Analysis**: Thorough analysis of Field 75 query
82/// - **Investigation**: Detailed investigation of queried transaction
83/// - **Response Formulation**: Comprehensive answer preparation
84/// - **Quality Review**: Answer completeness and accuracy verification
85///
86/// ### Answer Content Guidelines
87/// - **Complete Response**: Address all points raised in original query
88/// - **Clear Format**: Organized and structured answer information
89/// - **Accurate Information**: Verified and current information
90/// - **Reference Consistency**: Maintain reference accuracy throughout
91///
92/// ## Regional Considerations
93/// - **Global Standards**: Consistent answer format across all SWIFT regions
94/// - **Local Requirements**: Regional regulatory response requirements
95/// - **Time Zone Coordination**: Response timing considerations
96/// - **Language Standards**: English language requirement for international answers
97///
98/// ## Error Prevention Guidelines
99/// - **Query Review**: Thorough review of original query requirements
100/// - **Answer Completeness**: Ensure all query points are addressed
101/// - **Reference Accuracy**: Verify all transaction references
102/// - **Format Compliance**: Follow established answer format standards
103///
104/// ## Related Fields Integration
105/// - **Field 75**: Queries (corresponding query field)
106/// - **Field 20**: Transaction Reference (answer context)
107/// - **Field 21**: Related Reference (query linkage)
108/// - **Field 79**: Narrative (extended answer information)
109///
110/// ## Compliance Framework
111/// - **Audit Documentation**: Complete answer documentation for audit trails
112/// - **Regulatory Compliance**: Meeting regulatory response requirements
113/// - **Customer Service**: Providing effective customer query resolution
114/// - **Service Level Agreements**: Meeting response time commitments
115///
116/// ## Answer Quality Standards
117/// - **Timeliness**: Prompt response within established timeframes
118/// - **Completeness**: Comprehensive answers addressing all query aspects
119/// - **Accuracy**: Verified and current information provision
120/// - **Clarity**: Clear and understandable answer format
121///
122/// ## Best Practices
123/// - **Response Time**: Timely processing and response delivery
124/// - **Complete Resolution**: Comprehensive answers avoiding follow-up queries
125/// - **Documentation**: Proper documentation of answer rationale
126/// - **Follow-up**: Proactive follow-up on complex query resolutions
127///
128/// ## See Also
129/// - Swift FIN User Handbook: Answer Field Specifications
130/// - MT n96 Message Standards: Answer Message Types
131/// - Query Processing Guidelines: Answer Quality Standards
132/// - Field 75 Documentation: Query Field Specifications
133
134#[derive(Debug, Clone, Serialize, Deserialize, PartialEq, SwiftField)]
135pub struct Field76 {
136    /// Answer information
137    ///
138    /// Format: 6*35x - Up to 6 lines of 35 characters each
139    /// Contains structured responses to queries, codes, and descriptive information
140    /// Used to provide clarifications, status updates, and detailed transaction information
141    #[component("6*35x")]
142    pub information: Vec<String>,
143}
swift_mt_message/fields/field76.rs

swift_mt_message/fields/
field76.rs
