swift_mt_message/fields/
field79.rs

1use serde::{Deserialize, Serialize};
2use swift_mt_message_macros::SwiftField;
3
4///   **Field 79: Narrative**
5///
6/// ## Purpose
7/// Provides extended narrative information for various Swift MT messages, offering
8/// comprehensive text capacity for detailed transaction descriptions, explanations,
9/// and supplementary information. This field supports extensive documentation
10/// requirements across multiple message types, enabling complete transaction
11/// context and detailed communication between financial institutions.
12///
13/// ## Format Specification
14/// - **Swift Format**: `35*50x`
15/// - **Structure**: Up to 35 lines of 50 characters each
16/// - **Total Capacity**: Maximum 1,750 characters
17/// - **Character Set**: Standard SWIFT character set with extended line capacity
18///
19/// ## Business Context Applications
20/// - **Extended Documentation**: Comprehensive transaction documentation
21/// - **Free Format Messages**: Core narrative field for MT 199 and MT 299 messages
22/// - **Query/Answer Support**: Extended information for query and answer messages
23/// - **Cancellation Reasons**: Detailed explanations in cancellation messages
24/// - **Amendment Details**: Complete amendment descriptions and justifications
25///
26/// ## Message Type Integration
27/// ### Primary Applications
28/// - **MT 199**: Free format customer messages
29/// - **MT 196**: Customer payment answers (optional extended narrative)
30/// - **MT 292**: Treasury cancellation (reason details)
31/// - **MT 296**: Treasury answers
32/// - **MT 299**: Free format treasury messages
33/// - **MT 705**: Documentary credits (as Field 79Z)
34/// - **Various n96**: Answer messages requiring extended explanations
35/// - **Various n99**: Free format messages across categories
36///
37/// ## Network Validation Requirements
38/// - **Line Capacity**: Maximum 35 lines of 50 characters each
39/// - **Character Set**: Must use valid SWIFT character set
40/// - **Format Restrictions**: Prohibited content and special character rules
41/// - **Code Validation**: Special validation for specific content codes
42/// - **Reference Patterns**: Restricted slash patterns for security
43///
44/// ## Content Categories and Applications
45/// ### Transaction Documentation
46/// - **Detailed Descriptions**: Comprehensive transaction explanations
47/// - **Business Context**: Complete business rationale and background
48/// - **Regulatory Information**: Compliance and regulatory details
49/// - **Amendment Justifications**: Detailed reasons for transaction changes
50///
51/// ### Reason Codes and Explanations
52/// #### Common Reason Categories (from MT 292 integration)
53/// - **AGNT**: Agent/Intermediary related issues
54/// - **AM09**: Wrong amount scenarios
55/// - **COVR**: Cover payment problems
56/// - **CURR**: Currency-related issues
57/// - **CUST**: Customer-related matters
58/// - **CUTA**: Cut-off time violations
59/// - **DUPL**: Duplicate transaction handling
60/// - **FRAD**: Fraudulent transaction detection
61/// - **TECH**: Technical processing problems
62/// - **UPAY**: Unpaid transaction situations
63///
64/// ### Free Format Communication
65/// - **Institutional Messages**: Communication between financial institutions
66/// - **Customer Communications**: Detailed customer information
67/// - **Operational Instructions**: Complex operational procedures
68/// - **Exception Explanations**: Detailed exception handling explanations
69///
70/// ## Special Content Validation
71/// ### Prohibited Content Patterns
72/// - **Security Restrictions**: Certain slash patterns prohibited for security
73/// - **Code Validation**: `/REJT/` and `/RETN/` codes have specific rules
74/// - **Reference Restrictions**: Invalid reference patterns must be avoided
75/// - **Format Compliance**: Structured content must follow established patterns
76///
77/// ### Content Structure Guidelines
78/// ```logic
79/// :79:CATEGORY: [Description]
80/// Detailed explanation across multiple lines
81/// Additional context and information
82/// Supporting details and references
83/// Conclusion or summary information
84/// ```
85///
86/// ## Regional Considerations
87/// - **Global Standards**: Consistent narrative format across all SWIFT regions
88/// - **Local Requirements**: Regional regulatory narrative requirements
89/// - **Language Standards**: English language requirement for international messages
90/// - **Cultural Considerations**: Appropriate cultural sensitivity in narrative content
91///
92/// ## Content Quality Standards
93/// ### Clarity and Completeness
94/// - **Clear Communication**: Unambiguous and clear narrative content
95/// - **Complete Information**: Comprehensive coverage of relevant details
96/// - **Logical Structure**: Well-organized information presentation
97/// - **Professional Tone**: Appropriate professional communication style
98///
99/// ### Technical Requirements
100/// - **Character Limits**: Adherence to line and total character limits
101/// - **Format Compliance**: Proper formatting and structure
102/// - **Content Relevance**: Relevant and appropriate information only
103/// - **Reference Accuracy**: Accurate references and cross-references
104///
105/// ## Error Prevention Guidelines
106/// - **Content Review**: Thorough review of narrative content before transmission
107/// - **Format Verification**: Confirmation of proper format compliance
108/// - **Character Validation**: Verification of valid character set usage
109/// - **Length Checking**: Confirmation of line and total length compliance
110///
111/// ## Related Fields Integration
112/// - **Field 75**: Queries (extended query information)
113/// - **Field 76**: Answers (extended answer information)
114/// - **Field 77A/B**: Other narrative fields (complementary information)
115/// - **Field 20/21**: References (narrative context)
116/// - **Field 72**: Sender to Receiver Information (institutional context)
117///
118/// ## Compliance Framework
119/// - **Regulatory Documentation**: Meeting regulatory narrative requirements
120/// - **Audit Trail**: Complete narrative documentation for audit purposes
121/// - **Customer Communication**: Effective customer information provision
122/// - **Legal Documentation**: Proper legal and contractual documentation
123///
124/// ## Best Practices
125/// ### Content Development
126/// - **Structured Approach**: Organized and logical information presentation
127/// - **Completeness**: Comprehensive coverage of all relevant aspects
128/// - **Clarity**: Clear and unambiguous communication
129/// - **Professional Standards**: Appropriate professional communication style
130///
131/// ### Quality Assurance
132/// - **Content Review**: Multi-level review of narrative content
133/// - **Technical Validation**: Format and character set validation
134/// - **Relevance Check**: Confirmation of content relevance and appropriateness
135/// - **Compliance Verification**: Regulatory and standard compliance checking
136///
137/// ## See Also
138/// - Swift FIN User Handbook: Narrative Field Specifications
139/// - Free Format Message Standards: MT 199 and MT 299 Guidelines
140/// - Content Guidelines: Narrative Content Best Practices
141/// - Regulatory Standards: Narrative Documentation Requirements
142
143#[derive(Debug, Clone, Serialize, Deserialize, PartialEq, SwiftField)]
144pub struct Field79 {
145    /// Extended narrative information
146    ///
147    /// Format: 35*50x - Up to 35 lines of 50 characters each (1,750 total characters)
148    /// Contains comprehensive narrative information, explanations, and documentation
149    /// Used for detailed transaction descriptions, reasons, and extended communication
150    #[component("35*50x")]
151    pub information: Vec<String>,
152}
swift_mt_message/fields/field79.rs

swift_mt_message/fields/
field79.rs
