Title: Correct your books with reversals, not edits: a practical method

Updated for FY 2026-27 (AY 2027-28).

Posted entries are evidence, not drafts: how to correct books with reversals instead of edits

Most small-business books in India are corrected the wrong way: someone opens a posted journal entry from three months ago, changes the amount or the ledger, and saves. The trial balance balances again, so it feels fixed. What has actually happened is that the signed accounts, the filed GSTR-3B and the TDS return now disagree with the ledger, and nobody can explain why.

What changes when an entry is posted

A draft entry is a working paper. A posted entry is a statement of fact tied to a date, a document number, and usually to something outside your books: a GST return, a TDS challan, a bank statement line, a balance sheet a bank has already seen.

Once you have used an entry for any of those, editing it breaks three things at once.

• Reconciliation. Your bank reconciliation for July was signed off against a ledger that no longer exists in that form.
• Returns. GSTR-1 for the month was filed from figures you have since changed. The return does not change when your ledger does.
• Explainability. Six months later, nobody — including you — can say whether the ₹2,36,000 in the ledger was always ₹2,36,000 or was once ₹2,63,000.

The test is simple. Ask: has anything left this system based on this entry? If a customer has the invoice, if a return has been filed, if the month has been reported to a lender or a partner, the entry is posted in the real sense and must be corrected by a new entry, not by overwriting the old one.

Reverse, void or adjust: picking the right tool

Three corrections, three different situations. Mixing them up is where most messy ledgers begin.

Void (or cancel). The transaction should never have existed. A duplicate invoice, a bill entered twice from the same PDF, a payment voucher raised for a supplier you never paid. A void keeps the document number alive and marked cancelled, so the numbering series stays unbroken, and reduces the amounts to nil.

Reversal. The transaction existed but is wrong in a way you cannot patch — wrong party, wrong GST treatment, wrong period. You post a mirror-image entry, usually dated in the period where you discovered the error (or the same date, if the period is still open), and then post the correct entry fresh.

Adjusting entry. The transaction is mostly right and only one leg needs moving — ₹18,000 sitting in Repairs that belongs in Capital work in progress, or an expense accrued at the wrong amount. One clean entry moving the difference, with a narration explaining it.

A rough rule: if the error changes the taxable value, the party, or the tax head, reverse the whole thing. If it only changes which expense bucket a cost sits in, an adjusting entry is enough.

Worked example: a ₹2,36,000 invoice booked against the wrong customer

On 8 July you raised invoice INV-0412 for consultancy of ₹2,00,000 plus 18% GST and posted it against Patel Traders. The work was actually for Nair Logistics. GSTR-1 for July has already been filed on the 11th of August.

Original posted entry, 8 July:

Do not touch it. Post a reversal on the date of discovery, say 22 August, referencing the original:

Narration: Reversal of INV-0412 dated 08-07-2026, raised on wrong party. Credit note CN-0007 issued to Patel Traders. Approved by DK.

Then post the correct invoice to Nair Logistics with a new document number, and amend the B2B detail in the next GSTR-1 (or issue a credit note and a fresh invoice, as your CA advises for the specific case). You now have three documents telling one story. Anyone reading the Patel Traders ledger sees a debit, a credit, and a reason.

Had you simply edited INV-0412 to say "Nair Logistics", your filed GSTR-1 would show Patel Traders' GSTIN against an invoice that your books say was never theirs — and Patel Traders would see ₹36,000 of input credit in their GSTR-2B for a supply they never received.

Worked example: the ₹60,000 receipt that was quietly deleted

A consultant files under section 44ADA. Gross receipts for FY 2026-27 are ₹24,60,000, all through bank. Presumptive income at 50% is ₹12,30,000.

In October, a ₹60,000 receipt was posted twice. Instead of voiding the duplicate, someone opened one of the posted entries and deleted it — and deleted the wrong one, the genuine receipt. Books now show receipts of ₹24,00,000, presumptive income ₹12,00,000, and under the new regime that is nil tax, because the section 87A rebate makes tax nil up to ₹12 lakh of total income. Comfortable. No advance tax paid by 15 March.

In June, bank reconciliation picks up the missing ₹60,000. Real total income is ₹12,30,000. Tax under the new regime:

• Up to ₹4,00,000: nil
• ₹4–8 lakh at 5%: ₹20,000
• ₹8–12 lakh at 10%: ₹40,000
• ₹12,00,000 to ₹12,30,000 at 15%: ₹4,500
• Total before relief: ₹64,500

Marginal relief caps the tax at the income above ₹12,00,000, i.e. ₹30,000, plus 4% cess — ₹31,200. Not ruinous on its own. But a 44ADA assessee must pay 100% of advance tax by 15 March, and nothing was paid, so interest under sections 234B and 234C sits on top, and the ITR has to be filed against a ledger that shows a deletion with no explanation.

If the duplicate had been voided instead of deleted, the ledger would have read: receipt ₹60,000 posted twice, one voided on 12 October with a narration. Receipts stay at ₹24,60,000, advance tax of roughly ₹31,200 goes out by 15 March, and there is nothing to explain.

Keep GST and TDS in step with the correction

A reversal in your books does not fix a filed return by itself. Two habits to build.

GST. Once GSTR-1 is filed on the 11th and GSTR-3B on the 20th, a sales correction is a credit note or a return amendment, not a ledger edit. Post the credit note in the books, give it its own number, and carry it into the next period's return. On the purchase side, do not force an input credit into your books to match a supplier's invoice if it is not in your GSTR-2B — park it in an "ITC not yet in 2B" ledger and clear it when it appears.

TDS. Thresholds are per-deductee and cumulative, so edits move the deduction date. A professional bill of ₹45,000 is below the ₹50,000 threshold for section 194J. If a second bill of ₹25,000 arrives, you post a new bill and deduct 10% on the full ₹70,000 — you do not edit the first bill to ₹70,000, because the deduction and the challan belong to the month the second bill was booked. The same applies to section 194C (1%/2% above ₹30,000 single or ₹1,00,000 aggregate), section 194H commission (2% above ₹20,000) and section 194I rent (10% above ₹6,00,000 a year). Your 24Q/26Q returns are built from deduction dates, and editing history quietly misstates them.

Narration, numbering and period locks

Three low-effort habits make reversals readable a year later.

1. Write a narration a stranger can follow. Four elements: what is being reversed (document number and date), why, what replaces it, and who approved it. "Rectification entry" is not a narration.
2. Never reuse or renumber documents. Voided invoice INV-0412 stays INV-0412, marked cancelled. The replacement gets the next number in the series. Gaps in a numbering series are a red flag to any auditor; cancelled documents in the series are not.
3. Lock the period. Close each month after the GSTR-3B is filed and the bank is reconciled, and close the year once accounts are finalised. After that, corrections flow only as dated entries in an open period. For companies there is also an audit-trail expectation on accounting software — ask your CA how it applies to your entity, but the operating habit is the same for everyone.

One more: keep the supporting document with the reversal. The supplier's credit note, the e-mail confirming the wrong party, the bank statement page. A reversal without evidence is just a second opinion.

Doing this in FlipAccounts

FlipAccounts is double-entry, so posted vouchers are corrected by voiding or reversing them rather than being rewritten — open the invoice, bill or journal and use the void or reverse action, and the original stays visible with its document number intact. The tamper-evident audit log records who posted, voided or reversed what and when, and a read-only auditor role lets your CA inspect the trail without being able to change anything. The GSTR-1 and GSTR-3B summaries, and the TDS summaries, are built from the posted ledger, so a reversal flows through to the next period's figures instead of silently changing a month you have already reported. Bank statement reconciliation is where most of these errors surface first, and the statements pack (P&L, balance sheet, trial balance, general ledger) is what you hand over once the corrections are in.

What to do this week

1. Pull the general ledger for the last completed quarter and look for entries with no narration or a narration shorter than five words. Those are the ones you will not be able to explain later; add the explanation now while you still remember.
2. Agree a one-line house rule with whoever posts entries: after the GSTR-3B for a month is filed, nothing in that month gets edited — only reversals dated in the current month.
3. Reconcile your bank for the current financial year to date. Duplicate and deleted receipts show up there before they show up anywhere else, and before advance tax dates make them expensive.

Frequently asked questions

Can I edit an entry if the month's GST return has not been filed yet?

Usually yes, and that is the point of keeping the period open. If nothing has left your books — no return filed, no invoice sent to the customer, no statement given to a lender — correcting a draft or recently posted entry is housekeeping. The moment any of those has happened, switch to reversals.

Does a void leave a gap in my invoice numbering?

No, if you do it properly. The voided document keeps its number and is marked cancelled, and the next invoice takes the next number. Deleting the entry outright is what creates a gap, and a gap is the thing an auditor will ask about.

My accounting software lets me delete posted entries. Should I disable that?

Restrict it to one person and make the default workflow void-and-repost for everyone else. The ability to delete is not the problem; the absence of a record of who deleted what is. Use a read-only role for anyone who only needs to look, and keep an audit log you cannot edit.

What if the error is from a prior financial year that is already filed?

Do not touch the prior year. Post the correction in the current year with a clear narration referencing the original entry and the year it belongs to, and speak to your CA about whether a revised return, a credit note or a prior-period adjustment disclosure is needed. The books and the return have to be reconciled in writing, not patched quietly.

More guides