Most expense automation platforms are marketed on their ability to flag out-of-policy submissions. In practice, the enforcement logic is only as precise as the policy rules entered during configuration. This is where experienced finance teams frequently discover the limits of the tooling.
Where configuration falls short
Platforms like Concur and Expensify allow rule-based flags for spend categories and per-diem limits. What they handle poorly is contextual judgment: a EUR 280 client dinner in Cork may be reasonable; the same amount submitted by someone who attended no external meetings that week is worth scrutiny. No current tool resolves this without human review.
Resources worth examining before configuration
- GBTA expense policy benchmarking reports for sector-specific thresholds
- Your platform vendor documentation on conditional logic depth
- Internal audit findings from the previous two financial years
Brigid Hartnett, an internal auditor with experience across three mid-market firms, noted that most misconfigured expense tools share one pattern: the team automated the easy rules and left the edge cases to manual review without documenting which cases those were.
The practical fix is a written exception register maintained alongside the automation configuration. Every rule the tool cannot enforce should appear there with a named owner and a review cadence. Without this, the gaps compound quietly over time.