Rossum’s data extraction billing has a complex structure. But, a major part of Rossum’s subscription is the volume allowance for document processing. This article explains exactly when and how Rossum charges for a document or a page.

The basic rule of Rossum’s data extraction billing is that we charge for documents or pages processed by our platform. That is, we count each document or page that you import into Rossum. Also, the data capture configuration determines the exact billing mode. Let’s look at some specific examples.

Which documents or pages are billled

A document or page is billed when it is processed by Rossum’s AI Engine. That means when the document goes from importing state to review, confirmed, or exported state for the first time, depending on the configured automation level. (Documents that end up in the failed_import state are not billed.)

For per-page billing, we charge for all document pages (regardless of which pages contain captured data). However, this only applies to the configured maximum number of pages per document processed by the AI Engine (32 pages by default).

Currently, the duplicate documents are processed by AI Engine and therefore you will be billed for such documents.

Extraction billing for line items

Billing for document processing with line item extraction is applied differently than for document processing without line item extraction. The extraction schema configuration determines such a distinction. 

Let’s say a table (“multivalue tuple” in Extraction schema terminology) is configured as part of the schema. In such a case billing for the document or page as undergoing line item extraction applies (regardless of whether line items are eventually found on the document or page). 

The “tax_details” table is an exception because it does not count as line items.

Limiting data extraction to first N pages

You can instruct Rossum only to capture data from the first N pages. In this case, we will only charge for those first N pages. 

You can set this limit over the API on a Queue object by setting attribute rir_params to f.e. effective_page_count=1 if you would like to limit the extraction only to the first page.

Moving documents to another queue

If documents are routed to another queue, Rossum does not charge again for processing the documents or their pages. It refers to both situations in which documents are automatically routed to another queue based on captured data and situations in which users manually move documents to another queue.