Centralised Operations Hub for NBFCs: Design Guide
Last reviewed: November 2026
A centralised operations hub for NBFCs is a single back-office team that processes loan files for many branches, handling data entry, document checks, disbursement and post-disbursement work under one standard process. Most non-banking financial companies (NBFCs) want the cost and control benefits, but fear that moving work away from branches will add days to every loan.
This guide is for chief executive officers (CEOs) and chief operating officers (COOs) planning a hub. It covers which functions to move, what Reserve Bank of India (RBI) directions allow, how to protect turnaround time (TAT), the economics, and how Digiqt can build branch-to-hub workflows on the Digiqt Lending Platform.
Key Takeaways
- Move processing, not relationships. Rule-based work goes to the hub; borrower contact stays at the branch.
- Scan first, courier later. Hubs slow loans only when paper must arrive before work starts.
- RBI limits what a third party can run. Loan sanction and compliance decisions cannot be outsourced.
- Hand-offs can be made systematic. Queues, service levels and live file status can run on one platform.
What Is a Centralised Operations Hub for NBFCs?
A centralised operations hub for NBFCs is the back office of a hub-and-spoke model, where branches act as spokes that source and serve borrowers and the hub processes their files. Hubs can be national or regional, and many lenders start with one hub per state cluster.
| Model | Branch Does | Hub Does | Typical Fit |
|---|---|---|---|
| Fully branch-led | Everything | Nothing | Small lenders, under 20 branches |
| Regional hub | Sourcing, field work | Processing for one state or cluster | Lenders spread across languages and states |
| National hub | Sourcing, field work | Processing for all branches | Standard products, high volumes |
| Hybrid | Sourcing plus urgent cases | Standard processing | Mixed secured and unsecured books |
Which Functions Should Move to a Centralised Operations Hub?
Six functions usually move to the hub: file data entry, document verification, disbursement processing, post-disbursement document (PDD) tracking, repayment mandate processing and loan closure. These are high-volume, rule-based tasks where specialist teams work faster and make fewer errors than generalist branch staff.
| Function | Move to Hub? | Reason |
|---|---|---|
| Login data entry | Yes | Volume and standard fields |
| Document verification | Yes | Specialist checks, one standard |
| Credit underwriting | Yes, with branch input | Separates sales from credit |
| Disbursement processing | Yes | Payment control |
| PDD tracking | Yes | Central follow-up |
| Personal discussion and field checks | No | Needs the borrower |
| Collateral inspection | No | Location-bound |
Login data entry is often the first function to move. Our guide to loan login desk automation covers how that desk can work from structured data instead of paper.
Which Functions Should Stay at the Branch?
Five functions should stay at the branch: sourcing, document collection, personal discussions, field and collateral verification, and local collections. Branches also remain the place where many borrowers collect original documents after closure.
What Does Branch-Level Processing Cost Compared With a Hub?
Branch-level processing costs more because every branch carries its own operations staff, whose time is split across tasks and uneven through the month. In this illustrative scenario, 60 branches process 18,000 files a month.
| Measure | Branch-Led Processing | Centralised Hub |
|---|---|---|
| Operations staff | 120 (2 per branch) | 70 |
| Files per person a month | 150 | About 257 |
| Monthly cost to company (CTC) per person | ₹35,000 | ₹38,000 |
| Staff cost a month | ₹42.0 lakh | ₹26.6 lakh |
| Scanning and courier a month | – | ₹3.0 lakh |
| Total a month | ₹42.0 lakh | ₹29.6 lakh |
The hub saves ₹12.4 lakh a month, or about ₹1.49 crore a year, before technology costs. Our guide to branch profitability for NBFCs shows how lower operations cost changes branch break-even.
What Do RBI Rules Say About Centralising Loan Operations?
RBI rules shape a centralised operations hub in four ways: who may run it, who may do video KYC, where documents are returned and how offices are closed. An in-house hub staffed by the NBFC's own employees is not outsourcing, but a vendor or group entity running it is.
| RBI Instrument | Rule | Hub Design Impact |
|---|---|---|
| NBFC Managing Risks in Outsourcing Directions, 2025 (RBI/DOR/2025-26/363), para 6(1) | Outsourcing includes using a group entity or outside party for continuing activities | Vendor or group-run hubs need outsourcing governance |
| Same Directions, para 15 | Core management functions and decisions such as loan sanction cannot be outsourced | Sanction authority stays with NBFC staff |
| NBFC Know Your Customer (KYC) Directions, 2025 (RBI/DOR/2025-26/361), para 27(2)(i) | Video-based Customer Identification Process (V-CIP) is run only by trained NBFC officials | A hub can run V-CIP with its own staff |
| NBFC Responsible Business Conduct Directions, 2025 (RBI/DOR/2025-26/362), paras 35 to 39 | Original documents returned within 30 days of repayment, at the servicing branch or another office holding them; ₹5,000 a day for delay | Hub storage must support fast branch returns |
According to para 102 of the same Responsible Business Conduct Directions, an NBFC must give at least three months' public notice before closing any branch or office. That matters if centralisation leads to merging branches.
How Do NBFCs Keep Loans Fast After Centralising?
NBFCs keep loans fast after centralising by fixing three design choices: how files reach the hub, how the hub queues work and how branches see status. Getting any one wrong adds days.
How Should Files Travel From Branch to Hub?
Files should travel to the hub as scanned images on the day of login, with physical originals following on a fixed courier cycle. The hub works from images, and originals go straight to storage, which our guide to loan document vaulting covers in detail.
Every hand-off of paper should be logged, as described in our guide to loan file movement tracking.
How Should the Hub Prioritise Its Queues?
The hub should split work into specialist queues and order each one by service level targets, not arrival order alone. Our guide to credit underwriting queue management explains ageing, priority and capacity rules that apply equally to operations queues.
| Hub Queue | Service Level Target (Illustrative) | Daily Cut-Off |
|---|---|---|
| Login and data entry | 4 working hours | 3 pm |
| Document verification | 6 working hours | 2 pm |
| Disbursement | Same day | 1 pm |
| PDD follow-up | Weekly cycle | – |
How Does the Digiqt Lending Platform Support a Centralised Hub?
The Digiqt Lending Platform supports a centralised hub by giving branches and the hub one system for uploading files, working queues and releasing disbursements. Every stage then leaves a timestamp both sides can see.
The Digiqt Lending Platform lets fintech startups and NBFCs launch a custom lending product or platform in weeks, covering onboarding, disbursement and repayments through user-friendly application programming interfaces (APIs). Digiqt can build the branch-to-hub workflows below on it as configurable, custom-built workflows.
| Stage | Manual Today | With Workflows on the Digiqt Lending Platform |
|---|---|---|
| Login | Branch couriers the file | Branch uploads scans during onboarding |
| Allocation | Hub supervisor assigns by email | Files routed to hub queues by rule |
| Processing | Status chased on phone | Stage and owner visible to branch and hub |
| Disbursement | Payment sheets prepared by hand | Disbursement through APIs after checks |
| Repayment setup | Mandates tracked in spreadsheets | Repayments set up within the same platform |
Your credit policy, sanction authority and hub staffing remain your decisions. Hub software hosted or run by a vendor can also count as information technology (IT) outsourcing, and according to a Vinod Kothari analysis, middle layer and higher NBFCs had to align older IT contracts by 10 April 2026 or at renewal, whichever came first.
Digiqt's process bottleneck intelligence AI agent page shows how stage timestamps can reveal where files wait.
Worried that a central back office will add days to every loan?
See How the Digiqt Lending Platform Supports Hub Workflows
Find out how onboarding, disbursement and repayment flows run on one platform, or discuss your hub design with our lending team.
Worked Example: Moving 40 Branches to One Hub
In this illustrative example, a scan-first hub cut average login-to-disbursement time from 74 working hours to 34, a fall of 54%. A courier-first design would have added about 48 hours of transit and made loans slower than before.
| Stage | Branch Model (Hours) | Scan-First Hub (Hours) |
|---|---|---|
| Login and data entry | 10 | 4 |
| Document verification | 16 | 6 |
| Credit queue wait | 24 | 12 |
| Sanction conditions and agreement | 16 | 8 |
| Disbursement | 8 | 4 |
| Total | 74 | 34 |
Most of the gain came from queue discipline and specialist checks, not from faster typing. Errors found at booking also fell, which our guide to loan booking errors explains.
How Should an NBFC Phase the Move to a Centralised Operations Hub?
An NBFC should phase the move to a hub in four stages: one pilot cluster, one function at a time, a parallel run and then a full cut-over. Moving every branch and function at once is the most common cause of backlogs in the first month.
| Phase | Scope | Exit Test |
|---|---|---|
| Pilot | 5 to 10 branches, login and verification only | TAT no worse than branches |
| Expand functions | Add disbursement and PDD | Error rate below branch baseline |
| Parallel run | Branch staff shadow hub for one month | Backlog under one day |
| Cut-over | All branches in the cluster | Branch staff redeployed to sales |
Which Metrics Show the Hub Is Working?
Four metrics show the hub is working: TAT by stage, first-time-right rate, backlog age and branch satisfaction. Exceptions that bounce between hub and branch should be tracked separately, as our guide to loan servicing exception queues describes.
Ready to turn branches into sales points and one hub into your processing engine?
See How Digiqt Builds Centralised Loan Operations
Learn how Digiqt builds custom lending workflows for NBFCs, or visit Digiqt to schedule a conversation.



