A distributor we work with gets their day’s orders as a spreadsheet. Around four hundred lines, roughly seventy invoices, arriving as a download from the buyer’s portal every evening. Two people then spend the next morning typing those invoices into TallyPrime so the stock and the GST return are right.
The spreadsheet is correct. TallyPrime can import vouchers. And yet the retyping continues, because of a detail that sits underneath every Excel to Tally sales import and that almost nobody writes about: TallyPrime will not invent a ledger or a stock item that does not already exist in the company.
Miss that, and your import either fails outright or, worse, half succeeds and leaves you with vouchers pointing at masters nobody meant to create.
Why the voucher is the easy part of an Excel to Tally sales import
A sales voucher is a simple object. A date, a voucher number, a party, one or more stock item lines with quantity and rate, a sales ledger, and the tax ledgers. TallyPrime accepts all of that from outside, and Tally publishes sample spreadsheet layouts showing the exact column shape it expects.
If every name in your file already exists in your company, the import is genuinely a two-minute job. Point TallyPrime at the file, let it run, check the totals.
That condition is the whole difficulty. Real sales files do not satisfy it. A new customer appeared last week. A product got a new size. Somebody wrote “Shree Traders” in one row and “Shree Traders.” in another. Each of those is a master that either does not exist or exists under a different name, and TallyPrime has no way to guess which you meant.
The masters problem nobody mentions
TallyPrime’s own guidance is to import masters first, then vouchers. That advice is correct and it is also the step that gets skipped, because building a master file by hand defeats the point of importing.
When a voucher references something missing, TallyPrime records it rather than silently dropping it. Depending on your release, entries that need a new master land in an Import Exceptions report, and entries that need an existing master altered land in the Event Log. You resolve them from there.
Useful, but it is a queue of work, not an answer. If forty of your seventy invoices are for parties that need creating, you are back to manual entry with extra steps.
Party ledgers
A ledger needs a name and a group before it can exist. Your sales file has the customer’s name and, if you are lucky, their GSTIN and state.
That is enough to create the ledger properly: under Sundry Debtors, with the GSTIN, the registration type and the state set, so that the place-of-supply logic works later. It is not enough if the file only carries a shop name, which is why matching on GSTIN rather than on spelling is the difference between a clean import and a debtors list with four versions of the same customer.
Stock items and units
A stock item needs a unit of measure before it exists. If your spreadsheet says “12 NOS” and your company has no unit called NOS, the item cannot be created, and every line using it fails.
Units also have to be real Tally units, and if you file GST returns the unit needs to correspond to a valid UQC, or your returns carry blanks where the quantity code should be.
GST ledgers and place of supply
This is the part that decides whether your GSTR-1 is right. Whether an invoice attracts CGST plus SGST or IGST depends on the place of supply against your own registered state, not on anything written in the spreadsheet.
A file that carries a fixed “GST 18%” column and nothing else cannot produce a correct return. The tax split has to be derived from the customer’s state at import time, and the correct tax ledgers picked accordingly.
What a working Excel to Tally sales import needs from your file
Before automating anything, get the source file to a state where every row can be resolved without a judgement call.
| Column | Why it has to be there |
|---|---|
| Invoice number and date | Voucher identity. Duplicates are the most common cause of a rejected batch. |
| Customer name | The ledger name, or the name to create. |
| Customer GSTIN | The reliable match key, and the basis for registration type. |
| Customer state | Decides CGST plus SGST versus IGST. |
| Item name | The stock item name, or the item to create. |
| Unit | Mandatory for creating a stock item, and the basis for the UQC. |
| Quantity and rate | Inventory movement and value. |
| Taxable value | The check figure. Compare it against what Tally computes. |
| GST rate | Drives the tax ledger and amount. |
| HSN or SAC | Needed for the rate-wise HSN summary in GSTR-1. |
Two habits are worth adopting on top of that. Keep one row per item line rather than one row per invoice, so multi-item invoices survive. And keep the raw export from the source system as it came, with your mapping applied in a separate sheet, so that when the portal changes a column heading next quarter you can see exactly what moved.
Where a supported import beats a free converter
There are free Excel-to-Tally converters, and for a one-off batch of clean data they are fine. They stop being fine when the file is your daily operating input, because then somebody has to own the mapping when a customer’s GSTIN changes, a new unit appears, or the portal renames a column.
That ownership is the work we do at Plug & Play Computers. We build the import against your actual file, with your master-matching rules and your ledger routing, and because we also supply and support the TallyPrime licence, the same team fixes it when the source format shifts. The video above walks through a sales import creating the inventory and the ledgers as it goes.
What breaks, and how to catch it before it reaches GSTR-1
Duplicate masters. The single most damaging failure, because it is invisible. Two ledgers for one customer means outstanding split across both, and nobody notices until a payment does not knock off. Match on GSTIN, and review the list of masters an import intends to create before it creates them.
Ampersands and special characters. Names like “A & B Enterprises” have to be escaped correctly for the import to parse. A file that imports fine until one customer with an ampersand appears is almost always this.
Duplicate voucher numbers. If your source system restarts numbering each year and your company does not, the second year of data collides with the first.
Date format drift. A spreadsheet column that Excel decided was American will silently swap day and month for the first twelve days of each month, which is the hardest error to spot after the fact.
Importing straight into live data. Do the first run against a copy of the company. Compare the sales register total and the GST summary against the source file before repeating it on the real one.
Frequently asked questions
Can TallyPrime create ledgers and stock items automatically during an Excel import?
Not on its own. TallyPrime expects the ledgers and stock items referenced by a voucher to exist already, and it lists anything missing in the Import Exceptions report for you to resolve. Automatic creation during the import comes from a TDL add-on or conversion tool that builds each missing master, with its group, unit and GST details, before writing the voucher.
Does an imported sales invoice appear in GSTR-1 correctly?
Yes, if the underlying masters are right. Imported vouchers are ordinary vouchers, so GSTR-1 reads them the same way as typed ones. Problems in GSTR-1 after an import almost always trace back to a party ledger missing its GSTIN or state, or a stock item without an HSN.
What is the difference between importing with inventory and importing accounting only?
An accounting-only sales import posts the value to the party and the sales ledger and nothing else. Importing with inventory also moves the stock, so quantities, valuation and the stock summary stay correct. If you carry stock, accounting-only imports will balance your books and quietly wreck your inventory.
Can I import sales invoices for a previous financial year?
Generally yes, as long as the period is open in the company and the vouchers fall inside it. Be careful with voucher numbering conflicts and with any period you have already filed returns for.
How is this different from migrating from another accounting package?
An import is a recurring operation on new transactions. A migration is a one-time move of your entire history, including opening balances and bill-wise references, which is a different job and covered on our Busy to Tally migration page.
Can receipts and purchases be imported the same way?
Yes. The mechanism is shared; the decisions differ per voucher type. See importing receipt entries from Excel and importing GSTR-2B purchase entries.
Deciding what to do next
If your sales data already exists as a file and somebody is retyping it, the decision is not whether to automate but how carefully. A quick converter will get the vouchers in. Whether your debtors list, your stock summary and your GSTR-1 are still trustworthy in six months depends entirely on how the masters were handled on the way through.
The honest test is to run one real day of your file and then look at three things: the sales total, the list of new masters created, and the GST split on an interstate invoice. If all three are right, the approach works for you.
Send us one day’s sales file and we will run exactly that test on a copy of your company, and show you what came out before you commit to anything. Call, or see what else we build on the solutions page.