Last reviewed: 6 August 2026. When a working-capital or term-loan file comes back with queries — or silence — the cause is usually in the file, not the fates: numbers that disagree across documents, projections without arithmetic, security papers with gaps. Here is the returns map from the appraisal side of the table, written to be fixed. (Educational, from process experience — every bank’s policies are its own.)
The returns map
| Return reason | What the credit team saw | Fix |
|---|---|---|
| Returns ↔ financials mismatch | GST turnover, ITR and statements telling different stories | The reconciliation bridge with reasons — timing/valuation differences explained line-wise |
| DSCR that does not survive arithmetic | Projections reverse-engineered to clear thresholds | Honest driver-based projections with sensitivity; bankable beats optimistic |
| Working-capital ask unjustified | Limits sought without operating-cycle math | The cycle computation: debtors + inventory − creditors, evidenced from your own ageing |
| Stale/incomplete KYC & documents | Old utility bills, unsigned deeds, missing title links | The document freshness sweep before submission — boring, decisive |
| Banking conduct questions | Returns/penal charges/heavy cash in statements unexplained | Pre-empt with the conduct note: what happened, when, why it is past |
| Security/margin gaps | Collateral papers incomplete; margin story thin | Title chains completed and valuations current before, not during, appraisal |
Resubmission playbook
- Ask for the query list in writing — fix the named things first
- Rebuild the CMA so every schedule ties to a filed document
- Add the two bridges most files lack: GST↔books turnover, and bank-statement conduct notes
- Resubmit as a fresh, indexed file — appraisers reward files that respect their time
Frequently asked questions
The bank just went quiet. Is that a rejection?
Often it is a parked file awaiting the queries nobody sent — a polite written request for the pendency list restarts more files than fresh collateral does.
Our GST turnover genuinely differs from books. Fatal?
Differences are normal; UNEXPLAINED differences are fatal. The bridge (timing, inclusions, credit notes) converts the red flag into a footnote.
Should projections show what the banker “wants to see”?
They should show what your drivers support — inflated projections fail at appraisal or, worse, at renewal when actuals betray them. Honest numbers with sensitivity read as competence.
Does switching banks solve a returned file?
The file travels with the same defects — fix it once, then choose lenders on terms. Serial submissions of a weak file also leave enquiry trails.
How much does Udyam/priority-sector status help?
It changes the lending category and targets, which helps files be WANTED — but wanted files still need arithmetic. Pair the certificate with the cycle math.
CC limit vs term loan returned for different reasons?
Yes — CC returns are usually cycle-math and conduct; term-loan returns are DSCR and security. Diagnose per product before rebuilding.
Can a CA “manage” sanction?
No, and walk away from anyone who says so. What professional preparation does is make approval the path of least resistance for a file that deserves it — sanction stays the bank’s call.
What is the fastest single upgrade to a returned file?
The reconciliation bridge plus an indexed file. Appraisers approve what they can verify quickly; friction is the silent killer of marginal files.
We rebuild the CMA, write the bridges and conduct notes, and resubmit an indexed file — then support every query to decision.
CMA Data & Project ReportsBooks & FinancialsRequest a Scope DiscussionThis article is a general educational summary as on 6 August 2026 and is not professional advice or an assurance of any approval, registration or outcome — departmental decisions rest with the authorities on each case’s facts. Requirements change; verify current rules or discuss your specific case before acting.