A document review system: from incoming files to confirmed imports
Keep the source file, fields to check, corrections and import result together. Follow a document through administration, review and operations.
A delivery note arrives by email. Administration enters its quantities in a spreadsheet, and operations copies them into another system. An extra page arrives later, but the two records may not both change. A document review system can connect intake, preparation, checking and import, with a status and owner for each file and corrections attached to the same record.
This guide focuses on the intake list, source comparison, review queue and import history that staff use each day. Extraction tools can suggest text and fields. Azure Document Intelligence, for example, recommends evaluating results and confidence scores for the intended use. The surrounding system still needs a clear owner for uncertain, missing and duplicate information.
Microsoft Learn — Document Intelligence accuracy and confidence
Make the intake list show who owns the work
Administration can upload a PDF, scan or email attachment and add its type, source and related order. The list shows receipt time, owner and states such as Preparing, Awaiting review, Needs information and Imported. Staff can open the source and history from that entry instead of preparing a separate handover list.
When a document arrives again, flag a possible duplicate and let staff compare its number, source and original. Attach extra pages and revisions to the existing entry while retaining received versions. Matching filenames alone are not a reason to discard a file.
Check the source beside the extracted fields
A review screen can place the original beside fields such as date, document number, order number, items and quantities. It marks uncertain numbers, missing order references and items that do not match existing data, each with a reason. Staff can correct and recheck them while the history retains the suggested value and who changed it.
If a delivery note contains two products and one quantity is unclear, place that field in the review queue. If the reviewer still cannot read the source, record the question and request clarification. Hold the next step until the required information is present rather than inventing a value for a blank field.
Match existing records before confirmation
Checks depend on the document. A delivery note may need an existing order, matching items and cumulative receipt quantities within the agreed amount. An invoice may need its number, supplier and previous processing history. Explain whether an issue is formatting, a mismatch or a decision for another colleague instead of calling every exception Validation failed.
Leave an import result staff can trace
After confirmation, export an agreed Excel or CSV layout or write through the destination system’s supported interface. Check field mappings, permissions and identifiers, then store the resulting record number on the document page. An unsuccessful attempt needs a reason and a recovery action so operations can distinguish Nothing written from Written but acknowledgement missing.
A repeated confirmation or retry after a connection failure should check the existing result first. Keep a stable link between the document and destination record to avoid duplicate receipts or invoices. Correct an imported record through the destination system’s supported revision process and retain the history.
Use the Demo to try a document that needs clarification
ProApp offers a Demo before payment. Bring a redacted document, the intended import fields and your current checks to discuss the screens staff need. Follow intake, find a missing value, supply it, review again and inspect the import result and history.
Administration should find the pending files, reviewers should see the source and reason, and operations should receive confirmed data. Try a duplicate submission and a failed import to see whether the next owner knows how to continue. Evaluate extraction on actual samples separately; a complete screen walkthrough cannot establish reading accuracy.
