Digicust
Web AppPricingBlogContact
  • 👋Welcome to Dexter
  • Guides
    • 🔎Getting started
    • ⬆️Upload Cases
    • 📚Upload Master Data
    • 📚Bulk Edit Master Data
    • 🔧Configure Execution Strategies
    • 🧳Manage Projects
  • Working with Digicust
    • 1️⃣Onboarding Checklist
    • 2️⃣Checklist Recurring Client
    • 3️⃣Checklist Walk-in Clients
  • Features
    • 🔌Integrations
      • Riege Scope
      • BEO
      • FORMAT
      • DHF Zolaris
      • AEB
      • LDV
      • DBH
      • Dakosy
      • SFTP
      • Web Hooks
      • Asycuda
    • 🔎Tariff Classification
      • Auto-fix tariff numbers
      • Automatic classifications
      • Bulk material classifications
    • 🪄AI-Generated Goods Descriptions
    • ✨Rules & Templates
    • ⬆️Upload Scenarios
    • 📃Document Splitting
    • 🛠️Data Extraction
      • Emails
      • Invoices
      • Waybills
      • Packing Lists
      • Delivery Notes
      • Export Declarations
      • Temporary Storage Documents
      • ATR Certificates
      • EUR1
      • Weighing Certificates
      • Excel Files
    • 🪄Data Enrichment & Customs Coding
      • Freight Cost Distribution
      • Preference Check
      • Procedure Detection
      • Automatically Add Negative Codings
      • Document Type Codes
      • Special Unit Measures
      • Currency Conversion
      • Address Normalization
    • 📚Master Data
      • Material Data
      • Stakeholder Data
    • ✔️Data Validation
      • Stakeholder Validation
      • Consistency Check
    • 📧Custom Events
    • Splitting Customs Cases
  • Developer API
    • Getting Started
    • Uploading a Case
    • Fetching a Case
    • Tariff Classificaiton
    • Type Definitions
    • Full Upload API Documentation
    • Full Generic API Documentation
  • Use-Cases
    • Import
      • From Invoices, Emails, Master Data
      • From Export Declarations and Above
      • From Waybills, Turkish Export Declarations and Above
      • From Temporary Storage, Transit Declarations and Above
      • From Delivery Notes, Packing Lists and Above
      • From Preference Documents (A.TR, EUR.1, etc.) and Above
      • Create A.TR from Export Declaration
    • Export
      • From Invoices, Emails, Master Data
      • From Invoices, Packing Lists, Delivery Notes
    • Transit
      • From Invoices, Emails, Export Declarations
    • Intrastat
      • From Invoices
Powered by GitBook
On this page
  • Create New Customs Cases Per Recipient
  • Create New Customs Cases As Mentioned In Email
  • Important Notes

Was this helpful?

  1. Features

Splitting Customs Cases

PreviousCustom EventsNextGetting Started

Last updated 5 months ago

Was this helpful?

Create New Customs Cases Per Recipient

Setting: createNewCustomsCasesPerRecipient.active

When enabled, this setting automatically creates separate customs cases for each unique recipient when multiple invoices with different recipients are present in a case.

Behavior

  • The system identifies unique recipients across all invoices in the case

  • For each additional recipient (after the first):

    • Creates a new customs case

    • Copies relevant documents to the new case:

      • All invoices for that specific recipient

      • Associated export lists for the recipient

      • All non-recipient-dependent documents

    • Appends the recipient name to the case reference

  • The original case retains:

    • Documents for the first recipient

    • All non-recipient-dependent documents

    • Updated reference with the first recipient's name

Use Cases

  • Processing shipments to multiple recipients

  • Maintaining separate customs documentation per recipient

  • Organizing cases by recipient for better tracking

Create New Customs Cases As Mentioned In Email

Setting: createNewCustomsCasesAsMentionedInEmail.active

When enabled, this setting creates separate customs cases based on shipment references mentioned in email documents, particularly when multiple invoices are referenced.

Behavior

  • The system scans email documents for shipment references and associated invoice numbers

  • For each additional reference (after the first):

    • Creates a new customs case

    • Includes invoices matching the reference based on:

      • Invoice number

      • Buyer order number

      • Seller order number

    • Sets the shipment reference as the case reference

  • The original case retains:

    • Documents associated with the first reference

    • Updated reference matching the first shipment reference

Use Cases

  • Processing multiple shipments mentioned in a single email

  • Organizing cases by shipment reference

  • Handling consolidated shipping documentation

Important Notes

  1. Both settings require multiple invoices to be present in the case to trigger

  2. New cases inherit the execution strategy from the original case

  3. The system automatically initiates data normalization for newly created cases

  4. Processing may take up to 10 minutes per case creation

  5. Each new case maintains its own unique reference based on the splitting criteria

Splitting cases