Choosing a data source
Fetching years from Tally, uploading an ITR JSON, or entering everything yourself.
Three ways to get the historical figures in. You can mix them — import what you have and type the rest.
From Tally
The usual route, and the most complete.
OptiVida asks Tally which years it holds
Tally must be open on this machine with the client's company loaded.
Tick the years to import
Usually the historical years and the estimated year.
Fetch
Ledgers come across and are mapped to CMA lines.
The report arrives Auto-mapped, with anything OptiVida could not place listed for you.
Tip
If Tally does not answer, see OptiVida cannot reach Tally.
From an ITR JSON
Upload the income tax return JSON downloaded from the e-filing portal. ITR-3 and ITR-5 are read.
- Where to get it
The e-filing portal, as the downloadable JSON for that assessment year.
- More than one year
Upload one per year.
Figures from a return are badged ITR in the grid, so you can always see which came from where.
Warning
A return carries the figures it reports, which is less than a trial balance holds. Expect to fill in more by hand than with a Tally import — particularly the balance sheet detail a CMA needs and a return does not require.
Enter it yourself
Skip the import. You get an empty grid with all the right rows, and you type in from the audited accounts.
Reasonable when the books are not in Tally, when the client's accountant works elsewhere, or when a single year is missing from an otherwise complete import.
Which to choose
- The books are in TallyFrom Tally
Most complete, least typing.
- Only the return is availableITR JSON
Then fill the gaps.
- NeitherManual
Type it in. Everything still recalculates.
You can combine them
Import what Tally has, upload a return for an earlier year, and type in anything still blank. Every cell shows where its figure came from, so a mixed report stays auditable.
Last updated 31 Aug 2026
Still stuck? Ask us