Q.What do you mean by 'errors' in Book-Keeping and Accountancy? Why must an error always be corrected through a proper rectifying entry, rather than by simply overwriting or scoring out the original wrong entry?
An error, in Book-Keeping and Accountancy, is any unintentional mistake committed while journalising a transaction, posting it to the ledger, casting (totalling) a subsidiary book or an account, or balancing an account. The word 'unintentional' matters: a deliberate manipulation of the books for personal gain is fraud, a wholly different matter, even though an undetected genuine error can occasionally end up concealing one.
An error must always be corrected through a proper rectifying entry — a fresh journal entry (or, before the Trial Balance stage, a direct posting) passed specifically to correct the mistake — and never by erasing, overwriting, or scoring out the original wrong figure, for two connected reasons:
- It preserves the audit trail. Every entry that has ever been made in the books should remain visible exactly as it was made; erasing it would make it impossible for anyone — the trader, a partner, or an auditor — to later verify what was originally recorded, what turned out to be wrong, and how and when it was corrected.
- It keeps every earlier total genuinely traceable. Ledger balances, subsidiary book totals, and the Trial Balance itself are all built up by adding entries as they occur; overwriting a figure after other totals have already been struck on top of it would silently break the arithmetic of everything already calculated, whereas a fresh rectifying entry corrects the position going forward without disturbing anything already recorded.
An error is any unintentional mistake in journalising, posting, casting, or balancing a transaction. It is always corrected by passing a fresh rectifying entry, never by overwriting or scoring out the original wrong entry, because doing so would destroy the audit trail and silently corrupt totals already struck on the earlier (wrong) figure.
Unlock everything free for 14 days
- Full step-by-step solutions
- Concept-first explanations
- Methods, shortcuts & mistakes
- PYQ mapping + timed mock tests
Full access for 14 days. No credit card required.