MyTaxFlow — UCO Bank Statement to Tally XML Converter

UCO Bank Statement to Tally XML Converter

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

Updated 4 November 2026 · 6 min read

UCO Bank is a major public sector bank in India with a strong presence in Eastern and North-Eastern India. UCO statements from NetBanking and the UCO app are widely handled by CA firms and small businesses.

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

Works with: UCO NetBanking PDF, UCO app e-statements, UCO email statement PDFs, UCO Excel/CSV exports, and password-protected PDF statements.
At a glance: the UCO Bank 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 UCO Bank Statement to Tally XML

1 Download your UCO Bank statement — Log in to UCO NetBanking and download your statement as PDF.

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

3 Select UCO — Choose UCO Bank 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 UCO 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 UCO XML file you downloaded
  4. Confirm the import — make sure your UCO bank ledger exists in Tally
  5. Verify entries in Day Book

Why Use a Dedicated UCO PDF to Tally Converter?

UCO statements have unique characteristics that generic converters fail to handle:

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

UCO Bank Account Types Supported

What You Get in the Tally XML Output

UCO Bank Statement Conversion Checklist

UCO Bank statements can include savings, current, cash credit and branch-generated formats. This checklist helps prepare the file for reviewable XML output.

  • Select UCO Bank in the converter before uploading the PDF.
  • Use a digital UCO statement instead of an image scan or photo PDF.
  • Review cheque, transfer, service charge and interest rows in the preview table.
  • Download normalized CSV if you want to verify the rows before importing XML into Tally.
Related workflow: Start with the bank statement to Tally XML converter, read the Tally XML format guide, and then import the downloaded XML through Gateway of Tally.

Which UCO Bank statement to download

The source file matters more than the bank's layout. A UCO 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 UCO Bank 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

Most failures after a conversion come from the Tally side, not from the PDF. These are the usual ones:

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 UCO Bank ledger after import

After the vouchers are imported, the bank ledger closing balance should match the closing balance printed on the statement. Open Bank Reconciliation for that ledger and compare the two figures. If they differ, the usual causes are a transaction missing from the start or end of the period, a voucher posted to the wrong ledger, or an opening balance entered by hand.

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 UCO Bank Statement to Tally XML

Import UCO bank statement in Tally Prime instantly. Supports UCO NetBanking & all UCO formats.

Convert UCO Bank PDF to Tally XML Now

Frequently asked questions

Can I convert the UCO Bank statement PDF to Tally XML?

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

Does Tally Prime import the UCO Bank 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 UCO Bank statement formats are supported?

UCO 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