MT700 Field 71A — Charges Field Errors That Trigger Document Discrepancies

Introduction

A documentary credit's Field 71A — the Charges field in an MT700 SWIFT message — specifies which party bears the costs associated with the letter of credit. This field is an essential structural element: one wrong code, one missing instruction, or one misapplied rule on charge allocation, and the entire transaction collapses under UCP 600. Banks reject roughly 70% of first presentations due to discrepancies. A disproportionate share originates in the mismatch between what Field 71A declares and what the documents actually contain, or what UCP 600 Articles 13, 18, and 37 mandate. This guide isolates the failure modes, maps them to the operative regulatory language, and prescribes a deterministic resolution architecture.

Failure Mode Analysis

Failure Mode 1: Field 71A Code Mismatch

Mechanism: The issuing bank populates Field 71A with a charge code that contradicts the actual charge allocation in the documents. Common mismatches include:

• Field 71A = "OUR" (charges for applicant) but invoice shows charges deducted from proceeds
• Field 71A = "BEN" (charges for beneficiary) but documents show charges prepaid by applicant
• Field 71A = "SHA" (charges shared) but no mechanism for sharing exists in the documents

Regulatory violation: Direct contravention of UCP 600 Article 37(c) and Article 14(d). The discrepancy is structural: it exists in the credit's issuance, not in the beneficiary's presentation.

Consequence: The examining bank must refuse the presentation. Under Article 16(c)(ii), the refusal notice must cite the specific mismatch. The beneficiary has no cure period — the five-banking-day examination window under Article 14(b) is absolute.

Binary outcome: The beneficiary must reject the credit and request amendment, or proceed knowing the credit is unenforceable under UCP 600.

Failure Mode 2: Field 71A vs. Invoice Deduction Conflict

Mechanism: Field 71A allocates charges to the beneficiary ("BEN"), but the invoice does not reflect the deduction of these charges from the proceeds. The examining bank detects the mismatch between the credit's charge allocation and the invoice's value statement.

Regulatory violation: ISBP 745, paragraph C9 requires additional charges to be included within the value shown on the invoice. When Field 71A = "BEN" but the invoice shows the full contract value without deduction, the invoice conflicts with the credit's terms under UCP 600 Article 14(d).

Consequence: The examining bank refuses the presentation with a discrepancy citing the invoice value conflict. The beneficiary must either:
1. Amend the invoice to reflect the charge deduction, or
2. Request amendment of Field 71A to "OUR" or "SHA"

Systemic root cause: The beneficiary's accounting system calculates invoice amounts based on the contract value, not the credit's charge allocation. Field 71A is treated as an administrative field, not a structural constraint on the invoice.

Failure Mode 3: Field 71A vs. Transport Document Freight Discrepancy

Mechanism: Field 71A allocates freight charges to the applicant ("OUR"), but the transport document shows "freight collect" (indicating charges are for the consignee at destination). This creates a conflict between the credit's charge allocation and the transport document's freight terms.

Regulatory violation: ISBP 745, paragraph D30 allows flexibility in transport document charge statements but prohibits conflict with the credit's terms. When Field 71A = "OUR" but the transport document shows "freight collect," the examining bank detects a data conflict under UCP 600 Article 14(d).

Consequence: The examining bank refuses the presentation. The discrepancy is systemic: it originates in the mismatch between the credit's terms and the underlying contract's freight arrangement. The beneficiary must either:
1. Negotiate with the carrier to amend the transport document to "freight prepaid," or
2. Request amendment of Field 71A to reflect the actual freight arrangement

Binary outcome: The discrepancy is not cosmetic — it reflects a fundamental conflict in the transaction's charge structure.

Deterministic Resolution Architecture

Step 1: Pre-Validation of Field 71A Against the Credit's Charge Allocation

Before issuance, the issuing bank must verify that Field 71A is consistent with the credit's charge allocation clause. The rules:

• Field 71A = "OUR": Charges are for the account of the issuing bank. The beneficiary's presentation must not deduct charges from the proceeds.
• Field 71A = "BEN": Charges are for the account of the beneficiary. The invoice must reflect the deduction of these charges.
• Field 71A = "SHA": Charges are shared between the applicant and beneficiary. The credit must specify the allocation mechanism.

Validation checklist:
1. Does Field 71A match the underlying contract's charge arrangement?
2. Does the invoice reflect the charge allocation specified in Field 71A?
3. Does the transport document's freight statement conflict with Field 71A?
4. Are reimbursing bank charges allocated consistent with Article 13(b)(iv)?

Step 2: BIC-to-Charge Code Reconciliation

When Field 71A contains a charge code, the issuing bank must confirm that the code resolves to the correct allocation. Common errors:

• Using "OUR" when the contract allocates charges to the beneficiary
• Using "BEN" when the contract allocates charges to the applicant
• Using "SHA" without specifying the sharing mechanism

Resolution: Maintain a current charge code mapping table. Validate against the underlying contract before issuing the credit.

Step 3: Post-Issuance Field 71A Audit

When a beneficiary queries the charge allocation or when the nominated bank receives a presentation, the following audit sequence applies:

1. Identify the credit's charge allocation clause (Field 71A). Is it "OUR," "BEN," or "SHA"?
2. Extract the invoice's charge disclosure. Does the invoice reflect the charge allocation specified in Field 71A?
3. Apply the applicable ISBP 745 paragraph (C9, D30, or D31). Does the transport document's freight statement conflict with Field 71A?
4. If discrepancy detected: Issue a notice of refusal under Article 16(c), specifying the exact mismatch. Hold documents per Article 16(c)(iii)(a), (b), (c), or (d) as applicable.

Step 4: Amendment Protocol for Field 71A Errors

When a Field 71A error is discovered post-issuance:

1. The issuing bank must issue an amendment under UCP 600 Article 10.
2. The amendment must correct Field 71A to reflect the actual charge allocation.
3. The beneficiary must communicate acceptance or rejection of the amendment per Article 10(c).
4. If the beneficiary fails to communicate, a presentation that complies with both the original credit and the unaccepted amendment is deemed acceptance.
5. The confirming bank (if any) must be consulted separately per Article 10(b) — confirmation does not automatically extend to amendments.

Step 5: Interplay with Transferable Credits

Under UCP 600 Article 38(g), the transferred credit must accurately reflect the terms and conditions of the original credit, with limited exceptions. Field 71A in the transferred credit must allocate charges consistent with the original credit unless the transfer specifically modifies this field. The transferring bank must not alter Field 71A without explicit authorization, as doing so would change the credit's charge structure.

Conclusion

Field 71A is a structural field — it does not merely describe but defines the credit's charge allocation architecture. Errors in this field are not cosmetic discrepancies that can be waived or cured; they are systemic failures that invalidate the credit's charge structure or render presentations non-complying. The resolution is deterministic: verify Field 71A against the underlying contract before issuance, reconcile charge codes to legal allocations, and apply ISBP 745 paragraphs C9, D30, and D31 with mechanical precision. There is no ambiguity in these rules. There is only compliance or failure.

FAQ

Q1: Can Field 71A be left blank in an MT700?
A: Yes, but only in specific circumstances. When a credit is silent on charges, the default allocation under UCP 600 Article 37(c) applies: the issuing bank bears charges unless the credit explicitly allocates them to the beneficiary. However, leaving Field 71A blank creates ambiguity that may lead to discrepancies. Best practice is to specify the charge allocation explicitly.

Q2: What happens if Field 71A = "BEN" but the invoice does not deduct charges?
A: The presentation contains a discrepancy. ISBP 745, paragraph C9 requires additional charges to be included within the value shown on the invoice. When Field 71A allocates charges to the beneficiary but the invoice shows the full contract value without deduction, the invoice conflicts with the credit's terms under UCP 600 Article 14(d). The examining bank must refuse the presentation and cite the specific discrepancy under Article 16(c)(ii).

Q3: If Field 71A = "OUR" but the transport document shows "freight collect," is this a discrepancy?
A: Yes. ISBP 745, paragraph D30 allows flexibility in transport document charge statements but prohibits conflict with the credit's terms. When Field 71A allocates freight charges to the applicant ("OUR") but the transport document shows "freight collect" (indicating charges are for the consignee), the examining bank detects a data conflict under UCP 600 Article 14(d). The beneficiary must negotiate with the carrier to amend the transport document or request amendment of Field 71A.

Q4: Is a Field 71A error the beneficiary's responsibility?
A: No. Under UCP 600 Article 4(a), the credit is a separate transaction from the underlying contract. Under ISBP 745, Preliminary Considerations, paragraph v, "The applicant bears the risk of any ambiguity in its instructions to issue or amend a credit." The issuing bank is responsible for correctly populating Field 71A. If the field contains an error, the issuing bank must amend the credit. The beneficiary's obligation is limited to complying with the credit as issued.

Q5: Can Field 71A and Field 71B (Charges Detail) conflict?
A: Field 71B specifies the detailed charges (e.g., "COMMISSION USD 50"). Field 71A specifies the charge allocation. These are complementary fields — they do not directly constrain each other. However, the documents must satisfy both: the invoice must reflect the charge allocation specified in Field 71A (ISBP 745, C9) and must include the detailed charges specified in Field 71B. A conflict between the two fields (e.g., Field 71A = "BEN" but Field 71B shows charges for the applicant) creates an internal inconsistency in the credit that the issuing bank must resolve before issuance.