Expense Management: Designing a Process People Will Actually Follow
Structured guidance for professionals who need their financial processes to work reliably - not just theoretically.
Individual licence; team licences available at reduced per-seat rate
Expense management sits at an awkward intersection: finance wants control and auditability, employees want to submit a receipt and move on. Most expense processes fail one group or the other. Usually both.
This course looks at expense workflow design from both sides. It covers how to write a policy that is specific enough to be enforceable without being so detailed that no one reads it, how to choose between available tools based on your actual transaction volume and team structure, and how to build an approval process that does not create a backlog every time a manager is travelling.
The compliance gap
In most organisations, expense non-compliance is not deliberate. It is a product of unclear policy, inconvenient submission processes, and approval delays that make the whole thing feel pointless. Fixing the process reduces non-compliance more reliably than adding enforcement.
FBP teams that have gone through this program typically find that their largest compliance problems trace back to 2 or 3 specific policy ambiguities rather than widespread bad behaviour.
Module 2 includes a policy language audit - a set of 17 questions that identify where your current expense policy is creating unintentional grey areas.
Tools covered in this course
Expensify, Pleo, SAP Concur, and spreadsheet-based systems. Selection criteria are covered in Module 3.
Programme Structure
Individual licence; team licences available at reduced per-seat rate
Diagnosing your current expense process
Submission rates, approval times, query volume, and common rejection reasons as diagnostic data.
Policy design and language audit
Includes the 17-question policy review checklist.Tool selection criteria
How to evaluate expense management software against your specific transaction types and team size.
Approval workflow design
Single-level versus multi-level approval, delegation rules, and handling exceptions.
Reporting and anomaly detection
What to monitor, how often, and what actually warrants investigation versus what is noise.