MyTaxFlow — Central Bank of India Statement to Tally XML Converter

Central Bank of India Statement to Tally XML Converter

Convert Central Bank NetBanking & mobile app PDF statements to Tally Prime XML. Fast, accurate, and secure.

Updated 4 November 2026 · 6 min read

Central Bank of India is one of the oldest and largest public sector banks, serving millions of customers nationwide. Central Bank statements from NetBanking and the mobile app are widely handled by accounting professionals.

Our Central Bank of India bank statement to Tally XML converter handles all common CBI statement formats automatically. Upload your CBI PDF and download a Tally-ready XML file for direct import into Tally Prime or Tally.ERP 9.

Works with: Central Bank NetBanking PDF, Central Bank mobile app e-statements, Central Bank email statement PDFs, Central Bank Excel/CSV exports, and password-protected PDF statements.
At a glance: the Central Bank of India PDF statement, a Tally company with the bank ledger created, and about five minutes. The conversion runs in the browser; a new Google sign-up includes 15 free page credits for 30 days.

How to Convert Central Bank of India Statement to Tally XML

1 Download your Central Bank of India statement — Log in to Central Bank NetBanking and download your statement as PDF.

2 Upload to MyTaxFlow — Go to the bank statement to Tally XML converter and upload your CBI PDF.

3 Select CBI — Choose Central Bank of India from the bank list.

4 Convert — All transactions are extracted automatically.

5 Download Tally XML — Get your Tally-ready XML file and import into Tally Prime.

How to Import CBI XML into Tally Prime

  1. Open your company in Tally Prime
  2. Press Alt+O (Import) and choose Transactions — shown as Vouchers in some releases. Tally.ERP 9 uses Gateway of Tally → Import of Data → Vouchers
  3. Select the CBI XML file you downloaded
  4. Confirm the import — make sure your CBI bank ledger exists in Tally
  5. Verify entries in Day Book

Why Use a Dedicated CBI PDF to Tally Converter?

Central Bank of India statements have unique characteristics that generic converters fail to handle:

MyTaxFlow's parser is built specifically for Indian bank formats. It correctly handles CBI's Central Bank NetBanking layout, Central Bank mobile app exports, and password-protected statements.

Central Bank of India Account Types Supported

What You Get in the Tally XML Output

Which Central Bank of India statement to download

The source file matters more than the bank's layout. A Central Bank mobile app export and a NetBanking PDF both convert, an email e-statement usually arrives password-protected, and an Excel or CSV export can be uploaded as it is. Keep the same source for the whole period, so the columns do not change halfway through the file.

For a Central Bank of India current account with heavy UPI and NEFT traffic, download the statement as PDF rather than retyping entries. The converter keeps the UTR and reference text inside the narration, which is what makes a later reconciliation possible.

Before you convert: what to check

Common import errors and what they mean

If Tally rejects the file, the cause is usually a missing ledger or a date outside the financial year. Check these first:

What you seeWhy it happensFix
Ledger not foundThe bank ledger or the opposite ledger does not exist in the companyCreate both ledgers, then import the XML again
Voucher type not foundPayment or Receipt voucher types are missing or renamedCheck the voucher types available in the company
Date out of rangeThe voucher date falls outside the active financial yearChange the statement period or the company's book-start date
Duplicate vouchersThe same XML file was imported twiceDelete the extra vouchers in the Day Book with Alt+D, or reset bank statement data
Entries in the wrong companyA different company was open during importOpen the correct company and import again

Reconcile the Central Bank of India ledger after import

The import is only finished when the Tally bank ledger agrees with the statement. Open Bank Reconciliation for the bank ledger and match the closing balance. A mismatch normally means a missing transaction at the edge of the period, a voucher posted to the wrong ledger, or a manually entered opening balance.

If the figures still do not match, delete the imported vouchers from the Day Book with Alt+D or reset the bank statement data from F1 → Troubleshooting → Reset Bank Statement Data, then import again. Take a backup first.

Convert Your Central Bank of India Statement to Tally XML

Import CBI bank statement in Tally Prime instantly. Supports Central Bank NetBanking & all CBI formats.

Convert Central Bank of India PDF to Tally XML Now

Frequently asked questions

Can I convert the Central Bank of India statement PDF to Tally XML?

Yes, when the file is a digital Central Bank of India statement from Central Bank mobile app or NetBanking. A scan or a photo has no text layer, so it cannot be parsed.

Does Tally Prime import the Central Bank of India PDF directly?

No. TallyPrime's Bank Statement import accepts a bank-generated CSV or Excel file for supported banks. A PDF has to be converted to Tally XML first and then imported through Alt+O (Import) → Transactions, which appears as Vouchers in some releases.

Which Central Bank of India statement formats are supported?

Central Bank mobile app and NetBanking PDFs, email e-statements, Excel or CSV exports, and password-protected PDFs up to 50 MB.

Is there a free option?

A new Google sign-up includes 15 free page credits for 30 days. One credit is one PDF page, charged when you download the output.

What if the amounts or dates come out wrong?

Compare the first and last transaction with the PDF, then check the closing balance. A wrong sign on a single amount column or a mixed date format is the usual cause.

Related Guides

How this guide was checked

The import steps, menu paths and error behaviour were tested in TallyPrime and cross-checked against Tally's official documentation for XML import, bank statement import and import errors. Read the editorial policy for how we handle corrections.

Last reviewed: 4 November 2026

Sources