Kosha Financial¶
The banking domain behind LedgerLens MCP: a fictional Indian digital bank that serves retail customers through a partner-bank model and gives its staff AI agents that read customer, payment, risk and policy information.
Parties¶
Customer: A person or sole proprietor who holds one or more Accounts with Kosha, identified by a CIF number. Avoid: User, client, account holder
CIF number: The bank's permanent 10-digit identifier for a Customer (Customer Information File), stable across all their Accounts. Avoid: Customer number, customer ID (when meaning the bank-facing number)
Persona: The behavioural archetype a Customer belongs to (salaried, student, gig worker, SME owner, NRI, senior citizen), which shapes their spending and income patterns. Avoid: Segment (a different concept)
Segment: The commercial tier a Customer is served in (mass, affluent, premium). Avoid: Persona, tier
Staff member: A Kosha employee who acts through an agent, holding exactly one Role. Avoid: User, operator, agent (an agent is software)
Role: The job function a Staff member performs — support agent, analyst, compliance officer, or demo viewer — which determines what they may see and do. Avoid: Permission, group
Accounts and money¶
Account: A deposit relationship (savings, salary, current, fixed or recurring deposit) owned by one Customer. Avoid: Wallet, profile
Ledger balance: The balance implied by every posted entry on an Account. Avoid: Balance (ambiguous)
Available balance: Ledger balance minus Holds — what the Customer can spend right now. Avoid: Usable balance, free balance
Hold: An amount on an Account earmarked and unavailable for spending, pending an outcome. Avoid: Block (used for cards)
Lien: A legally enforceable claim marked on an Account balance, typically under a court or regulator order. Avoid: Hold
Freeze: A restriction on an Account: a debit freeze stops money leaving, a credit freeze stops money arriving, a total freeze stops both. Avoid: Block, lock
Dormant account: An Account with no Customer-initiated activity for 12 months, flagged for reactivation outreach. Avoid: Inactive account
Inoperative account: An Account with no Customer-initiated activity for 24 months, which per RBI rules requires re-KYC before it can be operated again. Avoid: Dormant account (a different threshold)
Journal entry: A balanced set of Postings recording one economic event. Avoid: Ledger entry, booking
Posting: A single signed amount against one ledger account within a Journal entry; the Postings of an entry always sum to zero. Avoid: Line item, leg
GL account:
A general-ledger account that Postings land in: customer_deposits, whose sub-ledgers are the Customers' Accounts, or an internal account such as a rail's settlement account, fee income, GST payable or suspense.
Avoid: Ledger (the whole book), nostro (a different concept)
Payments¶
Transaction: A single movement of money into or out of an Account through one Rail, with its own lifecycle. Avoid: Payment (a customer-intent concept), transfer
Rail: The payment network a Transaction travels on: UPI, IMPS, NEFT, RTGS, card, ATM, NACH or internal. Avoid: Channel (a different concept), method
Channel: The touchpoint where a Transaction was initiated: mobile app, web, POS terminal, ATM or API. Avoid: Rail, source
VPA:
A UPI virtual payment address such as name@kosha that routes to an Account.
Avoid: UPI ID, handle
UTR: The unique reference a clearing network assigns to an IMPS, NEFT or RTGS Transaction. Avoid: Reference number (ambiguous)
RRN: The 12-digit retrieval reference number identifying a UPI or card Transaction. Avoid: Reference number (ambiguous)
Beneficiary: A saved payee Account a Customer can send money to, subject to a Cooling period after it is added. Avoid: Payee, recipient
Cooling period: The window after a Beneficiary is added during which transfers to it are capped, to blunt account-takeover fraud. Avoid: Grace period
Credit delayed: A Transaction state where the Customer's Account is debited but the beneficiary bank has not yet credited the recipient. Avoid: Stuck payment, pending (too broad)
Deemed success: A UPI Transaction treated as successful because the beneficiary bank timed out after the network approved it, pending later confirmation or reversal. Avoid: Assumed success
Reversal: The return of a debited amount to the Customer's Account after a Transaction fails downstream. Avoid: Refund (merchant-initiated), chargeback
Refund: A merchant-initiated return of money for a completed purchase. Avoid: Reversal
TAT: The regulator-mandated turnaround time within which a failed Transaction must be resolved, beyond which the Customer is owed compensation. Avoid: SLA (internal targets)
Know your customer¶
KYC profile: The record of how a Customer's identity was verified, its current KYC status and when it must next be reviewed. Avoid: KYC (alone), verification
Min-KYC: A limited verification level permitting restricted Account usage until Full KYC is completed. Avoid: Basic KYC, small account
Full KYC: Complete identity and address verification permitting unrestricted Account usage. Avoid: Complete KYC
V-CIP: Video-based Customer Identification Process: live video verification by a trained Kosha official. Avoid: Video KYC (informal)
OVD: An Officially Valid Document accepted as proof of identity or address under the RBI KYC Master Direction. Avoid: ID proof
CKYC number: The 14-digit identifier (KIN) a Customer holds in the Central KYC Registry. Avoid: KIN (alone), CKYC ID
Re-KYC: The periodic refresh of a KYC profile, due every 2, 8 or 10 years for high, medium or low risk Customers. Avoid: KYC renewal, re-verification
Risk category: The money-laundering risk rating (low, medium, high) assigned to a Customer, which drives Re-KYC frequency and monitoring depth. Avoid: Risk score (a per-Transaction number)
Financial crime¶
PEP: A Politically Exposed Person, or a close associate or relative of one, requiring enhanced due diligence. Avoid: VIP
Screening: Checking a name against sanctions and PEP lists, producing clear, potential match or true match. Avoid: Background check, name check
AML alert: A signal raised when a Customer's activity matches a Typology rule, to be investigated and dispositioned by an analyst. Avoid: Flag, case
Typology: A recognised money-laundering or fraud pattern, such as structuring, mule account or round-tripping. Avoid: Scenario, rule (a rule detects a typology)
Mule account: An Account used to receive and rapidly pass on illicit funds on behalf of others. Avoid: Money mule (refers to the person)
STR: A Suspicious Transaction Report filed with FIU-IND when an investigation concludes activity is suspicious. Avoid: SAR (US term)
CTR: A Cash Transaction Report filed with FIU-IND for cash activity above the reporting threshold. Avoid: Large cash report
Transaction review: A request, raised by a Staff member, that a specific Transaction be examined by the risk team. Avoid: Flag, alert
Dispute: A Customer's formal challenge to a Transaction, tracked to resolution within TAT. Avoid: Complaint (broader), ticket
Chargeback: The card-network process of reclaiming a disputed card Transaction from the merchant's bank. Avoid: Reversal, refund
Knowledge¶
SOP: A Standard Operating Procedure: the step-by-step way a Department performs a recurring task. Avoid: Process doc, guide
Policy: A board- or management-approved statement of rules that SOPs implement. Avoid: SOP, guideline
Document: Any controlled knowledge artefact — Policy, SOP, runbook, playbook, API reference, FAQ or template — with a code, version, owner and effective date. Avoid: File, article, page
Department: The organisational unit that owns a Document: Compliance, Onboarding, Legal, Risk & Fraud, Customer Support, Sales, Marketing, Engineering or Corporate. Avoid: Team, function
Classification: A Document's sensitivity — public, internal, confidential or restricted — bounding which Roles may read it. Avoid: Visibility, access level
Effective version: The single version of a Document currently in force; earlier versions are superseded. Avoid: Latest version (a draft can be later)