CODISE-IT field guide · October 2026
Five email checks for a law firm
Questions to ask before the next urgent payment request or suspicious attachment arrives.
1. Protect sign-in
Review MFA coverage and account recovery methods. Ask your provider to explain how unusual sign-ins are investigated.
2. Verify payment changes
Use an independently known telephone number to verify bank-detail changes. Email alone should not be the approval channel.
A payment-change verification procedure for LA law firms
A familiar sender name does not establish that a request is authentic. Agree a procedure with the person responsible for payments before a request becomes urgent.
- Pause the change. Leave the payment details unchanged while the request is checked.
- Use a trusted contact route. Call a previously verified number from your firm’s approved records, rather than a number supplied in the new message.
- Record verification and approval. Keep a reference to the callback and obtain the authorization required by your firm’s payment policy.
- Escalate inconsistencies. If the details cannot be verified, inform the designated payment owner and IT contact. Suspected transfers require prompt contact with the bank and the appropriate incident-response contacts.
3. Review forwarding
Check mailbox forwarding rules and delegated access with your email administrator. Remove rules and permissions without a current business purpose.
4. Train with relevant examples
Practice spotting impersonated clients, urgent filing requests and unexpected document links. Give staff a clear reporting route.
5. Plan response
Document who to contact if an account is compromised and how access will be contained. Preserve relevant evidence and involve your legal and insurance contacts when appropriate.
Payment-change verification worksheet
Print this blank planning sheet and adapt it to your firm’s approval process. Keep completed records in the firm’s approved system.
| Check | Internal reference or assigned owner |
|---|---|
| Request reference and date (no bank details here) | |
| Person responsible for checking the request | |
| Trusted contact record used for verification | |
| Callback completed: date and verifier | |
| Required approval obtained: internal reference | |
| Any inconsistency and escalation reference | |
| Payment owner’s final decision |
Fictional training example
An apparent vendor asks your bookkeeper to use a new account before today’s deadline. Staff keep the existing details unchanged, call the vendor through an already verified contact record, and refer the outcome to the firm’s authorized approver. This example illustrates a process; it is not a CODISE-IT client case or a guarantee of fraud prevention.
Do not write account numbers, confidential client details or passwords on this website. Follow your firm’s own financial-control and incident-response policies.
General operational guidance. Consult your IT provider and designated advisers about your specific environment.