If you prepare GST returns in one system but keep your books in Tally, re-entering every invoice by hand is a waste of time and an invitation for mismatches. Learning how to export GSTR-1 to Tally cleanly means your sales register, GST liability, and books stay in sync without duplicate data entry.
This guide covers what to export, the step-by-step process, a field mapping reference, and how to resolve the import errors that come up most often.
Why Move GSTR-1 Data Into Tally
Many businesses prepare their marketplace and offline sales data for GSTR-1 filing in a dedicated GST tool because it handles B2B/B2C splitting, HSN summaries, and validation better than manual entry, but still run their core books and vendor ledgers in Tally for its familiar interface and existing history. Exporting the GSTR-1 sales data as a Tally-compatible file avoids double entry and keeps your Tally sales register consistent with what was actually filed.
This matters most for sellers with meaningful order volume from marketplaces such as Amazon, Flipkart, or Meesho, where typing each invoice into Tally manually is not just slow but a real source of transcription errors — a wrong HSN code, a mistyped GSTIN, or a tax amount off by a rupee due to rounding. A structured export removes that manual step entirely for the bulk of transactions, leaving your team to focus on reviewing exceptions rather than re-keying every line.
What OneBooks GST Exports Support Tally
OneBooks GST supports exporting your prepared GST data in several formats, including Tally XML, alongside GSTR-1 JSON, CSV, Excel, Miracle, and Profit NX formats. The Tally XML export is structured to be imported directly through Tally's own import function, carrying voucher-level sales entries with party, item/HSN, and tax details.
Step-by-Step: Exporting From OneBooks GST
Step 1: Prepare and upload your sales data
Bring in your sales data through Admin > Upload Files — this covers marketplace reports (Amazon, Flipkart, Meesho, Myntra, AJIO, JioMart) or a plain Excel/CSV of your invoices. Make sure GSTIN, invoice numbers, HSN codes, and tax rates are complete before moving forward, since gaps here carry through to the export.
Step 2: Review under GSTR-1 Details
Go to Admin > GSTR-1 Details to review the B2B, B2C, and credit/debit note summaries the system has generated, along with any validation warnings. Resolve warnings such as missing GSTIN, invalid HSN, or duplicate invoice numbers here — they will otherwise surface as messier errors in Tally.
Step 3: Check the detailed report
Use Admin > Detailed Reports to spot-check individual invoices against your source data before exporting, particularly for high-value transactions or ones flagged during validation.
Step 4: Export as Tally XML
From the export options on your GSTR-1 workspace, choose the Tally XML format. The file is generated in Tally's expected XML structure, ready for import as sales vouchers.
Importing the XML Into Tally
- Open the target company in Tally.
- Go to Gateway of Tally > Import Data > Vouchers (menu path can vary slightly by Tally version).
- Select the exported XML file and confirm the import.
- Review the import log Tally displays for any rejected or skipped vouchers.
- Open the Day Book or Sales Register in Tally to spot-check a sample of imported entries against your GSTR-1 summary.
Field Mapping Reference
| GSTR-1 / OneBooks GST Field | Tally Equivalent |
|---|---|
| Invoice number and date | Voucher number and date (Sales voucher type) |
| Buyer GSTIN and name | Party ledger (must exist or be auto-created, depending on settings) |
| HSN/SAC code and item description | Stock item or sales ledger, based on your Tally item/ledger setup |
| Taxable value | Sales ledger amount |
| CGST / SGST / IGST amounts | Respective tax ledgers (must be pre-created in Tally with matching rates) |
| Place of supply | State field on the party ledger / voucher |
Troubleshooting Common Import Errors
- "Ledger does not exist" errors: Tally XML import expects certain ledgers (party names, tax ledgers) to already exist unless auto-creation is enabled in your Tally configuration. Pre-create standard tax ledgers (CGST, SGST, IGST) with matching names before the first import.
- Duplicate vouchers on re-import: If you re-export and re-import the same period, Tally may create duplicate entries unless you delete the previous batch first or use unique voucher numbering per export.
- Tax rate mismatches: If a tax ledger in Tally is set to a different rate than what's in the export, the voucher may import with an incorrect amount. Confirm tax ledger rates match your HSN-based rates before importing.
- State/place of supply errors: Incorrect or missing state codes on customer ledgers can cause CGST/SGST vs IGST to be applied incorrectly. Verify state settings on party ledgers, especially for interstate customers.
Before your first bulk import, it's worth running a small test batch — a handful of invoices from one day — to confirm ledger mapping and tax rates behave as expected, rather than discovering an issue after importing an entire month.
Reconciling After Import
Once the import completes, don't treat it as finished until you've reconciled totals. Compare the total taxable value and total tax amount shown in your OneBooks GST GSTR-1 summary against the Sales Register total in Tally for the same period. A mismatch usually points to one of a small number of causes: a voucher that was rejected during import (check the import log), a tax ledger with a slightly different rate than expected, or an invoice that existed in Tally before the import and got duplicated. Doing this reconciliation every period, rather than only when something looks obviously wrong, keeps small discrepancies from accumulating into a larger cleanup job later.
Related Reading
If you're weighing whether to stay on Tally, move fully to cloud GST software, or run both together, see our comparison of Tally vs cloud GST software. If you also need to bring bank data into Tally, our guide on bank statement to Tally XML covers the same import mechanics for bank vouchers. For the GSTR-1 preparation itself, see GSTR-1 automation, and reach out to support if an import doesn't behave as expected.
Frequently asked questions
Does OneBooks GST export directly into Tally, or do I need to import manually?
OneBooks GST generates a Tally-compatible XML file for download; you then use Tally's own Import Data function to bring it into your company. This keeps the process within Tally's standard import workflow rather than a direct live sync.
What Tally versions support this XML import?
Tally's XML import function has been part of Tally ERP 9 and TallyPrime for many versions, but exact menu paths and options can differ by version. Check your specific Tally version's import documentation if the menu path described here doesn't match what you see.
Will imported vouchers overwrite my existing Tally data?
A standard XML import adds new vouchers; it does not automatically overwrite existing ones. Re-importing the same data without removing the earlier batch is what typically causes duplicates, not overwriting.
Do I need to create ledgers in Tally before importing?
It's strongly recommended. Pre-creating party ledgers and tax ledgers (CGST, SGST, IGST) with correct names and rates avoids "ledger does not exist" errors and rate mismatches during import.
Can I export credit notes and debit notes to Tally as well?
Yes, the same Tally XML export from OneBooks GST includes credit/debit note data prepared as part of your GSTR-1 workspace, structured as the corresponding Tally voucher types.
What should I check first if an import fails completely?
Confirm the XML file downloaded completely and wasn't modified, check that you're importing into the correct company in Tally, and review Tally's import log for the specific error message, which usually points to a missing ledger or a formatting issue.
