GSTR-1 invoice data preparation

The outward-supply details that go into GSTR-1 have to come from somewhere: your own sales invoices, credit notes, and debit notes. Every B2B invoice carries a recipient GSTIN, an invoice number and date, a place of supply, an HSN/SAC code, a taxable value, and a CGST/SGST or IGST split, and someone has to read all of it into a working sheet before the return gets prepared. Dynamite Docs turns that pile of sales documents into invoice-level rows — GSTIN, invoice no/date, place of supply, HSN/SAC, taxable value, tax split — so data preparation when preparing GSTR-1 starts from clean structured rows instead of a stack of PDFs and an empty spreadsheet.

Try this workflow free or view pricing.

Outward-supply data preparation still runs on retyping

Sales invoices, credit notes, and debit notes arrive in every format, billing-software exports, email PDFs, WhatsApp photos, and each one has to be read into the outward-supply working sheet by hand.
The fields repeat on every document, recipient GSTIN, invoice number and date, place of supply, HSN/SAC, taxable value, and the CGST/SGST or IGST split, but the layout is different every time.
The tax split is exactly where preparation errors hide: a wrong GSTIN or a swapped CGST and SGST amount in the working sheet has to be traced back to the original invoice days later.
When preparing GSTR-1, the quality of the return depends on the quality of that prepared data, and retyping under a deadline is the weakest link in the chain.

How Dynamite Docs prepares outward-supply data

01 — Drop the sales batch in

Upload a folder of sales invoices, credit notes, and debit notes. Clean digital PDFs, including most billing-software exports, are parsed deterministically from their text layer: no AI call, identical results every time.

02 — Schema inferred, not built

GSTIN, invoice number and date, place of supply, HSN/SAC, taxable value, CGST, SGST, IGST, and totals are read from each layout on the spot. No template library to maintain for every billing software or customer format.

03 — Review by confidence

Every field carries a confidence score. You check the low-confidence values, usually a GSTIN, a place of supply, or a tax split that doesn’t tie to the taxable value, and each correction becomes a pattern the next batch reuses.

04 — Export the working sheet

Convert rows to Excel, CSV, or JSON. The invoice-level outward-supply detail is ready for the person preparing GSTR-1 to review, cross-check against the originals, and use.

Document types this workflow handles

Tax invoices (B2B) — sales invoices carrying a recipient GSTIN
Tax invoices (B2C) — consumer sales, no recipient GSTIN
Credit notes — reductions for returns and corrections
Debit notes — upward adjustments to earlier invoices

What gets extracted from a sales document

The exact fields are inferred per layout. A typical outward-supply run yields these, each confidence-scored:

GSTIN (supplier) — 27AABCS1429B1ZP
GSTIN (recipient) — 27BAAFG2874Q1ZX
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

A realistic example

A batch of outward-supply documents extracts to rows like these, each row one invoice or adjustment ready to review when preparing GSTR-1:

Invoice #	Date	Recipient GSTIN	Place of supply	HSN/SAC	Taxable value	CGST	SGST	IGST	Invoice value
INV/24-25/0144	2026-08-02	27BAAFG2874Q1ZX	Maharashtra (27)	4820	₹24,000	₹2,160	₹2,160	—	₹28,320
INV/24-25/0145	2026-08-03	33AAECR7614M1ZK	Tamil Nadu (33)	8467	₹1,86,000	—	—	₹33,480	₹2,19,480
CN/24-25/0031	2026-08-06	27BAAFG2874Q1ZX	Maharashtra (27)	4820	₹4,000	₹360	₹360	—	₹4,720

The working sheet behind GSTR-1

GSTR-1 is the outward supplies return, and its invoice-level detail is expected to trace back to your own records: the recipient’s GSTIN, the invoice number and date, the place of supply, the HSN/SAC code, and the taxable value and tax split for each document. The work of assembling that detail is data preparation, not filing. Dynamite Docs is a document-processing and data-preparation layer. It reads your sales invoices, credit notes, and debit notes and hands you clean, confidence-scored rows. Preparing the return, deciding the classification, and filing on the GST portal stay with your CA and your own processes.

The credit and debit note story matters as much as the invoices. When a sale is returned or corrected, the adjustment has to appear in the same outward-supply working data, with its own document number, date, and tax split. Because the same schema covers invoices and adjustments, the whole outward-supply picture sits in one workspace instead of two spreadsheets that have to be merged by hand.

The volume is the real argument. A trader or practice processing a few hundred outward documents a month can spend days assembling the working sheet alone. Batch processing turns a month of sales documents into one review session, and because corrections are remembered per layout, the second batch from the same billing software extracts cleanly and the review shrinks to the fields that genuinely need a human.

HSN/SAC classification is worth checking by hand. Extraction reads the code exactly as printed on the document; whether that code is the right classification for the item is a judgment that stays with your team and your advisor. Consult your tax advisor and the GST portal for current rules before relying on any prepared data.

Why bring-your-own-AI matters for outward-supply data

GSTR-1 quality is decided before filing, in the working sheet: recipient GSTIN, place of supply, HSN/SAC, taxable value, and split, invoice by invoice. Assembly is data preparation, not filing, and the reader that turns your sales documents into that preparation is your choice, paid at your provider’s rate with no markup.

Billing-software exports of your sales documents parse deterministically for free, identical results every run. Photographed and handwritten sales records are read by the vision model you pick, so the cost of the outward-supply working sheet tracks the documents in it.

The prepared rows, invoices, credit notes, and debit notes together, are what your CA reviews before the return, and corrections your team makes in review are remembered per layout. Export to Excel, CSV, or JSON, and keep the working sheet yours.

Questions, answered

Does it file GSTR-1 or push data to the GST portal?

No. Dynamite Docs is a document-processing and data-preparation layer. It extracts your outward-supply detail into structured rows; preparing the return and filing it remain with your CA or your team, who review the confidence-scored rows before exporting.

Does it read credit notes and debit notes too?

Yes. Adjustments for returns and corrections are extracted with the same schema, document number, date, GSTIN, place of supply, taxable value, and tax split, so the whole outward-supply picture is in one place.

Can I export the outward-supply detail to Excel, CSV, or JSON?

Yes. Export to Excel, CSV, or JSON, or push rows to Google Sheets, ready for your own working sheet or your accounting workflow.

How do I know a GSTIN or tax amount was read correctly?

Every field carries a confidence score. Low-confidence values, usually a GSTIN, a place of supply, or a tax split that doesn’t tie to the taxable value, are flagged for you to check, and each correction becomes a pattern the next batch reuses.