Skip to main content

Tally Batch Export

What it is

Exports sales invoices and credit notes over a date range as a single Tally XML file, so the auditor imports one file rather than creating vouchers one at a time.

It is the counterpart to Accounting, which works record-by-record from a pending queue and covers purchases and supplier payments too. This screen is date-range driven and covers the sales side.

Who can open it

Requires a signed-in session — the page redirects to /login without one — and the finance.compliance feature grant while FEATURE_GRANULAR_RBAC is on. The owner bypasses the grant. With the flag off, any signed-in account can reach it by URL.

Before you start

Preview before exporting. The preview tells you how many invoices and credit notes fall in the range, and it refreshes whenever you change any filter. An empty preview means an empty file.

Exporting here marks nothing. Unlike Accounting, which sets is_exported_tally and moves records out of the pending queue, this screen is a pure read. Running it twice produces the same vouchers twice — there is nothing to stop you importing the same range into Tally more than once. Keep track of what you have handed over.

"All Entities" is the default for the entity filter. That produces one file spanning every company. If your auditor keeps separate books per entity, select one.

Every control on the page

ControlWhat it does
From / ToThe date range. Both default to a sensible recent window
Sales InvoicesInclude invoices. On by default
Credit NotesInclude credit notes. On by default
EntityAll Entities or one company
Status FilterAll Statuses or Paid Only
PreviewCounts what the current filters match
ExportDownloads the XML

The preview re-runs on every change to the dates, the two checkboxes, the entity or the status — so the count on screen always describes the filters as they stand.

The downloaded file is named from the server's Content-Disposition header, falling back to tally-batch-<from>-to-<to>.xml.

What it writes

Nothing. Both /api/exports/tally-batch/preview and /api/exports/tally-batch are reads; the export returns a file. No invoice, credit note or flag is modified.

When it goes wrong

The preview says nothing matches. Widen the dates, check both document-type boxes, and check the entity filter — an entity with no invoices in the range produces nothing.

"Export failed" followed by the server's message. Nothing was downloaded.

Tally rejects the import. The vouchers depend on the ledger names and voucher types configured at /settings/tally. A ledger Tally does not have will fail on import — check that configuration first.

Duplicate vouchers in Tally. Expected if the same range is exported twice; this screen keeps no record of what has been handed over. Use Accounting if you want the pending/synced distinction tracked for you.

  • Accounting — record-by-record Tally handover with a synced flag.
  • GSTR-1 — the statutory return from the same sales data.
  • Credit Notes — which also exports Tally XML, for credit notes alone.
  • Invoices — the source records.