What is a Z report? X and Z reports explained

Ask a shop owner what a Z report is and most will say “the thing the till prints at night”. That is right, and it undersells it. The Z report is the one document that says what your shop took today, how it was paid, and whether the money in the drawer agrees. If you only ever keep one piece of paper from your till, keep that one.

Its partner, the X report, is the same picture taken halfway through the day. The difference between the two is small on paper and large in practice, so it is worth getting straight.

Where the names come from

The letters come from old electronic cash registers. Those machines kept running totals in memory: sales, tax, cash, card, voids. Reading those totals without clearing them was an X reading. Reading them and resetting them to zero for the next day was a Z reading, Z for zero.

So on a traditional register, printing a Z report was the act of closing the day. Print it twice by accident and the second one shows nothing, because the totals were already wiped. That is why older staff are nervous of the Z key.

Modern systems keep every sale in a database, so nothing is ever really wiped, but the idea survives: an X report is a look, a Z report is a close.

What an X report is for

An X report shows the current shift so far without ending it. Use it for:

• A mid-shift check. Is the drawer roughly where it should be at two o’clock, or has something gone wrong already?
• A handover. One person hands the till to another; an X report plus a quick count shows where things stood at that moment.
• Knowing when to lift cash. If the drawer is holding far more cash than it needs, an X report tells you how much to take out to the safe.

Nothing about the shift changes when you print one. You can print as many as you like.

What a Z report is for

A Z report closes the shift and records it. A good one shows:

• The opening float, so the count has a starting point.
• Sales for the shift, usually as gross sales, then discounts, refunds and voids, then net sales.
• Tax collected.
• Takings by payment method: cash, card, store credit and anything else you accept.
• Money in and out that was not a sale: cash paid out for a delivery, change brought in from the bank, drawer opened with no sale.
• Expected cash in the drawer, worked out from all of the above.
• Counted cash, what was actually there.
• The difference, over or short.

The last three lines are the reason it matters. Everything above them explains what should have happened; those three say what did.

Why the Z report should never change

Here is the property that separates a useful Z report from a decorative one: once printed, it must not change.

Suppose a sale from this afternoon is voided tomorrow morning. If your system quietly recalculates today’s Z report, the figure you counted against last night no longer matches the paper in your cash book, and a shortfall you investigated has vanished or grown for no visible reason. A Z report is a record of a moment. Later corrections belong to the day they are made, and should show up there.

The same logic applies to refunds. A refund given on Tuesday for Saturday’s sale comes out of Tuesday’s drawer, so it should appear on Tuesday’s Z report, not be pinned back onto Saturday. Systems that attach the refund to the original sale leave Tuesday’s till mysteriously short. There is more on the causes of that kind of shortfall in why your till never balances.

What to do with it

A Z report is only useful if someone reads it. A simple routine:

1. Print it at the close of every shift, not once a week.
2. Write the counted figures on it if your system does not, and sign it.
3. Look at the difference line first. Small and in both directions over a week is normal arithmetic. The same amount every day, or always short, is a pattern worth chasing.
4. Keep them. File them with the day’s takings or keep them in a cash book. In many countries tax authorities expect you to be able to show daily sales records, and a signed Z report is the simplest proof there is.
5. Compare card totals against your card terminal’s own end-of-day report. If they disagree, a card payment was keyed wrongly or never recorded.

For the counting itself, step by step, see how to cash up a till at the end of the day.

One thing to avoid: the peek

A common habit is for the person closing to look at the expected cash figure first and then count. It feels efficient. It is also how a real shortfall disappears: a count that is “nearly” right tends to get nudged until it is exactly right.

The fix is a blind count: count the drawer and write the figure down before being shown what it should be. It is not an accusation, it is how every bank counts cash, and it makes the difference line on the Z report mean something.

Where StoreWave sits

In StoreWave every register runs in shifts. A shift opens with a counted float, records pay-ins, pay-outs and no-sale drawer opens with a reason for each, and serves an X report at any point without closing anything. Closing the shift takes a count for each payment method and produces a Z report with the float, expected and counted amounts, the difference, and every pay-in and pay-out. It prints on a receipt printer, sized for a cash book.

The Z report is a snapshot, so a later void cannot rewrite it, and refunds land on the drawer that is open when they are given. Blind close hides the expected figures from whoever is counting. There is more on shifts and cash-up.