Mark IT Solutions

Excel to TallyPrime: Import Choices and Checks

Updated:
•
10 min read
•
Mark IT Solutions Team
Excel to TallyPrime: Import Choices and Checks

Start with TallyPrime's native Excel import before buying a conversion utility. Use a supplied sample file when you can arrange your data to fit it, or a mapping template when you need to keep an existing workbook layout. Test a small batch, check the preview and reconcile the result before importing the rest. Repeated imports from another business system may need a separate integration assessment.

This guide covers masters, sales vouchers and journals using current TallyHelp import instructions, checked on November 4, 2026. Native Excel import was introduced in TallyPrime Release 4.0. If your screen differs, record your installed release before following a current workflow.

Which Excel import route fits your work?

Choose by the structure of your source data and how often it changes. A one-off ledger list, an invoice workbook and a daily feed from an online store are different jobs. The best first step is a representative trial, rather than a commitment to migrate every file at once.

  • Supplied sample file: useful when starting a ledger or stock list from scratch. Enter your data in the appropriate worksheet and use its Default Template during import.
  • Your workbook with mapping: useful when your sales or purchase records already have an established layout. Map worksheet columns to TallyPrime fields and save that mapping for the same structure.
  • Recurring integration: consider this when a source application changes records, sends daily batches or needs scheduled processing. A saved mapping alone does not define duplicate prevention, failure alerts or reconciliation between systems. Discuss these separately with our Tally integration team.

Masters include the reference records your transactions depend on, such as ledgers, stock items, groups and units. Transactions use those records. Check that the required parent groups, units, currencies and other dependencies exist before importing their children. Choose a sample or mapping that fits your actual voucher scenario; there is no single universal invoice workbook.

Four import controls: preserve a backup, choose a sample or mapping, preview a small batch, and reconcile before continuing
Import control checklist, not a TallyPrime application screen.

Should you use a sample file or your own mapping?

Use a sample when you can enter records into Tally's structure. Keep your existing layout when restructuring it would create extra work or errors, then build a mapping. In either case, preserve an untouched source copy and use a small, representative set of records for the first import.

Export a sample file

Open Alt+O (Import) > Manage > Sample Excel File > Masters. Configure the master type and Excel export location, then export the sample. The equivalent route is available for transactions. Follow the supplied worksheet structure, remove any demonstration records and enter your own data. See Tally's sample-file workflow for the current options.

Map an existing workbook

TallyPrime supports horizontal mapping only. Reorganize vertical layouts, such as a price list or payroll sheet, before building the mapping. See the official import FAQ for this limitation.

Open Alt+O (Import) > Manage > Mapping Templates, select MASTERS > Create or TRANSACTIONS > Create, then choose your workbook and worksheet. Set the row and column details, map the required fields and save with Ctrl+A. Check the mapping again whenever the export layout changes. The official mapping guide separates the two record types.

For accounting masters, Name and Group Name are required. For transactions, use the fields required by the chosen scenario. Inspect actual cell values for dates, amounts and names instead of assuming their display format tells you how the import will interpret them. Preserve meaningful invoice references and avoid totals or headings being treated as data rows.

What should you check before pressing Import?

Select the correct company, record your source totals and take a backup before a production import. Then use Alt+O (Import) > Masters or Transactions. Choose the Excel file, worksheet and matching template. A sample file normally uses its Default Template; an existing workbook uses the mapping you created.

  1. Check the destination: confirm the company and period are the ones you intend to change.
  2. Protect the starting point: take and identify a pre-import backup. A backup is a recovery option, not a promise that a later restore will preserve work entered after it.
  3. Review import settings: decide how existing masters should be treated. Do not accept an overwrite or balance-combination setting without understanding its effect.
  4. Enable Preview Import Summary: compare the records TallyPrime expects to import with your intended small batch. A preview is a useful check, not proof that the accounting is correct.
  5. Import and verify: press I (Import) only after the checks agree. Review exceptions and accounting reports before increasing the batch size.

Master example: can you explain every new ledger?

Suppose your trial file contains two new customer ledgers. Put each under its intended group and check for an existing ledger with the same business purpose before import. Your expected result is two intended ledgers, with the right names, group placement and any opening balances, rather than simply two source rows processed.

For stock items, establish their parent stock groups and units first. After the trial, compare item names, units and opening quantities or values where supplied. Keep opening balances separate from the transactions that generated them so that the migration does not represent the same balance twice. This is a reconciliation decision for your accountant, not something a column mapping can decide for you.

Sales and journal examples: what should the result contain?

A sales invoice spread across rows

For a test invoice with two item lines, check that the mapping creates one intended invoice containing both lines. Do not assume that repeating a voucher number is sufficient. Tally's default transaction grouping uses the combination of Voucher Type Name, Voucher Date, and Voucher Number; configure the mapping for your row structure, including Ledger Details from Multiple Rows where applicable. The unique-values reference explains the grouping controls.

Compare the imported invoice with the source: party, date, number, items, quantities, ledger allocation, tax treatment and final total. Check the applicable tax configuration and source invoice rather than copying a universal CGST/SGST/IGST column recipe. Grouping rows within a file is not a guarantee against duplicate vouchers when the file is imported again.

A balanced journal trial

Use a simple, known journal before testing a complicated allocation. For example, a trial with a debit of ₹1,000 to an expense ledger and a credit of ₹1,000 to the intended bank ledger should produce that balanced entry in the correct period. Check how your mapping interprets debit and credit columns or signs; do not assume every workbook uses the same convention. Verify both ledger postings and the narration after import.

What happens when the import reports exceptions?

An import can finish while some records remain under exception. Those records may not yet appear in the books. Treat the completion message as a reason to inspect the result, rather than confirmation that every intended transaction is ready for use.

  • Creation problems: open Alt+O (Import) > Exceptions. Inspect the affected master or voucher and resolve the missing or invalid details.
  • Problems altering existing records: also check F1 (Help) > Troubleshooting > Event Log. The appropriate action may be to alter a record already present.
  • Missing dependencies: inspect the referenced ledger, parent group, unit or other required master before deciding how to correct the import.

Do not re-import the whole workbook just because the first attempt showed an error. First identify which records exist, which remain under exception and which need correction in TallyPrime. Resolving an exception can create its record, so replaying the source as well can duplicate it. If a new import is necessary, reconcile the intended subset and test the retry approach on a copy before applying it to live books.

See TallyHelp's exception-resolution guidance. If you cannot establish the resulting state, stop the batch and get assistance instead of trying repeated imports.

When is an integration or migration service useful?

Native Excel import is a practical starting point for a defined batch. A service becomes useful when the work involves inconsistent names, several source systems, complex opening balances, repeated changes or a recovery that needs a controlled plan. XML and JSON are separate supported import routes; choose them because the source structure and integration need fit, not because every Excel file must be converted first.

For a recurring feed, agree how updates, deletions, duplicate references and failed batches will be handled before commissioning automation. For a one-off move, agree a cut-off, trial acceptance and final reconciliation. Our customization service and Tally support team provide routes to discuss the appropriate scope; this guide does not promise a fixed migration price or turnaround.

When is the batch ready to use?

Keep a simple acceptance record for each batch. Compare intended voucher counts rather than Excel row counts when one voucher spans several rows. Reconcile source and destination totals for the same date range and check representative records in detail.

  • Masters: intended records, group or unit placement, and opening balances where relevant.
  • Transactions: voucher counts, dates, references, ledger postings, debit/credit totals and invoice totals.
  • Inventory: quantities, units and values against the agreed source.
  • Exceptions: outstanding records explained and resolved before declaring the job complete.

Have the person responsible for the books accept the trial before the full batch. For bank-related work, use the distinct bank reconciliation workflow as appropriate; importing a workbook does not itself prove reconciliation.

Prepare a useful migration inquiry

Use the contact form to request a callback with your contact details; it does not collect a migration brief. For the discussion, prepare your TallyPrime release, source software, approximate records and companies, whether this is a one-off move or recurring feed, and the problem you need solved. Note any existing import attempt and its exception category. Start with a description and column headings, and agree a suitable way to review any necessary sample data with the team. Do not send passwords or confidential ledger data in an initial inquiry.

Request a migration callback, or call 022 6199 2222. You can also use the native workflow above without purchasing a migration service.

Frequently Asked Questions

Do I need a paid Excel-to-Tally converter?

Not for every job. TallyPrime has native Excel import from Release 4.0. Try an appropriate sample file or mapping with a small batch first. A recurring integration or complex migration may need separately scoped assistance.

Can I keep my existing Excel layout?

Often, if the layout is suitable for horizontal mapping. TallyPrime does not support vertical mapping: reorganize vertically arranged price lists or payroll details first. Check the worksheet, row structure and required fields, and review the mapping if your source layout changes.

Can I import from Google Sheets or CSV?

Export a Google Sheet as an Excel workbook, or save CSV data as .xls or .xlsx before using the Excel import route. Check the resulting dates, amounts and worksheet layout before a trial import.

Does a repeated voucher number prevent duplicate imports?

No. The default combination of voucher type, date and number helps define transaction grouping in the mapping. It is not a guarantee that importing the same workbook again will avoid duplicates. Check the existing records and test any retry approach first.

What if the import completes with exceptions?

Inspect Alt+O (Import) > Exceptions and, for problems altering existing records, F1 (Help) > Troubleshooting > Event Log. Resolve the affected records and reconcile the books before deciding whether any data needs importing again.

What should I prepare for a migration callback?

The contact form collects contact details for a callback. For that discussion, prepare your TallyPrime release, source system, approximate record volume, one-off or recurring need and any import problem. Do not send passwords or confidential ledger data in an initial inquiry.

Need Help with Data Migration?

Request a callback using your contact details. Keep your source, record volume and import issue ready for the discussion.

Request Callback
Mark IT Solutions Team

About Mark IT Solutions Team

With over 20 years of experience, Mark IT Solutions is a certified 5-star Tally partner in Mumbai. We specialize in TallyPrime implementation, customization, training, and support for businesses across India.

Share this article