# REGISTER111: Cash movement reversal refused

## What this means[​](#what-this-means "Collegamento diretto a What this means")

You reversed a paid in or paid out — with **Undo** on the confirmation, or **Void** in the register panel — and your store refused the reversal.

The till shows the movement as reversed. Your store still counts it.

## Your data[​](#your-data "Collegamento diretto a Your data")

Nothing is lost. The original movement is intact in your store and the reversal exists only on this device, so the two disagree about the expected drawer total by the amount of that movement.

## Troubleshoot[​](#troubleshoot "Collegamento diretto a Troubleshoot")

1. Open the register panel's paid in / out list. The movement the reversal was aimed at is the one your store still counts.
2. A movement can only be reversed once, and only while its session is open. Once counting starts, your store refuses reversals by design — that is what keeps a counted shift from changing underneath the count.
3. If the reversal was a mistake, nothing needs doing: your store never applied it.
4. **Do not record an opposite movement to compensate.** A new movement reaches your store *and* this till, so it moves both totals by the same amount and the gap between them stays exactly where it was. Your store's figure is the correct one.
5. Expect the till's expected-cash figure to read wrong by that amount until the register is counted. Note the difference on the count so the variance is explained rather than unexplained.

## Details[​](#details "Collegamento diretto a Details")

* Codice

  `REGISTER111` (`CASH_MOVEMENT_VOID_REFUSED`)

* Gravità

  warn

* Introdotto in

  WCPOS

  <!-- -->

  2.0.0