Extract CGST, SGST, IGST, and cess into separate columns with AI

Dynamite Docs
Source → result
PRINTED TAX BREAKDOWN: Tax splits keep their labelsCGST (rate · amount): 9% · ₹2,160.00. SGST / UTGST (rate · amount): 9% · ₹2,160.00. IGST (rate · amount): 18% · ₹33,480.00. Illustrative example, not extracted customer data.SOURCE DOCUMENTPRINTED TAXBREAKDOWNCGST (rate · amount)9% · ₹2,160.00SGST / UTGST (rate ·…9% · ₹2,160.00IGST (rate · amount)18% · ₹33,480.00KEEP THE TAX COMPONENTS SEPARATE1CGST (rate ·amount)9% ·₹2,160.002SGST / UTGST(rate ·amount)9% ·₹2,160.003IGST (rate ·amount)18% ·₹33,480.00Compare each component with the printed…
CGST (rate · amount)
9% · ₹2,160.00
SGST / UTGST (rate · amount)
9% · ₹2,160.00
Separate cess if present Illustrative example.

By Dynamite Docs. Published . Updated .

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

GST invoices can show CGST and SGST or UTGST, IGST, cess and several tax rates across line and summary tables. Dynamite Docs extracts the printed components into separate columns and calculates review checks between taxable value, tax amounts and the invoice total. These checks can expose a missing or misread number. They do not determine the correct place of supply, confirm the legal tax treatment or prove that the supplier calculated GST correctly. Your tax reviewer remains responsible for those decisions.

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

Dynamite Docs
The handoff
PRINTED TAX BREAKDOWN: Tax splits keep their labelsUpload your invoices. Verify calculations. Export for your books. Illustrative example, not extracted customer data.FROM SOURCE FILE TO A RESULT YOU CAN USEPRINTED TAXBREAKDOWNReview workspaceTax splitskeep theirlabels1Upload yourinvoices2Verifycalculations3Export for yourbooks
  1. 01Upload your invoices
  2. 02Verify calculations
  3. 03Export for your books
Separate cess if present Illustrative example.

Tax calculation and breakdown errors cause bookkeeping mismatches

  • Intra-state sales require equal CGST and SGST splits, while inter-state transactions apply IGST. Recording the wrong tax type leads to ledger discrepancies.
  • Suppliers format tax tables differently: some use 3-column layouts, while others stack tax lines beneath each product.
  • Multi-rate invoices containing 5%, 12%, 18%, and 28% items create complex mathematical splits that simple tools flatten into an unstructured sum.
  • Small rounding differences or misread digits can cause invoice totals not to tie out to taxable amounts.

Document types this workflow handles

  • Intra-state tax invoices: equal CGST and SGST/UTGST splits
  • Inter-state tax invoices: integrated IGST rate and amount
  • Multi-rate purchase bills: mixed 5%, 12%, 18%, and 28% tax rates
  • Invoices with Compensation Cess: cess on motor vehicles and luxury goods

What gets extracted from the tax block

Dynamite Docs
Inside the output
PRINTED TAX BREAKDOWN: Tax splits keep their labelsCGST (rate · amount): 9% · ₹2,160.00. SGST / UTGST (rate · amount): 9% · ₹2,160.00. IGST (rate · amount): 18% · ₹33,480.00. Illustrative example, not extracted customer data.Source-linked field inspectorPRINTED TAX BREAKDOWN9% · ₹2,160.009% · ₹2,160.0018% · ₹33,480.00CGST (rate · amount)9% · ₹2,160.00SGST / UTGST (rate · amount)9% · ₹2,160.00IGST (rate · amount)18% · ₹33,480.00
CGST (rate · amount)
9% · ₹2,160.00
SGST / UTGST (rate · amount)
9% · ₹2,160.00
IGST (rate · amount)
18% · ₹33,480.00
Separate cess if present Illustrative example.

The tax split is captured as distinct, confidence-scored rate and amount fields tied to the place of supply:

  • Taxable value (subtotal): ₹24,000.00
  • CGST (rate · amount): 9% · ₹2,160.00
  • SGST / UTGST (rate · amount): 9% · ₹2,160.00
  • IGST (rate · amount): 18% · ₹33,480.00
  • Compensation Cess (rate · amount): 12% · ₹6,000.00
  • Place of Supply (POS): Maharashtra (27) / Karnataka (29)
  • Statutory supply regime: Intra-state / Inter-state
  • Mathematical tie-out status: Balanced (Taxable + Tax = Total)

Understanding GST tax splits and calculation checks

Dynamite Docs
The review
PRINTED TAX BREAKDOWN: Tax splits keep their labelsRead the printed tax label. Separate cess if present. Reconcile the tax total. Illustrative example, not extracted customer data.SOURCE DOCUMENTPRINTED TAXBREAKDOWNCGST (rate · amount)9% · ₹2,160.00SGST / UTGST (rate ·…9% · ₹2,160.00IGST (rate · amount)18% · ₹33,480.00Review before exportCGST (rate · amount)9% · ₹2,160.00Compare with the source on the leftAccept after reviewSeparate cess if presentOriginal stays…
CGST (rate · amount)
9% · ₹2,160.00
SGST / UTGST (rate · amount)
9% · ₹2,160.00
IGST (rate · amount)
18% · ₹33,480.00
Separate cess if present Illustrative example.

The printed tax split gives the extraction workflow its first clue, but it should not be the only basis for classification. Place-of-supply and supplier-location rules can be fact-specific. Capture the supplier GSTIN, buyer GSTIN, place-of-supply text, document type and printed tax labels together so the reviewer sees the context behind each amount.

Multi-rate invoices need both line-level and summary-level review. Calculate the expected tax for each taxable base and compare the sum with the printed tax summary. Keep discounts, freight, round-off and cess separate. If the difference is within a configured rounding tolerance, record it as such; do not silently force the values to balance.

A useful exception schedule distinguishes extraction problems from source-document questions. "Unreadable amount" means the image needs review. "Arithmetic variance" means the printed components do not add up. "Unexpected tax type" means the displayed split conflicts with the reviewer's expectations. Those exceptions require different owners and should not be collapsed into one generic error.

Credit and debit notes also need sign handling. Preserve the document type and source amounts, then apply the reporting sign in a separate reviewed field. This prevents an adjustment from looking like an ordinary invoice simply because all values were printed as positive numbers.

Mathematical checks can highlight rounding differences, dropped digits and rows assigned to the wrong column. They cannot establish whether the rate, classification or GST treatment is legally correct. Retain the source document and reviewer decision with the exported schedule.

Tax breakdown with source review and data ownership

Every signed-in tier can connect a supported provider key. Free and Hobby own-key pages use monthly PE; Pro and Ultra own-key runs do not consume PE.

Digital PDFs may expose embedded text, while paper scans need visual extraction. Calculation checks help find exceptions, but the source remains the authority.

Reviewed tax rows can be exported to Excel, CSV or JSON, or pushed to Google Sheets. Map and test the file before using it in Tally, BUSY, Zoho Books or another accounting system.

Questions, answered

How does the system distinguish intra-state from inter-state invoices?

The workflow extracts supplier location, place-of-supply text and printed tax columns so a reviewer can assess the treatment. It does not make a final place-of-supply or intra-state versus inter-state determination.

How does it handle multi-rate invoices with different tax percentages?

Taxes are extracted at both the line-item level and summary level. Each product retains its specific rate and taxable amount, while the summary table confirms the total tax breakdown.

What happens if CGST and SGST amounts do not match?

The workflow can flag a difference between the displayed CGST and SGST values, such as ₹2,160 versus ₹2,168. The reviewer should check whether it is an extraction mistake, source arithmetic issue, rounding treatment or a transaction that needs specialist review.

Does extraction capture GST Compensation Cess?

Yes. When an invoice includes Compensation Cess (such as on passenger vehicles or luxury goods), cess is extracted into its own column rather than merged with IGST.

Related extraction articles

Open the document extraction workspace, no credit card required.

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