Verify Tally Data After Restore Trial Balance and Voucher Checks
Restore finished without an error. That is not the same as the books being right. Two minutes of checking - Trial Balance, Day Book, and a few real vouchers - is the difference between a clean handover and discovering a bad transfer at filing time.
Technical AnshuTallyPrime and Tally.ERP 96 minute read
Watch the full video - exporting Tally company data to a client PC, step by step
Every failed Tally transfer has the same sad ending: someone notices weeks later that the numbers do not feel right, by which time new vouchers sit on top of the damage. Verification exists to catch the problem at the only moment it is free to fix - right after the restore, before a single new entry is typed. This page is that check, in order.
The two-minute verification sheet
Source PC Client PC (restored)
Trial Balance total : ? Trial Balance total : ? must match
Last voucher no. : ? Last voucher no. : ? must match
Company period : ? Company period : ? must match
If any pair disagrees, do not start work. Re-restore from the original file.
Three comparisons catch almost every bad transfer before it becomes a month of wrong books.
1
Match the Trial Balance First
Open Trial Balance on the source PC for the full period and note the grand totals. Open the same report, for the same period, in the restored company. The totals must agree to the paisa. A difference here means the data that arrived is not the data that left - usually an incomplete backup file, a damaged transfer, or the wrong company entirely. Nothing else on this page matters until this number matches.
2
Check the Ends of the Day Book
Open the Day Book on both PCs for the last working day before the backup
The last voucher number and its amount should be identical
Scroll the full last day - the count of vouchers should match, not just the final one
Spot-check the first day of the financial year too - old data is where incomplete copies quietly lose history
3
Open Real Vouchers, Not Just Reports
Reports can look right while individual records are damaged, so open two or three actual vouchers you know well: the biggest sale of the month, a recent payment with a long narration, and one voucher with inventory items. Amounts, ledger names, narrations, and stock items should all be intact and readable. If a voucher opens with an error or shows blank fields, stop - the restore is not healthy.
4
Confirm the Company Identity
Company name and financial year are the ones expected - not last year's similarly named company
Books beginning from date is unchanged
Statutory details (GSTIN and state, where applicable) are present and correct on the company screen
The company opens without repair or rewrite prompts on the second open as well as the first
Record the three matched figures (Trial Balance total, last voucher, period) in the handover message to the client. That short note is your proof the transfer was verified, and the client's reference if totals are ever questioned later.
"Restore completed successfully" is Tally reporting that files were written - not that the books are correct. The verification above is the only point where a bad transfer is still cheap to fix, because the original backup file and the source PC are both still untouched.
Watch the Complete Process in the Video
Backup, transfer and restore shown live on screen, with the full knowledge and installation details.
About two minutes: match the Trial Balance totals, compare the last Day Book voucher on both PCs, and open two or three known vouchers. That catches incomplete files, wrong-company restores and damaged transfers.
The Trial Balance matches but one voucher looks damaged. What now?
Do not start work in that copy. Restore again from the original .tbk file on a clean Data folder. If the same voucher is damaged in a fresh restore, the problem is in the source data itself - repair it on the source PC and take a new backup.
Should the client delete the backup file after verification?
No. The .tbk file is the safest archive of the company as it stood on handover day. Keep it, labelled with the date, somewhere outside the Tally Data folder.
This guide is based on the Technical Anshu video on exporting Tally data to a client PC. Stuck on a step? Ask in the video comments.