Not about your tax return — about the document you send and the terms printed on it. Which document you are actually issuing, what every invoice should carry, a numbering series that survives being asked about a year later, terms people honour, and a three-step follow-up ladder for a late payment.
Invoicing is the part of freelancing that feels like admin and behaves like infrastructure. A clean invoice gets paid faster, a clear payment term prevents most of the chasing, and a numbering series you can explain a year later turns filing season from an investigation into an afternoon. This guide is about the document and the terms — not about your tax return, which is a separate subject covered in freelance taxes and GST in India. What applies to you depends on whether you are registered and on rules that change, so read this as orientation and confirm the specifics with a qualified chartered accountant.
Which document are you actually sending?
Three documents get called “the invoice” and they do different jobs. Sending the wrong one is rarely a disaster, but it causes delays — a client's accounts team that receives a proforma when it needs a tax invoice will simply wait, often without telling you why.
| Document | What it is | When you send it |
|---|---|---|
| Quotation or estimate | Your offer. Not a demand for money and not an accounting document. | Before the work is agreed, while the client is deciding. |
| Proforma invoice | A preview of the invoice, usually so the client can raise a purchase order or release an advance. Not a tax invoice. | Before supply, when the client's process needs a document to act on. |
| Invoice (tax invoice if you are registered) | The actual demand for payment against work supplied. This is the accounting document on both sides. | On or after supply, per what you agreed. |
| Receipt | Acknowledges that money has been received. It does not replace the invoice. | After payment, if the client asks for one. |
The distinction that matters most: a proforma is not an invoice, and issuing one does not record a sale. If a client asks for “an invoice for the advance”, ask whether their accounts team wants a proforma or a tax invoice — the answer depends on their process, and guessing wastes a week. If you are GST-registered, the particulars a tax invoice must carry are prescribed, and both the list and the timing rules have changed over the years, so get your standard format confirmed by your CA once rather than copying a template from the internet.
What every invoice should carry
Whatever your registration status, an invoice that a stranger in an accounts department can process without emailing you back has the same core contents. Missing fields are the most common reason a payment sits in someone's queue.
- Both parties, fully. Your legal name and address, and the client's registered name and address — not the brand name or the contact person's name. Accounts teams match on the registered entity.
- A unique invoice number, from a series you can explain. See the next section.
- The invoice date, and separately the period or date of supply if they differ. These two being conflated causes real confusion at year end.
- A description tied to the deliverable, not to your effort. “Website development — milestone 2: product catalogue and cart, as per scope dated 14 July” is processable. “Development work” invites a question.
- The amount, in words as well as figures if it is a large sum, and the currency stated explicitly. “45,000” without a currency is a genuine ambiguity on a cross-border invoice — and if your client is overseas there is more to set up than the invoice itself, covered in getting paid by international clients from India.
- The tax treatment, if you are registered. Your registration number, the client's where applicable, the place of supply, and tax shown as a separate line rather than folded into the total. If you are not registered, say nothing about tax rather than inventing a line.
- Your payment details and, if relevant, your tax identification details — the ones the client needs to pay you and to report the payment correctly.
- A due date, as an actual date. “Net 15” requires the reader to do arithmetic, and people do not chase their own arithmetic.
A numbering series that survives scrutiny
The principle is durable even though the rules around it are not: invoice numbers should be unique and consecutive within a series, with no gaps you cannot account for. That is what makes a set of invoices auditable, and it is why “I just use the date” stops working the moment you issue two in one day.
A format that works indefinitely is a short prefix, the financial year, and a running number — something like a three-letter code for your practice, the year span, and a four-digit sequence. Start at one each financial year and never reuse a number. If you have to cancel an invoice, do not delete it and reissue the same number: mark it cancelled, keep it in the file, and move on to the next number. A gap in a series is the single easiest thing for anyone reviewing your records to ask about, and “I deleted that one” is a poor answer a year later.
If you invoice in more than one way — domestic and export, or two distinct services — you can run separate series with different prefixes, as long as each is internally consecutive. Whether you should, and how the series must be structured for your registration status, is exactly the sort of detail worth settling with your CA at the start rather than reconstructing later.
Payment terms people actually honour
A payment term is a commercial agreement, not a legal formula. The conventions — an advance percentage, a number of days from invoice, a charge for late payment — work because both sides recognise them, so use the conventional shape and put it in the scope of work rather than only on the invoice. A term first seen on an invoice is a term the client never agreed to.
- An advance, or a funded milestone. Historically freelancers asked for a share up front. A funded milestone takes far less negotiating and puts the commitment on the record before you start — which is not the same thing as money already received, for the reason given below.
- A stated number of days, and then an actual due date on the invoice. Shorter is better and fifteen days is a reasonable default for a solo supplier; the longer terms large companies prefer are a financing arrangement you are providing for free.
- A late-payment clause you can state without hostility. Something like: “Invoices are due within 15 days. Accounts unpaid beyond 30 days may attract a late fee of 2% per month, and work on any active milestone pauses until the account is settled.” Put it in the agreement, mention it once, and you will rarely need to invoke it.
- Who pays the transfer charges, especially on a cross-border payment where they can be deducted in transit and your invoice arrives short.
- What happens on a disputed line. Agree that an undisputed portion is paid on time while the disputed one is discussed. Otherwise one contested item holds the whole invoice.
How working through milestones changes the sequence
Working through funded milestones changes the order of events, and it is worth understanding because it changes what the rest of this article is doing for you.
The conventional sequence is: do the work, issue the invoice, wait, chase, get paid. The milestone sequence is: agree the deliverable, the client commits to the amount before you start, you deliver, they approve, and the agreed amount is released to you. Having the commitment first is what takes most of the pressure out of payment terms, because you are no longer quietly financing someone who has promised nothing in writing. Be accurate about how far that goes, though: on LanceGuru today, funding a milestone records the commitment rather than collecting the money at that moment, so a released milestone is still a payment you need to watch arrive and reconcile — not one that was banked before you began. What a funded milestone is and is not is set out in milestone payments and escrow for clients, and the sequence itself is on how it works. Which is why the three-step ladder further down is not redundant: keep it.
You still need invoices. The release is a payment and your books need a document for it, so raise an invoice against each approved milestone with the description tied to that milestone. Two other things to note: commission is deducted from your side, so the amount released to you and the amount the client funded are not the same figure, and your invoice and your accounting need to reflect that correctly — the current commission rates for each plan are on the pricing page. And how a platform-mediated payment should be invoiced and reported for your registration status is a genuine question rather than an obvious one, so raise it with your CA early.
A three-step ladder for a late payment
Most late payments are not refusals. They are an invoice sitting in a queue, a person on leave, or a process you do not know about. So the ladder is designed to escalate slowly and to stay usable — every step should leave you able to keep working with this client, right up until the point where you have decided not to.
- On the due date, a reminder with no edge to it. “Invoice 0042 was due today — attaching it again in case it needs re-sending. Could you confirm it is in the payment run?” This is the step that resolves most of them, and asking about the payment run is the useful part: it invites a process answer rather than a promise.
- A week later, ask for a date and a name. “Still showing as unpaid. Could you let me know the expected date, or who in accounts I should follow up with directly?” Getting a named person is often the whole solution, because the person you have been talking to may have no visibility of payments.
- A fortnight later, state the consequence. Reference the agreed term, state that work on the active milestone is paused until the account is settled, and give a date after which you will treat the engagement as on hold. Keep it short and unemotional. A message that reads like a form letter is more effective than one that reads like a grievance, because it signals that this is your standard process rather than a personal escalation.
Two rules throughout. Keep it in writing, in one thread, so the sequence of what was asked and when is intact. And separate the payment conversation from the work conversation — do not use a status update to chase money, because it muddles both and makes the delivery thread harder to rely on later.
Stopping work, and record-keeping that makes March boring
At some point continuing to work is a decision to extend more credit to someone who has not honoured the last of it. Say so in one paragraph, and do it before resentment does it for you: “I have paused work on the current milestone as of today, since invoice 0042 remains unpaid beyond our agreed terms. Everything completed so far is on the staging link. I am glad to pick it straight back up once the account is settled — just let me know.” That is firm, it is not a threat, and it leaves the door open, which is what you want because most of these do get paid.
Then the habit that makes all of this easy. Keep every invoice you issue in one folder, in numerical order, with the bank credit or platform release that settled it noted against it. Reconcile monthly rather than annually — an hour a month, matching what you invoiced against what actually arrived, catches short payments, deducted transfer charges and the invoice that was never sent while you can still do something about it. Keep the scope of work alongside it too, because an invoice whose description points at an agreed deliverable is one nobody queries; the checklist for that document is in the freelance contract and scope of work checklist.
How long you must retain records, in what form, and what your registration status requires of your invoice format are all prescribed, and all subject to change. Get your invoice template, your numbering series and your terms reviewed by a qualified chartered accountant once, before you have issued two hundred invoices in a format that turns out to be wrong. It is an hour of fees against a problem that is expensive to fix retrospectively, and nothing in this article is a substitute for it.
The takeaway: know which document you are sending, because a proforma is not an invoice and the confusion costs you a week. Put both registered entities, a unique consecutive number, a description tied to the deliverable, the currency, the tax treatment if you are registered, and an actual due date on every one. Agree terms in the scope of work, never first on the invoice. Where you can, work through funded milestones so the commitment is agreed, itemised and dated before you start. Chase in three calm steps, reconcile monthly, and have a CA confirm your format and terms once.