Pending Review Queue
Understand how Receipt flags low-confidence receipts for human review and how to resolve or approve them.
Last updated: 2026-06-02
What is the pending review queue?
When Stareceipt's recognition flow needs human confirmation, it creates the receipt and marks it Needs Review. The receipt is visible in normal receipt flows, but it is not treated as fully reviewed until someone confirms or rejects it.
Common reasons a receipt enters pending review:
- The image is blurry, rotated, or partially obscured.
- The total amount could not be located or was ambiguous (e.g. tip lines, multi-currency receipts).
- The merchant or date still needs manual confirmation.
- Multiple receipts were detected in one upload.
Finding pending items
| Surface | How to access |
|---|---|
| Receipts list | Filter by Status → Needs Review |
| Home / action cards | Open the card showing receipts waiting for confirmation |
| Mobile task queue | Open the receipts task panel and continue the review flow |
Pending-review visibility is scoped to the current ledger and the current user's review permissions. Creators and reviewers may both encounter items that still need confirmation.
Reviewing a pending item
- Open the pending receipt from the queue.
- The AI pre-fills as many fields as it could extract.
- Verify or correct the important fields:
- Merchant name — type the correct name or select from suggestions.
- Total amount — enter the correct amount from the receipt.
- Date — confirm the transaction date.
- Category — change the category if the AI's guess is wrong.
- Confirm the review. The receipt leaves Needs Review and becomes a normal verified receipt.
Rejecting a pending item
If the capture is not a valid receipt, reject it from the review flow or delete it from the receipt UI instead of confirming it.
If your client exposes recycle or restore controls, deleted items can be recovered during the recycle-bin retention window. See Recycle Bin.
Team workflows
In shared ledgers, pending review is a useful quality gate. Current Web and mobile clients surface these receipts inside their normal receipt and task flows rather than through a separate settings-only queue.
Tips
- Address the pending queue at the end of each day — the longer a receipt sits in review, the harder it is to remember the correct details.
- For consistently problematic merchants (e.g. a local cash-only shop with handwritten receipts), consider setting a Category Rule so the merchant is auto-assigned even when recognition confidence is low.
- If your client surfaces duplicate candidates during review, resolve them before final confirmation.
