Insights · Governance

Audit trail requirements for NBFCs and regulated workflows, explained

An audit trail is the time-ordered record of who did what to a business record, when, and under which authority. For NBFCs in India, two rules shape it: the RBI’s 2026 IT and cybersecurity directions, and the Companies Act edit-log rule for accounting software. Almost every system logs something. The question is whether the log answers what the auditor asks, quickly, and whether anyone could have changed it.

Updated 26 October 20267 min read
Audit trail requirements for NBFCs and regulated workflows, explained

What an audit trail is for

An audit trail is the running record of what happened to a business record: who created it, who changed what, who approved it and when. In lending and funds, it is how you prove that your controls worked, not just that they exist in a policy PDF.

Auditors rarely ask "do you have logs?". They ask things like: who approved this sanction? Was it within their limit? What did the record look like at the moment they approved it? Did anyone touch it afterwards?

What a useful audit trail captures

  • Who. The actual person, or the system or service account, that did it.
  • On whose behalf. Delegations and proxies, recorded as such.
  • What. The action, plus the before and after values.
  • When. A reliable timestamp on every step.
  • Under which authority. The role, limit or policy that allowed it.
  • Context. The version that was reviewed, and the comments, especially on deviations.

What the RBI expects from NBFCs

The RBI’s Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions for NBFCs (31 July 2026) define an audit trail as a chronological record that reconstructs the sequence of activities around an operation or event, from inception to result. What they require depends on the NBFC’s layer and size.

  • Base layer NBFCs with assets of ₹500 crore and above: audit trails must exist for IT assets, meet business, regulatory and legal requirements, support audits, serve as forensic evidence and help resolve disputes, and record any unauthorised user activity (paragraph 21(8)).
  • Middle layer and above: every application or system that can access or affect critical or sensitive information needs audit logging and must provide audit trails (paragraph 109).
  • Those trails must be detailed enough for audits, forensic evidence and dispute resolution, including non-repudiation (paragraph 110).
  • Audit trails and system logs must be monitored regularly to detect, understand or recover from unauthorised activity or attacks (paragraph 111).
  • Data migrations need their own audit trail and sign-offs from business users and application owners at each stage (paragraph 99).
  • Where technology is outsourced, the provider must keep audit trails and admin logs and make them available to the NBFC (paragraph 62(2)(i), base layer ₹500 crore and above).

The Companies Act audit trail rule, which also applies to NBFCs

Separately from the RBI, every company in India that keeps its books in accounting software, NBFCs included, has had to use software that records an audit trail since the financial year starting 1 April 2023. Under the proviso to Rule 3(1) of the Companies (Accounts) Rules, 2014, the software must record an audit trail of each transaction, create an edit log of each change with the date of the change, and not allow the audit trail to be disabled. The statutory auditor reports on it. ICAI’s journal explains the rule and the auditor’s duty in detail in The Chartered Accountant (March 2026).

This rule covers the books of account. It does not cover approvals that happen in email or in a separate workflow system, which is where most lending and fund decisions are made.

The two rules side by side

RBI IT and cybersecurity directions (2026)Companies Act edit-log rule
Applies toNBFCs, by layer and asset sizeEvery company keeping books in accounting software
In force from31 July 2026Financial year starting 1 April 2023
CoversApplications and systems that can access or affect critical or sensitive informationTransactions and edits in the books of account
Key requirementAudit trails good enough for audit, forensics, dispute resolution and non-repudiation, monitored regularlyAudit trail of every transaction, dated edit log, cannot be switched off
SourceRBI/DoS/2026-27/461, paras 21(8), 109 to 111Proviso to Rule 3(1), Companies (Accounts) Rules, 2014

What "tamper-evident" means in plain terms

A tamper-evident log is one where you can’t edit or delete an entry without that change itself showing up. Usually the log is append-only, entries are written as the action happens, and integrity checks make any alteration visible.

Why does it matter? Because a log that an administrator can quietly tidy up isn’t evidence. It’s a claim. Tamper-evidence is what lets you hand the record to an auditor without a knot in your stomach.

The gaps we see most often

  • The change is logged, but not who approved it or on what authority.
  • Shared logins, which make "who" meaningless.
  • Approvals given in email, outside the system that holds the record.
  • No record of which version was approved, so later edits are invisible.
  • Logs that technically exist but take days to search and export.

Stop preparing for audits

The practical goal is that nobody has to "get ready for audit" anymore. If approvals, committee decisions and changes happen inside a governed workflow, the platform records who, what, when and under which authority as a side effect of people doing their jobs. Pulling evidence for a period then takes minutes.

Averoic records a complete, time-stamped audit trail on every action, including on-behalf-of and system actions, alongside maker-checker controls and attribute-based access control.

General information for operations and compliance teams, not legal or regulatory advice. RBI references are to the Reserve Bank of India (Non-Banking Financial Companies – Cybersecurity, Technology: Risk, Resilience and Assurance Framework) Directions, 2026 (RBI/DoS/2026-27/461), which apply by layer and asset size, and to the proviso to Rule 3(1) of the Companies (Accounts) Rules, 2014, as read in October 2026.

DG
· Sales Director, Averoic

Works with alternative lenders, AIFs, NBFCs and insurers in India on approvals, maker-checker controls and audit readiness.

See how your own process would run on Averoic — configured, not coded, with maker-checker controls and a complete, time-stamped audit trail built in.

Frequently asked questions

What should an audit trail include?

Who performed each action, on whose behalf, what changed (before and after), when it happened, under which role or authority, and the version and context of the record, especially for approvals and deviations.

What are the RBI audit trail requirements for NBFCs?

Under the RBI’s 2026 IT and cybersecurity directions for NBFCs, base layer NBFCs of ₹500 crore and above need audit trails that support audit, forensics and dispute resolution and record unauthorised activity (para 21(8)). Middle layer and above NBFCs need audit logging in every system that can access or affect critical or sensitive information, detailed enough for non-repudiation, and regular monitoring of those logs (paras 109 to 111).

Does the Companies Act audit trail rule apply to NBFCs?

Yes. The proviso to Rule 3(1) of the Companies (Accounts) Rules, 2014 applies to every company that keeps its books in accounting software, from the financial year starting 1 April 2023. The software must record an audit trail of each transaction and a dated edit log, and the audit trail cannot be disabled. It covers the books of account, not approvals made outside them.

What is a tamper-evident audit trail?

An audit log where entries cannot be edited or deleted without the change being detectable, usually append-only, written at the time of the action and protected by integrity checks, so it can be relied on as evidence.

How should an audit trail record actions taken by AI models?

Record the model and its version on every action it takes or recommends, in the same trail as the human approvals, along with the person or role it acted for and who approved the result. Treat a change of model, for example when a provider retires a version, as a controlled change: keep a register of where each model version is used, re-test on real past cases, and have a different person sign off before the new version goes live. Months later you can then show which model produced which decision.

How do you make a business process audit-ready?

Run approvals and changes inside a governed workflow with enforced controls (maker-checker, authority limits, role-based access) that records a tamper-evident audit trail automatically, so evidence for any period can be exported on demand.

Start building on your process.

Spin up a free workspace in minutes — no card. Or book a 30-minute walkthrough on your real workflow.