Review flagged receipts
Understand the main receipt statuses and how to handle suspicious or incomplete submissions.
Not every non-valid receipt means fraud. In Transactions, a flagged receipt can be incomplete, duplicated, pending, or rejected for several legitimate reasons.
Statuses operators should know
| Status | What it usually means | Common next step |
|---|---|---|
PENDING | The receipt passed policy but manual review is still required. | Review the receipt and validate or reject it. |
INCOMPLETE | OCR could not extract enough reliable data. | Ask for a clearer resubmission or correct manually if the receipt is readable. |
DUPLICATE | The same physical receipt appears to have been submitted already. | Compare context before approving. |
REJECTED | The receipt failed policy or was manually refused. | Confirm the refusal reason or amend if OCR data was wrong. |
INVALID | OCR processing failed more deeply than a normal incomplete read. | Use operator judgment and, if needed, amend or reject definitively. |
REPLACED submissions are intentionally hidden from normal displays because they were superseded by a resubmission.
Good review questions
When a receipt looks suspicious, ask:
- Is the merchant clearly visible?
- Is the amount readable and plausible?
- Does this look like the same receipt already submitted by the same participant?
- Would a minor amendment fix the OCR mistake, or does the receipt genuinely fail the challenge terms?
Remember the participant-side rule
Only INCOMPLETE receipts are designed for participant resubmission. Duplicate or rejected cases normally need operator intervention instead of another blind upload attempt.