Overview
Your CA still keeps the books in Tally. Without this, someone re-types every invoice and every payment into Tally by hand at month-end — slow, and one fat-finger off your GST. Tally export packs a date range of invoices and payments into a file your CA imports straight into Tally Prime, GST split and all. No re-keying.
Opt-in Capability · off
Tally Export is switched offTally Export
You can read the guide. An owner or manager flips this Capability on in settings — it then lights up across the app.
Tally export switches on after our CA-validation pass. Until then, running it returns a "disabled until CA validation" message — the file shapes are built and tested, we just want a real CA to confirm your ledger names line up before any books move.
Where to find it
Web only, under Reports (/reports). Open Reports, pick the period, and run the Tally export from there. There is no mobile screen for this — it's a desk job for month-end.
It shows in the Reports sidebar for OWNER, MANAGER, OPERATOR and ACCOUNTANT, but seeing the Reports page is not the same as being able to run this export — who can actually generate the file is covered in Role notes below.
Key concepts
- Tally import XML — a file in Tally Prime's own import shape. Your CA loads it in Tally via File → Utilities → Import Data → XML. Each invoice becomes a Sales voucher and each payment a Receipt voucher.
- Ledger name — the account a line posts to in Tally (the customer's ledger, "CGST Output", "SGST Output", "IGST Output", "Cash" or "Bank Account"). Every Tally company names these slightly differently, so your CA should eyeball them once before the first import.
- GST breakup — each invoice line carries its own HSN code and CGST / SGST / IGST / Cess amounts, so the imported voucher rebuilds the exact tax split instead of one lumped total.
- Format — pick
xml(the file Tally imports),excel(a workbook your CA can read and check), orboth.
Common workflows
Go to Reports. Choose the from and to dates for the run — say 01/04/2026 to 30/04/2026 for April. The window covers invoices by their date and payments by the date they were recorded.
Choose xml for the Tally import file, excel for a workbook to review, or both. both gives your CA the import file plus a readable copy in one go.
Generate it. Neev pulls every finalized and paid invoice in the window — with its line items, HSN and GST split — plus every payment, and builds the file(s).
A download link comes back for each file. The Excel workbook lands as four sheets — Invoices, Line items, Payments and a Summary tile (tenant, GSTIN, period, counts). Send the XML to your CA to import into Tally.
Role notes
All three tagged roles can run this export — they hold the same reports.tally-export permission, so there is no who-can-do-what split here. A matrix would just show three identical rows.
Owner Manager and Accountant can all open Reports and generate the Tally export.
One thing to flag for Accountant: the team-invite screen describes Accountant as the person who "handles exports", but by default that only means this Tally export. The GST-return exports — GSTR-1, GSTR-3B and HSN summaries — sit on a separate permission an Accountant does not hold by default. If your accountant needs those, the OWNER grants them explicitly.
OPERATOR sees the Reports page but cannot run the Tally export — they lack the permission.
Tips & time-savers
both at month-end. Your CA imports the XML into Tally, and keeps the Excel open side-by-side to tally the invoice count and GST totals against what landed — one click, two jobs.Stick to whole-month windows (1st to month-end) so a run lines up with how your CA files GST. Drafts stay out automatically — only finalized and paid invoices export — so you never have to clean up half-done bills before running it.
Gotchas
Before the very first import, have your CA confirm the ledger names in the XML match your Tally company (customer ledgers, "CGST Output", "Bank Account", and so on). Names differ per company, and a mismatch makes Tally reject the voucher.