How to Import Bank Statements into BUSY and Reconcile Them

To import bank statements into BUSY, first check which BUSY 21 release and edition is installed. Current releases expose a Bank Statement utility under Administration → Data Export/Import, with predefined bank formats and an option to configure a format. The source data can then be brought in from a supported spreadsheet format or pasted into the grid, depending on the screen available in that installation.

Three jobs sit behind the phrase “bank statement import”, and they are not interchangeable:

• Import statement rows: bring the bank-side transactions into the dedicated utility in the format BUSY expects.
• Reconcile existing vouchers: match those rows against Receipt, Payment, Contra or other entries already recorded in the books.
• Create missing vouchers: make an accounting entry only after deciding that the transaction is absent and determining the correct voucher type and ledger treatment.

The dates explain why BUSY’s own search results appear contradictory. The BUSY 21 release history records that release 10.5, dated 9 May 2024, introduced Import Bank Statement under Administration → Data Export/Import, including predefined or configurable bank formats, Excel or grid input, and default-account mapping. Release 11.6, dated 11 November 2024, subsequently added automatic reconciliation using Excel statements and more default bank formats.

Older BUSY FAQs describe importing Receipt or Payment vouchers from Excel and then entering clearing dates with F4. That guidance reflects the workflow available before the dedicated statement utility, and it may still be relevant to an older installation or to the separate task of creating vouchers. It should not be read as a current, universal statement that BUSY cannot import bank data.

Confirm the version, edition and visible menu before proceeding. Importing rows does not by itself prove that every transaction has been posted correctly, matched to the right voucher or protected from duplication. Unmatched and ambiguous items need review before any accounting entry is created.

Choose the operation before you touch the file

Start with one question: is the transaction already in the books? The answer determines what the bank file should be used for.

Position in BUSY	Appropriate operation	Main control
The voucher already exists	Import the statement rows and reconcile them against the recorded voucher	Confirm the amount, date, reference and bank account before accepting a match
The transaction is genuinely missing	Create or import the appropriate accounting voucher, then reconcile it	Decide the voucher type and ledger treatment before posting
It is unclear whether an entry exists	Keep the line unmatched while you investigate	Search the ledger by amount, date range, narration and reference

The distinction matters because a bank line is evidence of movement in the account, not a complete accounting instruction. A debit on the statement could be a supplier payment, bank charge, loan instalment, transfer or reversal. The file alone does not decide which ledger should be used or whether an entry has already been recorded with a different narration.

Automatic reconciliation assists with matching. It is not a blanket instruction to post every unmatched line, and it does not establish that the same date range is safe to import repeatedly. Where several transactions share an amount, check other fields rather than accepting an amount-only match.

Import routes are also specific to the destination system. The supported paths and controls in bank statement import routes in TallyPrime should not be assumed to apply to BUSY simply because the source spreadsheet contains the same transactions.

Prepare Excel or CSV data for the selected BUSY format

Use the bank’s native Excel or CSV export if one is available. It retains transaction columns more reliably than a PDF conversion, but the file extension is not a compatibility guarantee. In BUSY, choose the predefined format for the relevant bank or configure a format that matches the actual columns in the export.

Map by meaning, not by column position:

Source field	What to establish before import
Transaction date	The date the bank records for the movement; do not silently substitute the value date or clearing date
Clearing or value date	Retain separately when supplied and when the selected BUSY format accepts it
Reference	Preserve cheque number, UTR, transaction ID or other bank reference to support matching
Narration	Keep enough text to identify the counterparty and investigate an exception entry
Debit and credit	Confirm the bank’s direction convention and map separate columns correctly
Signed amount	If the export uses one amount column, confirm which sign represents money in and money out before configuring it

The transaction range should contain transaction rows only. Exclude opening and closing balances, carried-forward figures, subtotals, page headers, repeated column headings, blank lines and footer notes. Keep an untouched copy of the bank export, then clean a working copy so every imported row can be traced back to its source.

Check spreadsheet types as well as visible values. Dates that look identical on screen may be stored as text in one row and native dates in another. Amounts can contain commas, currency symbols or brackets that affect parsing. References with leading zeroes should not be converted to numbers. If a configured BUSY format expects separate debit and credit columns, do not feed it a signed amount column without transforming and checking the direction first.

Reliable transaction handling is becoming more consequential as digital payment volumes grow. According to RBI's 2025–26 payment-system data, cashless transaction volume grew by 26.8% during 2025–26, after 34.8% growth in the previous year.

Before processing a full month, test a few representative rows: one debit, one credit, a transaction with a long narration, and any row with a separate clearing date. Review how BUSY interprets them, correct the mapping if necessary, and only then use the complete period.

Import, match, and review exceptions without duplicate postings

In a current BUSY release, open Administration → Data Export/Import → Bank Statement. Choose the relevant predefined bank format or the configured format you tested, select the prepared file or paste the rows into the grid, and complete any default-account mapping the screen requires. The labels and controls can change by release or format, so treat the screen in your installation and current BUSY help as authoritative for the final choices.

Keep the first run controlled:

1. Limit the import to the exact account and statement period being reconciled.
2. Confirm the first and last transaction dates and the row count against the source statement.
3. Inspect debit and credit direction, dates, references, narration and amounts in the preview or imported grid.
4. Review candidate matches before accepting them, particularly where the same amount appears more than once.
5. Record or export the exceptions so they are not lost when the reconciliation work is handed to another person.

A strong candidate match agrees on more than the amount. Check the bank account, transaction or clearing date, cheque number or UTR, narration and the voucher already in BUSY. Timing differences are normal: a cheque entered in the books on one date can clear later. That is a reconciliation difference, not necessarily a missing accounting entry.

Unmatched lines need classification before action. Common cases include:

• a legitimate Receipt or Payment voucher that has not been recorded;
• bank charges or interest requiring the correct ledger and accounting treatment;
• a reversal paired with an earlier failed or returned transaction;
• a transfer between bank accounts recorded from the other side;
• an existing voucher with a different reference, narration or clearing date; and
• a statement row outside the intended period or duplicated in the prepared file.

Do not convert every unmatched line into a voucher. First establish the correct explanation, then enter or import only the transactions that are genuinely absent from the books. If an item is ambiguous, leave it unmatched and investigate the source documents or obtain approval rather than forcing a match.

After processing the exceptions, compare the reconciliation report with the statement balance and review the bank ledger for the period. Before importing the same date range again, establish what the first run imported, matched or posted. BUSY’s public material confirms statement import and automatic reconciliation features, but it does not establish a universal duplicate safeguard for every release, edition and configured format.

---

Convert a PDF statement before mapping it to BUSY

A native bank spreadsheet is the better source whenever the bank provides one. A PDF or scan adds an extraction step, and the resulting rows must be checked against the statement before they are mapped to BUSY.

For a PDF bank statement to BUSY workflow, request one transaction per row and keep the fields needed for both mapping and exception review. These usually include transaction date, clearing or value date where present, reference, narration, debit, credit, amount, and balance. If the statement uses one signed amount column, preserve the sign convention. Exclude opening and closing balances, page totals, repeated headers and non-transaction summaries.

Invoice Data Extraction accepts native or scanned PDFs and image files. You upload the statement and describe the required fields and row structure; the system analyses the documents, asks a brief clarifying question when the instructions leave a material ambiguity, and presents an extraction plan for approval before processing. The result can be downloaded as XLSX or CSV. Values that warrant checking can be marked Review Needed, and output rows can carry source-file and page references for comparison with the original.

That makes it possible to extract bank statement data into Excel or CSV as a preparation step. It does not connect to the bank, decide the accounting treatment, post Receipt or Payment vouchers, enter clearing dates, or reconcile transactions inside BUSY. The accountant still reviews the rows, selects or configures the relevant BUSY format, maps the columns, and decides what to do with unmatched items.

If the PDF contains rotated pages, faint scans, multi-line narrations or totals repeated at page breaks, test several representative pages before processing the full period. Compare the extracted row count and period totals with the source, then spot-check high-value entries, charges, reversals, references and any Review Needed cells. The broader guide on how to convert a PDF bank statement to Excel covers conversion methods in more detail; the BUSY-specific task begins after the transaction table has been verified.

---

When the older voucher-import and F4 route still applies

If Administration → Data Export/Import → Bank Statement is not visible, confirm the installed BUSY release and edition before changing the source file. The company may be using a release from before the dedicated utility was introduced, or the available feature set may differ from the current product page. Current BUSY support or the help material for that installation should settle which route is available.

The older workflow remains relevant in two situations: the installation does not expose the newer statement utility, or the accountant has established that missing transactions must be created as vouchers. At a stable level, that route is:

1. Prepare separate Excel data for the relevant Receipt or Payment vouchers.
2. Open Administration → Data Export/Import → Import Vouchers from Excel.
3. Select the voucher type, configure the import format, map the Excel columns, and specify the sheet and row range shown by the screen.
4. Test the mapping with a small set and inspect the vouchers created in BUSY.
5. Use the Bank Reconciliation report and enter the clearing date with F4 where that workflow applies.

Voucher import changes the accounting records. It therefore requires decisions that a bank statement cannot make: whether the entry is a Receipt, Payment, Contra or another voucher; which ledger and bank account apply; whether GST, TDS or another treatment is relevant; and whether the transaction has already been posted. Leave a line unposted until those questions are resolved.

Take a company backup before testing a voucher import, and retain the original bank statement plus the working spreadsheet. Start with a small sample containing different transaction types rather than a run of nearly identical rows. After the test, compare the created vouchers to the import file and confirm that no existing voucher was duplicated.

For either the current or older route, use the same control sequence:

• verify the release, edition and available screen;
• identify whether the job is statement import, reconciliation or voucher creation;
• preserve the source statement and test a limited batch;
• resolve unmatched and ambiguous entries rather than forcing them; and
• confirm the bank ledger, clearing dates and reconciliation report against the statement.