How Page Consumption Works
This guide explains how pages are counted as documents move through the system, so you can understand what contributes to your page consumption.
General Principle
Every page of every document ingested into the system is counted. The system makes every effort to count each page only once, even as a document is processed, converted, or moved through multiple steps.
Counting Rules by Document Type
Scanned or paper documents Every physical page that is scanned and ingested counts as one page.
Electronic documents (Word, Excel, TXT, CSV, etc.) An electronic document counts as 1 page, regardless of its actual page count when opened or printed, unless it is converted to an image (see below).
Electronic documents converted to an image If an electronic document is converted to an image (for example, to a PDF or TIFF), it is counted at its converted page count rather than as 1 page.
Web forms A web form is counted at the number of pages in its snapshot or mapped PDF.
Attachments to a web form
-
Attachments to a web form are appended to the form and counted at their own page count.
-
If an attached file is an electronic document, it is converted using the standard conversion steps and counted at its converted page count.
Workflow-Related Consumption
Some workflow nodes affect page consumption because they create new documents or add content to existing ones.
Nodes that create new processes When a workflow node creates a new process, the standard counting rules above apply to that new process. This includes:
-
Create Generator
-
SQL / CSV
Nodes that add to an existing process Some workflow nodes inject documents or pages into a process that's already running, which adds to that process's page count. This includes:
-
iPaaS
Things to Watch For
-
Workflow loops: Workflows that are built to loop can reprocess the same documents repeatedly, causing pages to be counted more than intended. Review any looping logic in your workflows to avoid unexpected consumption.
-
Adding pages without considering impact: Some workflows create unexpected consumption by adding pages without accounting for the effect on your volume.
-
High-volume batch loading: Loading large document volumes into a workflow without considering the impact can also cause overconsumption. This can additionally lead to throughput issues, since large volumes of older work need to finish processing before newer work can begin.
Daily Volume Limits
Daily page limits depend on your licensing:
-
Customers using GlobalSearch as their document repository have a default limit of 10,000 pages per day for documents flowing through capture processes.
-
Customers licensed only for GlobalCapture products have daily limits enforced at their licensed tier.
If you have a demonstrated need for more volume, you have options:
-
Customers with a demonstrated need for additional page volume may request an increase up to 25,000 pages per day.
-
Customers who need more than 25,000 pages per day require additional Boost licensing. At this level you are not volume-capped, but the system may not be able to process more than this volume in a single day.
-
Boost licensing may also be needed if you need to process pages faster, even if your daily volume is below the 25,000-page threshold.
If you exceed your licensed volume limit, the system will continue to accept new work, but will not process it until licensed volume becomes available. That work remains queued rather than being rejected or lost.
Monitoring Your Page Volume
You can keep track of your page consumption in a few ways:
-
Check the Registration tab in the GlobalCapture admin interface, or visit http://dashboard.mysquare9.com .
-
If you're licensed for iPaaS, you can deploy a workflow that monitors and notifies you of capture page volume on whatever cadence you need.
InquireAI Volume
InquireAI has its own, separate consumption rules:
-
InquireAI volume is counted monthly, not daily.
-
InquireAI licensing limits apply to all customers, regardless of license configuration.
-
If you exceed your InquireAI volume limit, documents will not be processed — unlike standard capture volume, this work is not queued.
-
You can watch for this condition and configure your process to automatically retry when appropriate.
-
You also have the option to purchase one-time page volume on top of your monthly volume band. This is a good option if you're concerned about one-off spikes in volume, or want to ensure there's no work stoppage if you hit your limit.
-
-
As with capture volume, customers licensed for iPaaS may deploy a workflow to monitor and notify of InquireAI volume at whatever cadence you need.