Originally published at finovo.tech/blog/huf-enterprise-ekyc — the canonical version has the latest updates.
HUFs (Hindu Undivided Families) are a long-standing tax structure that brokers and NBFCs frequently see — and traditionally one of the most paperwork-intensive account types to open. A typical HUF onboarding requires:
- KYC of the Karta (head of family) as an individual
- A separate PAN for the HUF
- The original HUF deed
- Capture of all coparceners (other family members with a share)
- A bank statement in the HUF's name
- Specimen signatures of the Karta on the HUF letterhead
In a paper world this routinely takes 2-3 weeks. Digitally, it's the same 6 documents — but they all flow through one screen.
The Karta-KYC step
The Karta is treated as a regular individual KYC subject for this part — Aadhaar OTP, PAN-OCR, video PD where required by SEBI, address proof. Most brokers already have an individual KYC pipeline; HUF reuses it for the Karta.
The trick is the Karta's KYC and the HUF's KYC are two distinct records. You can't open an HUF account by just having the Karta's KYC; you need a separate HUF-PAN-anchored KYC packet. Plenty of in-house onboarding tools fail here because they assumed "1 customer = 1 KYC".
The HUF PAN
Every HUF needs its own PAN — separate from the Karta's. It's issued by the Income Tax Department on Form 49A with the HUF deed attached. Most HUFs already have one; if not, the customer has to apply (we don't issue PANs).
Validation step: PAN-OCR + an Income Tax Department lookup to confirm the PAN belongs to an entity of type "HUF" (not individual). Without this check, you can accidentally open an HUF-flagged account against an individual PAN — a SEBI violation.
The HUF deed
The HUF deed is the legal document that establishes the family. It names:
- The Karta
- The list of coparceners at the time of formation
- The HUF's name (usually "[surname] HUF" or similar)
- The date of partition / formation
In the digital flow, the deed is uploaded once and parsed (OCR + light NLP to extract the names + dates). The customer reviews the parsed list of coparceners on screen and confirms or edits — usually a 30-second step. The original deed PDF is signed by the Karta with Aadhaar e-sign at the end of the flow.
Coparcener capture
Coparceners are family members with an inherent share in the HUF. SEBI doesn't require their KYC, but they do need to be listed for audit purposes. The flow captures each coparcener's name, relation to Karta, and date of birth — typically pre-filled from the deed parser.
Bank account proof
The HUF needs a bank account in its own name (not the Karta's personal account). A canceled cheque, passbook front-page, or bank statement establishes this.
What enterprise adds
Vanilla HUF eKYC works for one ARN with a standard form. Enterprise HUF eKYC (the enterprise version) adds:
- White-label flow on the broker's domain
- Custom fields per the broker's compliance team (e.g. specific HUF sub-types)
- Integration with the broker's CRM so HUF accounts route to the right RM
- Bulk import for legacy HUF customers being migrated from a paper system
Common edge cases
A few things that look obvious until you ship them:
- Karta change: when an HUF Karta dies, the next-eldest male coparcener becomes Karta. The flow has to re-issue KYC under the new Karta without re-creating the HUF entity.
- Partition: if an HUF partitions, the entity dissolves. We mark the account as closed-by-partition (SEBI category 'partitioned') rather than just inactive.
- Single-coparcener HUFs: legally still HUFs but with quirks around bank-account holding patterns. Most KYC tools mis-classify these as individuals.
Live in production for 15+ Indian brokers. Median Karta-to-account-active time: 8 minutes.
Top comments (0)