Faster Tally Reporting. No Complex Keys Required!
It works until it doesn't — and when it fails, it fails silently, inside your statutory books.
Tally is already there. The licence is paid, the accountants know it, the statutory returns come out of it. So when a group needs one consolidated view across a parent on SAP or Navision and subsidiaries on Tally, the obvious move is to push everything into Tally.
The logic is sound. The consequence is that Tally becomes a warehouse, and it was never built to be one.
A retried import creates duplicates, silently. Tally does not enforce uniqueness on an incoming document. Run the import twice — after a timeout, a network failure, a partial batch — and the same invoice enters twice. Nothing objects.
Bad data enters the books directly. Tally accepts what is pushed. A wrong ledger, a missing allocation, a negative stock position — all of it enters, and surfaces months later during audit.
Party masters fragment. The same vendor arrives from two systems with two spellings and becomes two ledgers. Ageing splits. Reconciliation stops being possible.
Inter-company transactions are not eliminated. Push both sides of a group transfer into one Tally company and consolidated revenue counts it twice.
You pushed 4,000 documents from SAP. Tally shows 3,940. Which sixty are missing, and were they missing before or after?
Tally holds no transfer record. There is no register of what arrived, no reconciliation back to source, no way to ask the question. You can compare totals — and a total that matches can still hide an equal and opposite error.
A consolidation layer built for this keeps a record of every source document and its fate: loaded, rejected with a reason, or duplicated. The question becomes answerable rather than a matter of confidence.
SAP and Navision carry account structures Tally has no equivalent for — profit centres, cost objects, dimensions, segments. Pushing that data into Tally means flattening it into ledgers, and whatever does not fit is dropped.
Nobody writes down what was dropped. Six months later, nobody remembers.
Consolidation needs a mapping that is stated, reviewed and signed off before any data moves — every source account to its consolidated account, every entity, every party. The map is the deliverable, not a by-product.
Consolidated COGS is where multi-system groups usually give up.
Valuation methods differ between systems. Standard costing in SAP, weighted average in Tally. Inter-company stock transfers count as a sale in one entity and a purchase in another. Batch and godown detail exists in one system and not the other.
Push it all into Tally and you get one number that reconciles to nothing.
A single Tally voucher holds ledger lines, inventory lines, bill references and cost-centre allocations nested inside one another. It is a document, not a row.
That structure is right for entry and wrong for analysis. It means no consolidation tool and no audit tool can query Tally directly — they must first unpack it, and unpacking it correctly is the hard part.
Reading consolidated numbers out of Tally also means opening each company in turn. There is no view across entities — the group figure is assembled by hand each month, and assembled again the next month, with no record of how the previous one was built.
A voucher altered today shows only today's version. Tally's edit log records that a change happened; it does not preserve what the number was before.
For consolidation this matters more than it first appears. Last month's consolidated figure was built on values that may since have changed, and there is no way to reproduce it. When the auditor asks why September's number differs from the September you reported in October, there is no answer available from the system.
Tally is your statutory system. GST returns, TDS, financial statements — all produced from it.
A duplicate in a reporting layer is an inconvenience. A duplicate in Tally is a number you have filed.
Each system is read independently and reconciled back to its own trial balance — so every figure ties to the source it came from, before anything is combined.
From that single layer: consolidated profit and loss, balance sheet and cash flow across all entities and all systems. Inter-company transactions eliminated. Every consolidated line traceable back to the source documents behind it, in either system.
And a standing comparison between the two systems, so the question "do SAP and Tally still agree?" has an answer on any given day rather than at year end.
Tally stays what it is — the system of entry and statutory record for the entities that run on it. The consolidated view is built alongside, not inside.
Most groups discover this after the fact. The first question is how many duplicates exist and which source records never arrived — both answerable, and worth answering before the next filing.