Skip to main content

Reviewing Documents Flagged by Auto Review

Step-by-step guide for handling a document that Auto Review flagged with a red lightning icon, including trusting a new value.

When Auto Review sees something different from what it learned for a trading pair, it does not approve the document. Instead it leaves it in your Pending queue with a red lightning icon, so a person can take a look. This guide shows how to review a flagged document and, when the change is genuine, teach Docupath the new value so future documents pass.

Prerequisites

  • A document flagged by Auto Review (a red lightning icon in the Auto Review column of the Pending tab).

  • A role that can open and approve documents.

  • To trust a new value, the Admin or Manager role, or a Custom role that includes the Auto Review module.

Steps

A Pending row showing the red lightning icon that marks a document Auto Review flagged
  1. On the Pending tab, find the document with the red lightning icon and open it.

  2. Open the Validation & Trust tab on the document.

  3. Review the list of key fields. Each is marked Verified or Unverified, and the reason the document was held back is shown - a key detail that no longer matches, a business check that did not pass, an empty critical field, or a custom validation that failed. Where custom validations applied to the document, the tab lists the ones that passed as well as the ones that failed, so you can see everything that was checked.

  4. Decide whether the flagged value is correct:

    • If it is genuinely correct (for example, the supplier has moved address), click Add on the Unverified row and confirm. The new value is added to the trust ledger for that pair.

    • If it is wrong, correct the field or reject the document as you normally would.

    • If an empty critical field or a failed custom validation is listed, fill in the field or correct the data the validation checks. Adding a value to the trust ledger does not clear these; they are checked again when you approve, and Approve stays blocked until they pass.

    Note: Adding a value to the trust ledger requires the Admin or Manager role, or a Custom role that includes the Auto Review module.

  5. Approve the document once you are satisfied with it.

The Validation and Trust tab of a flagged document - Auto-review status Failed, with an Unverified value that can be added to the trust ledger

Expected Outcome

If you added the value, the document is cleared and future documents carrying that value are approved automatically. If you corrected or rejected the document, it continues through the normal review flow. Either way, the document leaves the flagged state.

Common Issues

Issue

Cause

Resolution

No Add button on the Validation & Trust tab

Your role cannot trust values (for example, Reviewer or Validator)

Ask an Admin, Manager, or a user with a Custom role that includes the Auto Review module, to add the trusted value.

Similar documents are still flagged after adding a value

Another field or check also did not pass on those documents

Open each flagged document and review the remaining Unverified rows or reasons.

Approve is blocked even though every value is now trusted

The document also has an empty critical field or a failed custom validation

Open the Validation & Trust tab, clear the remaining items, then approve. The Validations failed modal lists whatever is still outstanding.

The document is not auto-approved again after you fixed it

A document Auto Review marked Failed stays on the manual approval path permanently

Approve it manually. Later documents from the same pair are still eligible for Auto Review.

Notes

  • Adding a value trusts it from that point on; it does not change documents already approved.

  • Empty critical fields come from Customize captured fields and reflect the configuration as it stands now. Custom validations come from Instruction Builds and were fixed when the document was extracted, so a document has to be reprocessed to pick up a changed validation.

Did this answer your question?