Correct the record without destroying its history
A registered person should not erase, efface or overwrite entries in GST registers, accounts and documents. Rule 56(8) requires incorrect non-clerical entries to be scored out under attestation and the correct entry recorded; electronic records require a log of every entry edited or deleted. The result should explain both what is now correct and what changed. This guide addresses correction evidence checked on 26 October 2026, rather than return-amendment eligibility or a tax-computation method. ICAI April 2026 GST bare-law compilation: CGST Rules 56(8), 56(9), 56(16) and 57.
Read the clerical wording narrowly
The rule distinguishes incorrect entries otherwise than those of a clerical nature in its scoring-out requirement. That wording is not a general permission to erase or overwrite source records. Where the distinction matters, document why the correction is clerical and retain a traceable record of it. For a substantive manual correction, preserve the original readable amount, identify the correction and obtain the required attestation. Rule 56(9) separately requires serial numbering of each manually maintained volume.
Design the electronic log around changes, not just final balances
The legal requirement concerns every edited or deleted entry. A month-end export showing only the latest amount cannot establish the intermediate versions. As practical control fields, retain the record identifier, original and revised values, operation type, user, time and reason, linked to supporting evidence and approval where the taxpayer’s policy requires it. These fields are an implementation recommendation, not a prescribed statutory log form or a claim that the rule names a particular software product.
Reconcile edits, reversals and reallocations differently
An amount correction changes a balance; removal of a duplicate changes both population and value; reassignment to the correct customer can leave the overall total unchanged. Test each accordingly. Reconcile original balance plus supported adjustment movements to the corrected balance. Also check document identifiers, customer or supplier, tax period and registration. An equal grand total can conceal an incorrect account or period. Preserve sequential changes even when their net amount is zero.
Keep source documents and returns under their own rules
Changing an accounting row does not automatically amend an issued tax invoice, credit note, e-invoice, filed return or electronic credit ledger. Identify each affected document and apply its own legal correction procedure and time limits. A deletion log records an event; it does not authorise destruction of required records. Read Rule 56(8) with preservation and access under subrule (16), and electronic production under Rule 57. See the CBIC rule text, cross-checked with the 2026 ICAI consolidation.
Review exception patterns at closing
Look for unexplained bulk edits, missing record identifiers, edits after a period was closed, deleted supporting documents and corrections made under shared user credentials. Sampling can help identify weaknesses, but it does not create a permitted percentage of missing statutory logs. Keep the correction population, explanations and residual exceptions together so the financial reconciliation can be reproduced. The examples below use bookkeeping amounts or quantities only; none calculates tax due or an entitlement to input credit.
Applicable primary references
ICAI April 2026 GST bare-law compilation: CGST Rules 56(8), 56(9), 56(16) and 57 CBIC official older consolidation: Rule 56 correction and serial-numbering text
Six worked illustrations
All facts and amounts below are fictional. Assumptions describe the model, not additional statutory rules.
Illustrative example 1: Correct an overstated manual entry
A register contains ₹54,000 but the supporting record establishes ₹45,000. The correction decreases the balance by ₹9,000. For this substantive correction, retain the readable original, score it out under attestation and record ₹45,000; simply replacing the written figure loses the evidence.
Illustrative example 2: Remove a duplicate accounting row
Three legitimate records are ₹20,000, ₹30,000 and ₹40,000. A duplicate ₹30,000 row makes the recorded total ₹1,20,000 across four rows. Correct population is three records totalling ₹90,000. Preserve the duplicate identifier and the ₹30,000 reversal or deletion history; the example is not permission to delete statutory source documents.
Illustrative example 3: Keep two edits even when the final figure returns to its starting point
An electronic entry moves from ₹80,000 to ₹95,000 and then back to ₹80,000. The two movements are plus ₹15,000 and minus ₹15,000; net movement is ₹0. Both edits need to remain traceable. A comparison of only the opening and closing values would miss them.
Illustrative example 4: Fix the customer without changing the grand total
A supported ₹70,000 receivable belongs to Customer B but was posted to Customer A. Reducing A by ₹70,000 and increasing B by ₹70,000 gives net overall change ₹0. Reconcile both customer accounts and retain the reallocation trail; a grand-total check alone cannot prove the correction.
Illustrative example 5: Repair a quantity error independently of the amount
A goods register shows 250 units while the supporting document establishes 205 units, with the monetary amount already correct. Quantity adjustment is minus 45 units. A monetary reconciliation with ₹0 difference does not resolve that 45-unit error or establish the correct physical stock.
Illustrative example 6: Reconcile a batch of supported corrections
The original accounting total is ₹5,00,000. Supported adjustments are plus ₹12,000, minus ₹7,000 and minus ₹5,000. Net adjustment is ₹0 and the final total remains ₹5,00,000, but the absolute adjustment movements total ₹24,000. Review all three events rather than treating the unchanged total as evidence of no changes.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Identify the affected records | Registration, period, register and source-document identifiers. |
| 2 | Establish the correct facts | Original invoice, contract, receipt or other supported evidence. |
| 3 | Classify the correction | Amount, quantity, duplicate, counterparty, period or other change. |
| 4 | Preserve manual originals | Readable prior entry and required scoring-out and attestation. |
| 5 | Check manual volumes | Serial numbering under Rule 56(9). |
| 6 | Extract electronic change events | All relevant edits and deletions, including intermediate versions. |
| 7 | Link changes to reasons | Record IDs, supporting evidence and recommended user/time fields. |
| 8 | Reconcile value and population | Before/after bridge, quantities and affected subledgers. |
| 9 | Review separate legal corrections | Invoice, return, e-invoice and credit implications assessed independently. |
| 10 | Retain the completed trail | Correction evidence, accessible records and unresolved-exception ownership. |
Sixteen practitioner FAQs
1. Does a correct closing total prove Rule 56(8) compliance?
No. It does not show the original entry or the history of edits and deletions.
2. Can a substantive manual error be rubbed out?
The rule prohibits erasure, effacement and overwriting; use the required correction trail.
3. What does attestation relate to?
The rule requires incorrect non-clerical entries to be scored out under attestation before the correct entry is recorded.
4. Does the clerical wording permit all erasures?
No. Do not turn that distinction into a general exemption from the prohibition.
5. What must electronic records retain?
A log of every edited or deleted entry.
6. Are user and time fields quoted statutory columns?
No. They are recommended evidence fields for a useful, attributable change log.
7. Is a daily balance snapshot enough?
It may support reconciliation but can omit intermediate edits and deletions.
8. What if two edits cancel each other?
Retain both events even where their net monetary effect is zero.
9. Does a logged deletion become legally authorised?
No. Logging an event does not override preservation duties.
10. Can a bookkeeping edit amend an issued invoice?
No automatic legal amendment follows; test the relevant invoice procedure independently.
11. Can a ledger correction alone change a filed return?
No. Apply the applicable return-correction framework and restrictions separately.
12. Why test quantities when rupee totals agree?
An incorrect quantity can survive an otherwise correct monetary total.
13. Why check counterparty allocations?
An amount can be moved between accounts without changing the grand total.
14. Are manually maintained volumes numbered?
Rule 56(9) requires each volume to be serially numbered.
15. Does this rule require a named ERP product?
No. Verify the actual implementation’s ability to retain the required trail.
16. Does a backup replace a correction log?
No. Recovery and production controls support preservation, while the log explains record changes.
Conclusion
Preserve the original GST accounting trail when correcting entries. Rule 56(8) requires electronic edit and deletion logs; a corrected total alone is insufficient.