Concurrent Audit for NBFCs With System Access, Not Extracts
Last reviewed: November 2026
Concurrent audit for NBFCs is the examination of lending transactions, such as sanctions, disbursements, cash receipts and Know Your Customer (KYC) records, soon after they happen rather than months later. When auditors depend on spreadsheet extracts sent by the teams they audit, they cannot prove the data is complete, and problems surface weeks too late.
This guide is for heads of internal audit and chief financial officers (CFOs) at non-banking financial companies (NBFCs) and housing finance companies (HFCs). It covers what the Reserve Bank of India (RBI) actually requires, a six-step system-access workflow, eight exception checks worth automating and the metrics that show the audit is working.
Key Takeaways
- There is no standalone RBI concurrent audit direction for all NBFCs, but accounts opened through video-based KYC must pass concurrent audit before they go live.
- RBI's NBFC Internal Audit Function Directions, 2026 require risk-based internal audit for deposit-taking NBFCs and those with assets of ₹5,000 crore and above, and push for new audit tools that reduce manual monitoring.
- Spreadsheet extracts prepared by the auditee are the weakest link, because completeness cannot be proven.
- Read-only system access with standard exception queries turns concurrent audit from document chasing into risk testing.
What Is Concurrent Audit for NBFCs?
Concurrent audit for NBFCs is a near-real-time audit layer that tests individual transactions within days of booking. RBI's description in its bank directions is useful here: concurrent audit "aims at shortening the interval between a transaction and its independent examination."
Preparing for an RBI inspection is a different, periodic exercise, covered in our guide to RBI inspection readiness for NBFCs. This guide is about the day-to-day audit that should make inspection findings rare.
What Does RBI Require From NBFCs on Concurrent Audit?
RBI requires three things that shape concurrent audit for NBFCs: risk-based internal audit for larger NBFCs, an internal audit function that is not outsourced, and concurrent audit of video-KYC accounts. None of them prescribes a branch-by-branch concurrent audit for every NBFC.
| Requirement | Source | What It Means in Practice |
|---|---|---|
| Risk-based internal audit (RBIA) | NBFC Internal Audit Function Directions, 2026 | Deposit-taking NBFCs and those with assets of ₹5,000 crore and above need a risk-based audit plan |
| No outsourcing of internal audit | Same directions, paragraph 39 | Experts can be hired, but audit report ownership stays in-house |
| Access to all records | Same directions, paragraph 40 | The Head of Internal Audit (HIA) and staff can see any record they need |
| Concurrent audit of video-KYC accounts | NBFC Know Your Customer Directions, 2025 | Accounts opened by video-based customer identification stay inactive until audited |
According to the RBI (Non-Banking Financial Companies – Internal Audit Function) Directions, 2026 (RBI/DoS/2026-27/464, 31 July 2026), the board or Audit Committee of the Board (ACB) should "promote the use of new audit tools / new technologies for reducing the extent of manual monitoring." That sentence is a mandate for system access, not more spreadsheets.
According to the RBI (Non-Banking Financial Companies – Know Your Customer) Directions, 2025 (RBI/DOR/2025-26/361, 28 November 2025), an NBFC shall make all accounts opened through Video-based Customer Identification Process (V-CIP) "operational only after subjecting them to concurrent audit." Our guide to video KYC for lenders explains that onboarding flow.
Why Does Concurrent Audit Fail When It Runs on Spreadsheet Extracts?
Concurrent audit fails on spreadsheet extracts for five reasons: the auditee controls the data, completeness cannot be proven, extracts arrive late, samples are chosen by convenience and files leak. Each has a direct prevention check.
| Cause | Effect | Prevention Check |
|---|---|---|
| Branch or operations team prepares the extract | Rows can be filtered, knowingly or not | Auditor runs the query directly, read-only |
| No control totals | Missing records go unnoticed | Match row count and amount to the general ledger |
| Extract requested, then awaited | Days lost before testing starts | Scheduled exception reports ready each morning |
| Auditor samples what is easy to open | High-risk items stay untested | Risk-ranked exception list drives the sample |
| Borrower data emailed as files | Privacy and leakage risk | Access inside a logged, masked environment |
Why Is Auditee-Prepared Data an Independence Problem?
Auditee-prepared data is an independence problem because the people being tested decide what the auditor sees. RBI's internal audit directions give the HIA and audit staff authority to "get access to all records," and a filtered extract quietly undermines that.
The practical trap in concurrent audit for NBFCs is usually innocent, not fraudulent. An operations analyst applies a status filter to "clean up" the file, and cancelled-then-rebooked disbursements disappear from the population.
What Is the Right Concurrent Audit Workflow for NBFCs?
The right concurrent audit workflow for NBFCs has six steps: map risks, provision access, build exception queries, test, track rectification and review coverage. Each step moves effort away from collecting data and towards judging it.
- Map risks by product, branch and process from the annual risk assessment.
- Provision read-only access to the loan origination system (LOS), loan management system (LMS) and ledger.
- Build exception queries for each audit check, with control totals.
- Test exceptions and a random sample, and record evidence in the system.
- Track rectification of every observation to closure, with ageing.
- Review coverage quarterly and rotate auditors across units.
Step 1: Which Areas Should Concurrent Audit Cover First?
Concurrent audit should cover first the areas where money leaves the NBFC or a customer is created: disbursements, cash receipts, sanctions and KYC. These are where a mistake becomes a loss quickly.
RBI's Commercial Banks – Concurrent Audit Directions, 2026 extend coverage to centralised processing centres, including those doing business origination. For an NBFC, that means the central credit hub and disbursement desk deserve the same attention as branches.
Step 2: What Does Read-Only System Access for Auditors Look Like?
Read-only system access for auditors is a dedicated audit role that can view and query, but never edit, every record in the LOS, LMS and ledger. The best setups use a reporting copy of the data, so audit queries never slow down live operations.
Three design points matter. Mask Aadhaar and bank account numbers by default, log every query the auditor runs, and record the data snapshot time on every report.
Our guide to RBI IT governance directions for NBFCs covers information technology (IT) access control and audit trail expectations that apply to this role too.
Steps 3 and 4: How Do You Build Exception Queries That Auditors Trust?
Build exception queries that auditors trust by writing each one from an audit check, testing it against known cases and reconciling its population to the ledger. A query that cannot reproduce last month's known exceptions should not be used this month.
Keep a random sample alongside the exceptions. Rules only find what you already expect, and the random sample is how new patterns are spotted.
Steps 5 and 6: How Should Observations Be Tracked to Closure?
Observations should be tracked in a system where each one has an owner, a risk rating, a due date and evidence of closure. Email trails cannot show the ACB how many high-risk observations are overdue.
RBI's NBFC internal audit directions require pending high and medium risk observations to be reported to the board or ACB. The internal audit issue tracking AI agent shows how artificial intelligence (AI) can monitor open issues without manual follow-up.
Which Exception Checks Should Concurrent Audit Automate?
Concurrent audit should automate eight exception checks: payee mismatch, delegation breach, unapproved deviation, rate outside grid, same maker and checker, back-dated entries, cash not deposited and video-KYC accounts awaiting audit. Each one uses data already in lending systems.
| Exception Check | What It Catches |
|---|---|
| Disbursement payee name differs from borrower or approved third party | Diverted disbursements |
| Sanction amount above the approver's delegated limit | Delegation matrix breaches |
| Credit policy deviation with no recorded approval | Silent deviations |
| Interest rate or fee outside the approved pricing grid | Mispricing, unauthorised waivers |
| Same user as maker and checker on one transaction | Broken maker-checker control |
| Value date earlier than entry date beyond tolerance | Back-dating |
| Cash receipt not deposited by the next working day | Cash held at branch |
| Video-KYC account active before concurrent audit sign-off | KYC Directions breach |
Two of these link to topics covered in our guides to disbursement reconciliation and loan booking errors. The audit check and the operations control should use the same definition, or the two teams will argue about numbers instead of fixing problems.
How many of last month's audit observations started with a spreadsheet someone else prepared?
Talk to Our Software Development Specialists
Visit Digiqt to see how custom software can give your auditors direct, read-only access to lending data.
How Much Time Does System Access Save in Concurrent Audit?
System access can release roughly a quarter of concurrent audit capacity from data collection to actual testing. In this illustrative scenario, an NBFC has 40 concurrent auditors, each working about 176 hours a month.
Assume auditors spend 35% of their time requesting, chasing and cleaning extracts today. With read-only access and scheduled exception reports, assume that falls to 10%.
| Measure | Spreadsheet Extracts | Read-Only System Access |
|---|---|---|
| Auditor hours a month | 7,040 | 7,040 |
| Share spent on data collection | 35% | 10% |
| Hours on data collection | 2,464 | 704 |
| Hours available for testing | 4,576 | 6,336 |
| Population screened by rules | Sample only | Every transaction |
The lesson for leadership: the 1,760 hours matter less than the change in coverage. Moving from a sample of what was sent to a screen of every transaction is what makes concurrent audit genuinely concurrent.
Where Does Custom Software Development Fit in Concurrent Audit for NBFCs?
Digiqt's custom software development service builds web and app products with a dedicated development team, starting with problem statement analysis. Its listed capabilities include user interface and user experience (UI/UX) design with wireframing and prototyping, web and app development, quality assurance, and backend, database, DevOps and data engineering work.
For concurrent audit, those capabilities map to the workflow above. Each piece below can be built around your existing LOS and LMS rather than replacing them:
- Data engineering and database work, to build a read-only audit copy of loan, ledger and KYC data with control totals.
- Backend development, to run the eight exception checks on a schedule and store each result with its data snapshot.
- Web development and UI/UX design, to give auditors a workbench for sampling, evidence upload and observation tracking.
- Quality assurance, to test every exception query against known cases before auditors rely on it.
Start with one high-risk process, such as disbursements, and test the queries on your own past audit findings. Our lending tech stack audit guide helps map which systems hold the data first.
The transaction quality audit AI agent shows how transaction-level checks can be extended with AI once the data foundation is in place.
Which Concurrent Audit Model Fits Each NBFC?
The right concurrent audit model depends on the NBFC's size, product mix and onboarding channels.
| NBFC Situation | Recommended Approach |
|---|---|
| Base layer NBFC below ₹5,000 crore, no deposits | Board-approved concurrent audit of disbursements and cash, with read-only LMS reports |
| NBFC at or above ₹5,000 crore | RBIA plan with an audit data copy and scheduled exception checks |
| Gold loan NBFC with many branches | Daily branch exceptions plus physical collateral checks on a rotating basis |
| NBFC using video-based KYC | Pre-activation concurrent audit queue for every V-CIP account |
| NBFC with external chartered accountant firms doing branch audits | In-house HIA ownership of plans and reports, firms working inside the NBFC's system |
Which Metrics Show Concurrent Audit for NBFCs Is Working?
Five metrics show whether concurrent audit for NBFCs is working: detection lag, coverage, closure time, repeat observations and data requests. Review them quarterly with the ACB.
| Metric | Formula | What a Weak Number Signals |
|---|---|---|
| Detection lag | Days from transaction to audit observation | Audit is periodic in practice |
| Coverage | Transactions screened by rules ÷ transactions booked | Sampling only what was sent |
| Closure time | Days from observation to verified closure | Weak ownership in business units |
| Repeat observation rate | Observations repeated within 12 months ÷ total observations | Root causes not fixed |
| Data requests | Manual data requests raised by auditors per month | Access still incomplete |
Track data requests closely in the first year. When concurrent audit for NBFCs runs on proper system access, that number should fall towards zero within two or three quarters.
Which Mistakes Weaken Concurrent Audit in NBFCs?
Four mistakes weaken concurrent audit in NBFCs, and each one is a design choice.
- Accepting extracts as the population. Without control totals against the ledger, missing rows are invisible.
- Giving auditors edit rights "temporarily". An auditor who can change data is no longer independent of it.
- Running rules without a random sample. The checks only find yesterday's frauds.
- Leaving the same auditor on a branch for years. RBI's bank directions cap a concurrent auditor's stay with one branch or business unit at three years, which is a sensible benchmark for NBFCs too.
What Is Changing Next?
RBI reset audit rules for banks and NBFCs on the same day. According to RBI, the Commercial Banks – Concurrent Audit Directions, 2026 (RBI/DoS/2026-27/409) and the NBFC Internal Audit Function Directions, 2026 (RBI/DoS/2026-27/464) were both issued on 31 July 2026.
The bank directions now spell out risk-based coverage, random transaction testing and auditor rotation. NBFC audit heads should expect inspectors to use them as a reference point, and our compliance calendar for NBFCs can help schedule the resulting board reviews.
Want your next concurrent audit to start with data, not a data request?
Talk to Our Software Development Specialists
Visit Digiqt to see how custom software development can build audit access and exception tracking on your lending systems.
Sources
- RBI: Reserve Bank of India (Non-Banking Financial Companies – Internal Audit Function) Directions, 2026 (RBI/DoS/2026-27/464, 31 July 2026)
- RBI: Reserve Bank of India (Commercial Banks – Concurrent Audit) Directions, 2026 (RBI/DoS/2026-27/409, 31 July 2026)
- RBI: Reserve Bank of India (Non-Banking Financial Companies – Know Your Customer) Directions, 2025 (RBI/DOR/2025-26/361, 28 November 2025)
- Digiqt: Custom Software Development Company



