Onboarding Automation at a Retail Bank
A classic pain: the bank attracts SME clients but account opening takes 3–5 days — and 30–40% of applicants leave without waiting. The cause is not technology but organizational gaps between departments.
A familiar situation: the bank invests in SME acquisition, marketing works, applications are coming in. But out of every ten applicants, three or four leave without waiting for their account to be opened. Not to competitors with better rates — simply to whoever opens accounts faster.
Why does this happen? When we break down the onboarding process step by step and time it, the picture is almost always the same. The application goes through three departments — compliance, operations, IT. Each works to its own regulations, with its own queue. Compliance checks documents manually, cross-referencing registries in a separate browser window. Operations staff re-type data from the form into core banking by hand. IT enrolls digital banking by ticket. Total client wait: 3–5 business days, and nobody in the bank can say exactly what stage their application is at.
What’s characteristic — the solution almost always turns out to be surprisingly simple on the technical side. The bank’s core banking system typically already has an API for programmatic account creation — it was implemented, but nobody connected it. Government registries for KYC checks are available via API. The main work goes not into code but into redesigning the process: formalizing compliance’s intuitive rules into a set of automatic rules. And here’s an important point — the automatic process turns out to be stricter than the manual one, which becomes the argument for regulators.
What to expect: account opens in 4 hours instead of 5 days. The client gets an SMS at each stage. Dropout during onboarding falls by 60%+. And the operations department, freed from manual entry routine, processes 40% more applications without hiring new staff.
Typical Problem
The bank is actively attracting SMEs. Marketing works — applications are growing. But conversion from application to open account is catastrophically low: 30–40% of applicants leave without waiting for the process to complete. They don't leave for competitors with better rates — simply for whoever opens accounts faster. If this sounds like your bank — read on.
Why This Happens
Onboarding in many banks is built on 2010s logic: paper form, manual document review, physical branch visit, manual data loading into core banking. Each stage is a separate department with its own queue. Compliance, operations, IT — each working to its own regulations with its own SLAs that nobody monitors. The client goes through three independent procedures instead of one.
How We Diagnose It
In diagnostics we always start with a process audit with time measurement. And we almost always find the same thing: the problem isn't technological. Core banking typically already has an API for automatic account creation — nobody has connected it. The problem is organizational: several departments have no shared process, each works in isolation. The client goes through three independent procedures instead of one.
The Right Model
A unified end-to-end process with four automation points: (1) digital form with pre-fill by tax ID; (2) automatic check through government registries and sanctions lists; (3) direct write to core banking via existing API; (4) automatic digital banking access. Critically — parallel department work instead of sequential.
How We Implement It
A typical project takes 3–4 months. We conduct a process audit timing each stage, design the target process, build an integration layer between the web form, compliance system, and core banking, configure automatic checks through government registries, launch application status tracking for the client via SMS. The hardest phase isn't the code — it's working with compliance: formalizing intuitive verification rules into automatic rules. The result: automatic verification turns out to be stricter than manual.
How the Team Works
Projects like this run with a team of 4: 2 developers, 1 business analyst, 1 integration engineer. I lead the process architecture, integration model, and negotiations with the compliance department — that's always the hardest phase. The team implements integrations, tests, and documents.
Results
If your bank spends more than one day on onboarding — you're losing clients. And most likely the solution costs 3–5× less than you think: your core banking APIs are ready — nobody is using them.
Key Lessons
- • Before building workarounds — check the core banking documentation. In 80% of cases, the necessary APIs already exist; nobody has just connected them.
- • Organizational barriers between departments are the main enemy of speed. Technology is secondary.
- • Formalize compliance's intuitive rules — automatic verification will be stricter than manual, and that becomes the argument for regulators.
- • SMS application status tracking reduces call center load by 30% — clients stop calling to ask.
Similar challenge?
Tell me what's going on. I'll review the situation and suggest a concrete path forward.
Обычно отвечаю в течение нескольких часов