Audit path
How a Dev Route Path engagement moves from first call to signed findings—built for treasury desks, not software demos.
The audit path is our working sequence for financial audits of treasury management applications. Use it to brief internal stakeholders before you request a scoping call.
1. Scoping conversation
We confirm the application landscape, entities, bank channels, and review period. You leave with a draft document request and a fee range.
2. Access and preparation
Read-only access or escorted sessions are arranged. Bank statements, mandate registers, and payment calendars land in a shared folder we specify.
3. Fieldwork at the desk
Auditors walk payment runs, cash positions, and interface logs with your operators. Samples are selected from live periods, not staged demos.
4. Draft findings
Exposure-ranked findings arrive with evidence references. Management has a set window to comment on factual accuracy.
5. Close-out meeting
Treasury, controllership, and internal audit meet to agree remediation owners and timing. The signed pack follows within three business days.
What you should prepare
- Named owner for each bank interface
- Calendar of payment factory runs during the review window
- Current dual-approval matrix
- List of recent system configuration changes that affect cash or payments
When you are ready, open the engagements list or go straight to contact to book the scoping call.