What a UCO Bank e-statement PDF looks like
UCO Bank statements downloaded from NetBanking follow a standard layout. The header carries the account details; the body is a transaction table:
- Account number — a 14-digit number (e.g. 0780…), shown with the branch and statement period in the header.
- Transaction table — Date, Particulars, Credit, Balance, with a closing balance at the end.
- No password — the UCO Bank statement we tested opened directly with no encryption.
Two-digit years and a Particulars column
Two UCO Bank details that matter when you're converting:
- dd/MM/yy dates. The tested statement printed dates like 09/03/24 — a two-digit year. The extractor expands them to a full year before building the voucher, so Tally gets an unambiguous date.
- Particulars column. UCO labels its description column Particulars — the converter reads the actual header, so nothing is missed.
- Closing balance row. Match the last converted row against it as a sanity check.
NEFT-heavy statements
The tested statement's entries were mostly NEFT, each leading with NEFT/… in the Particulars — convenient for mapping outgoing transfers to one ledger.
Convert a UCO statement in three steps
Upload your UCO Bank statement PDF
Download the statement from UCO Bank NetBanking, then upload it. The tested file opened directly — no password needed.
Preview the extracted rows
UCO statements print dates with two-digit years and a Particulars column. Spot-check the rows — dates are read correctly.
Download Tally XML
Export a Tally-ready XML file and import it via Gateway of Tally → Import Data → Vouchers. CSV export is included too.
This works for savings and current account statements from UCO Bank. If your bank isn't UCO, the same flow covers 21 other tested Indian banks — see the full converter.
Importing the XML into Tally
Once you've downloaded the XML, open Tally Prime and go to Gateway of Tally → Import Data → Vouchers, then select the file. New to the import step? Read the step-by-step import guide.