Preparation plan
Role of the organization
Determine the role the company plays in digital ruble transactions—whether as a bank, retail outlet, online store, or payment recipient—and which of its processes are affected.
Systems Map
Compile a list of affected systems: remote banking services, cash registers, website and application, ERP and 1C, accounting subsystem, payment backend, and their integrations.
Security and Testing
Review permissions and roles, completeness of logs, cryptographic operations, availability of test environments, and procedures for operating the new payment route.
Preparation plan
Define the sequence of tasks: pilot script, enhancements and integrations, team composition, internal documents, and checkpoints.
Who does what: role plan
Preparation rarely stalls due to technology—it stalls where no one is assigned responsibility. Below are the roles typically needed in a project and the first task for each. See the original source for timelines of regulatory stages and participant requirements— at page of the Bank of Russia on the digital ruble; we do not replace it with our own dates.
| Role | What is responsible for in preparation | Where to start |
|---|---|---|
| Chief Financial Officer | Recording transactions in accounting, period closing, bank reconciliation, fees, refunds, and their impact on working capital | Identify in which postings and reports the new calculation form appears and who in the finance department is responsible for this |
| IT Director | Affected systems and integrations, cash register modifications, website, application, ERP and payment environment enhancements, test environments | Compile a list of payment pathway systems with owners and current integrations |
| Chief Information Security Officer | Roles and access permissions in the new environment, event logs, cryptographic operations, contractor requirements, and monitoring | Check whether the new payment path falls within the existing threat model and response protocols. |
| Head of Payment Solutions | Agreements with the bank, payment scenarios, transaction statuses, dispute situations, and refund procedures | Discuss with the servicing bank the format and timeframe in which it will provide access to transactions. |
| Operating Unit and Support | Customer interaction scenarios, support scripts, cashier and operator training, handling objections | Describe what the employee tells the customer in case of a failed payment and to whom they escalate it. |
| Chief Accountant | Primary documents, cash discipline, reconciliations, reporting, and storage of transaction confirmations | Clarify which documents confirm the transaction and how they are entered into the accounting system |
Practical rule: until each line has a last name assigned, the plan remains a presentation. Roles can be combined, but there should be no empty lines left.
First entry
Practical start - readiness audit within 10 business daysHe is assembling a readiness matrix, a systems map, risks, and the first pilot plan.
Frequently asked questions
Who should participate?
CIO, CISO, CFO, payment/cash environment, e-commerce, ERP/1C and operations block.
Is it possible to start without a partner bank?
Yes, a readiness audit can be conducted before selecting a specific integration scenario.
What will be the result?
Readiness matrix, systems map, information security risks and preparation roadmap.
Let's look at your scenario
Describe the task and current systems - we will offer a practical implementation scenario and a clear first step.
