Reports shows how capture is going: how much arrives and is finished, where work waits, how productive operators are, how well classification and extraction work, and whether exports arrive. Use the ready-made reports, build your own, save them for yourself or your team, download them, and have them e-mailed every day, week or month.
Open it from Reports in the left-hand menu. The dashboard's own Performance figures are explained further down.
Who can use it
| Permission | What it allows |
|---|---|
Module.Reports |
Run reports, build custom reports, save them for yourself or share them with your own roles, download them and schedule your own reports. The Administrator, Supervisor, Operator and Verifier roles have it from the start. |
Reports.Manage |
Also share reports with everyone or with any role, and change, delete or schedule anyone's saved reports. Administrators and Supervisors have it from the start. |
Some reports need an extra permission: Deleted batches and pages, discarded changes reads the audit log and needs Admin.Audit.
Every report only reads batches of the Batch Setups your roles may use — also reports someone else shared with you, and also scheduled reports (they run with their owner's rights). So two people can see different numbers in the same report. See Users, roles and permissions.
Run a report
- Click Reports in the menu.
- Find the report under Built-in reports: type in Find a report, or click a category.
- Click the report. It runs straight away with its usual period.
- Change the parameters and click Run.
| Parameter | What it does |
|---|---|
| Period | Today, yesterday, the last 7, 30 or 90 days, this or last week, month or year, your own dates, or all dates. Weeks start on Monday. Days follow the server's time zone. |
| Per | For reports over time: one row per hour, day, week or month. |
| Batch Setups | Only these Batch Setups. Choose none for all you can use. Ctrl+click chooses several. |
| Operator | Only work of people whose user name contains this text. |
| Queue | Only this workflow step (module). |
Each report shows only the parameters it uses.
The result
- A chart (bars or a line) for reports where a picture helps. Point at a bar or point to see its value.
- A table with a row count and the time the report was made. Click a column heading to sort by it; click again to reverse. Long results show 200 rows at a time: click Show more rows.
- A yellow note when the report had to stop early, for example "Only the first 5,000 rows are shown". Choose a shorter period or fewer Batch Setups.
Download or print
Click Export and choose:
| Format | What you get |
|---|---|
| Excel (.xlsx) | The table with a bold, frozen header row and filter buttons; numbers are numbers. A second sheet About lists the report, its parameters and when it was made. Printed pages have the title and DocView Capture by DocView.AI at the top and page numbers at the foot. |
| CSV | The table as comma-separated text in UTF-8 (opens in Excel with accents intact). It holds only the table, so other systems can read it. |
| A printable table with the title, the parameters, the time it was made and page numbers. Wide reports are landscape. Long text in a cell is shortened with "…". Every page carries the DocView Capture by DocView.AI brand at the top and its credit at the foot. | |
| Your browser's print, without the menu and the parameters. |
Downloads are recorded in the audit log as ReportExported.
Built-in reports
| Report | Category | What it shows |
|---|---|---|
| Batches received and completed | Volume | Batches and pages received, and batches, documents and pages completed, per hour, day, week or month. |
| Volume by Batch Setup | Volume | Batches, documents and pages received per Batch Setup, with how many are finished. |
| Pages per month (licence) | Volume | Batches, documents and pages per month, against the licence's monthly page limit. |
| Throughput per workflow step | Workflow and queues | Per step: batches, pages, documents and fields finished, average minutes per batch and errors. |
| Work waiting in each queue | Workflow and queues | Open batches per queue and step now: waiting, open by someone, suspended, in error, and the average and longest wait. |
| Open batches by age (SLA) | Workflow and queues | Every unfinished batch, oldest first: where it is, since when, how old, who has it open. |
| Turnaround time by Batch Setup | Workflow and queues | Time from receiving a batch to finishing its export: average, median, fastest, slowest, and the share finished within 24 hours. |
| Errors, suspensions and rejections | Workflow and queues | Every error in a step, every suspension and rejection, with who and why. |
| Batches in error or suspended now | Workflow and queues | Batches stopped right now, with the reason and attempts. |
| Operator productivity | People | Per person: batches, pages scanned, documents and fields, hours with batches open, documents and fields per hour, minutes per batch, and the active hours with rates per active hour. |
| Operator work per step | People | The same per person and step. |
| Operator performance | People | One row per person across preparation and every manual step: active hours, % of target, output and rates, rescans, values changed after them, rejections (Operator performance). |
| Operator effort on field values | People | Per person and step: field values changed, characters keyed, edits (Levenshtein distance) and the OCR accuracy of the values they worked on (Effort on field values). |
| Effort per field (OCR against people) | Quality | Per Batch Setup and field: how often people changed what OCR read, in which steps, the edits needed and the OCR accuracy (Effort on field values). |
| Operator performance per day | People | The same per person and day. |
| Preparation | People | Per person and client: boxes prepared, working and paused hours, pages scanned from them, minutes per 100 pages, documents per hour, exceptions (Preparation station). |
| Boxes in preparation now | People | Who is preparing which box, since when, and whether they are paused. |
People reports show everyone's work only to users with Reports.People; others see their own work only.
| Classification accuracy | Quality | Per document type: classified automatically, classified or changed by people, flagged for review, average confidence. |
| Extraction confidence and corrections per field | Quality | Per field: values found automatically, average confidence, values below the field's threshold or not valid, keyed by people, and changed by people. |
| Quality check results and rescans | Quality | Pages checked, passed and failed, batches sent back to Scan, and the most common reason. |
| Rejected documents | Quality | Documents operators rejected (they are not exported), with the reason. |
| Batches by channel | Import and export | Batches received by browser upload, scanning, watched folders, e-mail and the REST API. |
| Import sources | Import and export | Watched folders and mailboxes: on or off, last checked, batches imported and the last error. |
| Export results per destination | Import and export | Per export destination: delivered, failed and waiting, attempts, last delivery and the last problem. |
| Deleted batches and pages, discarded changes | Audit | Who deleted batches or pages, and who discarded changes. Needs Admin.Audit. |
How the figures are counted
- Reports by period count batches received (created) in the period. Batches received and completed and Turnaround time count batches finished in the period too, and the history-based reports (throughput, errors, people) count what happened in the period.
- Time worked counts only while a person has a batch open, from opening it to moving it on, at most 8 hours per batch. Steps finished without opening them (for example releasing a scan) count, without time.
- Changed by people counts every change of a value by a person (old and new values are in the audit log); changes by the DocView Worker do not count.
- Deleted batches no longer count in reports by Batch Setup. Their history stays and is shown to people who may see every Batch Setup. Keep archived batches and batch history long enough for the periods you report on; see Archive and retention.
Build a custom report
On Reports, click New custom report.
Data and period: choose what to report on, the period and the Batch Setups.
Report on One row per Batches Batch: name, Batch Setup, queue, step, state, channel, pages, documents, received, finished, exported, error, turnaround and age. Also its batch fields (index fields). Documents Document: batch, document type, classification and confidence, review state, reject reason, pages. Also its document fields (index fields), for example the invoice number. Pages Page: size, resolution, blank, side, quality check result and reason, OCR confidence. Field values Value of a batch, document or table field: value, confidence, below threshold, valid, entered by, verified by. Batch history Event in a batch's life: when, what happened, step, by whom, message, duration. Export deliveries Batch and export destination: delivered, failed or waiting, attempts, message. The period applies to when the batch was received, or for batch history to when the event happened.
Columns: click Add column for each column. For each, choose the field and optionally:
- a summary: Count, Count different, Total, Average, Lowest or Highest. As soon as one column has a summary, the rows are grouped by the other columns. For example "Batch Setup" + "Count of Batch" + "Total Pages" gives batches and pages per Batch Setup;
- for dates, a period (per hour, day, week, month or year) to group by, for example pages per month;
- your own heading.
Use the arrows to change the order and × to remove a column.
Filters (optional): click Add filter, choose a field, a condition (is, is not, contains, starts with, is more than / after, is empty…) and a value. Every filter must match. Dates compare by whole days: "Received is 2026-09-30" is any time that day.
Sort (optional): choose columns and directions. Without a sort, rows are newest first, and grouped rows are in order of their grouping columns.
Set Rows at most (up to 10,000) and a Chart (bars or a line of the summary columns).
Click Preview. If a column or filter does not fit, a red message says why, for example a total of a text field.
Click Save (see below) or Export.
Fields marked * (age, waiting time, turnaround) and comparisons on index fields are worked out after reading. Summaries read at most 100,000 rows; the report says so when there were more. Narrow the period or add filters.
Tip: "Average Turnaround (hours)" per "Batch Setup" per "Finished (per month)" on Batches makes a monthly service-level report. "Count of Batch" per "Document type" on Documents with the filter "Classified is Manual" shows which types people correct most.
Save and share reports
Click Save on a report or in the builder.
- Give it a name and, if you like, a description.
- Choose who can see and run it:
- Only me;
- People in my roles (with
Reports.Manage: People in these roles), and tick the roles; - Everyone who uses reports (only with
Reports.Manage).
- Click Save.
Saving a built-in report keeps its parameters, so "Volume by Batch Setup, last month, Invoices only" is one click away. Relative periods move on: "Last 7 days" always means the 7 days up to the day you run it.
Saved reports are listed at the top of Reports: My reports and Shared with me (people with Reports.Manage see Other people's reports, all of them). Only the owner and people with Reports.Manage can change or delete a saved report; everyone else can open it, change the parameters for one run and Save as… a copy of their own. To change a saved custom report, click the pencil (Edit) to open it in the builder; others get Copy and change.
Saving, changing and deleting reports is recorded in the audit log as ReportSaved, ReportChanged and ReportDeleted.
Send a report by e-mail on a schedule
The DocView Worker can run a saved report on a timetable and e-mail it as Excel, PDF or CSV. An administrator must first set up e-mail under Settings › E-mail (see Settings).
- Save the report and open it.
- Under E-mail this report on a schedule, choose Every day, Every week (and the day) or Every month (and the day; day 31 means the last day of shorter months), the time, the format, and the e-mail addresses (separated by commas).
- Click Add schedule.
Times are in the server's time zone and follow summer time. The report runs with its owner's current rights and the saved parameters, so a "Last 7 days" report always covers the week before it is sent. The e-mail lists the parameters and the number of rows, with the report attached.
On each schedule:
| Button | What it does |
|---|---|
| Send now | Runs and sends the report straight away, to check the e-mail and the file. The next scheduled time does not change. |
| Pause / Resume | Stops and restarts sending. |
| Delete | Removes the schedule; the report stays saved. |
The schedule shows the Next time and the Last result: sent, or failed with the reason (for example an SMTP error, or "The report's owner no longer has an active account" when the owner's account was switched off). The last ten sendings are listed under Last sent. Reports › Schedules lists every schedule of your reports, or with Reports.Manage every schedule.
Several DocView Workers can run at the same time: each sending is claimed by one DocView Worker, so nobody gets the report twice. If no DocView Worker is running, due schedules are sent when one starts again. See DocView Workers.
Dashboard performance figures
The Performance report on the dashboard shows similar figures at a glance: how many pages go through, how many batches need no manual work, how confident extraction is, and how productive operators are. Choose Last 24 hours, 7 days or 30 days above it. It counts only batches of the Batch Setups you may use.
Key figures
Six tiles sit at the top of the report. "Completed" means the batch finished its export and was archived in the period.
| Tile | What it shows |
|---|---|
| Completed batches | Batches that finished in the period, with their number of documents under it. |
| Pages | Pages in those batches, with the average per hour (24 hours) or per day (7 and 30 days). |
| Straight-through | The share of completed batches that nobody had to open in a manual checking step. |
| Avg. field confidence | The average extraction confidence of the fields of batches created in the period. |
| Avg. time to complete | The average time from creating a batch to finishing it, in minutes or hours. |
| Errors | How many times batches failed in a step. This includes errors that were retried successfully (incl. retried). The tile turns red when there are errors. |
Straight-through processing rate
The straight-through processing (STP) rate is the most important measure of automation. A completed batch counts as straight-through when nobody opened it in a Quality check, Classification, Index / Validate or Verify step. This happens when classification and extraction were confident and valid, so the workflow skipped those steps.
To raise the rate:
- improve classification rules or train the classifier (see Classifier training);
- add or improve finders and validation rules (see Finders and zones and Validation rules);
- check that manual steps are set to be skipped when there is nothing to do (see Workflow).
Average field confidence
Confidence is a value from 0% to 100% that extraction gives each value it finds. A low average often points to poor image quality or to finders that match the wrong text. Check scan profiles and image cleanup first.
Pages completed per hour or day
The bar chart shows Pages completed per hour for the last 24 hours, or per day for 7 and 30 days. Hover over a bar to see its pages, documents and batches. The label in the middle shows the highest bar.
Use it to see your busy times, and to check that DocView Workers keep up at peak hours. If pages pile up in automatic steps at peak times, add DocView Worker capacity. See DocView Workers.
Operator productivity
This table shows the people who worked in manual steps (for example Classification, Index or Verify) during the period:
| Column | Meaning |
|---|---|
| User | The operator. |
| Docs | Documents they completed. |
| Fields | Fields they completed. |
| Docs/h | Documents per hour. |
| Fields/h | Fields per hour. |
How time is counted: time counts only while the user has a batch open, from opening it to moving it on. Time a batch waits in a queue does not count. Each batch counts for at most 8 hours, so a batch left open overnight does not spoil the figures.
The table has a row filter and an Export button for Excel (.xlsx) or CSV.
Tip: Compare operators on the same kind of work. Documents with many fields or line items take longer, so fields per hour is fairer than documents per hour for mixed work.
When nobody worked in a manual step in the period, the table says "No manual review or indexing in this period."
Errors by step
When there were errors, a list shows how many happened in each step, for example OCR, separation & classification or PDF generation & export.
- Errors in export usually mean a destination could not be reached, for example a network share or a web service.
- Errors in OCR often mean missing language data or cloud OCR keys. See OCR engines and languages.
Open the Batch Manager with the Error state to read each message and retry.
Where the figures come from
The report is calculated from the batches and their batch history, which every workflow step writes. It is not a separate data store.
- The figures are up to date each time you open the dashboard or change the period.
- Batches that were deleted no longer count. With the default Delete archived batches after (days) of 30, the 30-day view is at its limit. Keep archived batches longer if you need full 30-day figures.
- If Batch history retention (days) is shorter than the period, older history is missing from the straight-through rate and productivity figures.
See Archive and retention for these settings.