Reviewing document detail and line items
How detail view is structured, which accounting and payment fields matter, and how operators correct OCR output.
The detail page is a working surface, not a read-only preview
The document detail screen exposes item details, amount blocks, payment blocks, and line items in one page. It also shows reject reasons, approval states, file metadata, and business-linked references.
Line items are connected to chart of accounts
The detail API fetches `line_items` together with linked `account_id` records. This makes document review part of the accounting pipeline rather than only an OCR correction task.
Reject handling is standardized
The UI includes predefined reject reasons such as low image quality, cropped files, unreadable text, missing data, duplicates, and wrong uploads.
That list is worth documenting because it shapes how operators classify quality issues and rework requests.
Continue with adjacent workflows
Uploading and classifying documents
What happens when a file is added, how business scoping works, and where the five document types appear across the product.
Document statuses, approvals, and archives
How list tabs and status mutations are wired, including processing, accurate, approval, and archive transitions.
Managing ready-for-payment priorities
How payment officers see urgent, medium, low, and unset queues after approvals are complete.