Concur: expense report rejected with policy violation"
Clears Concur policy-violation rejections by finding the fired audit rule in the exceptions list and fixing the flagged line. Use when a submitted report comes back rejected with a policy violation flag. Not for approver-declined reports with no rule cited.
TL;DR
A rejected report names the audit rule it broke in the report's Exceptions section. Open Exceptions, read which rule fired and on which line, fix that line (amount, receipt, business purpose, or category), and resubmit; do not resubmit unchanged or it will reject again.
Error
Concur: expense report rejected with policy violationSteps
- Open the rejected report and click the Exceptions tab. Expected: one or more named audit rules with the offending expense lines highlighted.
- Click each exception to read the rule text (for example, "meal amount exceeds the per-person limit"). Expected: you know exactly which policy clause and which line triggered it.
- Fix the line: split an over-limit charge across attendees, attach the missing receipt, add the business purpose, or correct the category. Expected: the exception clears or changes to a warning you can acknowledge.
- If the charge is legitimate but outside the default rule, add a comment with the business justification before resubmitting. Expected: the approver sees the justification inline.
- Resubmit the report and confirm the status moves to Submitted or Pending Approval. Expected: no new exceptions appear.
When to use
- The report status is Rejected or Returned with a policy violation or audit exception named.
- You need to know which rule fired before fixing anything.
When not to use
- An approver declined the report with a free-text comment and no rule cited (address the comment directly).
- The report is stuck in pending approval and was never rejected (see the stuck-approval skill).
Tool compatibility
- SAP Concur Expense, all current UI versions; audit rules configured by your Concur admin.
Variant phrasings
Expense report returned: audit rule exception
The same state with older Concur wording.
Policy violation on expense line
A line-level flag; fix that line rather than the whole report.
Why it happens
Concur runs every submitted report against your company's audit rules before it reaches an approver. A rule fires on amounts, missing receipts, categories, or missing fields, and the report bounces back until every hard exception is resolved.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_ljSywJwmxMQKVEgeJz8ckg