Tally Bank Import Testing

I am finalising a SaaS feature that lets Indian businesses push bank statements straight into Tally and I need fresh eyes on the workflow before release. Your job is to run real-world statements from multiple Indian banks through the importer, watch how Tally handles them, and tell me exactly where things break or mis-map.

Scope of the test
• Main task: validate the import itself—does the statement land in Tally exactly as it appears at the bank?
• File formats you will feed in: PDF statements, Excel or CSV statements, statements downloaded directly from bank websites and any Tally XML files you already generate.
• Post-import checks: confirm every transaction is read correctly, the closing balance and dates match the source, and that the tool flags (or silently creates) any duplicate or missing entries.

What I need from you
1. A mix of current statements from several Indian banks—enough variety to cover different layouts, naming conventions and encodings.
2. Screen-recorded walkthroughs or annotated screenshots of each import run.
3. A concise defect log listing incorrect parses, balance mismatches, duplicate handling issues or crashes, with the exact file that caused each problem.
4. A quick confirmation report when a format imports perfectly so I know it’s covered.

I will supply the build of the SaaS connector, a clean Tally data set and any access keys required. If you are already comfortable with Tally ERP/TallyPrime and routinely reconcile multiple Indian bank accounts, this should slot neatly into your workflow.