Home › Tally / Busy / Marg import
Your register, read the way your software exports it
Nobody should have to re-key a register to reconcile it. The exports that Tally, Busy, Easy Sol and Marg actually produce — not the tidy shape a specification imagines — are read natively, and anything else can be mapped column by column.
TallyBusy Easy SolMarg Tally Ledger VouchersYour own columns
| What the export does | What the reader does |
|---|---|
| One column per tax rate, spread across the sheet | Collapses the wide rate columns into one taxable value and one rate |
| Header split over two rows | Reads both rows as one header |
| No taxable column, only voucher totals | Derives the taxable value from the voucher |
| Dates in three formats in one file | Parses them all |
| A trailing grand-total row | Uses it to prove the read, then drops it |
The behaviours listed are the ones the readers implement; the layout is drawn for illustration.
Written against real exports
Every reader here was written against a register a working practice actually produced, not against a specification of what the export ought to look like. That distinction is most of the work: the awkward shapes are the normal ones.
The register proves itself
Most exports state their own control total — Marg’s trailing ledger line, Busy’s total row, Tally’s grand total, Easy Sol’s per-bill amount. The reader ties its parse back to the figure the file itself states, so a column read into the wrong field is caught by the file, not by you three screens later.
Tally’s grand total carries a double-count trap, and the reader knows about it.
Ledger vouchers as well as registers
A Tally Ledger Vouchers export is accepted in its own right. Handing one to a register reader does not fail — it reads the file wrongly, which is worse — so it is offered as its own format.
Anything else: map it once
For an export no named reader covers, map the columns yourself: the document number, the date, the party, the taxable value and the tax heads. A mapping with no taxable column is refused rather than accepted and silently reconciled against nothing.
One normalized register out
Whatever goes in, what comes out is the same standard register, and every tool downstream — reconciliation, the three-way ITC view, the sales cross-check, the Tally XML converters — reads that one shape.
Check the read before you trust it. The import screen shows the normalized register on screen so you can see what the reader made of your file before any reconciliation runs on it.
Sales or purchase. Both sides, all four packages.
Upload the register you already have
No re-keying, no template to fill in. Export it the way you always do and see how it reads.