Concept Design
Keeping settlement payment instructions tied to a verified source
A conveyancing team can receive revised directions in an email thread shortly before settlement. The matter file, client ledger and settlement workspace can hold different versions, each looking internally consistent.
System landscape
Source evidence comes from instructions and matter file. The proposed workflow sends the decision to authorised practitioner.
Proposed architecture
Link the instruction version, matter, independent verification record and proposed payment. Show precisely which change requires a call-back and invalidate prior approval if the destination or amount changes.
- Source recordsInstructions and matter file
- ProcessingBind approval to revision
- Decision ownerAuthorised practitioner
- Operational outputVerified payment direction
Reliability and operating controls
Authorised people perform verification using a trusted contact source. Separate instruction entry from release and retain the escalation route when settlement is close and the contact cannot be reached.
Illustrative operating scenario
A revised beneficiary arrives after the file was approved. The earlier verification remains in the history, but the replacement cannot inherit it simply because the email came from an existing thread.
Delivery boundaries
The practitioner decides authority, conflicts and lawful access. The system supplies traceability and enforces policies approved by the practice.
Expected business impact
Reduce the chance an obsolete payment direction can be reused after an instruction changes.
Acceptance test and handover
Test corrections before and after authority is granted. The supervising practitioner should be able to reproduce exactly which version was verified and who released it.
Industry evidence
The regulator identifies verification of payment instructions as a practical risk control for law practices. Victorian Legal Services Board and Commissioner on payment fraud controls