Use this checklist when a client's bank statement needs to become TallyPrime vouchers. It is written for CA teams that want a repeatable control around extraction, ledger decisions, XML import, and reconciliation.
Tick each section for every statement batch. If a row is unusual, unclear, or unsupported by evidence, record it as an exception instead of treating the checklist as permission to guess.
Before downloading the statement
- Confirm the client, company, bank account, and statement period.
- Check the expected opening and closing balances.
- Ask for the native bank statement PDF where available.
- Save the original statement without renaming away the account or period context.
- Note whether the period overlaps a previous import.
During extraction and review
- Confirm the first and last transaction dates.
- Check every debit and credit amount against the source PDF.
- Inspect long narrations and page breaks.
- Look for duplicate rows, repeated references, and overlapping statement periods.
- Flag scanned, damaged, or unusually formatted pages for manual comparison.
A tool can help extract the table, but the preview is still an accounting control. The transaction review guide gives the three-pass method used for this checklist.
Before exporting XML
- Map customers, suppliers, expenses, loans, owners, cash, and other bank accounts.
- Decide whether each row is Payment, Receipt, or Contra.
- Replace Suspense Account only when the evidence supports the ledger.
- Use exact ledger names from the destination company.
- Leave unresolved items in a documented follow-up queue.
- Compare total debits and credits with the source statement.
Use the ledger replacement guide and the voucher mapping guide for the decisions that most often cause cleanup.
During the TallyPrime import
- Open the correct company and select the intended bank ledger.
- Take the firm's normal backup or use the controlled import environment.
- Import the reviewed XML once.
- Read the import summary and investigate rejected or skipped vouchers.
- Do not assume a second import is safe because the first screen did not look complete.
The TallyPrime bank statement import guide covers the broader preparation and verification flow. Doxify's XML is intended for Tally Prime and Tally ERP, but the destination company's setup and import settings still matter.
After import
- Compare the imported transaction count with the reviewed source.
- Check the bank ledger balance and closing balance.
- Review Suspense, personal, related-party, loan, and high-value entries.
- Run bank reconciliation and investigate unmatched transactions.
- Check that internal transfers do not inflate income or expenses.
- Save the PDF, review notes, XML, and import result together.
Exception notes worth recording
| Exception | Useful note |
|---|---|
| Unidentified receipt | “Awaiting client remittance advice; retained as provisional.” |
| Page-break ambiguity | “Compared continuation with source PDF; row retained after manual check.” |
| Possible duplicate | “Matched reference and amount to prior batch; excluded from this period.” |
| Personal movement | “Client confirmed proprietor transaction; routed to approved drawings or related-party ledger.” |
Print-ready summary
Source: correct client, account, period, PDF, and balances. Review: complete rows, correct signs, no unexplained duplicates, supported ledger mapping. Export: exact ledger names, correct voucher types, documented exceptions. Import: correct company, one controlled batch, import summary checked. Close: bank reconciliation complete and working papers archived.
For a full end-to-end process, follow the complete bank statement to Tally XML workflow, then start the next batch from the Doxify converter.