Bulk uploads beat dashboards: cutting remittance TAT 80%
Mar 2025 ยท 4 min read
Our AD2 partners โ EbixCash, MakeMyTrip โ send outward-remittance transactions in bursts. Travel season doesn't spread itself evenly, and Operations was keying tickets in one by one: queues, overtime, and re-keying errors at exactly the peaks when speed mattered most.
The key decision was sociological, not technical: ops lived in Excel, so the automation went to Excel. Any solution demanding a new tool would have died on arrival. We built a validated bulk-upload flow โ row-level validation, so one bad row fails loudly and alone instead of blocking the whole batch.
The second decision: uploaded transactions flow through the existing Core Banking API integrations, not a parallel path. One ledger, one reconciliation story. A shadow pipeline would have doubled every future audit.
Around the upload, two adjacent time-sinks got automated: scheduled RBI compliance reports for the Business team, and risk-mitigation email alerts that flag suspicious transactions to Operations before they settle. Result: 80% TAT cut on the partner flow, on-time compliance at near-zero manual effort.
Lesson I'd generalize: find where the humans already are, automate the seam โ not the human.
keep reading
Benchmark 10 classifiers before trusting one5 minPending transactions need a tracer4 minCorporate ChatGPT is blocked. So I built ToolChat.7 minI built my own bitly โ with the analytics Bitly hides.7 minGroup chat on REST and polling. No WebSockets. (On purpose.)6 minStreaming LLMs through a 20-line edge proxy.5 min