# A commercial bank in Nepal builds customer 360 and faster loan processing on DataNature

> A commercial bank in Nepal uses DataNature in-country to build a customer 360, score cross-sell and credit risk with AI360 Studio, and extract loan application data with DocuContext. Data stays in Nepal, and every figure traces back to its source.

Source: https://datanature.ai/customers/nepal-commercial-bank-customer-360-loans
Publisher: Dlytica Inc. (DataNature is a Dlytica company)
Updated: 2026-11-05

- Customer: A commercial bank in Nepal
- Sector: banking
- Country: Nepal
- Hosted on: In Nepal
- Products: DataNature, AI360 Studio, DocuContext

## The challenge

Customer data was split across core banking, cards and digital channels. Loan officers re-keyed documents by hand. Data had to stay in Nepal.

## The solution

Connect unified core and channel data in the lakehouse. AI360 Studio built customer 360, cross-sell and credit-risk scores. DocuContext extracted and validated loan documents into the same governed tables.

## The results

- One customer view for branches and head office
- Loan documents processed without re-keying
- Cross-sell and credit scores in one governed model

(Anonymized at the customer's request.)

## What was the bank trying to fix?

A fragmented customer view and slow, manual loan processing.

## What did it deploy?

DataNature, AI360 Studio and DocuContext, hosted in Nepal.

## What changed?

Branches and head office see the same customer view, and loan files move without manual re-keying.

## How does this work as a customer data platform?

The bank's customer 360 is a lakehouse-native customer data platform built with AI360 Studio: core, card and digital data are collected by Connect, identities are resolved into one customer key, the profile and scores live in governed Gold tables, and branches and head office use the same view. The profile never leaves Nepal. See [CDPs for banks, credit unions and telecom](/blog/customer-data-platform-banks-credit-unions-telecom).

## How is it built?

- **Ingestion**: Connect loads core banking, card and digital-channel tables into Bronze, using incremental loads on change timestamps for large transaction tables.
- **Identity resolution** in Silver: dbt models match customers across systems into one key.
- **Customer 360** in Gold: holdings, balances, behaviour and risk attributes; AI360 Studio adds cross-sell and credit-risk scores, tracked by model version.
- **Loan documents**: DocuContext classifies and extracts fields from loan files with confidence scores, validates them against business rules, and writes clean fields into the same Gold tables.
- **Governance**: national ID numbers masked for analysts, customer IDs hashed for modelling, branch-level row filters for relationship managers.

## What can be added next on the same platform?

The customer 360 and scores the bank already runs are the inputs for personalized Nepali voice outreach. AI360 can select customers with an instalment due, an expiring KYC or a cross-sell opportunity and send them, with their own amount, date and language, to a Nepali voice platform such as TingTing, with answers and opt-outs returning to the profile. See [Nepali AI voice calls for banks and telcos](/blog/nepali-ai-voice-calls-banks-telecom-ai360-tingting).
