How to Convert GST Invoices to Excel for Tally

Dynamite Docs, 2026-08-12

What a GST invoice to Excel file should contain

A GST invoice to Excel conversion should produce one document record and a linked set of item rows. The document record keeps supplier and recipient details, invoice number and date, place of supply, reverse-charge flag, currency, taxable value, tax amounts, round-off, and invoice total. Item rows keep description, quantity, unit, HSN or SAC, rate, taxable value, and the printed CGST, SGST, IGST, or cess values.

Keep invoice data separate from Tally configuration. The supplier name printed on the bill may not match the party ledger. An HSN code does not choose an inventory item or purchase ledger by itself. Add ledger, voucher type, cost centre, and narration as reviewer-owned mapping columns.

The Excel file is a preparation layer. It is not a filed return, a Tally voucher, or proof that the tax treatment is correct. Review every extracted field against the invoice and current GST Portal guidance before importing or filing.

  • Source identity: filename, supplier GSTIN, recipient GSTIN, invoice number, date, and document type.
  • Supply details: place of supply, reverse charge, item description, quantity, unit, and HSN or SAC.
  • Amounts: gross value, discount, taxable value, tax rate, CGST, SGST, IGST, cess, round-off, and total.
  • Tally mapping: voucher type, party ledger, purchase or sales ledger, tax ledgers, cost centre, and import status.

Define the Tally mapping before extracting a batch

Check the target company before building the spreadsheet. Voucher types, ledger names, inventory settings, bill references, cost centres, and tax ledgers vary. Export or document the approved masters, then decide which values may map automatically and which must stop for review.

Use exact ledger names in mapping columns. Do not create a new supplier ledger merely because the invoice spelling differs from the master. Match on reviewed identifiers such as GSTIN and an approved alias table, then flag new or conflicting parties.

Keep one invoice identifier across the header and line-item tables. This prevents a multi-line invoice from becoming several unrelated vouchers. Preserve freight, discount, round-off, and tax components separately so the import step can map them under the company's accounting design.

Extract digital PDFs, scans, and invoice photos

Use the original billing PDF when available. Its text layer usually preserves small identifiers and decimals better than a screenshot. Scanned paper bills and phone photos need Indian invoice OCR or a visual model, so expect closer review of GSTINs, invoice numbers, tax rates, and faint amount columns.

Apply the agreed schema and extract the header, item table, and tax summary. Repeated headers, page totals, and carried-forward rows must not become invoice lines. Long descriptions should stay attached to the correct quantity and amount across page breaks.

Keep blank values blank. Do not infer a GSTIN, HSN or SAC, place of supply, or tax component when the source does not support it. Add a review reason such as Missing field, Unreadable scan, or Conflicting summary.

Validate GSTIN, item rows, and invoice totals

Check the supplier and recipient GSTIN character by character against the source, especially 0 and O, 1 and I, 5 and S, and 8 and B. A format check can flag an impossible value, but it does not prove that the GSTIN belongs to the right party or was active for the transaction.

Recalculate each item where quantity, rate, discount, taxable value, and tax amounts are present. Then compare item totals with the printed tax summary and invoice total. Respect the invoice's rounding and inclusive or exclusive presentation rather than forcing a universal formula.

Review the tax heads as source data. The applicable treatment depends on facts outside extraction, including the parties, place of supply, type of supply, and current law. If the invoice and expected mapping conflict, send the row to a qualified reviewer instead of silently moving an amount between CGST, SGST, and IGST.

  • Every header row and item row carries the same stable invoice identifier.
  • GSTINs, invoice number, date, and document type match the source.
  • Item taxable values and tax amounts reconcile to the printed summary within documented rounding.
  • Credit notes, debit notes, reverse charge, freight, discounts, and round-off remain explicit.
  • Unresolved differences have an owner and review note.

Build and test the Tally-ready Excel file

After the source rows balance, add the approved party, purchase or sales, tax, freight, discount, and round-off ledgers. Confirm voucher type, bill reference, narration, cost centre, and inventory mapping where the company uses them. Keep the original printed values beside the normalized import values.

Test a small, varied batch in a backup or controlled Tally company. Include a simple invoice, a multi-rate invoice, a credit note, round-off, freight, and a new supplier. A file that imports successfully can still create wrong vouchers, so inspect the resulting ledgers, tax amounts, bill references, and voucher totals.

Reconcile document counts and totals before and after import. Save rejected rows with the exact error, correct the mapping, and rerun only those records. Keep the source invoices, reviewed extraction, mapping version, import file, and result log together.

Use the official GST fields as the source checklist

CBIC's tax invoice rules list the invoice particulars, including supplier and recipient details, invoice number and date, HSN or service code, description, quantity for goods, values, tax rates and amounts, place of supply for inter-State transactions, delivery address where different, and reverse-charge status. Use the current rule and applicable notifications when deciding which fields the business must review.

The GST Portal's GSTR-1 guidance explains the return's invoice-level and summary data and the available preparation methods. Its GSTR-2B guidance also tells taxpayers to reconcile the auto-drafted statement with their own records. An extracted Excel file can support those checks, but it does not decide eligibility or prepare a return for filing.

  • CBIC tax invoice particulars under Rule 46 (Source: CGST Rules: tax invoice particulars (Rule 46))
  • GST Portal GSTR-1 preparation guidance (Source: Form GSTR-1 preparation and Returns Offline Tool FAQs)
  • GST Portal GSTR-2B reconciliation guidance (Source: Form GSTR-2B viewing and reconciliation FAQs)

Frequently asked questions about GST invoice to Excel

These answers keep extraction, Tally mapping, and tax review in their proper order.

  • Can a scanned GST invoice be converted to Excel? Yes. Use OCR or a visual model, then check small identifiers, decimals, signs, item rows, and totals against the scan.
  • Can the same Tally template work for every company? Not always. Ledger names, voucher types, inventory settings, cost centres, and bill-reference rules vary by company.
  • Should a supplier name create a new ledger automatically? Review it first. Spelling variants can create duplicate ledgers. Match against the approved master and GSTIN where appropriate.
  • Does a balanced invoice prove the GST treatment is correct? No. Arithmetic can agree while classification, place of supply, eligibility, or ledger mapping is wrong.
  • Can Dynamite Docs file GST returns? No. It extracts and prepares reviewable data. The taxpayer and qualified tax professionals remain responsible for books, returns, and tax decisions.

Convert one GST invoice batch before scaling

Start with a representative set of GST invoices and the actual Tally company configuration. Define the Excel schema, extract the source fields, reconcile the tax summary, add reviewed ledger mappings, and test the import in a controlled company. Fix mapping and source-data exceptions before processing the month.

Dynamite Docs can convert the invoices into reviewable Excel, CSV, or JSON data. Use the first batch to prove that GSTINs, HSN or SAC, item rows, tax heads, round-off, and Tally ledgers survive the full review. Then reuse the checked schema for the next GST invoice to Excel run.

Sources checked for this note

  1. CGST Rules: tax invoice particulars (Rule 46)
  2. Form GSTR-1 preparation and Returns Offline Tool FAQs
  3. Form GSTR-2B viewing and reconciliation FAQs

Related workflow: GST invoice OCR and extraction to Excel.

Keep reading

Try it yourself. Upload a PDF, scan, or image and let Dynamite Docs infer the schema.

Loading Dynamite Docs… This page is taking longer than expected. Reload page.