# End-of-Day Reconciliation

This page walks a cashier (or manager) through a day on the register: opening it with a float, recording cash in and out, counting the drawer and closing. For the Reports screen reference itself, see [Reports](/reports.md).

Free and Pro

Opening, counting and closing the register, and the numbered closing report, are in the free plugin. The free plugin's Reports screen covers today on its register; [WCPOS Pro](/getting-started/pro-license.md) adds earlier days, every register and every store, including the closures history.

If you don't use a cash drawer, register sessions can be switched off in POS settings and none of this applies. While they are on, a sale cannot be completed until the register is open: the POS shows *Open the register before completing the sale*.

## Before your first close[​](#before-your-first-close "Direct link to Before your first close")

Decide once, then stick to it across shifts:

* **Opening float amount.** A typical retail till starts the day with $100–$200 in small denominations for change. Set it as the register's **Opening float** (on the free plugin under [General › Register](/settings/wp-admin/registers.md); with Pro, per register) and it pre-fills every opening. Left blank, the opening pre-fills with the cash counted at the last close.
* **Variance threshold.** If you set one, a count that is out by more than the threshold needs a manager's approval before the register closes. With Pro it is a store setting, in the store editor's **Register** section.
* **Who counts and who approves.** A cashier who holds the *view reports* capability sees the expected cash while counting. A cashier without it counts **blind**: no expected figure, no variance. Approving an over-threshold count needs a manager account that is not the cashier closing the register. See [Access](/settings/wp-admin/access.md).
* **One drawer, one register.** Several devices on one counter share the register and its session, so the drawer is counted once. A second physical drawer is a second register (Pro). See [Stores, Registers and Devices](/stores/registers-and-devices.md).

## Opening the till[​](#opening-the-till "Direct link to Opening the till")

At the start of the shift:

1. Take the float out of the safe and put it in the drawer.
2. Sign in to WCPOS at the right store (multi-store sites). If the store has more than one register, pick the register for this drawer the first time this device is used.
3. The cart shows **Open register**, with the *Cash in the drawer* amount pre-filled. Count the float, correct the amount if it differs (a line shows the opening variance), and tap **Open register**.

That's it. Every sale, paid in and paid out is now recorded against this register's session. If another device already opened the register, this device joins that session instead, with its float and cashier (see [REGISTER221](/error-codes/REGISTER221.md)).

## During the shift[​](#during-the-shift "Direct link to During the shift")

Tap your avatar in the bar, then **In the drawer**, to open the **register panel**: the expected cash, the cash and card figures, paid in and out, **Print X-report**, the last closure, and **Close register**.

* **Record cash that moves without a sale.** Use **Paid in** and **Paid out** in the register panel, with an amount and a reason, for cash drops to the safe and cash paid out of the till. A **no sale** is recorded with no amount. A movement recorded by mistake can be voided from the panel while the register is open.
* **Use coupons or line-item discounts consistently.** Both work for ad-hoc adjustments; see [Discounts](/pos/cart/discounts.md) for how each is recorded.
* **Park orders rather than abandoning them.** A "POS - Open" order (saved with **Save to Server**) shows up clearly in Orders; an abandoned cart leaves no trail. Resume parked orders later when the customer returns.
* **Check the drawer mid-shift with an X-report.** **Print X-report** prints the open session as it stands, without closing anything.

## The close procedure[​](#the-close-procedure "Direct link to The close procedure")

1

### Stop taking sales

Lock the front door (or pause the queue) so no new transactions land mid-count. Once counting starts the register is no longer open, so the till cannot complete a sale on it; if a customer arrives, tap **Back to selling**, ring them up, and count again.

2

### Count the drawer

In the register panel, tap **Close register**. Count every denomination and enter the total — this is your **counted cash**.

If you hold the *view reports* capability, the screen shows the **Expected** cash beside your count and whether the drawer is short, over or exact. Expected cash is worked out for you:

> **Expected cash = Opening float + Cash sales − Cash refunds + Paid in − Paid out**

Counting blind, you see neither figure; enter what you counted.

3

### Get approval if the count is over the threshold

If the variance is over the threshold, the POS asks for a manager's approval: the manager enters their own username and password on this device. The approver cannot be the cashier who is closing or the one who opened the register. If you count again after the approval, the manager approves again.

A blind count is not exempt: the cashier never sees the variance, but if it is over the threshold the store refuses the close and the POS asks for a manager's approval in the same way. See [REGISTER301](/error-codes/REGISTER301.md) if an approval is refused.

4

### Close and print

Tap **Close & print** (**Approve & close** when a manager signed). The count is filed as the register's next numbered closure, and a completion sheet opens: tap **Print closure** to print the closing report, then **Done**. The next opening starts a new session.

5

### Reconcile card

Now check card payments against your card terminal. Run a **batch total** on the terminal (the exact menu varies by terminal, usually under *Reports* or *End of Day*) and compare it with the card figure on the closing report.

* **Terminal batch total** vs **WCPOS card total** for the same session — they should match.
* If you use a manual batch-settling terminal, **settle the batch now**, before you go home. Integrated gateways like Stripe Terminal auto-settle. For Square configuration through Web Checkout, see [Web Checkout](/payment/gateways/web-checkout.md).

6

### Drop cash and sign off

* Put the **opening float for tomorrow** back in the drawer.
* The rest of the cash goes in the safe drop bag with the printed closing report.
* Update any external system you use (spreadsheet, accounting software).
* Close the WCPOS app and lock up.

The closure stays on file. The register panel reprints the last closure, the Reports screen's **Closures** view reprints any closure you can see, and **Export closures** under **Tools** in `WP Admin > POS > Settings` downloads every closure as CSV.

## Variance handling[​](#variance-handling "Direct link to Variance handling")

If counted cash doesn't match expected, work through these in order before closing:

1. **Recount the drawer.** Mistakes happen. Recount, especially the coins, and enter the new figure. After a close, a manager can recount a closure from the Reports screen's **Closures** view; the original figures stay on record beside the corrected ones.
2. **Check that every device has synced.** When several devices share the register, a sale or a paid in or out that has not yet reached your store from another device is missing from the expected figure. Bring every device online before you count.
3. **Check for parked/open orders.** Filter Orders to *POS - Open* status — a sale that was rung up but not paid will show here. Either complete it now or expect the variance.
4. **Paid in and paid out.** Confirm every cash drop and payout is recorded in the register panel. A movement your store refused is listed at the top of the panel with **Retry** (see [REGISTER101](/error-codes/REGISTER101.md)).
5. **Wrong change given.** The most common variance source. Small differences (under $5) are usually here; large differences need investigation.

The variance is recorded on the closure whether you find the cause or not. A trail of small documented variances is better than untracked discrepancies.

## Multi-cashier or multi-store scenarios[​](#multi-cashier-or-multi-store-scenarios "Direct link to Multi-cashier or multi-store scenarios")

Several cashiers worked the same till today

The register has one session however many cashiers sell on it, so the drawer is counted and closed once. The session records who opened it and the closure records who closed it, and each cashier can see their own figure under **Your sales today** in the user menu.

If you want a separate count per cashier, close the register at the handover and let the next cashier open it again with a float. Each close is its own numbered closure.

One cashier worked at multiple stores today

Each store has its own register, so each one is opened and closed on its own. Use **Switch store** in the user menu to move between stores. At the end of the day, close the register in each store.

With Pro, the Reports screen's scope menu switches between registers and stores, so you can review each store's closures from one device.

Each store has a different person closing

That's the normal pattern. Each closer counts and closes their own store's register. With Pro, a manager can review every register's closures the next morning in the Reports screen's **Closures** view, for every store they are authorized for.

A sale went through after I closed

A sale or refund that reaches your store after the closure was written is recorded as a late correction against that closure: the closure itself is never rewritten, and the correction sits beside it in the Closures view so the Z report and the settled figure can both be read. It is not moved into the next session.

## Best practices[​](#best-practices "Direct link to Best practices")

* **Close every day.** Skipping a day means tracking variance across two days, which is much harder.
* **Keep the printed closing report** even on quiet days. The closure is also on file in WCPOS and can be exported as CSV.
* **Don't share user accounts.** Each cashier on their own WordPress user means the closure names the right people.
* **Cross-check weekly against WooCommerce Analytics** (`WP Admin → WooCommerce → Analytics`) — same orders, different presentation. If the totals diverge it usually means a parked order was completed late or a refund was processed in WP Admin rather than the POS.
* **Keep the float consistent.** Set a default float on the register so every opening starts from the same figure.

## Related Documentation[​](#related-documentation "Direct link to Related Documentation")

* [Stores, Registers and Devices](/stores/registers-and-devices.md) — one register per drawer, shared by devices
* [Register](/settings/wp-admin/registers.md) — opening float and the close rules
* [Reports](/reports.md) — the screen reference
* [Orders](/orders.md) — order lookup, refunds, parked orders
* [Discounts](/pos/cart/discounts.md) — how discounts and coupons are recorded
* [Refunds](/orders/refunds.md) — issuing refunds during the shift
