Tally and Your Used Car Business: What Stays in Tally, What Belongs in Dealer Software

Ask a used car dealer in India what software the business runs on and you will often hear “Tally”. Ask who uses it and the answer is “my CA”. Both are true, and the gap between them is where most dealers lose track of what each car actually earned. This guide is about closing that gap without asking anyone to give up Tally.

Key takeaways

• TallyPrime is accounting software, and good at it: statutory books, GST returns, bank reconciliation, the audit trail your CA signs. Keep it for that.
• Tally describes car inventory tracking by model, VIN, status and location - but not landed cost per car, the GST margin scheme under Rule 32(5), partner or investor shares, or brokerage deals, which are the things a used car business lives on.
• The working pattern is two systems, one direction: the dealer software is the record of each car and each deal; the CA receives per-vehicle records and exports from it and posts the books in Tally.
• Decide the split on paper first - the table below - so nothing is entered twice and nothing falls between the two.

What Tally does well for a dealership

TallyPrime is the default accounting package of Indian small business for good reasons. It produces the books in the form a CA and an auditor expect, files GST returns, reconciles bank statements, handles TDS and TCS, and keeps the audit trail. Tally’s own car inventory page describes tracking vehicle stock by model, VIN, colour, make and mileage, status across locations and branches, inventory by lot or sales staff, GST-compliant vehicle invoices, and recording additional charges such as registration, insurance and accessories, with pricing from ₹750 per month for a single user. None of that is wrong. For a new-car franchise selling at list price with full GST, it may even be enough.

Where it stops for a used car business

A used car business is not a shop with stock. It is a sequence of deals, each with its own purchase price, its own reconditioning, its own funding and its own tax treatment. Four things make it different from what a general ledger is designed for:

• Landed cost per car. The profit on a car is the selling price minus the purchase price minus every rupee spent on it: denting, tyres, service, transport, RTO agent, broker commission. In a general ledger those costs land in expense heads by month. Allocating them back to the individual car is manual work nobody does, so profit per car is unknown until the CA’s year-end (how to calculate it).
• The GST margin scheme. A dealer buying from an individual and reselling usually charges GST under Rule 32(5): 18% on the margin, nil if the margin is negative, no input tax credit on the purchase. The margin is per car, so the GST is per car. A sales invoice built for full-price GST does not know this, and the margin cannot be computed unless the purchase price sits on the same record as the sale (the margin scheme explained).
• Partner and investor money. Many cars are funded by a partner who takes a share of that car’s profit. The share is per car, agreed per deal, settled when the car sells. A ledger can record the settlement after the fact; it cannot compute it (how partner splits work).
• Brokerage and consignment. Cars you sell for someone else, earning a commission, are not your stock and must not be booked as purchases - but they still need a record, a buyer, a sale and documents (commission deals explained).

This is why dealers who “run on Tally” almost always have an Excel sheet beside it with a row per car. The sheet is the real system; Tally is where the CA posts the results. The sheet is also where the errors live (what the spreadsheet actually costs).

The split: what goes where

Two rules make the split work. First, every number flows one way: from the deal record into the books, never the other way. Second, the CA gets a per-vehicle view, not a monthly total, so when the auditor asks why a particular car’s GST was nil, the margin on that car is the answer. This is how VehicleERP is designed to sit beside Tally: the car is the record, the GST ledger shows what was charged and paid per car, and the data can be exported for the CA whenever needed (finance ledger module).

Three questions to ask any dealer software vendor about Tally

• “What exactly can I export, and how often?” You want per-vehicle purchase, expense, sale and GST records, not a monthly PDF. Ask to see the export, then show it to your CA before you sign.
• “Do you sync with Tally, or export for it?” A live sync sounds better than it usually is: it couples two systems, and a mapping error in one corrupts the other. Most dealers are better served by a clean export their CA posts, which is what VehicleERP provides. Be wary of a vendor who says “integration” and cannot show it.
• “Who owns the data?” Whatever runs the cars must let you export everything at any time. If the answer is vague, so is your exit.

Do you still need Tally at all?

For most dealerships, yes - because your CA needs it, your auditor expects it and your returns flow from it. Used car software is not trying to replace the statutory ledger; it is trying to replace the spreadsheet beside it. A dealer who keeps Tally for the books and runs every car, every expense, every partner and every margin scheme sale in software built for the trade has both the audit trail and the answer to the only question that matters on a Monday morning: what did we make on that car (ledger entries for a used car dealer, explained).

Frequently asked questions