Clients and KYC
One person, one client record.
The same borrower cannot be enrolled twice under two card formats. Fused normalises the Sri Lanka NIC, gives each client a nine-digit number from a gap-free counter, and keeps KYC documents with expiry and second-person verification, never deleting one.
- Name
- W. M. R. K. Wijesinghe
- Status
- Active
- National identity card
- 198512304567
- Home office
- Kandy
- Identity document
- Verified by a second person
- Group
- Kandy centre 14, group 3
What it does
NIC, old and new
Old and new NIC formats normalise to one form, so an active number cannot belong to two clients. Fused warns when the birth date or gender does not match the card.
Nine built-in ID formats
Sri Lanka NIC, three Indian formats, Pakistan CNIC, Bangladesh and Nepal national IDs, passport and driving licence, or a pattern the institution writes itself.
Groups and centres
A hierarchy of levels you define, with dated membership that is exclusive unless a setting says otherwise, and a responsible officer kept as dated periods.
KYC documents that stay
Five kinds seeded: identity, address, photograph, signature and income. Each has an expiry and a second-person verification, and a document is withdrawn with a reason, never deleted.
Custom fields and tables
Typed fields, dependent choices, conditions and computed values on a client or any other record, or standalone tables. Each publish creates a report view.
CSV import with a dry run
Clients load from a CSV file through the same checks the enrolment form uses, whole or not at all. A dry run proves the file first.
What it refuses
A control is only a control if the system enforces it.
- Fused refuses a second active client holding the same NIC.
- Fused refuses a loan application from a blacklisted or deceased client.
- Fused refuses a KYC document verified by the person who uploaded it.
- Fused refuses the deletion of a KYC document.
- Fused refuses a CSV file with any refused row, naming every one.
The rules underneath
The detail your finance and IT teams will ask about.
- Client number
- Nine digits from a gap-free counter.
- Names
- The full name exactly as on the identity document, plus a name with initials.
- Lifecycle
- Pending, active, rejected, withdrawn and closed, with reopening to pending. Blacklisting and a recorded death sit beside the status as restrictions.
- Activation
- A gated write that names every unmet condition at once.
- Home office
- A reporting tag, never a permission boundary: a client is the institution's, not one branch's.
- Import limits
- Up to 5,000 rows and 5 MB per file, in one transaction.
Works with
- LendingVersioned loan products, a quote frozen at submission, approval that reprices, and repayments in your own order.
- Field collectionsThe centre collection sheet, keyed back in as one batch that must equal the cash the officer counted.
- Messaging and integrationsEmail through AWS SES, any HTTP SMS gateway without a release, message templates and signed webhooks.
Clients and KYC: questions
Does it understand Sri Lankan NICs?
Yes. Old and new formats normalise to one form, so the same person cannot be enrolled twice, and Fused warns when the birth date or gender does not match the number.
Can we add our own fields to a client?
Yes. Custom fields and tables add typed fields, dependent choices and computed values to a client or any other record, without a release.
Can we import our existing clients?
Yes, from a CSV file with a dry run that proves the file before anything is written. Moving an existing loan book is planned with you during scoping.
What happens when a rejected client comes back?
They are reopened to pending, keeping their number and history, rather than enrolled a second time.
See it on your own products and numbers.
A walkthrough with the team that builds Fused: your loan products, your branches, your month-end.