Fixing a Wrongly Recorded Payment Without Deleting Anything

Mistakes happen — a payment of ₹2,000 gets typed as ₹20,000, or recorded against the wrong invoice entirely. The instinct is to delete the wrong entry and move on. That instinct, followed literally, is exactly how books quietly stop matching reality.

Why deleting is the wrong fix

The moment a payment record is deleted, every trace of what happened — when, how much, why it was wrong — disappears with it. If anyone (an accountant, an auditor, your future self reconciling months later) needs to understand why a party's balance changed on a given date, a deleted entry leaves a gap with no explanation. Worse, a payment already allocated across multiple invoices, once deleted, can leave those invoices' paid amounts quietly wrong with nothing pointing back to why.

The correct fix: reverse, don't erase

A reversal is a new, explicit entry that undoes the original — the invoice it was applied to goes back to its correct outstanding balance, the party's ledger reflects the correction with its own dated entry, and the original mistaken payment still exists in the record, clearly marked as reversed. Nothing is hidden; the mistake and its correction are both part of the permanent history.

What this actually protects against

• A genuine data-integrity check catching the mistake later stays meaningful — a system that cross-checks its own numbers can only do that reliably if history isn't silently rewritten.
• Re-allocating credit correctly — a reversed payment stops counting as available credit for future invoices, exactly as it should, without needing to manually track that it was "cancelled" separately.
• An honest audit trail — anyone reviewing the books later sees what actually happened, not a version of history with the mistake quietly removed.

This is exactly why Settle treats a payment correction as a reversal, not a delete — the same append-only principle behind how a party ledger is built in the first place.