Bank Statement to Tally Prime 7.0 Using TDL: Complete Guide for Accurate Accounting

Call CA Tally HelpDesk +91 9205471661, 8368262875

Managing bank transactions is a critical task for every business. Ensuring that transactions recorded in accounting software match the bank statement is essential for accurate reporting, timely reconciliation, and error-free financial records.

While manual entry is slow and prone to mistakes, using TDL (Tally Definition Language) in Tally Prime 7.0 automates bank statement imports, saving time and improving accuracy. This guide explains how to import bank statements to Tally Prime 7.0 using TDL step by step, along with best practices and common pitfalls to avoid.

What Is Bank Statement to Tally TDL Conversion?

TDL (Tally Definition Language) is a powerful tool in Tally Prime that allows automation and customization. Bank statement to TDL conversion is the process of converting bank transaction data (usually in CSV or Excel format) into TDL-compatible entries so that Tally automatically creates vouchers like:

• Bank Receipts
• Bank Payments
• NEFT / RTGS / IMPS transactions
• Cheque payments
• Bank charges and interest entries

With this method, there is no need for manual voucher entry, which saves time and ensures accurate accounting.

Why Businesses Prefer Using TDL for Bank Imports

1. Time-Saving – Manual entry for hundreds of transactions is time-consuming. TDL imports all transactions automatically.
2. Error Reduction – Avoid typing errors, wrong amounts, or skipped entries.
3. Faster Bank Reconciliation – Once imported, reconciliation becomes straightforward.
4. Scalable – Perfect for businesses with high transaction volumes or multiple bank accounts.
5. Audit-Ready – Ensures consistent and complete accounting records.

Supported Bank Statement Formats

TDL-based bank import usually works with:

• CSV (.csv) – Most common and easy to map in TDL
• Excel (.xls / .xlsx) – Easy to clean and organize
• PDF – Not recommended as TDL cannot read PDF directly

Best practice: Always use CSV or Excel for smooth TDL processing.

Prerequisites Before TDL Import

Before importing bank statements into Tally using TDL:

1. Bank Ledger Exists – The ledger name in Tally should exactly match the bank account name in the file.
2. Party Ledger (Optional) – If party-wise mapping is required.
3. Correct Accounting Period – Voucher dates should fall within the active financial year.
4. Backup of Tally Data – Always create a backup before any import.

Step-by-Step Process: Bank Statement to Tally TDL

Step 1: Prepare Bank Statement

• Download the statement from your bank portal in CSV or Excel.
• Include:
  • Transaction Date
  • Narration / Description
  • Debit Amount
  • Credit Amount
  • Balance (optional)

Tip: Remove blank rows, avoid merged cells, and maintain consistent date formats.

Step 2: Create or Use a TDL Script

A TDL script reads the bank statement and automatically creates vouchers in Tally Prime.

Sample TDL Logic:

[System: UDF]

CSVFilePath : String : "C:\\BankStatement.csv"

[Function: Import Bank Statement]

Parameter: CSVFilePath : String

01 : SET FileName : ##CSVFilePath

02 : READ FILE : ##FileName

03 : FOREACH Line

04 :     SPLIT : , : ##Fields

05 :     CREATE VOUCHER : ##BankVoucher

06 :         SET DATE : $$StringToDate:##Fields[1]

07 :         SET PARTYLEDGERNAME : "Bank Ledger"

08 :         IF ##Fields[4] = "Dr" THEN

09 :             SET AMOUNT : ##Fields[3]

10 :             SET ISDEEMEDPOSITIVE : Yes

11 :         ELSE

12 :             SET AMOUNT : ##Fields[3]

13 :             SET ISDEEMEDPOSITIVE : No

14 :         ENDIF

15 :         SET NARRATION : ##Fields[2]

16 :     END CREATE

17 : NEXT

Key Points:

• ISDEEMEDPOSITIVE differentiates Debit / Credit.
• Narration is automatically mapped from bank statement description.
• Vouchers are generated without manual intervention.

Step 3: Load TDL in Tally Prime 7.0

1. Open Tally Prime 7.0.
2. Go to F12 > Product & Features > Manage Local TDLs.
3. Load your .tdl file.
4. Run the Import Bank Statement function and provide the CSV/Excel path.

Step 4: Verify Imported Transactions

• Go to Display > Day Book.
• Check all vouchers for:
  • Correct dates
  • Correct debit and credit amounts
  • Accurate narration
• Make corrections if any mismatched ledger names or amounts appear.

Step 5: Reconcile Bank Ledger

• Go to Bank Reconciliation Statement in Tally Prime.
• Match imported transactions with bank statements.
• Identify and clear unmatched entries.

Common Mistakes to Avoid

1. Ledger Name Mismatch – The bank ledger name must match exactly.
2. Incorrect Date Format – Use consistent DD-MM-YYYY format.
3. Duplicate Imports – Avoid importing the same file twice.
4. Ignoring Exceptions – Always check Tally’s exception report after import.

Advantages of TDL-Based Bank Import Over Manual Entry

Best Practices

• Maintain consistent bank ledger names.
• Import monthly or period-wise to avoid large data errors.
• Verify CSV/Excel files before import.
• Keep backups of Tally data.
• Reconcile immediately after importing.

Who Should Use TDL Bank Import

• Chartered Accountants and CA firms
• Accounting service providers
• MSMEs and small businesses
• Businesses with multiple bank accounts and high transaction volumes

Conclusion

Using TDL in Tally Prime 7.0 for bank statement imports ensures accurate accounting, reduces manual effort, speeds up reconciliation, and prepares data for audits efficiently. With proper preparation, clean statements, and careful TDL mapping, businesses can automate their bank accounting workflow and focus on strategic financial management.

Frequently Asked Questions