Split

Under Review

This article is currently under review. Some content may be incomplete or inaccurate.

Category: Processing

The Split activity groups the transaction's pages into separate documents. A single upload (or batch of uploads) often contains several documents, and Split decides where each one begins and ends.

Configuration

Setting	Description	Default
Enable Splitting	When set to No, splitting is skipped and every file becomes one document (the One document per file mode).	Yes
Split Mode	How pages are grouped into documents (see below).	One document per file
Document Classes	Candidate document classes used by intelligent splitting.	(optional)
Split Fields	Fields that help the model decide boundaries.	(optional)
Guidelines	Extra instructions for intelligent splitting.	(optional)
Window Size	How many consecutive pages the model looks at in one go when deciding where a document ends. A larger window gives more context around a possible boundary and costs more per window.	2
Window Step	How far the window moves between checks. A step of 1 checks every boundary; a larger step is cheaper but can miss a split.	1

Intelligent splitting always analyzes every page of the transaction. There is no setting to look at only the first few pages, because a page the model never sees could not be placed in any document.

Split modes

Mode	Behavior
One document per file	Each file added to the transaction becomes one document, keeping its page order. Documents never span files.
One document per page	Every page becomes its own single-page document.
All pages in one document	The whole transaction is a single document, in the order the files were added.
Intelligent LLM splitting	The model detects document boundaries from content. All pages are analyzed as one stream, so a document may span several files.
Intelligent LLM splitting within files	The model detects document boundaries inside each file. File borders are always document borders, so documents never span files.

Pages always have to be grouped into documents, so there is no "no split" outcome. Turning Enable Splitting off simply pins the mode to One document per file; the mode selector is shown locked to that value.

Per-file split policies

API clients and connectors can pin a split constraint on individual files at upload time, overriding the project mode for just those files. A file can be marked as exactly one document, or as self-contained (one or more whole documents, analyzed inside the file only). The email import connector uses this to keep the email body separate from its attachments. See Per-File Split Policies.