Blog
The bank whose front end is digital and whose back office still prints things to sign
A good experience in the app usually ends at a document queue no customer can see.
Published
Here is a reasonable-sounding assumption that is usually false: if a customer can apply for a product in the app, that process is digital.
At many institutions, what happens after the customer taps confirm is that the application joins a work queue. An officer opens it, checks the attachments, prints part of it for an authorised signature, scans it back in, and passes it to the next unit, which does something similar again.
The customer sees "in progress" for three days, without knowing that nearly all of those three days is queue time rather than assessment time.
Why the back office is harder
The front end can change because it is a layer that can be rebuilt. The back office is bound to an old core system, to processes shaped by regulatory requirements, and to a division of duties deliberately designed to put several pairs of eyes on things.
Those constraints are not backwardness. Separating the person who records from the person who approves is sound internal control. The problem is not that there are several steps. It is that the steps still run on paper, or on files emailed between them.
What can be done without touching the core
Machine reading. ID copies, company registration certificates, financial statements, payslips — structured enough for current systems to extract accurately, and to report a confidence level per field. Low-confidence values go to a person; high-confidence values pass.
Immediate completeness checks. Instead of discovering a missing document when the case reaches a queue on day two, the system says so the moment it is uploaded. This is the part customers feel most, and it touches no rule.
Making the queue visible. Which unit holds the case, how many hours it has waited, which unit is the recurring bottleneck. This data frequently does not exist at all, because no single system holds the whole path.
The line regulation draws
In financial services the first question about any automation is not whether it can be done. It is whether it can be audited.
Every automated decision needs a trace of what data it used, under which version of the rules, and when. A system that updates a model in place, overwriting the old one, cannot answer an examiner asking about a case from six months ago.
Decisions that directly affect a customer's rights — credit approval above all — should have the model ordering and preparing, not deciding. And not only for legal reasons: a model trained on past approvals learns who was approved before, not who should be.
The safest way in
Choose a process that is high volume, low risk, and governed by clear criteria — a customer detail change, or document checks before a case enters assessment.
Make that faster first, measure the result in hours removed, and use it as the basis for the conversation about harder processes next time.
What GIPSIC does here
We build document tracking and systems that have to integrate with what large organisations already run. On one, document tracing went from hours to under five minutes — from making the path visible, not from replacing anything.
Where scope must be fixed because regulation is involved, we work waterfall. Where a part has to adjust to how it is actually used, we work agile. We are not dogmatic about either.
If you would like to talk through a back-office process, get in touch.
About the author
Film — Wisit. A businessman who still does his own BA work more often than he probably should, and writes a fair bit of code, front and back. Runs two or three small businesses. Follows technology and business obsessively, in Thailand and everywhere else. Off the clock: physics, astronomy, DIY, and anything to do with networks. Music always on, though he cannot sing. Plays instruments anyway, badly. Plays a lot of sport, racket sports above all. Not much of a traveller by himself, but happy to take Mint anywhere in the world. A man who fears — sorry, loves — his wife. One flaw: he barely touches video games.
Written with Claude Opus 5