## TL;DR

Concur matched the expense against an audit rule and wants either a fix or documentation. Open the exception, read exactly what the rule requires (receipt, business purpose, pre-approval), provide it on the expense line, and resubmit.

## Error

```text
Concur: exception audit rule triggered
```

## Steps

1. Open the expense's Exceptions and click the triggered rule. Expected: the rule text states the requirement plainly.
2. Determine whether the rule needs a correction (wrong category, missing receipt) or documentation (business purpose, attendee list). Expected: you know which of the two it is.
3. Provide what the rule asks for on the expense line: attach the receipt, write the business purpose, or add attendees. Expected: the exception clears or becomes an acknowledged warning.
4. For rules that allow it, add an approver-visible comment explaining the business context. Expected: the approver sees the context with the exception.
5. Resubmit. Expected: the report passes the audit check and routes forward.

## When to use

- Concur shows a named audit-rule exception on an expense.
- You need to know what documentation the rule wants.

## When not to use

- The expense is genuinely out of policy (it should be removed or marked personal).
- The report was rejected outright with no exception detail (see the policy-violation skill).

## Tool compatibility

- SAP Concur Expense; audit rules configured by the Concur admin.

## Variant phrasings

### Audit rule exception on expense

Same flag, shorter wording.

### Expense triggered a compliance rule

The compliance-team phrasing of the same event.

## Why it happens

Audit rules encode company policy as automated checks. They fire before human review so that every exception carries its documentation when the approver sees it.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_wP7E_5dYfV7ZHduf-k-EqQ