Fair Practices Code (FPC)

Definition

The Fair Practices Code (FPC) is a set of guidelines issued by the Reserve Bank of India that banks and NBFCs must adopt to govern transparent, fair conduct in lending, loan servicing, and debt recovery. Among other things, the FPC restricts how recovery and collection agents may engage borrowers—prohibiting harassment, limiting contact to reasonable hours (generally 8 a.m. to 7 p.m.), and requiring civil conduct—and mandates clear disclosure of loan terms, interest, and grievance-redressal channels.

Who this is for

For legal, compliance, and operations teams researching what fair practices code (fpc) means and how it connects to software, workflows, risk controls, and reporting.

Why It Matters

For lenders and collections teams, FPC compliance is a regulatory obligation with direct reputational and penalty risk. Recovery workflows must build in permissible contact windows, agent conduct rules, complaint handling, and documented consent, so that collection activity is both effective and auditable against RBI expectations. Non-compliance can trigger supervisory action and borrower complaints.

Key takeaways

• Fair Practices Code (FPC) helps legal and operations teams create a shared vocabulary for process, risk, and technology decisions.
• Strong fair practices code (fpc) practices improve visibility, accountability, and audit readiness across legal workflows.
• CaseDocker connects fair practices code (fpc) concepts to practical workflows, modules, reporting, and governance.

Examples

• A legal team uses fair practices code (fpc) to standardize how requests, documents, deadlines, and approvals are handled.
• An operations leader reviews fair practices code (fpc) data to identify bottlenecks, risk exposure, and automation opportunities.

Real workflows

Data sources

• Source records can include documents, matter data, contract metadata, notices, tasks, approvals, comments, and audit history.
• Connected workflows may also use imported spreadsheets, API data, eSigning status, email attachments, and reporting exports.

Limitations

• Glossary definitions are operational guidance, not legal advice for a specific dispute, contract, jurisdiction, or regulator.
• Implementation details depend on the customer workflow, source data, permission model, and connected systems.

Related Use Cases

• Obligation Tracking
• Regulatory Compliance Calendar

Related Modules

Frequently asked technical questions

Related reading