AI Split Detection

The AI Split Detection action examines a single multi-page document, detects the boundaries between separate transactions inside it, and splits it into a new Record per transaction — automatically, as part of a workflow.


Use it when several distinct documents have been scanned or uploaded together as one file. A common case is a stack of invoices from different vendors captured in a single PDF: the action recognizes where one invoice ends and the next begins and breaks the pile apart so each invoice becomes its own Record.


Unlike keyword or barcode splitting, boundaries are found by content, not by separator sheets or page counts. For invoices the action identifies each transaction by its Vendor and Invoice Number; when two consecutive pages share the same identity they stay together, and when the identity changes a new Record starts.


AZURE ONLY: This is a vision-based AI action and runs only on Azure-hosted / AI-licensed sites.


How it differs from AI Classification (Split)

Both actions can break up a document, but they answer different questions:

  • AI Classification decides what each page is against a list of categories you supply, and splits pages within a single Record by type.
  • AI Split Detection decides where one transaction ends and the next begins by reading the documents' own identity — no category list — and creates a separate new Record for each transaction it finds.

Reach for Split Detection when the incoming file is really many independent documents of the same kind (many invoices, many statements) that each deserve their own Record.


What it works on

  • The action splits the active Record's document. The active document is used, or the Record's first document if none is active.
  • No OCR is required. The action reads the pages with vision AI directly.
  • Very large files are not supported — extremely long documents (roughly 100+ pages) will fail loudly rather than split partially.


Options

The action's settings are grouped into four tabs.


Document

  • New Document Cat/Sub/Name — The Category, SubCategory and Name applied to each split Record's document. Leave blank to use the defaults.


Splitting

  • Commit Split — Controls what happens with the transactions the AI detects.
    • On (default): the action splits out a new Record per detected transaction and routes them automatically.
    • Off: the action does not commit the split. It stages the detected splits for a later Auto-Split Commit action (#91), so you can review or run other steps first.


AI Level

  • Quality — Vision split detection needs a capable model, so only two levels are offered:
    • Standard — good for most standard business documents.
    • Advanced — higher token cost; best for poor scans, dense pages, or subtle boundaries. 


Economy is intentionally not offered for this action as it would not do a good enough job.


Advanced

  • Extra Instructions — Free-form hints that describe boundary rules specific to your documents, for example "A remittance stub belongs with its invoice" or "A new PO number does NOT start a new invoice." Identity is driven by content (for invoices, Vendor + Invoice Number); when in doubt the AI keeps pages together rather than over-splitting.


TIPS

  1. If you want a person to review the detected splits before Records are created, turn Commit Split off and add an Auto-Split Commit action (#91) later in the process.
  2. Use Extra Instructions to teach the AI about attachments that belong to a transaction (remittance stubs, backup pages, terms sheets) so they aren't broken off into their own Record.
  3. The action favors keeping pages together when a boundary is ambiguous — if it is under-splitting, add an instruction describing what actually starts a new document; if it is over-splitting, describe what does not.
  4. Start with Standard quality and only move to Advanced if boundaries are being missed on poor scans or unusually dense pages.


NOTE ON (AI): Detecting splits with vision AI consumes tokens and may incur extra fees. Workflow tokens are billed separately from End-User or Admin tokens — check with your sales rep for more information.