Expense automation projects frequently stall not because the technology fails, but because established employees do not use it consistently. Finance teams often treat this as a training problem. In most cases, it is a design and trust problem.
What resistance actually looks like
Employees with long-standing expense habits submit receipts late, photograph them poorly, or continue emailing scans directly to finance. This is not obstruction. It reflects a rational preference for a process they know over one that is unfamiliar and whose benefits they do not personally experience.
The employee submitting expenses gains nothing from automation. The efficiency accrues entirely to the finance team. Acknowledging this honestly changes how the rollout is communicated and structured.
Interventions that have worked in practice
- Reducing reimbursement time as a direct, visible benefit for submitters
- Running a structured pilot with a willing team before a broad rollout
- Providing a documented escalation path for submissions the tool cannot handle
- Keeping the old process available for a defined transition period
Tomasz Wierzbicki, a finance systems lead at a Dublin professional services firm, found that reimbursement speed was the single most effective lever. When employees saw payments processed in four days rather than twelve, adoption in the pilot team reached consistent levels within six weeks. The broader rollout then had a credible reference point to draw on.