Document Review and Validation is the human-in-the-loop stage where AI-extracted data is examined, corrected, and approved or rejected by authorised users. This capability sits at the centre of the Docupath document lifecycle - between ingestion/extraction and export - and is accessed through the Document Queue and the Dual-Pane Review Screen.
The module provides status-based queue management, configurable column views, data enrichment indicators, confidence colour-coding, and a structured action bar for document disposition.
How It Works
The Document Queue
The Document Queue is the primary workspace for managing documents across their lifecycle. It presents all documents in a tabular queue organised by status tabs - Pending, Validated, Approved, and Rejected - with each tab reflecting a distinct stage of the document lifecycle.
Top Panel Features
The top of the Review Screen provides navigation and filtering controls. Users can redirect to the Upload Screen, search documents by name or content, and apply filters by region, urgency, document type, and organisation. Active filters are highlighted with a red bubble indicator for visibility.
Tab View and Status Indicators
Each tab contains sub-statuses that provide granular visibility into document state:
Pending tab: Processing (AI still extracting), Pending (ready for review), Failed (unsupported format or corrupted file)
Validated tab: Documents reviewed by a Validator but awaiting final disposition
Approved tab: Approved, Sent (pushed to external system), Acknowledged (external system confirmed), Not Acknowledged (sent but unconfirmed)
Rejected tab: Documents rejected manually by reviewers or automatically by business rules, each with a required rejection reason
The Dual-Pane Review Screen
When a reviewer opens a document, the dual-pane layout presents AI-extracted data on the left and the original document on the right. This side-by-side design enables direct comparison between raw input and processed output.
Left Panel - Extracted Data
Displays structured data in Docupath Internal Format (DIF), with a dynamic layout that adapts to the document type being processed. Fields are annotated with enrichment indicators showing whether values were verified from organisation data, AI-enriched, AI-standardised, or AI-transformed. Confidence colour-coding provides at-a-glance quality assessment.
The left panel also Includes expandable fields and layouts such as line-item tables, which can be expanded to view more information at a glance.
Right Panel - Original Document
Shows the original uploaded document in its native format (PDF, image, XML, etc.) with page navigation, zoom, rotation, text extraction, and Select Mode for drawing bounding boxes to capture data directly from the document.
The right panel also includes a dropdown to view attachments if any are present.
Smart Field-to-Document Linking
Clicking an extracted field in the left panel highlights the corresponding section in the original document. Conversely, selecting text in the document copies it into the active field - enabling rapid correction without manual typing.
Data Enrichment Layers
During processing, Docupath applies multiple enrichment types to extracted data:
Enrichment Type | Description |
Verified Org Data - Updated | Corrected using verified organization settings |
Verified Org Data - Autofilled | Populated from verified organization settings |
AI Enriched | Inferred contextually from document content |
AI Standardized | Formats normalized (dates, currency, identifiers) |
AI Transformed | Business rules and transformations applied |
What Search and Filters Match
The search bar on the Review Screen matches the document name, the extracted content, and the trading party values currently held against the document.
Trading party values are read from the assigned trading party record, so the value shown after enrichment is the one that is searchable. Searching for the value the AI originally extracted does not find the document once a trading party has replaced it.
Changes a reviewer makes on the review screen are searchable as well. Editing a party field, or using Switch back to detected value to restore what was originally extracted, makes that value findable. This covers every party field, including country, name, VAT number and GLN number.
The Regions filter follows the same rule. It matches the country on the assigned trading party, a country a reviewer changed on the document, and falls back to the document's own country when no trading party is assigned.
Footer Action Bar
At the bottom of the Review Screen, the Footer Action Bar provides the primary disposition controls:
Approve: Finalizes the document and optionally routes it to external systems. Available to Admins, Managers, Reviewers and Reviewer and Validators
Validate: Moves the document to Validated status. Available to Admins, Managers, users with the Validator or Reviewer and Validator role
Reject: Requires a rejection reason, which is logged for audit transparency. Available to the same roles that can approve
Close: Exits the document without applying changes
The footer also includes tab switching between the Input Tab (original document) and the Destination Tab (machine-readable output preview, e.g., XML).
Who Can Do What
Any role that can open documents sees the queue, open a document, reprocess it and download it. What differs is disposition and deletion:
Action | Admin | Manager | Reviewer | Validator | Reviewer and Validator |
See the document queue | Yes | Yes | Yes | Yes | Yes |
Approve or reject | Yes | Yes | Yes | No | Yes |
Validate | Yes | Yes | No | Yes | Yes |
Reprocess | Yes | Yes | Yes | Yes | Yes |
Download | Yes | Yes | Yes | Yes | Yes |
Delete | Yes | Yes | No | No | No |
Deleting documents is available to admins and managers only. Users with the Reviewer, Validator or Reviewer and Validator role can reprocess and download, but the delete action is greyed out for them with the tooltip "You don't have permission to perform this action".
Custom roles follow the same pattern: any action the role does not allow appears greyed out rather than hidden, so users can always see the full set of actions a document supports.
Checks That Run on Approve and Validate
Approve and Validate are not unconditional. Before either takes effect, Docupath checks the document against two configurations:
Empty critical fields. Fields marked Critical in Customize captured fields must carry a value. Criticality is read from the customizations that apply to the document right now, so it always reflects the current configuration.
Failed custom validations. Conditions written as instructions in Instruction Builds and compiled onto the document when it was extracted.
If anything fails, the action is blocked and a Validations failed modal lists what did not pass under two headings, Critical fields and Custom validations, so the reviewer can correct the document and try again. A critical field inside a table is checked on every extracted row and the modal names the blank rows; a table with no extracted rows never blocks approval.
Save and Reject are never blocked by these checks. A reviewer can always save changes, or reject the document, while critical fields are empty or a validation is failing.
Documents already in Approved status are not re-checked. A later configuration change never reopens them or changes their status, so an approved document can legitimately hold an empty critical field.
Bulk Actions
For high-volume environments, the Document Queue supports bulk operations on selected documents: Delete, Download, Reprocess, and Review. Bulk review accelerates throughput for repetitive workflows. Bulk Delete follows the same rule as single-document deletion and is available to admins and managers only.
Supported Configurations and Options
Configuration | Options |
Column visibility | Show/hide columns (Document Number, Uploaded Time, Document Type, Primary Party, Document Date, Status, Action) |
Column labels | DUP (duplicate), URG (urgent) |
Tab views | Pending, Validated (add-on), Approved, Rejected |
Filters | Regions, Documents, Organizations, Urgency, Document types, Status, Date, Validated by |
Search | By document name, document content, assigned trading party values, and reviewer changes to party fields |
Bulk actions | Delete (admins and managers only), Download, Reprocess, Review |
Validation lifecycle | Standard (Pending → Approved/Rejected) or Extended (Pending → Validated → Approved/Rejected) |
Approval checks | Empty critical fields (Customize captured fields) and custom validations (Instruction Builds); both block Approve and Validate only |
Other Technical Specifications
Parameter | Detail |
Maximum files for bulk review | 50 documents at once |
Supported original document formats in right panel | PDF, DOCX, DOC, XLSX, XLS, XML, JPG, PNG, TIFF, TIF, HEIC, HTML, TXT |
Data presentation format | Docupath Internal Format (DIF) |
Enrichment indicators | Hover-accessible info bubbles showing original vs. enriched values |
Right panel features | Page navigation, zoom in/out, rotate, view extracted text, Select Mode with bounding boxes |
Notes
Deleting documents, in single or bulk form, is available to admins and managers only
Reprocessing and downloading are available to every role that can open documents, including the Reviewer, Validator and Reviewer and Validator roles
Actions a role cannot perform are greyed out with a tooltip rather than hidden, so a user can see what the document supports and who to ask
Reprocessing a document resets all manual field edits - including manually assigned trading parties - and returns the document to Processing status
The DUP and URG column labels require their respective features to be active
Documents in Failed status (under the Pending tab) cannot be reviewed and require user action (re-upload or format correction)
Bulk review is limited to 50 documents per operation
Filter configurations are saved for each user and persist across browser sessions.
A blocked Approve or Validate is shown as a Validations failed modal listing the empty critical fields and the failed custom validations. Saving changes and rejecting the document stay available throughout.
Critical field marks are evaluated against the current configuration, so a customization change can block a document that was approvable yesterday. Custom validations are fixed at extraction, so a document must be reprocessed before a new or changed validation applies to it.
Auto Review runs the same two checks before auto-approving. A document that fails either is marked Failed by Auto Review and left in the queue for a person; it is not moved to Rejected, and it follows the manual approval path from then on.
