Guide
From Tally to signed statements
Connecting Tally takes about two minutes and is done once per computer. After that, each statement is three steps.
Once per computer
Fetch straight from Tally
With the Tally Suite installed, FYNEST reads the trial balance directly. There is nothing to install into Tally and nothing to export — the report definition travels inside each request and Tally forgets it afterwards.
- 1
Install the Tally Suite once, on the PC that runs Tally
Download it from your firm, run it, and leave every box ticked. It also switches Tally's own connector on for you, so you never open Tally's settings.
- 2
Open Tally with the company loaded
The suite reads whatever is open. It never writes to your books.
- 3
Open FYNEST and look for "Fetch straight from Tally"
It appears above the file box when the connector is running. Pick the company and the period, then press Fetch trial balance. That is the whole job — no file and no export.
Working from a trial balance a client emailed you instead? Drop it on the file box on the upload screen. It needs the same eight columns as the sample trial balance, and FYNEST names any that are missing before you upload.
Each statement
Generate the statements
- 1
Drop the exported file onto the upload box
On a
.csvFYNEST reads it in your browser straight away and tells you the ledger count, whether the trial balance balances, and whether any Tally group is unrecognised — before anything is uploaded. - 2
Choose the prior year option
A blank column to fill in yourself, or upload last year's trial balance to carry the comparatives across automatically.
- 3
Choose proprietorship or partnership
This picks the ICAI format. Partnership uses partners' capital accounts and adds partner remuneration.
- 4
Generate
The workbook downloads. It has the balance sheet, P&L, all twenty-three notes, and a Check tab.
Before you sign
Read the Check tab
It is the first tab, and it is the point of the whole tool. Ten things are checked and every one of them used to fail silently:
- 1Does the Balance Sheet balance? — Assets minus liabilities, worked out by FYNEST before you open the file — not left to a recalculation you might never trigger.
- 2Does the Trial Balance balance? — Total closing debits against total closing credits.
- 3Ledgers that reach no statement line — Money sitting in a category no note and no face sheet reads, plus any ledger left off for closing at nil.
- 4Ledgers merged from duplicate rows — Two ledgers with the same name, added together.
- 5Rows that could not be read — Any figure FYNEST did not understand, and the column it was in.
- 6Entity details still to fill in — The auditor, F.R.N., membership number, UDIN, date and place. FYNEST never invents these, so they arrive as [prompts] you replace.
- 7Balances on the unexpected side — An asset in credit or a liability in debit. The trial balance foots either way, so nothing else catches it.
- 8Depreciation — Fixed assets falling with nothing classified as depreciation — which prints the fall as a disposal and leaves the P&L reading zero.
- 9The capital account — Whether the note ties to the Balance Sheet, and for a partnership, what is still yours to do.
- 10Ledgers placed by name — Tally files salaries, bank interest and depreciation together, and both the GST you owe and the GST owed to you. Schedule III wants them apart, so FYNEST reads the ledger names — and lists every one it moved.
If the verdict at the bottom reads No issues found, every ledger in your file reached a statement line and the workbook balances. If it says NEEDS ATTENTION, fix that before signing — the figures above it are wrong, not merely untidy.
Set once, kept
Teach FYNEST your own Tally groups
FYNEST knows the standard Tally groups. If your practice uses its own — a custom group for digital assets, say — it will say so on the upload screen and offer a dropdown. Pick the right FS category once and it is applied to every statement from then on, for every client.
Rules are stored in your browser and never uploaded, so they are never linked to a client. Use Back up rules on the upload screen before clearing your browser or moving to a new computer.
Troubleshooting
When something goes wrong
"Fetch straight from Tally" does not appear
Why: The Tally Suite is not running on this PC, or Tally itself is closed.
Fix: The panel only shows when FYNEST can reach the connector on this computer. Start the Tally Suite and open Tally with the company loaded, then reload the page. Working from a file a client sent you? Drop it on the file box instead — the panel is not needed.
The company list is empty, or the fetch returns no ledgers
Why: No company is open in Tally, or the period you chose has no entries.
Fix: Open the company in Tally, then check the financial year on the fetch panel matches the year you are closing.
FYNEST says the file is missing columns, and names them
Why: The file came from a report that does not carry all eight columns — usually Tally's own Trial Balance, which has no Debit Totals or Credit Totals.
Fix: Fetch straight from Tally instead, which always sends the right columns. If you must work from a file, match the headers in the sample trial balance exactly.
The Check tab says the trial balance is out by some amount
Why: Total closing debits and total closing credits do not agree in the file FYNEST read.
Fix: Open Tally's own Trial Balance for the same dates and compare its closing totals with the two on the Check tab. If Tally agrees with itself but not with these, a ledger is missing from the export or the period does not match. If Tally shows the same difference, the books are out and no amount of editing the workbook will fix it.
A ledger is missing from the statements
Why: Its Tally group is not one FYNEST recognises, so it reached no statement line.
Fix: The Check tab lists these under "Ledgers that reach no statement line". Set a rule for the group on the upload screen and FYNEST will remember it for every future statement.
Two ledgers were merged into one
Why: They have the same name. FYNEST adds their balances together and says so.
Fix: Check whether they really are one ledger. If not, rename one in Tally so they can be told apart, and re-export.
A figure came through as zero
Why: The cell could not be read — often #N/A left behind by a formula in an edited copy.
Fix: The Check tab lists every row this happened to, with the column at fault. Correct the figure in Tally and re-export.
Still stuck? Call Himanshu on +91 99998 80092 or send us the details.