Document review is the control point between uploading a file and letting Worthic act on it. When a document is uploaded through the normal app flows, Worthic does not simply drop it into the Inbox or act autonomously. It stages the file, analyses it where appropriate, and opens the review flow so the user can confirm what the document is, where it belongs, and what should happen next.
The review process is used for documents uploaded from the Documents workspace, AI chat, account statement/import flows, mobile uploads, and other supported upload paths. Email ingestion and API document submissions are different because there is no user sitting in an upload modal at the moment the file arrives; those documents are placed into the Inbox/review queue for later review unless they are submitted as user-reference files.
What Worthic Analyzes
During review, Worthic uses the uploaded file, upload context, and extracted content to propose how the document should be handled. Depending on the file and where it came from, the review may include:
- the detected document type, such as statement, invoice, receipt, payslip, policy, tax document, or supporting evidence;
- the recommended route, such as transaction review, account support, reporting line support, real estate review, investment review, or general filing;
- the suggested account, reporting line, property, or other record context;
- the recommended Library path;
- the suggested next action, such as file only, import transactions, keep as support, or prepare a domain-specific review;
- extracted fields, summaries, tables, dates, amounts, merchants, counterparties, or statement rows where available;
- warnings where extraction was incomplete, ambiguous, or could not confidently match the document to an account or reporting line.
Worthic may use deterministic rules, file metadata, upload context, previous routing patterns, and AI-assisted extraction/review. The user remains the final checkpoint before the document is filed or downstream records are created.
Review Actions
In the review flow, the user can confirm the recommended handling, adjust the route or context where the UI allows it, save the document to My files instead of running analysis, defer the review or discard the document.
Confirming the review normally files the document into the workspace Library under the recommended Worthic HQ path. For example, a bank statement may be filed under an account-based statement path, while a property expense may be filed under the relevant real estate/reporting line path. Once filing succeeds, the document is no longer treated as Inbox work; it becomes part of the Library.
If the user chooses to review later, closes the review before completing it, or the review remains unresolved, Worthic keeps or sends the document to the Inbox. The Inbox is therefore the pending-work surface: it is for documents that still need a decision, not the default first stop for every upload.
If the user chooses My files for a personal reference document, Worthic saves it into the user’s personal file area and skips workspace analysis, routing, extraction, and transaction creation.
Discarding the document removes the document from the review flow and purges the document from the database entirely. If Worthic has already created imported transaction candidates from the document, the discard confirmation asks whether those imported transactions should also be discarded. Use this when the upload is wrong, duplicated, irrelevant, or should not be kept in Worthic.
AI document processing result and error displays
The following are the possible document processing results and associated error messages and workflows:
Account-related documents
| Processing result | Processing user message | Recommended action user message | Retry available? | Confirmation enabled? |
|---|---|---|---|---|
| Complete; confident match | Processed successfully. | File and import transactions for review. | No | Yes |
| Complete; review advised | Processed successfully. Review highlighted details. | Check highlighted fields, then confirm. | No | Yes |
| Account not confidently identified | Processed successfully. Select the correct account before continuing. | Edit, then select account | No | After selection |
| Dates need review | Processed, but one or more dates need review. | Confirm or correct highlighted dates. | No | After date review |
| Extraction incomplete or timed out | Extraction is incomplete. Worthic could not obtain all required document data. | Retry once, or file without importing and add transactions manually. | Yes, once | No, filing only |
| Transactions do not reconcile | Extraction completed, but the transactions do not reconcile to the statement. | Retry once; if unsuccessful, file without importing or discard. | Yes, once | No, filing only |
Reporting-line-related documents
| Processing result | Processing user message | Recommended action user message | Retry available? | Confirmation enabled? |
|---|---|---|---|---|
| Complete; confident match | Processed successfully. | File to Library using the recommended reporting line. | No | Yes |
| Complete; review advised | Processed successfully. Review highlighted details. | Check highlighted fields, then confirm. | No | Yes |
| Reporting line not confidently identified | Processed successfully. Select the correct reporting line before continuing. | Select reporting line. | No | After selection |
| Dates need review | Processed, but one or more dates need review. | Confirm or correct highlighted dates. | No | After date review |
| Extraction incomplete or timed out | Extraction is incomplete. Worthic could not obtain all required document data. | Retry once, or file the available document without extracted actions. | Yes, once | No, filing only |
| No supported downstream extraction required | Processed successfully. | File to Library. | No | Yes |
What Happens to Extracted Transactions
When a document is routed for transaction review, Worthic can extract transaction candidates from the file. These are not silently posted as final user-reviewed transactions. The document review confirms that the file should be used for transaction import; then Worthic queues or prepares the extracted transactions for account-level confirmation and review.
This means the document and the transactions follow related but separate workflows. The document can be filed to the Library as supporting evidence, while the extracted transaction rows appear in the appropriate transaction/account review surface for confirmation, categorisation, linking, or correction. If extraction is incomplete or reconciliation fails, Worthic keeps the issue visible for manual follow-up.
Inbox vs Library after review
A reviewed document moves to the Library when the user confirms the route and Worthic successfully files it. The Library is the long-term document store, organised under Worthic HQ for workspace documents and My files for personal files.
A document appears in the Inbox when review is still pending, deferred, incomplete, or unresolved. Email-ingested and normal API-submitted documents also enter the Inbox because they arrive without an interactive review modal. Processing failures, missing route confidence, filing failures, or unresolved extraction results can also leave a document in the Inbox so the user can decide what to do next.
Related Articles
For browsing and managing filed documents, see Document inbox and library. For document tags and collection views, see Tagging and collections. For transaction clean-up after import, see Transactions workbench and Transaction categorization and splitting.