Prepare Tally XML or Excel imports from reviewed invoice data

Confirm voucher types Illustrative example.

By Dynamite Docs. Published 2026-08-14. Updated 2026-10-19.

Turn GST invoices into clean, reviewed data for Excel and Tally.

Use this page after invoice extraction and review are complete. Choose reviewed Excel, CSV or JSON source rows for a company mapping workflow, or configure a Sales/Purchase voucher XML download on Starter and above. For XML, supply the Tally company, voucher date and number, party ledger and ledger amounts. Existing ledger names and accounting treatment remain your responsibility. The XML path uses ledger entries rather than stock-item inventory lines. Test the file in a test company before importing into live books. Dynamite Docs does not create masters or post directly to Tally.

Scope and tax review

Content owner: Dynamite Docs content team. Official-source review last updated: 2026-09-30.

Dynamite Docs extracts fields from source documents. It does not determine whether an invoice complies with GST law, prepare a return, or make a document ready to file. Review every extracted value against the original and use the current GST Portal guidance or a qualified tax professional before filing.

Choose file storage and an AI provider that meet your document requirements. Review encryption, retention, own-key processing, and local Ollama options in our Security & Compliance controls.

Official GST sources

Import data using any Excel file into TallyPrime, Tally Solutions. Excel mapping templates, master prerequisites, transaction imports, preview, and exceptions.
CGST Rules: tax invoice particulars (Rule 46), Central Board of Indirect Taxes and Customs. Mandatory 16 invoice particulars and tax invoice format requirements.
Form GSTR-1 preparation and Returns Offline Tool FAQs, GST Portal. GSTR-1 invoice data, preparation modes, validation, and error correction.

Try a GST invoice or compare its storage, processing, and export limits.

Stable source columns still need a TallyPrime mapping

Supplier layouts change, so the workbook needs stable source headers before a reusable mapping can work.
Party ledgers, voucher types, stock items, units, and tax ledgers come from the TallyPrime company, not from OCR.
Document fields and item rows may need separate sheets or multiple mapped rows for one voucher.
A technically successful import can still be wrong if signs, masters, dates, or tax ledgers are mapped incorrectly.

Document types this workflow handles

GST tax invoices: sales and purchase invoices with tax splits
Credit & debit notes: adjustments exported with distinct document types
Purchase bills: vendor bills for goods and services
Sales bills: outward customer invoices

What appears in the exported rows

Exports include reviewed invoice fields as clean, standardized columns. A typical extraction provides:

Source row key: INV/24-25/0144 · line 01
Document type: Tax invoice
GSTIN (party): 27AABCS1429B1ZP
Invoice number: INV/24-25/0144
Invoice date: 2026-08-02
Place of supply: Maharashtra (27)
HSN / SAC code: 4820
Taxable value: ₹24,000.00
CGST amount: ₹2,160.00
SGST / IGST amount: ₹2,160.00 / ₹33,480.00
Invoice total (incl. tax): ₹28,320.00
Mapping status: Party ledger review required

Standardized columns for a controlled accounting import

A stable export schema separates document capture from accounting configuration. The extracted invoice number, date, GSTIN, HSN or SAC, taxable value and tax amounts stay in predictable columns even when supplier layouts change. TallyPrime supports mapping Excel columns to company fields, but the required masters and import configuration still belong to the TallyPrime company. Keeping that translation outside extraction makes exceptions easier to see and mapping changes easier to audit.

Treat the export as a staging file, not as a posting-ready truth source. Review low-confidence fields against the invoice, confirm that line totals reconcile to the taxable value, and check that the tax components add up to the document total. Look for duplicate invoice references within the same supplier and financial period. If a source uses an unfamiliar item description or party spelling, resolve it to an approved master value in a separate mapping column rather than overwriting the captured source text.

Before a large import, use a small pilot containing a normal invoice, an interstate transaction, an adjustment document and at least one multi-line bill. Import it into a test company or controlled workflow, inspect the resulting vouchers, then lock the accepted header order and mapping version. Record who reviewed the source rows and who approved the import. This simple checkpoint makes rework much easier to trace than editing vouchers after a full batch has been posted.

Excel and CSV exports also work as review schedules. You can filter by supplier, GSTIN, document type or exception status; compare the batch total with the invoice register; and retain the reviewed sheet with the accounting period. JSON is useful when an internal script or integration needs explicit field names and predictable value types. Whichever format you choose, preserve the original documents and the reviewed export together so a later query can be traced back to its source.

Reliable data exports with complete user control

Consistent headers reduce repeated cleanup, but they do not decide which ledger, voucher type or tax treatment is correct for your company. That judgment stays with the reviewer and the accounting system mapping.

Digital PDFs may contain usable embedded text, while scans and photos require visual extraction. Both can contain ambiguous values, broken tables or missing labels, so both should pass through the same review controls.

Reviewed rows can be exported to Excel, CSV or JSON, or pushed to Google Sheets when that connection is enabled. Every signed-in tier can connect a provider key. Free and Hobby own-key runs use their monthly PE allowance; Pro and Ultra own-key runs do not consume PE.

Questions, answered

What export formats are supported?

You can export reviewed data to Excel XLSX, CSV or JSON. You can also push a table to Google Sheets after connecting the integration.

Can I import the exported Excel workbook directly into TallyPrime?

Use the workbook with a TallyPrime mapping template that maps its headers or columns to the required masters and transaction fields. Dynamite Docs does not create that template or post the voucher. Preview and test a small import, then inspect any exceptions before processing a full period.

Are credit notes and debit notes included in the export?

Reviewed source rows can identify credit and debit notes in the spreadsheet workflow. The configured XML builder supports Sales and Purchase vouchers only. It does not generate credit-note or debit-note vouchers, inventory movements or GST return classifications.

How do I configure the Tally XML export?

On Starter or above, select a saved extraction and open Tally in Apps. Choose Sales or Purchase, enter the exact company and party ledger names, voucher number and date, then add existing ledger names and reviewed amounts. Preview the XML before downloading. The party entry balances the ledger amounts; a balanced file still needs a test-company import and accounting review.

Do manual corrections carry over into the export?

Yes. Any corrections made during the review step are saved and reflected in your final exported file.