Operations
Exception queues that teach policy
Most expense queues are treated as a backlog to clear. Treated differently, they become the cheapest research programme a controller can run. Each exception is a vote on whether the handbook and the automation agree.
Start by tagging every closed item with one of four outcomes: true policy breach, missing receipt, rule too strict, or data quality failure. After three weeks, count the tags. If “rule too strict” dominates a category, the handbook — not the staff — needs a rewrite.
Make the queue teach in public
Publish a monthly digest of the top three tags to policy owners. Keep it under a page. Include one anonymised example per tag so debates stay concrete. Teams in our Exception Queue Clinic often discover that “pre-approved hospitality” was never defined for regional managers.
When you change a rule, note the date in the digest. The next month’s numbers tell you whether the change reduced noise or simply moved it. That loop is how an expense policy financial audit automation app stays aligned with how people actually travel and buy.
Protect reviewer attention
Teaching only works if reviewers have time to tag honestly. Cap daily queue depth, rotate ownership, and stop firing low-value alerts during closing week. Automation that exhausts AP will never educate the organisation.