What is Excel to Tally import, and when is it worth setting up?
Excel to Tally import is the process of converting rows in a spreadsheet into TallyPrime masters and vouchers automatically. It is worth setting up the moment the same kind of data arrives in Excel every week or month and someone re-types it.
The common sources are predictable. A billing or POS system at the shop exports daily sales. A marketplace sends a monthly sales report. A branch office keeps purchases in a sheet. Payroll comes from an HR tool as a summary. A CA firm receives a client’s transactions as an Excel dump. Each of these is structured data; typing it is pure cost and a steady source of errors.
A one-time import also makes sense when you are moving to TallyPrime from other software or starting a new company with opening balances and a long list of parties. That is a migration rather than a routine, and it has its own checks, covered below.
If data arrives daily from software that has an API, a live link may beat files altogether. Our page on connecting Tally with other software explains when to switch.
Can TallyPrime import data from Excel directly?
Yes. Current TallyPrime releases include Import Data from Excel for masters and transactions, reached with Alt+O (Import). Tally’s help pages describe sample Excel files with the expected columns, mapping templates that link your own column names to Tally fields, and an exceptions report listing rows that did not import cleanly.
Tally’s FAQ adds practical limits worth knowing: only one worksheet is imported at a time, masters cannot be imported into several companies at once, bank transactions are not supported through this feature, and for efficiency it recommends importing roughly 50,000 to 1 lakh transactions per run. Mapping templates saved for all companies are stored as files that can be shared across machines.
For a clean file in a steady format, this built-in Excel to Tally import is a good first choice and costs nothing extra. Where it runs out is messy source data: party names that do not match ledgers exactly, tax ledgers that depend on state and rate, a need to stop the import entirely if any row is wrong, and duplicate protection across months. That is the gap a custom tool fills.
Four ways to do Excel to Tally import
Choose by how often the file arrives, how clean it is, and how costly a mistake would be. As volume grows, the sensible move is usually further down this list.
TallyPrime’s own Excel import
Free, built in, mapping templates and an exceptions report. Best for clean files in a stable format.
Tally XML import file
Excel converted into Tally’s XML format and imported through Tally’s import option or its XML interface. Precise control over every field, but someone must write the conversion.
Ready Excel-to-Tally utilities
Third-party tools with their own templates. Quick for standard vouchers; you adapt your data to their format.
Custom import tool
Reads your files as they are, validates against your Tally masters and GST rules, and posts through Tally’s XML or JSON interface. Best for recurring, large or irregular data.
Our custom tools post through Tally’s own interfaces, so what reaches Tally is exactly what a person could have entered, and Tally’s response for every voucher is recorded.
How to design an Excel template for Tally import
A good template has one row per voucher line, one clear meaning per column, and no free-text where a list would do. Most import failures start in the template, not in Tally.
Decide first whether a row is a whole voucher or one line of it. Sales with several items per invoice need one row per item, grouped by an invoice number column; single-line journals can use one row each. Fix dates to one format, keep amounts as numbers with no currency symbols, and add a column for the source reference, such as the billing system’s invoice number, which becomes the duplicate check later.
Party and item names should come from a lookup of your Tally masters, not be typed. We generate a list sheet from Tally so the template’s drop-downs match ledgers exactly. Tax is better captured as rate and state than as ledger names, leaving the tool to pick the ledger. The template section below lists the columns we usually start from.
- One row per item line, grouped by voucher number
- Date in one fixed format across the file
- Party name picked from a list of Tally ledgers
- GSTIN and state for every B2B party
- Item, HSN, quantity, rate, discount, taxable value
- GST rate; the tool chooses the ledgers
- Source reference for duplicate checks
Import ledgers and stock items before any voucher
Masters must exist before vouchers that use them, and Tally’s help pages say the same for its own Excel import. Import ledgers, stock groups, units and stock items first, then transactions.
A ledger import needs name, parent group, and for GST parties the registration type, GSTIN and state; address and contact fields are optional but save work later. Stock items need name, group, unit, HSN and GST rate. Opening balances can come in at the same time for a migration.
The danger with masters is near-duplicates: “R K Traders” and “R.K. Traders” become two parties with split balances. Our tool compares incoming names with existing ledgers, flags close matches by GSTIN and spelling, and asks a person to confirm before creating anything new. Tally’s FAQ notes it does not treat a repeated GSTIN as an exception, because branches can share one, so that check has to be deliberate.
Importing sales vouchers from Excel into Tally
Sales import is the most common job and the one with the most rules: item or accounting invoice, the right sales ledger, tax ledgers by state, rounding, and a voucher number that matches what the customer received.
Item invoices carry stock items, quantities and rates, and update inventory; accounting invoices carry only ledgers and amounts. Businesses that bill from another system usually import item invoices so stock in Tally stays right. Voucher numbering can follow the source system when invoices were already issued to customers, which keeps GSTR-1 and the customer’s copy consistent.
Rounding deserves a rule: if the billing system rounds per invoice, the import should post a round-off ledger line rather than altering item amounts. Discounts need a similar decision, whether in the rate or as a separate ledger. We confirm both with your CA before the first test run.
Importing purchase and journal entries
Purchase import mirrors sales with two extra concerns: supplier invoice number and date must be kept exactly for input tax matching, and the same supplier invoice must never be posted twice. Journals need balanced debits and credits per voucher, checked before import.
For purchases, the supplier’s invoice number is the natural duplicate key, combined with the supplier’s GSTIN. The tool refuses a second voucher with the same pair. Where branches buy separately, each file carries the branch or cost centre so expenses land in the right place.
Journal imports usually come from payroll summaries, provisions, depreciation schedules or inter-branch adjustments. The tool checks each voucher balances to the paisa, that every ledger exists, and that the date falls inside an open period. For recurring journals with the same structure, a small template with only the amounts changing each month removes most manual work.
GST and HSN mapping in Excel to Tally import
GST mapping decides which tax ledgers each line uses, and it is where most silent errors come from. A voucher can import perfectly and still post IGST where CGST and SGST were due.
The rule set is short but must be exact: compare the party’s state with your registration state to choose intra-state or inter-state tax; pick the tax ledgers by rate; check the HSN on the line against the stock item’s HSN in Tally; treat unregistered, composition, SEZ and export parties by their own rules. The number of HSN digits your invoices must show depends on turnover under CBIC’s rules, and your CA should confirm which applies to you.
We write these rules as a table your accountant can read, not buried in code, and every rule shows in the validation report for the rows it affected. If you also generate e-invoices, see e-invoice API integration for keeping IRNs in step with imported vouchers.
How to stop duplicate vouchers when importing Excel into Tally
Give every voucher a unique source reference and check it against Tally before importing. Without that, importing the same file twice, or a file that overlaps last month’s, generally creates the same vouchers again.
Duplicates happen for ordinary reasons: a staff member re-runs an import after a partial failure, a marketplace report overlaps the previous one by a day, or two branches send the same invoice. Our tools store the reference in a voucher field, query Tally for existing references in the date range, and skip or flag repeats. Reruns after a failure resume from where they stopped.
For extra safety, each import writes a batch number into the voucher narration or a custom field. If a batch ever needs reversing, every voucher from it can be found and deleted together, instead of hunting through the day book.
- Unique reference per voucher, stored in Tally
- Pre-import query for existing references
- Batch number on every imported voucher
- Resume, not restart, after a failure
What to validate before an Excel file touches Tally
Validate every row against your Tally masters and your rules first, and import nothing until the file is clean or the exceptions are accepted. Fixing a spreadsheet is minutes; reversing hundreds of wrong vouchers is days.
The tool produces a report grouped by problem type rather than by row: twelve rows with an unknown party, three invoices where line totals do not match the invoice total, one date outside the financial year. Staff fix the source and run the check again. Only a clean file, or one where someone has approved the remaining warnings, goes further.
The validation table below lists the checks we build in by default. You can add your own, such as blocking sales below a minimum rate, which is similar to what a TDL validation does for manual entries.
Handling large monthly Excel batches
Large batches import reliably when they are split into chunks, run after office hours, and preceded by a backup. Tally’s own FAQ suggests importing around 50,000 to 1 lakh transactions at a time for efficiency, which is a sensible ceiling for any method.
Our tools split big files by date or by voucher type, post each chunk, read Tally’s response, and log counts before moving on. If Tally is busy with users, imports slow down and may time out, so month-end batches are best scheduled for the evening. A backup of the company is taken before each run, and the tool will not start without one.
At the end, a summary shows vouchers created per type, total taxable value and tax per rate, and anything skipped. That summary is what your accountant ticks against the source file, not the day book.
Reconciling after the import
Always compare totals, not just counts. Matching voucher numbers with mismatched tax totals is the classic silent failure.
The post-import report compares the source file and Tally by date, voucher type and tax rate: taxable value, CGST, SGST, IGST and invoice totals. Differences are listed by voucher so they can be traced. For sales, a second check compares Tally’s GSTR-1 figures with the source system’s report for the same period before filing.
For businesses that also want owner-level numbers after each import, the same totals can be pushed to a sheet, as described on Tally to Google Sheets.
How much does Excel to Tally import cost?
TallyPrime’s built-in import costs nothing beyond your licence. A custom Excel to Tally import tool from BtechWaleTech starts at ₹40,000, and a browser-based upload portal for several branches starts at ₹60,000.
Quotes in the market vary widely, from utility licences to fully managed data-entry services. What changes the effort is predictable: number of voucher types, how messy and varied the source files are, GST rules for special parties, number of Tally companies, and whether the job is recurring or a one-time migration. A clean single-format sales file is a small project; three branches sending files from three different billing systems is not.
Compare offers on what happens when a row is wrong. A cheap tool that imports everything and leaves your CA to find errors later is the most expensive option over a year.
Example: monthly Excel to Tally import for a CA practice
Take a hypothetical CA practice in Kolkata that keeps books in Tally for twelve small clients. Each month, clients send sales and purchase data in Excel from different billing apps, and two article assistants spend the first week typing it in.
A custom tool would start with one template per voucher type and a converter for each client’s billing export, so clients keep sending what they already send. For each file, the tool loads that client’s Tally company masters, validates rows, maps tax ledgers by state and rate, and flags new parties for confirmation. Clean files import in chunks with a batch number; exception reports go back to the client in plain language.
In this scenario, the practice would spend its first month on templates and rules for the three biggest clients, then add the rest one by one. The assistants’ week of typing would become an afternoon of reviewing exceptions. For wider practice automation, see automation for CA firms.
One-time migration: moving old books into TallyPrime through Excel
A migration is an Excel to Tally import done once, with a cut-off date, and judged by a single test: does the opening trial balance in Tally match the closing trial balance of the old system to the rupee? Everything else serves that test.
The order is fixed. First the chart of accounts, mapped from the old system’s groups to Tally’s groups, which is a decision for your CA rather than a developer. Then party ledgers with GST details, then stock items with units and HSN, then opening balances, including bill-wise opening bills for debtors and creditors so ageing reports work from day one. Transaction history is optional: you may bring only the current year and archive older years as reports.
We export the old system’s data to Excel, clean and map it in the tool, import into a test company, and produce a side-by-side trial balance for your accountant. Differences are traced before anything goes live. Stock needs its own check, quantity and value by item and godown, because an inventory mismatch on the first day distorts every margin report afterwards.
Plan the cut-off at a month-end or year-end, freeze the old system for new entries on that date, and keep it available read-only for a few months in case someone needs to look something up.
Client data, backups and who owns the import tool
Your data stays with you: the tool runs on your machine or your own hosting, and we work on sample files or trimmed copies during the build. You own the code, templates and mapping rules once delivered.
Spreadsheets for import often contain GSTINs, addresses, phone numbers and amounts. We ask for only the columns needed, delete working copies after testing, and never keep a client’s Tally backup after the project. A CA practice handling many clients can keep each client’s rules in its own configuration file, which also makes it easy to hand one client’s setup to another firm if needed.
Handover includes the source code, a short staff guide with screenshots, and the rule tables. Fixes are free for two months.
Excel to Tally import checklist
Use this before your first real import, whichever method you choose. Each item prevents a common, avoidable failure.
- Fresh backup of the Tally company taken
- Masters imported or confirmed before vouchers
- Template locked: fixed dates, numeric amounts, list-based names
- Unique reference column filled for every voucher
- GST rules agreed with your CA, including special parties
- Validation run clean, or warnings approved by a named person
- Large files split into chunks, run after office hours
- Post-import totals matched by rate and voucher type
If the same file keeps arriving from the same software every day, ask whether a live link would save more than a better import. Our Tally integration page covers that trade-off.