Which bank statement formats does Audit Suite accept?

PDF (text-based or scanned), Excel (.xls and .xlsx), CSV, and tab-delimited. Audit Suite auto-detects whether the first column is the date, the second the cheque number, and so on — across HDFC Bank, ICICI, SBI, Axis, Kotak, IndusInd, Yes Bank and over 30 other Indian banks. No template configuration needed before upload.

How does the matching algorithm work?

Three layers. First, exact amount + cheque number match (catches typical cheque payments and RTGS receipts). Second, exact amount + same-week date match (catches NEFT settlements that hit the bank a day after the Tally entry). Third, fuzzy match on narration keywords for items not caught by the first two layers. Manual review is required only for the unmatched residual.

Does the system handle multi-currency or just INR?

INR is the primary supported currency. EEFC accounts denominated in USD, EUR, GBP are also supported — the system reconciles in the foreign currency and reports the INR equivalent at the closing-rate alongside, which is what the auditor needs for the BRS working paper.

Can I export the reconciliation as a BRS working paper for the audit file?

Yes. The reconciled BRS exports as DOCX (on your firm's letterhead) and PDF. The format follows the standard Indian CA BRS layout: balance as per cash book, add cheques issued but not presented, less cheques deposited but not credited, balance as per pass book — with full backing schedules cross-referenced.

What about stale cheques? Are they flagged?

Yes. Any cheque issued more than 90 days before the balance-sheet date that has not cleared is flagged automatically — these are the cheques the audit team needs to chase, because they may need to be written back to creditors under the Companies Act and the Negotiable Instruments Act.

← Back to Audit Suite

Bank reconciliation software, designed for Indian audit teams.

Bank reconciliation is the second-most time-consuming working paper in an Indian statutory audit — surpassed only by ledger scrutiny. For audits where the client has more than one current account (and they almost always do), it is a week of an articled clerk's life. Audit Suite reduces it to an afternoon. Upload the Tally bank ledger and the bank statement; the platform matches automatically, flags exceptions, and exports a BRS that drops straight into your audit file on firm letterhead.

How the reconciliation works

STEP 1

Upload Tally book ledger

Export the bank ledger from Tally as Excel or CSV. Or pull it directly via the Tally connector once configured. Either way, takes seconds.

STEP 2

Upload bank statement

PDF, Excel, CSV, or tab-delimited — auto-detected. Works with statements from 30+ Indian banks without configuration.

STEP 3

Three-layer auto-match

Amount + cheque number first. Then amount + same-week date. Then fuzzy narration match. Most clearings get matched on layer 1 or 2.

STEP 4

Review the residual

Only unmatched items need attention. Each is flagged with a suggested classification — outstanding cheque, deposit in transit, bank charge, interest, error.

What gets flagged automatically

The whole point of a year-end BRS is not to balance two numbers — it's to identify what needs cleaning up before the financial statements are finalised. Audit Suite raises the items the auditor actually needs to chase:

Stale cheques — issued more than 90 days before the BS date, still not cleared. May need to be written back to creditors or escheated.
Outstanding cheques pre-FY — issued in earlier years, still uncleared at year-end. Almost certainly need write-back.
Suspense items — debits/credits in the bank statement with no matching entry in Tally. Often bank charges, interest, or fraud.
Bouncebacks — cheques credited and then debited within the same month. The receivable hasn't actually been settled.
Double-debits / double-credits — same amount, same cheque number, appearing twice in either system.
Round-trip transactions — equal-and-opposite postings between bank accounts within hours of each other.
End-of-period clustering — disproportionate number of entries in the last three days of the FY. May indicate window-dressing.

Why this matters under SA 240 and SA 500

A year-end BRS is not paperwork — it is the auditor's primary defence against undetected fraud at the cash level. SA 240 (Auditor's Responsibilities Relating to Fraud) makes it explicit that cash and bank transactions warrant heightened scrutiny because they are the easiest accounts to manipulate. SA 500 (Audit Evidence) requires the auditor to obtain sufficient appropriate evidence — which, for a bank balance, means a complete reconciliation, not just a confirmation from the bank.

Audit Suite's BRS module is structured to satisfy both standards: the reconciliation is complete (every item from both sides is classified), the working paper is preserved as evidence (with audit trail), and the exceptions are escalated to the audit team for follow-up.

Indian banks supported

30+ statement formats parsed out of the box

No template configuration — upload and reconcile. If your client banks somewhere not listed, the generic Excel/CSV parser handles it.

HDFC Bank ICICI Bank State Bank of India Axis Bank Kotak Mahindra Bank Yes Bank IndusInd Bank IDBI Bank Punjab National Bank Bank of Baroda Canara Bank Union Bank of India Bank of India Central Bank of India Federal Bank South Indian Bank RBL Bank IDFC FIRST Bandhan Bank DCB Bank Karur Vysya Bank City Union Bank CSB Bank Karnataka Bank Tamilnad Mercantile Dhanlaxmi Bank Indian Bank UCO Bank Indian Overseas Bank Punjab & Sind Bank HSBC India Standard Chartered

Output: a BRS your partner will sign without questions

The final reconciliation exports in the format every Indian CA grew up writing — except now it's pre-filled. The DOCX comes on your firm's letterhead with:

Bank name, account number (last four digits), period of reconciliation
Balance as per cash book (Tally) on BS date
Add: cheques issued but not presented (with detailed schedule)
Less: cheques deposited but not credited (with detailed schedule)
Add / less: bank charges, interest, errors not booked in Tally
Balance as per pass book (bank statement) on BS date
Preparer, reviewer, partner sign-off blocks

FAQ

Does the system store bank statements long-term?

Bank statements uploaded for reconciliation are retained in the engagement file for as long as the audit file is retained (the SA 230 retention requirement is 7 years from report sign-off; many firms keep them 10 years). Statements are encrypted at rest using AES-256-GCM, accessible only to authorised staff at your firm.

Can we reconcile multiple accounts at once?

Yes. For clients with multiple current accounts — typical for manufacturing and trading entities — each account is reconciled separately, and the platform produces a consolidated BRS summary at the entity level that ties to the cash and bank line in the financial statements.

What if the bank statement is a scanned PDF (image only)?

Audit Suite runs OCR on scanned PDFs as a fallback. Recognition quality on bank statements from major Indian banks is high enough that auto-matching still works for most line items; the residual that OCR can't parse cleanly is flagged for manual review.

Does it work for cooperative banks and rural / urban cooperative banks?

Yes — the generic Excel/CSV parser handles statements from cooperative banks. The bank-specific parsers are tuned for the major commercial banks; cooperative bank statements typically use simpler formats that the generic parser handles well.

Is the BRS module separately priced?

No — it is included in the Pro plan (₹2,999/month) along with Tally integration and the rest of the audit toolkit. There is no per-reconciliation or per-account fee.

Reconcile a week of bank statements in one afternoon.

14-day free trial · Full feature access · No credit card required

Start free trial →