The short answer
Document a reversed ledger entry with the immutable original identity, reason and authority, reversal identity, effective dates, external cash status, replacement entry if any, and every report or subledger requiring review. A reversal changes accounting records; it does not cancel a payment, message, or prior report by itself.
Operational checklist
Mark your progress, then save a working copy. Selections reset when you leave this page. A checked box is not an approval or evidence of completion.
0 of 7 marked
Key takeaways
Build one chain, not a replacement snapshot
Record the original entry ID, account, property/entity, amount, posting and effective dates, source record, preparer, approval, reason for correction, reversal ID, and any replacement entry. Use the system’s governed correction process; this article does not prescribe journal entries.
Add the payment, invoice, deposit, owner statement, tenant ledger, bank reconciliation, and reporting references that consumed the original. The packet should let a reviewer distinguish a record error from a real cash event.
Classify what the reversal did and did not change
Treat each downstream surface independently. A clean general-ledger balance can coexist with a wrong tenant allocation, an already-sent owner statement, or an external payment still in flight.
| Surface | Question | Evidence of resolution |
|---|---|---|
| General ledger | Do original plus reversal net as intended? | Linked entries and account proof |
| Subledger | Was the property/tenant/owner balance rebuilt correctly? | Before/after detail and reviewer |
| Bank/provider | Did external cash move? | Settlement, return, cancellation, or explicit absence |
| Reports | Which released outputs included the original? | Correction/disclosure decision and versions |
| Automation | Could the corrected source trigger another action? | Idempotency or suppression check |
Close the packet only after downstream review
The closeout names the final accounting state, final external cash state, affected outputs, communications where applicable, open residuals, and reviewer. Do not call a replacement entry “correct” solely because the net total returns to zero; confirm property, party, period, and source lineage.
If the same cause can recur—mapping defect, duplicate event, manual template, or role permission—link a prevention action with its own owner and test evidence.
Edge cases
Sources and references
Follow each source to check the underlying claim. Access checks and professional review are different steps.