Should a wrong transaction be deleted?

For a controlled reconciliation trail, the original transaction should normally remain visible and be corrected with a linked reversal or correction record.

Why do partial reversals need extra review?

Because only part of the original value movement may be reversed. Without a clear scope and reason, cash and platform balances can be corrected in the wrong direction.

Can a bad reversal create a shortage?

Yes. An incorrect reversal can change expected balances without changing the real-world cash or platform position.

Operational case file

Case File: A Reversal Fixed the Number but Destroyed the Evidence

The final balance changed, but nobody could reconstruct what the original transaction was or why it was corrected.

Field-derived caseAudit-trail riskReversal integrity

Evidence basisReversal handling became an explicit owner-control area during testing. The operating rule that emerged was simple: original transactions stay; corrections are linked.

Why deleting an error is dangerous

A deleted transaction can make today's numbers look cleaner while making tomorrow's investigation impossible. Once the original row disappears, the owner loses the original reference, staff member, time, service, amount and context that explain the correction.

A reversal is a new control event

The correct question is not “How do I erase the mistake?” It is “How do I show what happened, what was reversed, by whom, why, and whether the reversal was full or partial?”

Control pattern

Preserve → link → explain → approve

Keep the original transaction intact. Create a linked reversal/correction record. Reference the original transaction. State the amount and scope. Record the reason. For split or partial reversals, require an owner note because only one side or one portion of the original movement may be corrected.

How a bad reversal hides shortages

If a cash-out is deleted instead of reversed, expected cash may jump back up while the customer was actually paid. If a reversal is applied to both cash and platform when only one side needed correction, both balances can become wrong. Either failure can look like theft even when the root cause is a broken correction trail.

Control lesson

Do not delete original transactions.
Use linked reversal records.
Capture original reference, reason, amount and scope.
Require owner/manager approval for sensitive or split reversals.
Reconcile the corrected expected balance against actual cash/platform evidence.

The site publishes the audit-trail principle while keeping product permissions, reversal automation and backend design private.