Prepare systems for originator and beneficiary information, self-hosted-wallet risk, counterparties, data quality and interoperability.
Why this workstream matters
The Georgian implementation path requires prescribed transfer information and controls around counterparty VASPs and self-hosted wallets. The VASP implementation deadline is 31 December 2027, but new systems should be designed now to avoid expensive redesign.
What this guide covers
- Originator and beneficiary data
- Counterparty identification and due diligence
- Self-hosted-wallet controls
- Missing or poor-quality data
- Rejected, suspended and escalated transfers
- Privacy, security and vendor interoperability
How it connects to the application
Outputs must be consistent with the ownership structure, product and information flows, providers, business plan, staffing assumptions, policies and system behaviour. Any inconsistency should be resolved before filing or implementation.
Client inputs and dependencies
We confirm required founders, group records, product documentation, vendor information, system access, markets, transaction assumptions and responsible client personnel during scoping. The proposal separates adviser work, client responsibilities and third-party costs.