MT700 Field 39A: Field Contradicts Other Fields
Introduction
Field 39A of the SWIFT MT700 records the Percentage Credit Amount Tolerance as 2n/2n — two digits for the positive tolerance and two digits for the negative tolerance. The field is optional. Because 39A defines how far drawings may vary from the 32B amount and how that variation relates to the 39B maximum, a conflict between 39A and neighbouring fields is a recurring source of credit discrepancies.
This guide examines how 39A contradicts other MT700 fields, why those contradictions arise, and how to resolve them.
Failure Modes
- 39A upper bound exceeds 39B maximum. When field 39B (Maximum Credit Amount) is present and the 32B amount plus the 39A positive tolerance exceeds 39B, the credit allows a drawing above its own ceiling.
- 39A present with no 32B base. 39A is a percentage of the 32B amount; without 32B the tolerance is unanchored.
- 39A and 39B both used inconsistently. Where both appear, their interaction must keep the maximum drawable amount within 39B; conflicting values contradict Article 30.
- Tolerance digits malformed. The
2n/2nrule requires two digits each side; a single digit or a non-numeric entry breaches the field format. - 39A contradicts a "no tolerance" instruction elsewhere. If the credit states the amount must not vary, an open 39A contradicts that instruction.
Resolution
- Confirm 32B is present and correct before applying any 39A percentage.
- Compute 32B × (1 + positive tolerance%) and confirm it does not exceed 39B where 39B is present.
- Where both 39A and 39B appear, reconcile them so the maximum drawable amount equals the lower of the two constraints.
- Apply the
2n/2nformat strictly — two numeric digits before and after the slash. - Remove 39A where the credit explicitly forbids tolerance, to avoid self-contradiction.
- Use MT707 to correct tolerance or maximum where the two conflict.
- Return contradictory instructions to the applicant for a reconciled tolerance and maximum.
- Note the Article 30 basis in the credit file so the tolerance scheme is auditable.
Conclusion
Field 39A sets the allowable swing around 32B. Its contradictions with 39B and 32B are preventable by computing the upper drawable amount and confirming it stays within the maximum. Article 30 provides the rule that makes the reconciliation meaningful.
FAQ
- Is 39A mandatory? No. It is Optional.
- What format does 39A use?
2n/2n— two digits for positive tolerance and two for negative, separated by a slash. - Can 39A exceed 39B? The drawable amount after applying 39A must not exceed 39B; otherwise the credit is inconsistent.
- Which UCP article governs 39A? Article 30 (Tolerance in credit amount, quantity, unit prices).
- What if 39A is present but 32B is missing? 39A has no base to apply to; the credit is defective and must be corrected.
Source Notes
Context only. SWIFT MT700 field 39A specification (SWIFT SR2018 Category 7): format 2n/2n, Optional, definition (Percentage Credit Amount Tolerance), MT700 Usage Rules (MT 701 extension) and network rules C2/C3/C4 referenced. UCP 600 relationship: Article 30 (Tolerance in credit amount, quantity, unit prices). UCP 600 text in provided dossier; citations only.
Article 30 provides the rule that makes the reconciliation meaningful.
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| UCP 600 | Article 30 | Tolerance in Credit Amount, Quantity and Unit Prices | Binary determination (compliant/discrepant) |
← Scroll horizontally to see all columns
Quick Reference Summary
- No reference captured.
Compliance Checklist
Get the Full LC Compliance Checklist
15-point pre-submission checklist covering UCP 600, ISBP 745, and SWIFT MT700 fields. Free PDF download.
No spam. Unsubscribe anytime.
DraftLC generates compliant MT700 Field 39A — so you never face this failure mode.
DraftLC drafts your LC with UCP 600-compliant terms and flags conflicts during drafting — before documents reach the bank.
No credit card required · See how DraftLC drafts compliant credits