Prepare Tally XML or Excel imports from reviewed invoice data
Dynamite Docs- Source row key
- INV/24-25/0144 · line 01
- Document type
- Tax invoice
Answer in 30 seconds
Export reviewed invoice rows to Excel or configure Tally voucher XML in Dynamite Docs. Supply company ledgers, test imports, and reconcile totals.
Dynamite Docs- 01Upload your invoice batch
- 02Review with confidence scores
- 03Map into your accounting software
TallyPrime ledger mapping and import checks
- 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.
How to prepare standardized rows for accounting import
Upload your invoice batch
Add GST invoices as digital PDFs, scans or photos. The extractor proposes fields from each document and keeps the source available for side-by-side review.
Review with confidence scores
Check any flagged fields, such as vendor GSTINs or tax breakdowns, to verify numbers before exporting.
Export the source workbook
Choose Excel for a TallyPrime mapping template, or open the Tally export dialog to configure Sales/Purchase XML with your company and existing ledgers. Preview and test the resulting file. CSV, JSON and Google Sheets remain available for other handoffs.
Map into your accounting software
Download the reviewed file, add company-specific ledger or voucher values, and map its columns into the import template required by your accounting system. Test the mapping with a small batch before a full import.
Document types this workflow handles
What appears in the exported rows
Dynamite Docs- Source row key
- INV/24-25/0144 · line 01
- Document type
- Tax invoice
- Mapping status
- Party ledger review required
Exports include reviewed invoice fields as clean, standardized columns. A typical extraction provides:
Standardized columns for a controlled accounting import
Dynamite Docs- Source row key
- INV/24-25/0144 · line 01
- Document type
- Tax invoice
- Mapping status
- Party ledger review required
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 (opens in a new tab), 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 Starter own-key runs use their monthly PE allowance; Pro and Scale own-key runs do not consume PE.
Paid invoice intake · PRO and Scale
Stop downloading invoices from email.
Forward invoice attachments to your private Dynamite Docs address. They are stored in your account, extracted automatically, and placed in the dashboard for review and export.
- 01Invoice arrives
- 02Forward attachment
- 03Extract and review
- 04Export to your workflow
Questions, answered
You can export reviewed data to Excel XLSX, CSV or JSON. You can also push a table to Google Sheets after connecting the integration.
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.
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.
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.
Yes. Any corrections made during the review step are saved and reflected in your final exported file.
Extraction guides
Related document workflows
Extract TallyPrime invoice data for AI accounting
Extract TallyPrime invoice rows for AI accounting in Dynamite Docs. Check party GSTINs, HSN/SAC, line items and tax before mapping vouchers.
Convert GST invoice data to Excel with AI
Convert Indian GST invoices to Excel with AI in Dynamite Docs. Review GSTINs, HSN/SAC, line items, taxable values, and tax splits before downloading.
Convert GST invoices to JSON using AI
Extract Indian GST invoices to JSON with AI in Dynamite Docs. Review fields, line items, GSTINs, and tax splits before using the output in mappings or APIs.
Extract GST invoices for AI accounting
Extract Indian GST invoices for AI accounting in Dynamite Docs. Review GSTINs, HSN/SAC, line items and tax against the source before using the rows.
From the blog
Build a Tally invoice import workflow using AI-extracted data
Build a Tally import workflow with AI-extracted GST invoices from Dynamite Docs. Map reviewed rows to masters and voucher fields, then test and reconcile.
Build a Tally invoice import workflow using AI-extracted data
Build a Tally import workflow with AI-extracted GST invoices from Dynamite Docs. Map reviewed rows to masters and voucher fields, then test and reconcile.
Test a reviewed Tally export
Export reviewed Excel rows or configure a Sales/Purchase XML file using existing company ledgers. Import one file in a test company and reconcile the accepted voucher before preparing a full period.
