PARSER GUIDES

Document Classifiers

Document Classifiers

Sort mixed document batches and send each file to the right parser

Document Classifiers help when one upload contains different kinds of files, such as invoices, receipts, bank statements, and purchase orders. A classifier reads each document, decides what type it is, and sends it to the parser that should extract the data.

Use a classifier when your team receives mixed document batches and does not want to sort the files manually before uploading.

Before you start

Document Classifiers are available on Pro and higher plans. Teams using an active full-feature trial can also create and use classifiers during the trial.

Create the parsers you want to route documents to first. For example:

• Invoice parser for invoices and receipts
• Bank statement parser for bank statements
• Purchase order parser for purchase orders

The classifier does the sorting. The target parser still does the data extraction, exports, reviews, and webhooks.

Credit usage

Classification costs 0.1 credit per document classified.

• A document that is not routed still uses 0.1 credit for classification.
• A routed document uses 0.1 credit for classification, then the target parser uses its normal page-processing credits.
• If Split Before Routing creates several documents, each split document is classified separately.
• If Split with AI is enabled, its additional per-page charge also applies.

See Credits and Billing for examples and combined costs.

Create a classifier

1. In the sidebar, click Document Classifiers.

2. Click Create classifier.

3. Enter a clear Name, such as "Claims intake" or "Mixed finance documents".

4. Under Routing rules, add at least one rule:

• If document is: enter the document type, such as "Invoice".
• Send to: choose the parser that should process that document type.

5. Click Add rule for each additional document type.

6. Under Unmatched documents, choose what should happen when no rule matches:

• Do not process keeps the document in the classifier list as not routed.
• Send to parser sends unmatched documents to one default parser.

7. Click Create classifier.

Example setup

For a folder with invoices, bank statements, and purchase orders, create rules like this:

If document is

Send to

Invoice

Invoice parser

Bank statement

Bank statement parser

Purchase order

Purchase order parser

For Unmatched documents, choose Do not process if you want to review anything that does not match your rules.

Upload documents to a classifier

1. Open Document Classifiers.

2. Select the classifier from the left column.

3. Click Upload Documents.

4. Upload the mixed documents together.

The classifier sorts the files automatically. Routed documents appear in the classifier list with the parser they were sent to. Documents that do not match any route stay in the classifier list as not routed.

Send documents by email

Each classifier has its own email address, just like a parser. Copy the email address from the classifier header and send attachments to it.

Classifier emails process attachments as separate documents. If Split Before Routing is enabled, PDF attachments are split before routing.

Split before routing

Use Split Before Routing when one PDF may contain several documents. For example, one PDF might contain an invoice, a bank statement, and a purchase order.

In classifier settings:

1. Open the classifier.

2. Click Settings.

3. Find Split Before Routing.

4. Choose how PDFs should be split.

5. Click Save changes.

After splitting, each split document is routed through the classifier rules separately.

Edit routing rules

1. Open Document Classifiers.

2. Select the classifier.

3. Click Settings.

4. Update Routing rules or Unmatched documents.

5. Click Save changes.

You can add, remove, and reorder rules. Rule labels should match the document types you expect users to upload.

What happens after routing

• Routed documents are sent to the selected parser for extraction.
• Not routed documents stay in the classifier list so you can review them.
• Failed routing stays visible in the classifier list with the failure reason.
• Exports, reviews, webhooks, and extracted data are handled by the target parser after routing.

Tips

• Use simple rule names, such as "Invoice", "Receipt", or "Bank statement".
• Create one parser for each document type before creating the classifier.
• Use Do not process for unmatched documents when you want a human to review unexpected files.
• Use Split Before Routing for large PDFs that contain multiple document types.

Next steps

• Creating Parsers - Create the parsers used in routing rules
• Uploading Documents - Upload files from the app
• Send Documents by Email - Send documents by email
• API Access - Upload to classifiers through the API