EcomInsides

Export

Tally XML for marketplace GST sales

Tally needs ledger names and vouchers that balance. This step reads one processed batch, applies the ledger map saved on the client, and builds an XML file you import in Tally. You then check the vouchers in Tally before you rely on them.

Checklist updated 18 Nov 2026. Part of GST accounting. Check one amount in the GST calculator. Crop a label PDF in the shipping label cropper.

Ledger map on the client

Each client has their own map: sales, output CGST, output SGST, output IGST, cess, TCS receivable, marketplace commission, shipping, discount, and refunds or credit notes. Names must match the ledgers already in that Tally company. A missing name blocks the download.

The default voucher shape is one sales voucher per marketplace, supply type (intra-state or inter-state), and GST rate for the period, plus a credit note voucher for returns and a journal for fees when they are not already inside the sales voucher. The narration carries the batch id. Choose order-level vouchers on the client only when that company wants one voucher per order.

What is checked on the XML

Before download the file is checked for XML structure, voucher type, ledger names from the map, debit and credit totals that match, and amounts that tie back to the batch. A voucher that does not balance is not exported. Sales and returns are not posted twice: the export is linked to one batch, and importing the same export id again is your signal in Tally to skip it.

A failed processing batch cannot build XML. Regenerating after a new processing attempt creates a new file and leaves the previous XML in history.

Import and review

Import the XML in the Tally company that owns those ledgers. Open the vouchers for that batch id. Confirm output GST against the rate summary, TCS receivable against the reconciliation, and commission against the fees total. Correct a wrong ledger name on the client map and generate the XML again. Do not edit the XML by hand and also edit the map. The map is the source.

Do this in order

  1. Open the client and confirm every ledger name in the map exists in Tally.
  2. Choose the processed month and the batch.
  3. Generate the XML. Read any voucher that failed the balance check.
  4. Download the file and import it in Tally.
  5. Compare GST, TCS, and fees in Tally with the summaries on that batch.

Figures to keep

Default vouchers
One sales voucher per marketplace, intra-state or inter-state, and GST rate, for that period.
Returns
Credit note vouchers, separate from sales.
Fees
Journal to the commission ledger when the sales voucher does not already include them.
Balance rule
Debits equal credits on every voucher, or that voucher is held back.

Official references

Frequently asked questions

Which Tally versions can import this file?

Use a current TallyPrime company that already has the ledgers on the map. Import through Tally’s data import, then read the vouchers before you close the month.

Will two downloads create two sets of sales?

Each download is one export id for one batch. The narration includes that id. If those vouchers are already in Tally, do not import the same file again. A reprocess needs a new export, and you should reverse or skip the old batch id first.

Can two clients share a ledger map?

No. The map is stored on the client, because ledger names differ by Tally company.

Where does TCS go?

To the TCS receivable ledger on the map. It is not posted as output CGST, SGST, or IGST.

What if debit and credit differ by ₹1?

The voucher is held back. Fix the rounding row on the batch, or set the client’s rounding ledger, then generate the XML again.

Next accounting steps

All GST accounting steps