Skip to content
Finin2min
RBI · Returns and Annexures

RET-08: DNBS14 P2P parameters

Paragraph-level professional implementation page for Returns and Annexures.

Returns and AnnexuresRET-08BR Act, RBI Act and SARFAESI enabling provisions

Finin2min Summary — in 2 Minutes

RET-08 — DNBS14 P2P parameters. Quarterly NBFC-P2P financial and prudential data.

Official source and legal ownership

Instrument ownerBR Act, RBI Act and SARFAESI enabling provisions
Source statusCURRENT OFFICIAL SOURCE GATEWAY
Review date2026-07-19
Primary sourceFiling of Supervisory Returns Directions, 2024

Paragraph-wise Finin2min interpretation

Legal trigger

Quarterly NBFC-P2P financial and prudential data.

Control owner

Business identifies the event; Compliance confirms law; Operations/Technology executes; Independent review tests evidence.

Evidence

Official source snapshot, policy/SOP, system rule, customer/transaction record, maker-checker log, exception approval and regulatory acknowledgement.

Failure consequence

Customer harm, reporting defect, prudential misstatement, supervisory observation, monetary penalty, restriction or remediation.

Practical example

Scenario: An exception arises under DNBS14 P2P parameters. The owner records the trigger, regulated entity, paragraph/reference RET-08, affected customer or exposure, applicable threshold, approval and system evidence. Compliance then tests the result against the official source rather than relying on a generic policy statement.

Implementation and evidence controls

Practical Q&A

What is the first test for DNBS14 P2P parameters?

Confirm entity, product, event date, official paragraph and any stated exception.

Can a portal or system acceptance cure a legal defect?

No. Technical processing does not override the substantive Direction.

What should be retained for review?

The official source version, legal mapping, calculation or decision record, approvals, communications and filing evidence.

← PreviousNext →