Table of Contents
Loading table of contents...
Clearing ₹48 Lakhs in Open Bank & Ledger Exceptions in 48 Hours: A Technical Post-Mortem
How an enterprise finance team running on Tally Prime resolved 21 month-end exceptions across unapplied AR cash and TDS mismatches without touching their general ledger.
2026-11-10
Abhranshu Bagchi (Founder & Principal Systems Architect, Misora Labs)
5 min read
Provenance notice — pending founder confirmation
Metrics and timelines on this page describe an illustrative engineering deployment narrative used to explain Finora's deterministic matching behaviour. This is not a named customer endorsement unless explicitly labelled elsewhere with verified provenance.
The Context: Month-End Close Under Strain
At month-end, a high-volume manufacturing and distribution firm running their accounts on Tally Prime faced a recurring operational bottleneck. While day-to-day bookkeeping was disciplined, bank reconciliation (BRS) had accumulated 21 persistent breaks totaling ₹48,22,500 across three bank accounts.
The internal accounting team had spent over 35 hours cross-referencing bank CSV statements, gateway settlement summaries, and Tally sales registers without resolution. Month-end financial reporting was delayed, and working capital was locked in suspense accounts.
The Root Causes of the Break
Our initial diagnosis identified three distinct failure patterns that standard spreadsheets could not solve:
- Pattern 1: Unapplied Customer Remittances (AR Cash): High-value clients paid invoices via RTGS without including invoice references in the narration. The cash landed in the bank, but accountants could not allocate it to specific outstanding debtor vouchers.
- Pattern 2: TDS Withholding Variances: Clients deducted tax at source (Section 194C vs 194J) but failed to provide credit notes or TDS certificates, leaving partial balances open in Tally.
- Pattern 3: Split Gateway Settlements: Payment gateway settlements arrived net of merchant discount rates (MDR) and GST, causing the net bank credit to mismatch the gross customer invoice total.
The Finora Intervention: 48 Hours to Zero Exceptions
We deployed Finora alongside Tally Prime on read-only exports:
- Hour 0–4 (Ingestion): Ingested 90 days of bank statement CSVs, gateway settlement dumps, and Tally Prime XML daybooks into Finora's sandboxed environment.
- Hour 5–18 (Vertis Engine Execution): Finora's deterministic Vertis engine executed multi-pass matching:
- Pass 1: Exact UTR-to-narration matching cleared 11 straightforward exceptions (₹22,10,000).
- Pass 2: 1-to-many invoice bundling and MDR net-off algorithms resolved 6 gateway reconciliation breaks (₹14,87,500).
- Pass 3: TDS variance correlation isolated the exact 2% and 10% withholding lines on the remaining 4 vendor invoices (₹11,25,000).
- Hour 24–48 (Controller Readout & Sign-Off): Presented the financial controller with a ranked review queue showing 100% voucher provenance for all 21 items. The controller signed off on every proposed allocation in under 45 minutes.
Key Takeaways for Finance Leadership
1. Do Not Let Software Write Directly to Your Ledger: Finora’s read-only shadow operation protected general ledger integrity while automating 95% of the investigative toil.
2. Exact Arithmetic is Non-Negotiable: Every rupee of the ₹48.2 Lakhs was reconciled to exact paise using deterministic code—never hallucinated by an LLM.
Topic
Finance & deterministic reconciliationBank reconciliation, ERP-adjacent matching, and controller-safe automation beside systems of record — without autonomous ledger writes.
Related reads
Eliminate month-end reconciliation toil on your infrastructure
Our principal systems architects deploy Finora beside your existing Tally Prime or NetSuite ERP read-only, resolving multi-bank and unapplied cash exceptions with exact-decimal Vertis math.
Actionable Operations Excellence
Autonmis helps modern teams own their entire operations and data workflow — fast, simple, and cost-effective.