Raise a GST invoice without working out the split yourself. Enter both GSTINs and the tool reads the state codes and decides for you: within one state the GST is charged as CGST plus SGST, half each; between states it is charged whole as IGST. Both GSTINs are checked properly, including the check character, so a single mistyped digit is caught here rather than in somebody's reconciliation weeks later. Add line items with HSN or SAC codes, per-line rates and discounts, and you get the taxable value, the tax by head, an explicit round-off line and the total in words using lakh and crore. Everything runs in your browser and nothing you type is uploaded. It is a template — check the treatment with your accountant before you issue it.
| Supply | State codes | Tax charged |
|---|---|---|
| Within one state | Seller and buyer match | CGST + SGST, half each |
| Between states | Seller and buyer differ | IGST, whole amount |
| 18% intra-state | e.g. 27 to 27 | 9% CGST + 9% SGST |
| 18% inter-state | e.g. 27 to 29 | 18% IGST |
| Total tax | Either way | The same — only the heads change |
From the first two digits of each GSTIN, which encode the state. If the seller's and the buyer's codes match it is an intra-state supply and the GST is halved into CGST and SGST; if they differ it is inter-state and the whole amount is charged as IGST. Enter both GSTINs and it switches automatically.
It recomputes the check character from the other fourteen, which is the only way to catch a typo. A GSTIN with one wrong digit still matches the pattern perfectly, so format-only validation passes it. If the check fails, the tool tells you which character it should have been.
Yes, and in Indian grouping — thousand, lakh, crore — rather than millions. An Indian tax invoice written in millions is wrong on the document that matters.
Because the payable amount is rounded to the nearest rupee and the difference has to be visible. Absorbing it silently leaves a total that does not match the tax lines above it, which is exactly what gets queried.
Yes. Each line carries its own rate, and the totals are summed across them. Line discounts are applied before tax, which is the correct order.
The standard PDF font cannot encode the rupee sign, so drawing it would produce a question mark. Rather than that, amounts in the PDF use the INR currency code. On screen you still see the symbol.
No. The whole invoice, including both GSTINs, is held in the page and the PDF is built in your browser. Nothing is sent to a server and nothing is stored after you close the tab.
No — it is a template that does arithmetic. Rates, exemptions and place-of-supply rules change, and reverse charge, exports, e-invoicing and composition dealers are not handled. Check the treatment with your accountant.
Which tax heads appear on an Indian invoice is decided by geography, not by a setting: a supply within one state is charged as CGST plus SGST, half each, while a supply across states is charged whole as IGST. The deciding fact is the first two digits of each party's GSTIN, which encode the state, so the identifier drives the arithmetic rather than decorating the header. Both GSTINs are validated structurally and by their check character. That last part matters more than a pattern match: a GSTIN is fifteen characters in a fixed shape, and a single mistyped one still looks exactly like a GSTIN, so a regular expression passes it and the error surfaces weeks later in somebody else's reconciliation. The check character is recomputed from the other fourteen — each character's base-36 value weighted alternately by one and two, the products folded back in base 36, and the result being whatever brings the total to a multiple of 36 — and a mismatch names the character it should have been. Tax is computed per line and rounded to paise there, not only at the end, because the line values are what get printed and a total that does not equal the sum of the visible lines is the first thing a reviewer questions. On an intra-state line the odd paisa goes to CGST so that the two halves still add to the line's GST instead of drifting a paisa away from it. The payable amount is then rounded to the nearest rupee with the difference shown as an explicit round-off line rather than silently absorbed. The amount in words uses Indian grouping — thousand, then lakh at a hundred thousand and crore at ten million — because an Indian tax invoice reading "one million" is wrong on the document that matters, and the group count recurses so that figures above a hundred crore still read correctly. The PDF is drawn with pdf-lib and Helvetica, which cannot encode the rupee sign because it falls outside WinAnsi; rather than printing a question mark, money falls back to the INR currency code, and any other character the font cannot draw is reported once instead of being silently mangled.