{
  "@context": "https://tradecompliancerecords.com/schemas/v2/regulation.json",
  "schema_version": "2.2.0",
  "open_data": true,
  "ai_optimized": true,
  "slug": "us-cbp-importer-security-filing-2009",
  "name": "US CBP Importer Security Filing (ISF 10+2)",
  "authority": "US CBP",
  "region": "US",
  "cluster": "customs",
  "wikidata_qid": null,
  "wikidata_entity": null,
  "wikipedia_article": null,
  "official_source_url": "https://www.ecfr.gov/current/title-19/chapter-I/part-149",
  "gov_entry_url": null,
  "document_types": null,
  "key_obligations": null,
  "enforcement_bodies": null,
  "penalty_ranges": null,
  "affected_hs_codes": null,
  "mandatory_deadline": null,
  "applicability_scope": "Ocean cargo importers must file ISF 24 hours before vessel departure — 10 data elements with hash-verifiable document integrity.",
  "cryptographic_integrity": {
    "sha256_hash": "beb941e020026795325409d482435c5955887db3b5c332ca4915e786eea8d315",
    "hash_algorithm": "SHA-256",
    "status": "cryptographically_hardened",
    "source_document_verified": true,
    "provenance": "source_document",
    "provenance_note": "SHA-256 derived from an ingested source document.",
    "r2_key": "regulations/us-cbp-importer-security-filing-2009/us-cbp-importer-security-filing-2009.html",
    "pdf_url": "https://tcr-vault.tradecompliancerecords.com/regulations/us-cbp-importer-security-filing-2009/us-cbp-importer-security-filing-2009.html",
    "file_size_bytes": 10596,
    "version_date": "2026-06-07",
    "last_verified_at": "2026-06-07T03:01:02.146Z"
  },
  "operational_consequences": null,
  "logistical_liability_exposure": false,
  "verification_consensus_score": "0",
  "verification_notes": null,
  "tcr_authority_page": "https://tradecompliancerecords.com/wiki/us-cbp-importer-security-filing-2009",
  "created_at": "2024-01-01",
  "infographic_r2_key": null,
  "infographic_sha256_hash": null,
  "infographic_generated_at": null,
  "infographic_approved": 0,
  "origin_problem": "2001 September 11 attacks (2,977 deaths, US) exposed vulnerabilities in cargo security and led to increased scrutiny on import processes.",
  "problem_statement": "US lacked comprehensive pre-arrival cargo data, risking national security.",
  "pre_regulation_status_quo": "No mandatory pre-arrival cargo data submission. Importers could file minimal information, leading to security risks.",
  "operational_pain_points": [
    "ISF filing: 10 data elements required per shipment, including importer of record and consignee number.",
    "Filing deadline: 24 hours before vessel departure, strict adherence required.",
    "Data integrity: Must use hash-verifiable document integrity for submissions.",
    "Non-compliance risk: Potential for cargo holds and increased inspection rates.",
    "Technology requirement: Electronic submission via Automated Commercial Environment (ACE) portal."
  ],
  "search_intent_tree": null,
  "paa_questions": [
    {
      "q": "What are the penalties for non-compliance with US CBP Importer Security Filing (ISF 10+2)?",
      "a": "• Max penalty: $5,000 per violation\n• Trigger: Late or inaccurate filing\n• Enforcement body: US CBP\n• First offence vs repeat: Not publicly specified"
    },
    {
      "q": "Who must comply with US CBP Importer Security Filing (ISF 10+2)?",
      "a": "• Threshold: Not publicly specified\n• Entity types: Ocean cargo importers\n• Exemptions: Not publicly specified\n• Geographic scope: US"
    },
    {
      "q": "What is the compliance deadline for US CBP Importer Security Filing (ISF 10+2)?",
      "a": "• Phase 1 deadline: Not applicable\n• Phase 2 deadline: Not applicable\n• Transitional period: Not applicable\n• Enforcement start: January 26, 2009"
    },
    {
      "q": "What documents are required for US CBP Importer Security Filing (ISF 10+2) compliance?",
      "a": "• ISF Submission: Pre-arrival cargo data\n• Retention period: 5 years\n• Submission format: Electronic via ACE portal"
    },
    {
      "q": "How does US CBP Importer Security Filing (ISF 10+2) affect importers?",
      "a": "• Obligation: File 10 data elements 24 hours before vessel departure\n• Customs declaration requirement: Accurate and timely submission\n• Due diligence or traceability requirement: Not publicly specified\n• Cost estimate: Not publicly specified"
    },
    {
      "q": "What is the enforcement mechanism for US CBP Importer Security Filing (ISF 10+2)?",
      "a": "• Primary enforcer: US CBP\n• Investigation trigger: Non-compliance detected\n• Appeal process: Not publicly specified\n• Cross-border coordination: Not publicly specified"
    },
    {
      "q": "Are there exemptions under US CBP Importer Security Filing (ISF 10+2)?",
      "a": "• SME exemption: Not publicly specified\n• Sector exclusions: Not publicly specified\n• Transitional exemptions: Not publicly specified\n• Article reference: Not applicable"
    },
    {
      "q": "How does US CBP Importer Security Filing (ISF 10+2) 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 US CBP Importer Security Filing (ISF 10+2) require?",
      "a": "• Tier depth: Not publicly specified\n• Data fields required: 10 key fields\n• Technology standard: Not publicly specified\n• Audit frequency: Not publicly specified"
    },
    {
      "q": "What is the cost of US CBP Importer Security Filing (ISF 10+2) compliance for a mid-size company?",
      "a": "• Implementation cost: Not publicly specified\n• Annual compliance cost: Not publicly specified\n• Penalty risk: $5,000 per violation\n• Source: Not publicly specified"
    }
  ],
  "enrichment_status": "enriched"
}