swift_mt_message/fields/field75.rs
1use serde::{Deserialize, Serialize};
2use swift_mt_message_macros::SwiftField;
3
4/// **Field 75: Queries**
5///
6/// ## Purpose
7/// Specifies query information in Swift MT message query/response workflows. This field
8/// contains structured query requests used to obtain clarification, additional information,
9/// or status updates regarding original transactions. Essential component of the Swift
10/// query/answer ecosystem enabling systematic information exchange between financial institutions.
11///
12/// ## Format Specification
13/// - **Swift Format**: `6*35x`
14/// - **Structure**: Up to 6 lines of 35 characters each
15/// - **Content**: Structured query information with codes and descriptive text
16/// - **Character Set**: Standard SWIFT character set with narrative formatting
17///
18/// ## Business Context Applications
19/// - **Query Messages**: Core component of MT n95 series query messages
20/// - **Transaction Clarification**: Requesting clarification on previous transactions
21/// - **Status Requests**: Obtaining status updates on pending transactions
22/// - **Information Requests**: Requesting additional transaction details
23///
24/// ## Message Type Integration
25/// ### Query Message Types (MT n95 Series)
26/// - **MT 195**: Customer payment queries (Category 1)
27/// - **MT 295**: Treasury queries (Category 2)
28/// - **MT 395**: Foreign exchange queries (Category 3)
29/// - **MT 495**: Securities queries (Category 4)
30/// - **MT 595**: Securities lending queries (Category 5)
31/// - **MT 695**: Commodity queries (Category 6)
32/// - **MT 795**: Documentary credits queries (Category 7)
33/// - **MT 895**: Traveler's checks queries (Category 8)
34/// - **MT 995**: Cash management queries (Category 9)
35///
36/// ## Network Validation Requirements
37/// - **Line Length**: Maximum 6 lines of 35 characters each
38/// - **Character Set**: Must use valid SWIFT character set
39/// - **Query Structure**: Should follow structured query format
40/// - **Reference Consistency**: Must align with transaction references
41/// - **Code Validation**: Query codes must be properly formatted
42///
43/// ## Query Types and Codes
44/// ### Common Query Categories
45/// - **Status Inquiries**: Transaction processing status requests
46/// - **Clarification Requests**: Details about transaction elements
47/// - **Amendment Queries**: Questions about transaction modifications
48/// - **Settlement Queries**: Settlement status and timing inquiries
49/// - **Documentation Requests**: Additional documentation requirements
50///
51/// ### Structured Query Format
52/// ```logic
53/// :75:QUERY TYPE: [Description]
54/// Additional details on subsequent lines
55/// Reference information
56/// Specific questions or requirements
57/// ```
58///
59/// ## Query Processing Workflow
60/// ### Query Initiation
61/// - **Field 75**: Contains the specific query information
62/// - **Field 20**: Transaction reference being queried
63/// - **Field 21**: Related reference for context
64/// - **Message Context**: MT n95 message type for specific category
65///
66/// ### Query Content Guidelines
67/// - **Clear Identification**: Specific transaction or issue identification
68/// - **Structured Format**: Organized query information
69/// - **Complete Details**: Sufficient detail for proper response
70/// - **Reference Accuracy**: Correct references to original transactions
71///
72/// ## Regional Considerations
73/// - **Global Standards**: Consistent query format across all SWIFT regions
74/// - **Local Practices**: Regional variations in query handling procedures
75/// - **Time Zone Coordination**: Query timing considerations for global operations
76/// - **Language Standards**: English language requirement for international queries
77///
78/// ## Error Prevention Guidelines
79/// - **Reference Verification**: Confirm transaction references are accurate
80/// - **Query Clarity**: Ensure query is clear and specific
81/// - **Format Compliance**: Follow established query format standards
82/// - **Complete Information**: Provide sufficient detail for effective response
83///
84/// ## Related Fields Integration
85/// - **Field 76**: Answers (corresponding response field)
86/// - **Field 20**: Transaction Reference (query context)
87/// - **Field 21**: Related Reference (additional context)
88/// - **Field 79**: Narrative (extended query information)
89///
90/// ## Compliance Framework
91/// - **Audit Documentation**: Complete query documentation for audit trails
92/// - **Regulatory Requirements**: Meeting regulatory query and response requirements
93/// - **Customer Service**: Providing effective customer query resolution
94/// - **Operational Efficiency**: Streamlined query processing workflows
95///
96/// ## Query Resolution Process
97/// - **Query Receipt**: Acknowledgment and initial processing
98/// - **Investigation**: Detailed investigation of query subject
99/// - **Response Preparation**: Formulation of comprehensive answer
100/// - **Answer Delivery**: MT n96 message with Field 76 response
101///
102/// ## Best Practices
103/// - **Timely Processing**: Prompt query acknowledgment and response
104/// - **Complete Responses**: Comprehensive answers addressing all query points
105/// - **Reference Management**: Accurate reference tracking throughout process
106/// - **Documentation**: Proper documentation of query/answer cycles
107///
108/// ## See Also
109/// - Swift FIN User Handbook: Query Field Specifications
110/// - MT n95 Message Standards: Query Message Types
111/// - Query Processing Guidelines: Best Practices for Query Handling
112/// - Field 76 Documentation: Answer Field Specifications
113
114#[derive(Debug, Clone, Serialize, Deserialize, PartialEq, SwiftField)]
115pub struct Field75 {
116 /// Query information
117 ///
118 /// Format: 6*35x - Up to 6 lines of 35 characters each
119 /// Contains structured query requests, codes, and descriptive information
120 /// Used to request clarification, status updates, or additional transaction details
121 #[component("6*35x")]
122 pub information: Vec<String>,
123}