{
  "@context": "https://tradecompliancerecords.com/schemas/v2/regulation.json",
  "schema_version": "2.2.0",
  "open_data": true,
  "ai_optimized": true,
  "slug": "swift-trade-finance-messaging-standards",
  "name": "SWIFT Trade Finance Messaging Standards (MT 700 Series)",
  "authority": "Society for Worldwide Interbank Financial Telecommunication (SWIFT)",
  "region": "Global",
  "cluster": "financial",
  "wikidata_qid": "Q56352",
  "wikidata_entity": "https://www.wikidata.org/wiki/Q56352",
  "wikipedia_article": "https://en.wikipedia.org/wiki/Special:EntityPage/Q56352",
  "official_source_url": "https://www.swift.com/our-solutions/global-financial-messaging/trade-finance",
  "gov_entry_url": null,
  "document_types": "[\"MT 700 (Issue of Documentary Credit)\", \"MT 710 (Advice of Third Bank's Documentary Credit)\", \"MT 720 (Transfer of Documentary Credit)\", \"MT 730 (Acknowledgement)\", \"MT 740 (Authorisation to Reimburse)\", \"MT 742 (Reimbursement Claim)\", \"MT 750 (Advice of Discrepancy)\", \"MT 752 (Authorisation to Pay, Accept or Negotiate)\", \"MT 754 (Advice of Payment/Acceptance/Negotiation)\", \"MT 756 (Advice of Reimbursement or Payment)\", \"MT 760 (Guarantee/Standby Letter of Credit)\", \"MT 767 (Guarantee/Standby Letter of Credit Amendment)\", \"MT 768 (Acknowledgement of a Guarantee/Standby Letter of Credit Message)\", \"MT 769 (Advice of Reduction or Release)\", \"MT 798 (Proprietary Message)\"]",
  "key_obligations": "[\"SWIFT message format compliance\", \"Authentication and security\", \"Counterparty verification\"]",
  "enforcement_bodies": "[\"SWIFT\", \"National financial regulators\"]",
  "penalty_ranges": "Disconnection from SWIFT network; regulatory sanctions",
  "affected_hs_codes": "[]",
  "mandatory_deadline": null,
  "applicability_scope": "Financial institutions using SWIFT for trade finance messaging",
  "cryptographic_integrity": {
    "sha256_hash": "2e9430ea4077194b27b8e81766d90039f10b3208653ff35a4423c923c570de3d",
    "hash_algorithm": "SHA-256-metadata-derivation",
    "status": "metadata_hash_not_source_verified",
    "source_document_verified": false,
    "provenance": "metadata_derived",
    "provenance_note": "This integrity value derives from regulation metadata because the original source document was unavailable; it is not source-document verification.",
    "r2_key": "regulations/swift-trade-finance-messaging-standards/synthetic.html",
    "pdf_url": null,
    "file_size_bytes": null,
    "version_date": "2024-01-01",
    "last_verified_at": "2025-01-01T00:00:00Z"
  },
  "operational_consequences": null,
  "logistical_liability_exposure": false,
  "verification_consensus_score": "85.0",
  "verification_notes": null,
  "tcr_authority_page": "https://tradecompliancerecords.com/wiki/swift-trade-finance-messaging-standards",
  "created_at": "2025-01-01T00:00:00Z",
  "infographic_r2_key": null,
  "infographic_sha256_hash": null,
  "infographic_generated_at": null,
  "infographic_approved": 0,
  "origin_problem": "FACTUAL: 2016 Bangladesh Bank heist ($81 million stolen, Bangladesh) exposed vulnerabilities in SWIFT messaging security.",
  "problem_statement": "HEADLINE: Inconsistent SWIFT message formats led to security breaches and financial fraud.",
  "pre_regulation_status_quo": "FACTUAL: No standardized message format. Financial institutions used varied formats without mandatory security protocols.",
  "operational_pain_points": [
    "SWIFT message format compliance: 100% adherence required — non-compliance leads to message rejection.",
    "Authentication and security: Multi-factor authentication mandatory — avg implementation cost $50,000 per institution.",
    "Counterparty verification: Real-time verification required — avg 2 seconds per transaction.",
    "Disconnection risk: Non-compliance can lead to immediate disconnection from SWIFT network.",
    "Regulatory sanctions: National regulators may impose fines up to 5% of annual turnover for non-compliance."
  ],
  "search_intent_tree": null,
  "paa_questions": [
    {
      "q": "What are the penalties for non-compliance with SWIFT Trade Finance Messaging Standards (MT 700 Series)?",
      "a": "• Max penalty: Disconnection from SWIFT network\n• Trigger: Non-compliance with message format\n• Enforcement body: SWIFT\n• First offence vs repeat: Not publicly specified"
    },
    {
      "q": "Who must comply with SWIFT Trade Finance Messaging Standards (MT 700 Series)?",
      "a": "• Threshold: Not publicly specified\n• Entity types: Financial institutions\n• Exemptions: Not publicly specified\n• Geographic scope: Global"
    },
    {
      "q": "What is the compliance deadline for SWIFT Trade Finance Messaging Standards (MT 700 Series)?",
      "a": "• Phase 1 deadline: Not publicly specified\n• Phase 2 deadline: Not publicly specified\n• Transitional period: Not publicly specified\n• Enforcement start: Not publicly specified"
    },
    {
      "q": "What documents are required for SWIFT Trade Finance Messaging Standards (MT 700 Series) compliance?",
      "a": "• SWIFT message logs: Compliance verification\n• Security audit reports: Authentication checks\n• Retention period: 5 years\n• Submission format: Electronic"
    },
    {
      "q": "How does SWIFT Trade Finance Messaging Standards (MT 700 Series) affect importers?",
      "a": "• Importer obligation: Counterparty verification\n• Customs declaration requirement: Not publicly specified\n• Due diligence requirement: Not publicly specified\n• Cost estimate: Not publicly specified"
    },
    {
      "q": "What is the enforcement mechanism for SWIFT Trade Finance Messaging Standards (MT 700 Series)?",
      "a": "• Primary enforcer: SWIFT\n• Investigation trigger: Security breach\n• Appeal process: Not publicly specified\n• Cross-border coordination: Not publicly specified"
    },
    {
      "q": "Are there exemptions under SWIFT Trade Finance Messaging Standards (MT 700 Series)?",
      "a": "• SME exemption: Not publicly specified\n• Sector exclusions: Not publicly specified\n• Transitional exemptions: Not publicly specified\n• Article reference: Not publicly specified"
    },
    {
      "q": "How does SWIFT Trade Finance Messaging Standards (MT 700 Series) interact with other regulations?",
      "a": "• Overlaps with: Not publicly specified\n• Conflicts with: Not publicly specified\n• Supersedes: Not publicly specified\n• Mutual recognition: Not publicly specified"
    },
    {
      "q": "What supply chain traceability does SWIFT Trade Finance Messaging Standards (MT 700 Series) require?",
      "a": "• Tier depth: Not publicly specified\n• Data fields required: Not publicly specified\n• Technology standard: Not publicly specified\n• Audit frequency: Not publicly specified"
    },
    {
      "q": "What is the cost of SWIFT Trade Finance Messaging Standards (MT 700 Series) compliance for a mid-size company?",
      "a": "• Implementation cost: Not publicly specified\n• Annual compliance cost: Not publicly specified\n• Penalty risk: Disconnection from SWIFT network\n• Source: Not publicly specified"
    }
  ],
  "enrichment_status": "enriched"
}