Documents in Docupath can be rejected manually by users whose role allows document review, or automatically through configured Rejection Rules. All rejections require a documented reason. Rejected documents are moved to the Rejected tab for tracking and audit purposes.
When to Use
A document fails validation checks.
A document violates business rules.
A document contains incorrect or incomplete data.
You need to automate rejection of documents matching specific criteria.
Prerequisites
Manual rejection: an Admin, Manager, Reviewer or Reviewer and Validator role, or a custom role granted write access to document review. Validators cannot reject; they validate instead.
Automatic rejection: access to configure Rejection Rules. Admins can configure rules on all four scope tabs (Organization, Trading Party, Country and Global). Managers have the Organization and Trading Party tabs only, so Country and Global rejection rules are set by an admin.
Steps
Manual Rejection
Open the document in the Review Screen.
Review the extracted data and identify the issue.
Click Reject in the footer action bar.
Enter a rejection reason (mandatory).
Confirm the rejection.
Automatic Rejection via Rejection Rules
Navigate to Settings > Rejection Rules.
Configure rules that define the criteria for automatic rejection.
Save the rules.
Documents matching the configured criteria will be automatically rejected with the rule-defined reason.
Expected Outcome
The rejected document moves to the Rejected tab with a logged rejection reason.
If global rejection notifications are configured, an email is sent to designated notification recipients.
Common Issues
Issue | Cause | Resolution |
Reject is greyed out with the tooltip "You don't have permission to perform this action" | The user's role does not allow rejecting documents. Admins, Managers, Reviewers and Reviewer and Validators can reject; Validators cannot | Ask an admin or a manager, who both have Manage Users & Roles, to assign a role that can reject documents. |
No rejection notification email received | Rejection notification add-on is not enabled or no recipients are configured | Verify the add-on is active and that recipient email addresses are configured in notification settings. |
Need to re-approve a previously rejected document | Rejection is a terminal state | The document must be reprocessed through the full document lifecycle. It cannot be directly re-approved from the Rejected tab. |
Notes
Rejection is a terminal state - a rejected document cannot be re-approved without reprocessing it through the full document lifecycle.
All rejections, whether manual or automatic, require a documented reason for audit and compliance purposes.