GST-Compliant Billing Software: Requirements Guide 2026

GST-compliant billing software must do six things correctly: issue tax invoices with all fields mandated under Rule 46 of the CGST Rules (GSTIN, HSN/SAC codes, place of supply, tax breakup), apply the right CGST/SGST/IGST split automatically, generate e-invoices through the IRP if your turnover crosses ₹5 crore, produce e-way bills for goods movement above ₹50,000, export clean GSTR-1 and GSTR-3B data your accountant can file from, and keep an unbroken, auditable trail of every invoice, credit note, and amendment. If a billing system cannot demonstrate all six, it is a formatting tool, not a compliance tool.

This guide sets out the full requirements list — legal fields, e-invoicing thresholds, integration points, and what custom-built billing actually costs in 2026 — so you can evaluate off-the-shelf products or brief a development team properly. NexaEx builds billing and ERP systems for Indian SMBs, from Erode's textile traders to multi-state distributors, and this is the specification we build against.

What the law actually requires on an invoice

Rule 46 of the CGST Rules, 2017 defines the mandatory contents of a tax invoice. Your software must populate every one of these, automatically, on every invoice:

• Supplier's name, address, and GSTIN
• Consecutive serial number (unique for the financial year — gaps and duplicates both cause audit queries)
• Date of issue
• Recipient's name, address, and GSTIN (for B2B); delivery address and state for B2C above ₹50,000
• HSN code for goods / SAC code for services — 4 digits mandatory for turnover ₹5 crore and below, 6 digits above ₹5 crore
• Description, quantity, unit, total value
• Taxable value after discounts
• Tax rate and amount, split into CGST + SGST/UTGST (intra-state) or IGST (inter-state)
• Place of supply with state name and code for inter-state sales
• Whether tax is payable on reverse charge
• Signature or digital signature of the supplier

The CGST/IGST split is where homegrown Excel billing quietly goes wrong: the software must compare the supplier's state code with the place of supply — not the billing address — and choose the split accordingly. Get it wrong and the buyer's input tax credit (ITC) is at risk, which is how billing errors turn into angry customers. The software must also handle credit and debit notes referencing original invoices, because in GST you cannot simply delete an invoice; you reverse it, and the trail must survive.

Do you need e-invoicing? The thresholds that decide

E-invoicing is mandatory for businesses with aggregate annual turnover above ₹5 crore (in any financial year since 2017–18) for B2B invoices, exports, and credit/debit notes. It is not an invoice format — it is a registration process: your software sends the invoice JSON to a government Invoice Registration Portal (IRP), which validates it, assigns a 64-character IRN (Invoice Reference Number), and returns a signed QR code that must be printed on the invoice. No IRN on a mandated invoice means, legally, no invoice — and your buyer's ITC fails.

What this demands from software:

• IRP integration via API (direct or through a GSP such as ClearTax, Cygnet, or MasterGST), including retry handling for IRP downtime — invoices must queue, not silently fail.
• 30-day reporting window discipline: since April 2025 rules tightened, mandated taxpayers must report invoices to the IRP within 30 days of the invoice date. Software should surface unreported invoices as a red alert, not a buried report.
• Cancellation logic: an IRN can be cancelled within 24 hours; after that, only credit notes. The software must enforce this rather than let staff "edit" registered invoices.
• QR printing on PDFs and thermal-printer formats alike.

Below ₹5 crore, e-invoicing is optional — but the threshold has only ever moved downward (from ₹500 crore in 2020 to ₹5 crore now), so any billing system commissioned in 2026 should ship e-invoice-ready, even if the switch stays off for now. Retrofitting IRP integration later costs more than building the data model right the first time.

E-way bills, TCS/TDS, and the other moving parts

A compliant billing stack rarely stops at the invoice:

• E-way bills are required for goods movement worth over ₹50,000 (with state-level variations). Software should generate them from invoice data via the e-way bill API — re-typing consignment details is both wasted labour and an error source. For transporters and distributors this is the single biggest time saving in the system.
• GST TCS applies if you sell through e-commerce operators; your reconciliation reports must net it correctly.
• Composition scheme businesses (turnover up to ₹1.5 crore) issue a bill of supply, not a tax invoice, and cannot charge GST — software must support the distinction if any group entity uses the scheme.
• Reverse charge (RCM) transactions — common with goods transport agencies and unregistered-vendor purchases — need flagging at entry so returns pick them up.
• Multi-GSTIN support: one company, branches in two states, means two GSTINs and state-wise invoice series and returns. Many cheap products silently fail here.

Which returns must your software feed?

Billing software does not file returns — your accountant or a filing platform does — but it must produce filing-ready data. Concretely: GSTR-1 (outward supplies, monthly or quarterly under QRMP) needs invoice-level B2B detail and rate-wise B2C summaries; GSTR-3B needs summary tax liability; and your purchase records must reconcile against GSTR-2B so you claim only eligible ITC. The practical test when evaluating any product: ask for a GSTR-1 JSON export of a sample month and hand it to your accountant. If they can upload it to the GST portal or their filing tool without manual rework, the software passes; if they receive a PDF and re-type it, you are paying salary to compensate for bad software.

Off-the-shelf vs custom: what should you actually buy?

The honest guidance: if Tally or Zoho fits your workflow, buy it — you cannot custom-build GST filing plumbing cheaper than companies whose whole business is maintaining it. Custom wins when the workflow around the invoice is the hard part: an Erode powerloom job-work unit billing by weight and wastage, a Namakkal transporter combining e-way bills with trip sheets, a distributor with van-sales apps feeding a central GSTIN. In those cases we typically build the operational system custom and integrate with the IRP via a GSP, and with Tally for the accountant — the pattern that keeps CA relationships intact. Cost it for your case with our project cost calculator, and pressure-test any vendor quote against our guide to software development contracts in India before signing.

Audit trail and data protection: the requirements everyone forgets

Two compliance layers sit on top of GST itself. First, records retention: GST law requires books and records kept for 72 months (6 years) from the due date of the annual return — so the software needs reliable long-term storage and backups, not a database that gets "cleaned up" when it slows down. Companies Act–covered entities additionally need audit-trail (edit-log) accounting software: every change logged, with the log not disableable — a requirement in force since April 2023 that many small custom systems flunk. Insist on immutable edit logs for invoices, rates, and masters.

Second, your billing database is full of personal data — customer names, addresses, phone numbers, GSTINs — which puts it inside the DPDP Act, 2023 perimeter: access control, encryption, breach response. The controls are the same eleven we detail in our security checklist for business software; a billing system that emails the full customer ledger as an unprotected Excel every Monday fails both your competitive interests and the law.

Rollout: how to switch billing systems without breaking a filing cycle

Switching mid-quarter is where compliance accidents happen. The sequence that works: run the new system in parallel for one full month, matching its GSTR-1 export against the old system's, then cut over on the first day of a month (ideally a quarter for QRMP filers), carrying opening balances and the invoice series forward with a documented series break. Train the billing desk on credit notes and cancellations before go-live — those are the flows staff improvise on, and improvisation is what auditors find. A competent vendor will run this migration as a deliverable with acceptance criteria, not leave it to your staff on a weekend; see how we structure such projects in our case studies.

Talk to us

If your billing workflow has outgrown off-the-shelf software — job-work, multi-branch, dispatch-linked, or export-heavy — we will tell you straight whether custom makes sense and what it costs. Contact us or WhatsApp +91 97912 97741; we reply within 24 hours. Tax rules change frequently — confirm current thresholds with your CA before acting.