pub struct Field71A {
pub details_of_charges: String,
}
Expand description
§Field 71A: Details of Charges
§Overview
Field 71A specifies who bears the charges in SWIFT payment messages. This field indicates the party responsible for paying the various fees and charges associated with the payment transaction, including correspondent banking fees, intermediary charges, and beneficiary bank charges. The charge allocation is crucial for cost transparency and proper payment processing in international transfers.
§Format Specification
Format: 3!a
- 3!a: 3 alphabetic characters indicating charge bearer
- Character set: Alphabetic characters only (A-Z)
- Case: Typically uppercase
§Structure
OUR
│││
└┴┴─ Charge code (3 letters)
§Field Components
- Charge Code: Three-letter code indicating charge responsibility
- Must be exactly 3 alphabetic characters
- Standard codes defined by SWIFT
- Case-insensitive but typically uppercase
§Usage Context
Field 71A is used in:
- MT103: Single Customer Credit Transfer
- MT200: Financial Institution Transfer
- MT202: General Financial Institution Transfer
- MT202COV: Cover for customer credit transfer
- MT205: Financial Institution Transfer for its own account
§Business Applications
- Cost allocation: Determining who pays transaction fees
- Pricing transparency: Clear fee responsibility indication
- Correspondent banking: Managing charge arrangements
- Customer agreements: Implementing charge policies
- Regulatory compliance: Meeting charge disclosure requirements
- Payment processing: Automated charge handling
§Standard Charge Codes
§BEN (Beneficiary)
- Description: Beneficiary bears all charges
- Usage: All fees deducted from payment amount
- Impact: Beneficiary receives net amount after charges
- Common in: Incoming payments, salary transfers
§OUR (Ordering Customer)
- Description: Ordering customer bears all charges
- Usage: All fees paid separately by sender
- Impact: Beneficiary receives full payment amount
- Common in: Commercial payments, urgent transfers
§SHA (Shared)
- Description: Charges shared between parties
- Usage: Sender pays sending charges, beneficiary pays receiving charges
- Impact: Each party pays their respective bank’s fees
- Common in: Standard international transfers
§Examples
:71A:OUR
└─── Ordering customer bears all charges
:71A:BEN
└─── Beneficiary bears all charges
:71A:SHA
└─── Charges shared between parties
§Charge Code Details
-
OUR: Ordering customer pays all charges
- Sender bank charges: Paid by ordering customer
- Correspondent charges: Paid by ordering customer
- Beneficiary bank charges: Paid by ordering customer
- Result: Beneficiary receives full amount
-
BEN: Beneficiary pays all charges
- Sender bank charges: Deducted from payment
- Correspondent charges: Deducted from payment
- Beneficiary bank charges: Deducted from payment
- Result: Beneficiary receives net amount
-
SHA: Shared charge arrangement
- Sender bank charges: Paid by ordering customer
- Correspondent charges: Typically shared or negotiated
- Beneficiary bank charges: Paid by beneficiary
- Result: Beneficiary receives amount minus receiving charges
§Validation Rules
- Length: Must be exactly 3 characters
- Character type: Alphabetic characters only
- Case: Case-insensitive but normalized to uppercase
- Standard codes: Should use recognized SWIFT codes
- Required field: Must be present in applicable message types
§Network Validated Rules (SWIFT Standards)
- Must be exactly 3 alphabetic characters (Error: T15)
- Must use valid charge code (Error: T71)
- Code must be recognized by SWIFT network (Error: T72)
- Field is mandatory in applicable messages (Error: M71)
- Must be consistent with message type (Error: C71)
Fields§
§details_of_charges: String
Charge details code (3 characters)
Implementations§
Source§impl Field71A
impl Field71A
Sourcepub fn new(details_of_charges: String) -> Self
pub fn new(details_of_charges: String) -> Self
Create a new Field71A with the given charge code
Sourcepub fn charge_code(&self) -> &str
pub fn charge_code(&self) -> &str
Get the charge code
Sourcepub fn is_standard_code(&self) -> bool
pub fn is_standard_code(&self) -> bool
Check if this is a standard charge code
Sourcepub fn description(&self) -> &'static str
pub fn description(&self) -> &'static str
Get human-readable description of the charge code
Trait Implementations§
Source§impl<'de> Deserialize<'de> for Field71A
impl<'de> Deserialize<'de> for Field71A
Source§fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>where
__D: Deserializer<'de>,
fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>where
__D: Deserializer<'de>,
Deserialize this value from the given Serde deserializer. Read more
Source§impl SwiftField for Field71A
impl SwiftField for Field71A
Source§fn to_swift_string(&self) -> String
fn to_swift_string(&self) -> String
Convert field back to SWIFT string format
Source§fn validate(&self) -> ValidationResult
fn validate(&self) -> ValidationResult
Validate field according to SWIFT format rules
Source§fn format_spec() -> &'static str
fn format_spec() -> &'static str
Get field format specification
impl StructuralPartialEq for Field71A
Auto Trait Implementations§
impl Freeze for Field71A
impl RefUnwindSafe for Field71A
impl Send for Field71A
impl Sync for Field71A
impl Unpin for Field71A
impl UnwindSafe for Field71A
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Mutably borrows from an owned value. Read more