Mumbai handbook · 2,512 words

Mumbai DSA Loan Syndication Handbook: BKC, Fort and Andheri

Mumbai channel desks do not lose files to “lack of hustle.” They lose them to unnoticed inward returns and clerk Excel. This handbook is how 100+ files/week works without manual data entry.

Andheri East brokers and BKC institutional referrers live on TAT. Tata Capital, Bajaj, Piramal, HDFC and Aditya Birla desks will not wait while someone types a Flexcube PDF into a 14-column sheet. The shops that scale to 100+ files a week standardised one rule: the PDF is the book of record; the BSA engine is the typist; the human only reads exceptions.

Floor plan of a high-volume desk

1. Inbox: WhatsApp/email PDFs renamed Bank_Name_Months.pdf
2. Triage: password vs native vs scan
3. Engine: FinAnalyser batch
4. QA: bounce sheet + continuity exceptions only
5. Pack: Excel + FOIR/ABB screenshot + PDF
6. Portal: lender login; no re-key of ledgers

Mumbai bank mix

Lender packs: Tata, Bajaj, Piramal, HDB

BKC committees want bounce-aware turnover, not gross credits. Andheri PL volume wants FOIR and EMI ledger. Piramal housing/BL wants multi-bank continuity. AU SFB wants CC/OD without self-transfer inflation. One Excel pack with Law-4 and Law-6 beats five clerk workbooks.

Math of 100 files/week

100 files × 25 minutes of typing = 41 hours — more than one clerk. 100 files × 4 minutes of QA on an automated pack = 6.7 hours. That is how a two-person Andheri shop outruns a six-person typing floor in Fort. Errors fall because humans stop copying lakhs.

Co-operative banks are not optional in Mumbai

Saraswat, Cosmos, TJSB and SVC appear in SME files. Universal fallback plus continuity is the honest coverage sentence. Do not tell a Fort trader their co-op PDF “isn’t supported” if the identity holds.

Password and privacy on a crowded floor

In-memory unlock. Retention per plan. No shared password xlsx. Mumbai floors leak files; your process should not.

Local landing + tools

Use /dsa-loan-bank-statement-analyzer-mumbai for local lender tables. Use CTS/FOIR/ABB free tools for RM education. Then drop PDFs — the handbook fails if you still type.

Shift design for 100+ files

Morning shift: ingest and passwords. Midday: engine batch and bounce QA. Evening: portal submit and RM queries. Night: only exception PDFs that failed continuity. Do not let evening portals wait on morning typing. SLA is “exceptions same day,” not “all typing same day.” Measure files per analyst per hour on QA, not on keystrokes.

BKC institutional desks may still want a PDF pack plus Excel. Fort traders may want a one-page ABB. Andheri PL wants FOIR. Same engine, different cover notes. Stop maintaining three clerk templates that drift.

Co-lending and dual scrutiny

When Tata and a bank both see the file, bounce splits must survive both cultures. A lumped bounce that bank credit accepts may still fail the NBFC grid. Unmerged Law-4 is the intersection. Co-op PDFs in the pack must parse, or the bank leg dies.

Volume spikes (Navratri, year-end, monsoon lull)

Festival disbursals spike N. Clerk shops hire temps who type worse. Software scales with pay-per-file. That is the Mumbai-specific ROI: your cost curve should follow files, not headcount step functions.

Thane–Navi Mumbai corridor

The corridor feeds Andheri shops with Saraswat/Cosmos/HDFC mixes and salaried plus trader dual books. Treat them as Mumbai files, not as “interior.” TAT expectations are Andheri-like. Co-op PDFs must parse or you lose the trader leg. Train one SOP for the corridor; do not invent a fourth Excel.

Local conveyance and physical document pickup still happen. Software does not replace the boy on the bike. It replaces the boy’s cousin typing HDFC into Excel until 11 p.m. Keep the bike; fire the typing.

What a BKC committee pack contains at 5 p.m.

PDF, continuity-clean Excel, bounce paragraph, FOIR or ABB as relevant, and a one-line exception list. Not a 40-page novel. Not a clerk sheet with yellow highlights on random rows. If Layer-4 failed, the exception list says which page. If it passed, do not apologise for using software. Committees care about surprises. Your job is zero surprise bounces.

Hiring after automation

Hire people who can write the bounce paragraph and talk to RMs. Stop hiring for Excel speed. Interview with a live PDF and the lookup tool. If they cannot tell inward from NACH in five minutes, they are not your QA. If they can, they are more valuable than three typists.

Three Mumbai desks that look the same on Instagram and are not

Bandra-Kurla Complex institutional referrers live on committee packs: bounce-aware turnover, multi-bank continuity, Piramal / Tata Capital / HDFC housing and business files that will be read by someone who has seen every clerk Excel in India. Fort and Nariman Point still mix trade, diamond, and professional books — co-op banks are not optional. Andheri East and the WEH corridor are TAT machines: Bajaj, HDB, Tata, Aditya Birla personal and small business volume, WhatsApp PDFs at 9 p.m., disbursal conversations before lunch. The shops that scale to 100+ files a week did not hire faster typists. They standardised one rule: the PDF is the book of record; the BSA engine is the typist; the human only reads exceptions. If your Andheri floor still re-keys Flexcube into a 14-column sheet, you do not have a volume problem. You have a process that cannot survive page 20.

Thane and Navi Mumbai feed Andheri shops with Saraswat / Cosmos / HDFC mixes and salaried-plus-trader dual books. Treat them as Mumbai files, not as “interior.” TAT expectations are Andheri-like. Co-op PDFs must parse or you lose the trader leg. Local conveyance and physical document pickup still happen. Software does not replace the boy on the bike. It replaces the boy’s cousin typing HDFC into Excel until 11 p.m. Keep the bike. Stop the typing. Password folklore on a crowded floor is an incident: in-memory unlock, no shared “hdfc pass = PAN+DOB” sheet on Google Drive, no group chat named today-passwords.

What each lender pack actually wants at 5 p.m.

A BKC committee pack at 5 p.m. is PDF, continuity-clean Excel, bounce paragraph, FOIR or ABB as relevant, and a one-line exception list. Not a 40-page novel. Not a clerk sheet with yellow highlights on random rows. If Layer-4 failed, the exception list says which page. If it passed, do not apologise for using software. Committees care about surprises. Your job is zero surprise bounces. Andheri PL volume will not wait while someone types. If FOIR takes forty minutes, the RM has already logged a competing file.

The arithmetic of 100 files a week — and why clerks lose

100 files × 25 minutes of typing is 41 hours, more than one clerk, before lunch queues and password hunting. 100 files × 4 minutes of QA on an automated pack is 6.7 hours. That is how a two-person Andheri shop outruns a six-person typing floor in Fort. Errors fall because humans stop copying lakhs. The remaining human work is judgement: inward vs NACH, salary confidence, commercial title vs SB, and the phone call. Hire for that. Stop hiring for Excel speed. Interview with a live PDF and the CTS lookup. If they cannot tell inward from NACH in five minutes, they are not your QA. If they can, they are more valuable than three typists.

HDFC, ICICI, Axis, SBI — and the co-ops that decide SME files

HDFC FLEXCUBE: ACH return charges as credits if narration-type is naive; decimal drift; dedicated netbanking paths when the ledger is dense. ICICI Finacle: 2-token rows; IMPS ids as money if you count tokens instead of money-sanity. Axis: wrap plus Dr/Cr shift. SBI BaNCS: rightmost Balance versus header Close. Saraswat, Cosmos, TJSB, SVC: hybrid prints; header maps from national titans fail; universal fallback plus continuity is the honest coverage sentence. Do not tell a Fort trader their co-op PDF “isn’t supported” if the identity holds. Quality-flag scans. Native CBS exports are the SLA. Festival volumes (Diwali, Navratri, year-end) multiply files; they should not multiply typing. Batch upload, bounce-first QA, parallel passwords in-memory. The handbook fails if you still type.

1. Inbox: WhatsApp/email PDFs renamed Bank_Name_Months.pdf.
2. Triage: password vs native vs scan.
3. Engine: FinAnalyser batch — original PDFs only.
4. QA: bounce sheet + continuity exceptions only.
5. Pack: Excel + FOIR/ABB + PDF; no re-key of ledgers.
6. Portal: lender login; keep Excel for dispute and committee.

See /dsa-loan-bank-statement-analyzer-mumbai for local lender tables. Use CTS, FOIR and ABB free tools for RM education. Production files go through BSA. Night-shift TAT is a Mumbai sport; it is not an excuse to skip inward-cheque QA. The file you logged at 11 p.m. still has page 20.

A realistic high-volume week without a typing floor

Monday: forty Andheri PL PDFs, mostly HDFC/ICICI, FOIR from the engine, three salary-confidence stops, two inward CTS on page 18 that would have been invisible in a skim. Tuesday: BKC housing — multi-bank, bounce paragraph written by the senior in twelve minutes because the ledger was already split. Wednesday: Fort co-op plus Axis; one continuity break on a scan, flagged, customer asked for native PDF, file delayed honestly instead of typed wrong. Thursday: festival spike, batch passwords in-memory, no shared sheet. Friday: committee packs at 4 p.m. with exception lists that name pages, not vibes. That week is 100+ files if WhatsApp intake is disciplined. It is 40 files if you still re-key. The difference is not hustle. It is whether page 20 is a sheet or a rumour.

Syndication across two DSAs sharing one customer is a Mumbai special. If both shops type, you get two FOIRs. If both shops parse, you get the same extract and an argument about exceptions — which is the adult argument. Do not WhatsApp the password with the PDF to the other shop. Send the customer to upload twice or use a controlled workspace. Leakage on a crowded WEH floor is how you lose the principal. The handbook’s compliance section is not decoration. Piramal and HDFC housing files will ask how the statement was obtained. “Clerk typed it from a photo” is not an answer you want in writing.

Diamond, jewellery and wholesale Fort books add cheque velocity that retail PL juniors under-react to. Inward CTS on a trade payable is not “customer bounced a personal cheque.” Outward returns are collection quality. Keep Law 4. ABB on the 5th and 20th because supplier settlements cluster. Contra to sister concerns in BKC entities must not inflate turnover for the committee. If your clerk still copies the credit column into a “sales” sheet, you are manufacturing a sanction you cannot defend. Engine cashflow with Law 6 is the minimum. The senior’s job is naming the sister concern, not totalling.

Andheri East brokers who also run a Fort trade book should not keep two SOPs. Intake, engine, bounce-first QA, then a cover note that names the desk. The WEH volume machine and the BKC committee pack share a PDF spine. What changes is whether you lead with FOIR or with bounce-aware turnover. If you still maintain a “PL Excel” and an “SME Excel” typed by different cousins, you will miss the inward CTS that sits in both books. One engine. Two notes. That is the handbook in one line.