Skip to content
All case studies

Case study · Software

Multi-country banking onboarding platform

Horizon needed one onboarding surface that could travel across markets without losing auditability. We rebuilt the journey as an operable platform — permissions, evidence and handover included.

Horizon Financial11 min read

Professional reviewing a financial platform on a laptop
Client
Horizon Financial
Industry
Financial services
Category
Software
Engagement
Platform rebuild
Duration
18 weeks
Published
Feb 10, 2026

One operable onboarding path across markets — with evidence that compliance can reconstruct under audit.

Context

Horizon Financial was expanding into additional markets with a familiar problem: onboarding lived in disconnected tools, shared inboxes and spreadsheet workarounds. Each country team had invented its own process. Compliance could not defend a single evidence trail when regulators asked how a customer had been approved.

The commercial pressure was clear — new markets needed to open without adding another brittle stack. The operational pressure was clearer — operators were spending more time reconstructing history than making decisions.

The challenge

Previous attempts had focused on forms and portals. They improved intake in isolation, but left review, escalation and audit as afterthoughts. When a case moved between teams, context disappeared. When a market rule changed, engineering had to fork the flow.

The brief we accepted was not a prettier form. It was a system operators could run under audit pressure: clear ownership, durable evidence, and a path that could absorb market variation without becoming unmaintainable.

Approach

How we worked the problem

  1. 01

    Map the real journey

    We sat with operators, compliance and market leads to document where handoffs failed and which evidence was missing when reviews stalled.

  2. 02

    Design for auditability

    Every step produced durable evidence: who acted, what was reviewed, which rule applied, and how exceptions were resolved.

  3. 03

    Ship a modular core

    Market variants became configuration on a shared workflow engine instead of forked products that drift apart every quarter.

  4. 04

    Integrate as contracts

    Identity checks and core banking connections were specified as explicit interfaces so operations could change vendors without rewriting the journey.

Approach

We started with the operating model, not the UI. Workshops mapped the true journey — intake, verification, risk review, exception handling and activation — and named the roles accountable at each step.

From that map we designed a modular workflow core. Permissions, document types, review queues and escalation rules were first-class. Market differences were expressed as policy configuration rather than separate codebases.

Integrations were treated as product contracts. Identity providers and core banking systems were connected through stable interfaces so the journey remained coherent even when vendors changed.

What we delivered

The platform covers document capture, structured review, role-based access and an evidence model that survives handover. Operators see the same case timeline. Compliance can reconstruct why a decision was made without digging through email.

We also shipped the operational layer that makes software usable: runbooks for common exceptions, training paths for new market teams, and a configuration process for policy updates that does not require a full release cycle.

Outcome

Teams now operate one onboarding path with clear ownership. New market variants are configuration, not forks. Compliance can reconstruct decisions from the evidence trail instead of assembling narratives after the fact.

Most importantly, the system is operable. Horizon can expand the program without reinventing onboarding for every jurisdiction — and without losing the auditability that made the program viable in the first place.

Deliverables

  • End-to-end onboarding workflow with role-based access
  • Document capture and review queues for operators
  • Evidence model with reconstructable decision history
  • Market configuration layer for policy variants
  • Integration contracts for identity and core banking
  • Operator runbooks and compliance handover guides
Focus
Onboarding
Stack
Custom platform
Region
Multi-market
Engagement
18 weeks
KYCEnterprise softwareComplianceWorkflowAudit trail

Related service: KYC solutions

Next chapter

Discuss a similar program

Tell us what you want to build, automate or grow.