Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Map of every route money leaves the business
Before any control can be designed you need to know every way cash goes out: bank transfers, card payments, direct debits, cheques, payroll, the payment processor's refund button and the owner's own banking app. A one-page map of each route, who can start it, who can release it and what the limit is shows where a single email could move money with nobody else noticing.
First tasks
- List every bank account, company card and payment platform in use
- Write down who can add a payee and who can release a payment on each
- Look up the daily and single-payment limits in each banking platform
- Highlight every route where one person can pay without a second check
Payment fraud risk register
Fraudsters rarely break in; they persuade someone with the right access to pay. A register of the realistic scenarios for this business, such as a supplier's hacked email sending new bank details, a fake director asking for an urgent transfer or a payroll change request from a spoofed address, scored for likelihood and impact, turns a vague worry into a ranked list of controls to put in place.
First tasks
- Ask the finance team which suspicious payment requests they have seen this year
- Write each scenario as one sentence naming the payment route it would use
- Score each scenario for likelihood and impact on a simple scale
- Assign an owner and date to the three highest-scoring gaps
- Rescore the register against the latest attempts and incidents @recurring(quarterly)
Bank detail change callback procedure
Changed bank details are the single most common route for invoice fraud: a supplier's real email account is hacked, or a near-identical address is used, and a polite letter asks you to pay a new account. A written rule that every change is confirmed by phoning the supplier on a number you already held, never one in the request, closes most of that risk for the cost of a five-minute call.
First tasks
- Write the rule that no bank detail change is accepted from an email or letter alone
- Define where the callback number must come from and where it must never come from
- Create a change record with caller, contact name, date and confirmed details
- Walk the payments team through the procedure using last month's changes