The golden rule — never edit, never delete
A posted tax invoice is not a draft — it is a numbered tax document that exists in at least two places: your system and your customer's hands, and often a third, your GST return. Edit it in place and those copies disagree forever. Delete it and the invoice series has a hole that every auditor and GST officer is trained to probe. Both "fixes" convert a small mistake into a credibility problem.
So the golden rule of billing corrections: the original document is immutable; corrections are new documents. A wrong invoice is either formally cancelled — it stays in the register, marked cancelled, its number intact — or adjusted by a credit or debit note that references it. Either way, the paper trail reads forward: anyone reconstructing events sees the original, the correction, and the link between them. This principle is the backbone of everything else in this guide, and its violation is mistake number seven in our ten costly invoicing mistakes.
Cancel vs credit note — which, when
The two correction instruments do different jobs, and choosing correctly keeps both the ledger and the GST position clean:
| Situation | Instrument | Why |
|---|---|---|
| Wrong party, duplicate, wrong dispatch — caught early | Cancel | The invoice should never have existed; cancellation removes its effect and releases the dispatch for re-billing |
| Sales return — goods came back | Credit note | The sale was real; the return reduces its value — recorded against the original invoice |
| Short supply, agreed rate reduction | Credit note | Value adjustment on a genuine invoice |
| Under-charge, rate difference in your favour | Debit note | Value increase on a genuine invoice |
| Error found after the period's return is filed | Usually a note | The invoice has entered the return cycle; adjust it rather than remove it — confirm treatment with your CA |
The rule of thumb: cancellation erases a mistake; a credit note records a change. Timing matters — an invoice that has been reported (in a filed return, or under e-invoice rules where IRN cancellation has its own tight windows) generally needs a note rather than a cancellation. These windows and rules change; settle the current treatment for your cases with your CA. The note mechanics themselves — including the automatic credit note on a sales return — are covered on the Credit & Debit Notes feature page.
What a clean cancellation does under the hood
Here is the part most billing tools get wrong, and the reason cancellation deserves its own machinery. In a dispatch-linked billing system, every invoice line is raised against a dispatch, and the system tracks the already-invoiced quantity per dispatch line — that is the guard that prevents the same goods being billed twice (explained in the pillar guide). A posted invoice therefore consumes dispatched quantity.
A clean cancellation must do two things atomically: move the invoice to a formal cancelled state, and release exactly the quantity it had consumed — so the dispatch becomes billable again, once. Skip the release and you get one of two failure modes: dispatched goods that can never be invoiced (revenue stuck behind a dead document), or a manual workaround that bills them again outside the guard (the double-billing the guard existed to prevent). In Fast Billing this is the CancelInvoice mechanism: the invoice becomes a cancelled document, its used-quantity is released against the source dispatch, and the re-bill proceeds under the same guard as any other invoice.
Series discipline — why unbroken numbering matters
Invoice numbers should be system-generated, sequential and unbroken within each series — domestic invoices, export invoices, credit notes and debit notes each running their own sequence. The reason is evidentiary: an unbroken series proves completeness. If the register shows 0001 through 0450 with every number present — live or formally cancelled — then the register is the whole story. A gap, by contrast, proves nothing and implies anything, which is why gaps attract questions. Cancelled invoices are the series' friend: they are how a number stays accounted for even when the document it names was a mistake. Manual numbering, "adjusted" sequences and deleted documents are how billing records stop being evidence.
Want to see a cancellation release quantity, live?
In a 30-minute Fast Billing Software demo we will raise an invoice against a dispatch, cancel it, watch the quantity release, and re-bill it correctly — with the trail recording every step.
The audit trail — who did what, when
An audit trail is the system's memory of every write: document created, value changed, invoice cancelled, bill approved — each stamped with the user and the time. Nobody reads it daily; that is not its job. Its job is to make questions answerable after the fact: who cancelled invoice 0417 and when? Which user changed this party's rate? Was this supplier bill approved before or after payment?
In India this has moved from good practice to expectation: MCA rules require companies' accounting software to maintain an audit trail (edit log) of every transaction. Whether and how the requirement applies to your entity is a question for your CA — but the direction is unambiguous, and a billing system without write-level logging is on the wrong side of it. In Fast Billing, the audit layer captures every write to every document as a matter of architecture, not configuration — there is no "log off" switch for an operator to find.
Role-based access — separating the powers
Controls fail quietly when one login can do everything. Role-based access splits the billing chain into permissions that different people hold: raising invoices, cancelling invoices, approving supplier bills and expenses, configuring tax rates and account heads, and viewing reports. The separations that matter most in a small team:
- The person who bills is not the person who approves outgoing money. Invoicing and supplier-bill/expense approval sit with different users.
- Cancellation is a restricted permission. Anyone can raise a draft; few can void a posted document. This makes the cancellation trail short and meaningful.
- Masters are guarded. Tax configuration, HSN mapping and account heads change rarely and deliberately — not from the billing desk on a busy afternoon.
Even a five-person office can run this: it costs nothing but role assignment, and it means no single person can create, approve and erase the same transaction. In Fast Billing, the menu each user sees is driven by their role — the permissions are the navigation.
Approval gates on the money going out
Internal control is symmetrical: the same rigour that guards revenue (against-dispatch invoicing, the used-quantity guard) must guard spending. Two gates do the work — supplier bills are matched to their purchase orders and receipts, then approved before posting as purchase vouchers; expenses are entered under mapped types, then approved before touching the accounts. Both run maker-checker: the recorder is never the approver. The full setup, including budgets checked at approval time, is covered in expense tracking and approval, with the machinery on the Accounts, Vouchers & Expenses page.
The month-end control check — fifteen minutes
A short monthly ritual keeps the controls honest. Five checks, most of them one report each:
- Series check: the invoice register runs unbroken, and every cancelled number has a reason someone can state.
- Cancellation review: list the month's cancellations — who, why, and was each re-billed or genuinely dropped. A rising cancellation rate is a process smell.
- Note linkage: every credit and debit note references an invoice; none float free.
- Pending approvals: the supplier-bill and expense queues are current — nothing aged past the agreed approval window.
- Books agreement: billing totals reconcile with what posted to Tally — invoices to sales vouchers, receipts to receipt vouchers, notes to Cr/Dr notes.
These are the same views described in the essential billing reports — read once a month with a controls eye instead of an operations eye.
One wrong invoice, two very different endings
A billing operator raises an invoice against the wrong dealer's dispatch — same item, similar quantity, caught the next morning. In a template world: the file is edited, the printed copy in circulation now disagrees with the record, and three months later the real dealer's dispatch is billed by hand — twice, because nothing tracked what was already invoiced. In a controlled system: the invoice is cancelled with a stated reason, the dispatch quantity releases automatically, the correct invoice is raised under the same guard, and the register shows the whole episode — original cancelled, replacement live, trail complete. Same mistake; one version is an anecdote, the other becomes an audit finding.
How Fast Billing Software builds this in
Fast Billing Software treats controls as architecture rather than settings:
Frequently asked questions
Can I delete a GST invoice?
No — a posted tax invoice should never be deleted or edited in place. Deleting leaves a series gap that auditors and GST officers probe; editing makes the system disagree with the customer's printed copy. Either cancel it formally — it stays in the register, marked cancelled, number intact — or adjust it with a credit or debit note that references it. Which path applies can depend on filing status; confirm with your CA.
When should I cancel an invoice versus raise a credit note?
Cancel when the invoice should not exist at all — wrong party, duplicate, wrong dispatch — and it is caught early, typically before the period's return is filed. Raise a credit note when the invoice is genuine but its value must come down — a return, short supply, a rate reduction — or when it has already entered the return cycle. Cancellation erases a mistake; a credit note records a change. Timing rules change; confirm the current position with your CA.
What happens to the dispatched quantity when an invoice is cancelled?
A clean cancellation releases it. Because invoices are raised against dispatches and the system tracks the already-invoiced quantity per line, a posted invoice consumes dispatch quantity. Cancellation moves the invoice to a cancelled state and releases exactly what it had consumed, so the dispatch can be re-billed correctly, once — under the same guard that prevents double billing. Without the release, goods either become unbillable or get billed twice outside the guard.
What is an audit trail in billing software?
An automatic record of every write — who created, changed, cancelled or approved which document, and when. It answers questions after the fact: who cancelled this invoice, when did this rate change. MCA rules require companies' accounting software to maintain such an edit log, so it is a compliance expectation, not a luxury — confirm your specific obligations with your CA.
What internal controls should billing software have?
Six essentials: immutable posted invoices with corrections via cancellation or notes; an against-dispatch link with a used-quantity guard so nothing is billed twice and cancellations release quantity; an unbroken system-generated number series per document type; role-based access separating billing, approval and configuration; approval gates on supplier bills and expenses; and a write-level audit trail. Together they make the billing record evidence rather than something to reconstruct.