GST computation helper
LiveLine-by-line GST splits with citations, blocked-credit checks under §17(5), and a net-liability computation.
- ✓Per-line CGST / SGST / IGST split with the rate applied
- ✓Intra-state versus inter-state classification from the supplier and recipient states you give it
- ✓Export detection and zero-rating
- ✓Input-tax credit netting with §17(5) blocked credits identified
What it is.
The substantial engine here is the GST + TDS simulator. Give it payment lines with a supplier state and a recipient state and it returns the split per line — CGST plus SGST for intra-state, IGST for inter-state, zero-rated for exports — together with the input-tax credit position, including credits blocked under CGST §17(5). Every output line carries a citation and the rule-engine version that produced it, so a number can be traced back to the provision behind it.
Alongside it, a simple netting endpoint takes invoices you supply and returns net GST payable per head after eligible input credit. Neither surface connects to the GST portal: there is no GSTR-2B fetch, no reconciliation engine, and no e-invoice or IRN validation. Those are integrations we do not have, and calling them features would be a fabrication.
Three steps.
End to end.
Amount, nature of payment, supplier state and recipient state. State codes and state names are interchangeable.
CGST plus SGST, or IGST, or zero-rated export — per line, with the rate applied.
Eligible input credit netted off, with credits blocked under §17(5) called out, and a citation on every line.
What you get.
- ✓Per-line CGST / SGST / IGST split with the rate applied
- ✓Intra-state versus inter-state classification from the supplier and recipient states you give it
- ✓Export detection and zero-rating
- ✓Input-tax credit netting with §17(5) blocked credits identified
- ✓A citation and a rule-engine version on every output line
- ✓The 194Q versus 206C(1H) overlap resolved in the same run
Quick answers.
No. There is no GSTN or GSP connection, no GSTR-2B fetch and no matching engine. Input-credit eligibility is a flag you set on each invoice.
No. There is no e-invoice or IRN validation anywhere in the product.
It classifies intra-state against inter-state from the two states you provide. Separately, a contract scan can read a clause and estimate a place of supply — but that is reading the document, not deriving supply location from the place-of-supply rules.
No. Computation and analysis only.
More in Tax Intelligence.
A slab-accurate income-tax computation with §87A and surcharge marginal relief, and an advance-tax schedule.
Run a TDS pass over a contract and get the attracting clauses with section, rate, threshold and the text that triggered them.
Not built yet. Forty curated IFRS-to-IndAS mappings exist in the data layer with no surface over them.
Not built. There is no treaty rate table, no FTS/royalty classifier, no transfer-pricing engine, and no 15CA/CB generator.