India Sales Tax Invoicing Guide for Sales Teams Working With GST

This is written for the sales side of an Indian business: founders, sales managers, and the people who agree commercial terms with customers. It is not a substitute for advice from a chartered accountant, and GST rules, rates, thresholds, and prescribed particulars are amended regularly. Confirm anything specific to your business with a qualified adviser or on the GST portal before you rely on it.

The reason a sales guide to invoicing is worth having is simple. Almost every invoicing problem in a small Indian business starts in a sales conversation rather than in accounts. A GSTIN taken down verbally over a noisy call. A delivery location assumed rather than confirmed. A discount agreed on WhatsApp and never written anywhere. Accounts then produces a document from incomplete information, and the error becomes visible weeks later when a customer says their credit did not come through.

The prescribed particulars are set out in the rules, and your accountant will confirm the current list for your kind of supply. From a sales point of view, four of them cause almost all the trouble.

The recipient GSTIN

This is the field that decides whether your customer can claim input credit on what they bought. A single wrong character makes the document useless to them, and they usually discover it during their own reconciliation rather than on receipt. By then you are reissuing documents and having an awkward conversation about something that was entirely avoidable.

The fix is procedural. Capture the GSTIN as a field on the customer record at qualification, ask for it in writing rather than verbally, and check the format before saving. It takes thirty seconds at a point where nobody is in a hurry.

Place of supply

The most consequential field on the invoice, and the one most often filled in by inheritance from the billing address. Place of supply determines whether the transaction is intra-state or inter-state, which determines the tax heads. For goods it commonly follows where the goods are delivered. For services the rules vary by category and several service types have their own provisions, which is why services businesses make this mistake more often.

Treat it as a deliberate decision recorded on the deal, especially where the customer has offices in several states, where the person ordering sits somewhere other than where the work is done, or where delivery is to a third party.

Description, HSN or SAC, and rate

These need to match what was actually agreed, and they need to match between the quotation and the invoice. Where they are keyed twice, they drift. Where a discount was agreed verbally and never recorded, it drifts further.

Invoice number and date

A continuous series per financial year, no gaps, no reuse. This sounds administrative until you need to reconcile a year of documents, at which point a series that restarted casually in October becomes several days of work.

Where a supply is within a single state or union territory, tax is levied under two heads, central and state or union territory tax, and both appear separately. Where it crosses state boundaries, integrated tax applies as a single head.

The total is generally the same either way, which is exactly why the error is easy to make and easy to overlook internally. It is not overlooked by your customer, because the wrong split can prevent them using the credit. That turns a documentation issue into a commercial one, and it is the kind of thing that quietly costs you a repeat order.

Practical habit: before an invoice is raised, one person confirms the place of supply against the nature of the transaction rather than against the address on file. Where a customer has multiple registrations, ask which one this supply belongs to and record the answer on the deal.

Define it once, in writing, and month end gets substantially quieter. The definition is simply what must be true on the deal record before an invoice can be raised.

None of these are difficult. They are simply things that must be captured at the moment they are known, by the person who knows them, rather than reconstructed later by someone who was not in the conversation.

Mistakes happen, and the way you correct them matters more than the mistake itself.

Where the value or tax charged was too high, or goods come back, the correction is generally made through a credit note that references the original invoice. Where it was too low, a debit note. Both keep the original intact and create a documented trail that both sides can reconcile.

What causes lasting problems is editing an issued invoice or deleting it. Editing creates a mismatch with what your customer has already recorded. Deleting leaves a gap in your series that is hard to explain when someone examines the year. There are also timing considerations around when adjustments can be reflected in returns, so raise notes promptly and tell your accountant rather than holding them until a convenient moment. Confirm the correct treatment for your specific case with a qualified adviser.

Advances

Money received before the supply is made has its own documentation treatment, and it is frequently handled loosely in small businesses because the receipt feels like good news rather than like a document event. Record advances against the deal when they arrive, with the customer and the supply they relate to, so they are adjusted correctly rather than discovered at quarter end.

Electronic invoicing applies above a turnover threshold, and transport documentation applies to goods movements above a consignment value threshold with a range of exceptions. Both have been revised since introduction.

The operationally useful position is not to memorise numbers but to build a habit: confirm the current thresholds with your chartered accountant at the start of each financial year, and again whenever your turnover moves materially. If you are approaching a threshold, prepare before you cross it. The systems and process change is straightforward when planned and disruptive when it arrives as a surprise in the middle of a busy month.

A Pune-based services company sells an annual engagement to a customer headquartered in Bengaluru, with the work delivered to the customer team in Hyderabad, and the purchase order raised by a procurement office in Mumbai.

Four locations are now in play, and only one of them determines the tax treatment. The sales executive, reasonably enough, records the Bengaluru head office address because that is what appears on the customer letterhead, and the invoice is raised against the head office GSTIN.

The customer disputes it. Their Hyderabad entity is separately registered and is the one that will use the service, and they want the invoice raised against that registration. Because the original was issued against a different GSTIN, the correction is not a quick edit. A credit note is raised against the original and a fresh invoice issued correctly, and the customer payment is delayed by three weeks while their internal approvals catch up.

The fix afterwards costs almost nothing. The customer record now holds each registration separately, with a note on which entity receives which service. The deal record carries a place of supply field that the executive fills in during qualification by asking one question: which of your registrations should this be billed to, and where is the service being received. The quotation carries the same line items and tax treatment that will appear on the invoice, so accounts is not retyping anything.

Three months later the same situation arises with a different customer and takes ninety seconds instead of three weeks.

GSTIN captured verbally

Fix: ask for it in writing, store it as a validated field on the customer record at qualification, and never take it from an email signature without checking.

Place of supply inherited from the billing address

Fix: a separate field, filled in deliberately, with a single question asked of the customer where there is any ambiguity.

Quotes and invoices keyed separately

Fix: carry line items, rates, and tax treatment forward rather than retyping. Retyping is where drift comes from.

Verbal discounts

Fix: record the discount on the deal at the moment it is agreed, not when the invoice is being raised. If it is not written down, it will be remembered differently by two people.

Invoices edited or deleted after issue

Fix: correct through credit or debit notes that reference the original, and keep the series continuous.

Thresholds assumed rather than checked

Fix: an annual confirmation with your accountant, and a diary note if you are approaching one.

Three signs. Credit notes raised for documentation errors fall towards zero, which is the cleanest indicator that the handover is working. Month end takes less back and forth between sales and accounts, because the information accounts needs is already on the deal. And customers stop raising credit mismatches during their own reconciliation, which is the version of this problem you never hear about until it has already annoyed someone.

A fourth, softer sign: your sales team starts asking the place of supply question in the qualification call as a matter of routine. When that becomes normal rather than a special step, the process has been absorbed.

Your accounting software should remain authoritative for the ledger and for filing. What a CRM contributes is the sales-side information that feeds it: customer registrations, place of supply, agreed line items, discounts, and the documents raised against the deal, all in the place where the commercial conversation happened.

HelloGrowthCRM holds GSTIN and supply details on the customer record, carries agreed line items from quotation through to a GST invoice raised against the deal, and keeps WhatsApp and call history on the same record so an agreed discount is traceable rather than recollected. There is a free plan available, and paid access is ₹899/user/month in India.

Related reading: CRM in India, best CRM in India, WhatsApp CRM, CRM for small business, lead management software, India pricing, and product features.