# Handle a cash variance

TajerGo classifies the difference against the branch threshold and requests explanation or manager authorization when required. Review expected and actual cash, read the variance classification, and enter a clear reason. Count and document cash carefully; verify the shift and movement record before retrying a drawer action.

Canonical URL: https://admin.tajergo.ae/help/articles/pos/variance-approval/
Article ID: pos-variance-approval
Surface: POS
Category: Shifts and cash
Last reviewed: 2026-09-06

## Before you start

- An authenticated POS session on the intended branch and terminal.
- The current shift ID and drawer state are known before recording cash or closing the shift.

## Steps

1. Review expected and actual cash.
2. Read the variance classification.
3. Enter a clear reason.
4. Complete manager authorization when prompted.
5. Submit the shift close.

## Expected result

The approved or rejected variance decision, reason, approver, and shift remain traceable together. Count the drawer and review shift history before entering another movement or attempting closure again.

## Permissions

- The staff member needs shift access for the active branch; variance approval, no-sale, cash movement, safe drop, and closure may require a manager capability.

## Troubleshooting

### Staff cannot review expected and actual cash because the control is missing, disabled, or rejected before they read the variance classification.

First confirm the following access and record state: An authenticated POS session on the intended branch and terminal. The current shift ID and drawer state are known before recording cash or closing the shift. Check those conditions on /shifts and repeat only the blocked step once. Preserve the screen and ask Support to review the shift ID, terminal ID, movement, amount, branch, status, and time; omit drawer keys and credentials. Keep evidence of the result when staff review expected and actual cash.

### The shift, cash movement, variance, approval, queue, or closure history is inconclusive after the final checkpoint: Submit the shift close.

Compare the active shift, movement ledger, counted and expected cash, variance, approval, and closure state. Do not repeat a movement or shift transition while it is pending or queued. Retry only when history proves it absent. When no single result can be proved, pause and provide Support the shift ID, terminal ID, movement, amount, branch, status, and time; omit drawer keys and credentials. Before another attempt, establish whether staff could submit the shift close.

## Related articles

- [Open a shift](https://admin.tajergo.ae/help/articles/pos/open-shift.md)
- [Close a shift](https://admin.tajergo.ae/help/articles/pos/close-shift.md)
- [Record cash in](https://admin.tajergo.ae/help/articles/pos/cash-in.md)
- [Record cash out](https://admin.tajergo.ae/help/articles/pos/cash-out.md)