X Report vs. Z Report: Closing Your Register and Card Batch
Z report vs X report explained for retail shops: what each register report shows and how to find out why your Z total and card batch don't match.
Photo: Pixabay
On this page 6 sections
Key takeaways
- An X report only reads the register. A Z report closes that register's day, and on most systems it can't be undone.
- Your Z report and card batch come from separate systems, so confirm they cover the same hours before you hunt for missing money.
- A void entered on the POS but not on the terminal leaves the customer charged for a sale the register says never happened.
- File the Z with the batch report and a signed close sheet, because disputes and audits can arrive months after the sale.
An X report is a reading of the register's sales so far, and printing one changes nothing. A Z report is the end-of-day close. It prints the same totals, then resets the register's daily counters to zero so tomorrow starts clean. That reset is the whole Z report vs. X report distinction, and it's why a cashier who presses Z in the middle of the afternoon has just ended the business day for that register.
Neither report is your card batch. Your register records what was rung up, while the terminal and your processor record what was authorized and sent for funding. Most closing-time headaches in a shop live in the space between those two records, and each gap there has a cause you can trace.
Z Report vs. X Report: What Each One Shows
Both reports usually carry the same content. You get sales totals with tax broken out by tender type, along with counts of exceptions such as voids and "no sale" drawer openings. What differs is what happens after the paper comes out.
Run an X report any time you want a reading without closing anything. Managers use it for a midday cash drop or when two cashiers hand off a single drawer at shift change. You can print as many as you like.
A Z report runs once per business day for each register or drawer. It zeroes the daily totals, and most registers also print a sequential Z number plus a grand total that never resets. Those two counters let an owner or auditor confirm that no day was skipped or deleted. Some POS software drops the letters entirely and calls the same function a "day close" or "end-of-day report," run from a back-office screen rather than a key.
One rule catches a lot of shops off guard. On a standalone card terminal, running the register's Z does nothing to the card batch, because the two machines don't talk to each other. Some integrated systems do trigger batch settlement when you close the day. Find out which kind you have before assuming the card side is done.
How Your End-of-Day Register Report Ties to the Card Batch
Each approved card sale sits in the terminal or gateway as an authorization until the batch settles. Settling sends that group of authorizations to your processor for funding. A batch closes automatically at a preset time or manually when someone presses settle.
Your Z report's card tender line should equal the batch total when both records cover the same hours and contain the same transactions. In practice, "same transactions" means every card sale rung on the register went through its terminal, and nothing ran on the terminal without being rung up. Corrections also have to be made in both places, or the totals drift apart.
Timing causes more mismatches than anything else. Picture a store that closes in the evening while its terminal is set to auto-batch two hours earlier. Card sales from those last two hours land in tomorrow's batch, but the Z report counts them today. Nothing is missing, because the money is simply sitting in the next day's bucket. Move the auto-close time past your latest closing hour and this gap disappears.
How the amount reaches the terminal matters too. On a standalone terminal the cashier keys the amount by hand, and a pair of transposed digits means the card is charged a different amount than the register recorded. With integrated POS systems, the register sends the amount to the terminal, so that kind of typo can't happen. If you're weighing a switch, our buyer's guide to POS systems for retail stores covers what integration looks like in a small shop.
How to Close Out a Retail Register Cleanly
A close done in the same order every night makes every later question easier to answer. This sequence works for most shops running one register or a handful:
- Print an X report and count the cash drawer against it before closing anything. While the day is still open, you can recount and check receipts if the count is off.
- Settle the card batch, or confirm the auto-batch already ran, and save the batch report.
- Run the Z report.
- Compare the Z's card tender line with the batch total, and write both numbers and the difference on a close sheet.
- When they differ, jot the likely cause beside the difference while the cashier who rang the sale is still in the building.
- Build the cash deposit from the counted drawer, minus your starting float.
- File the reports with the close sheet, signed by whoever closed.
Two habits head off most problems. Have someone other than the person who counted the drawer review the variance. And train every cashier that X is the look-only report, so nobody runs a Z just to "check numbers."
Why the Z Report and Bank Deposit Don't Match
You have two gaps to work, in order. One sits between the Z report and the batch. The other sits between the batch and what lands in your bank.
The table below walks through an illustrative day. Every number in it is invented to show the arithmetic and does not come from a real shop or a real rate.
| Line (illustrative) | Amount |
|---|---|
| Z report card tender | $3,640.00 |
| Minus offline sale still stored on the terminal at batch time | −$86.50 |
| Plus sale voided on the POS but left captured on the terminal | +$45.00 |
| Batch total | $3,598.50 |
| Minus processing fees netted from the deposit (placeholder) | −$98.40 |
| Bank deposit | $3,500.10 |
This assumes a single register and terminal covering identical hours. It also assumes the processor takes fees out of each deposit. The fee line is a placeholder, not a quoted rate.
In this example, the first two adjustments make up a Z-to-batch gap of $41.50. That offline sale will go out with the terminal's next transmission, so it resolves itself. The voided sale is more serious. A cashier canceled it on the register, but the customer's card was still charged. So the shop owes that customer a refund and should issue it before a dispute arrives.
Between the batch and the deposit, look for these causes:
- Fees. Some processors take fees out of each daily deposit. Others debit them once at month end, which keeps daily deposits closer to the batch. Your statement shows which arrangement you have.
- Funding timing. Weekend batches often arrive together on the next business day, and bank holidays push deposits back as well.
- A separate American Express agreement. If you accept Amex directly with American Express rather than through your processor, those funds arrive as their own deposit.
- Deductions. A chargeback or reserve hold can come out of a deposit and shrink it without any change in sales.
- Debit cash back. The batch counts cash back as part of the card amount, while the Z report may show it as cash paid out of the drawer.
Tracing Voids and Refunds Across Both Systems
Each kind of correction leaves a different trail on the register and on the card side. Knowing which trail to follow tells you where to look first.
Voids Cancel a Sale Before It Settles
A void entered before the batch closes removes the authorization, so no money moves. Your customer may still see a pending charge in their banking app until the hold drops off. The danger is a one-sided void like the one in the table above. Make "void on both" a standing rule in any shop with a standalone terminal.
Refunds Move Money Back After It Settles
After a batch settles, the sale can no longer be voided and has to be refunded instead. That refund shows up as a credit in whichever batch you process it in, and it lowers that day's net. Most Z reports list returns on their own line, though some systems net them against sales, so read yours closely. A refund to cash or store credit skips the batch entirely. It shows up in the drawer count or your gift card liability instead. For help setting that policy, see our guide to choosing between card refunds and store credit.
Offline Sales Wait to Be Sent
Many terminals can store a card sale when the connection drops and transmit it later, a feature often called store-and-forward. Your register counts that sale immediately, but the batch won't include it until the terminal reconnects. If the card declines at that point, the shop has already handed over the goods and absorbs the loss. Save offline mode for real outages, and check the terminal for stored transactions before you settle. Our notes on selling through a system outage cover how to prepare.
Tips and Split Tender Change the Card Line
A shop with a tip prompt, such as a coffee counter inside a gift shop, can see tips added on the terminal that never reach the register. That pushes the batch above the Z. Split payments cause the reverse confusion when a cashier records a whole sale as card. Our guide to ringing up split tender at the register shows how to put each tender in its own column.
Storing Reports for Audits and Disputes
File each day's reports as one set. That means the Z and the batch report, plus the signed close sheet and any X reports from cash drops.
A Z on its own won't win a dispute. Chargebacks name a single transaction, often weeks or months after the sale. Answering one takes the receipt and batch detail for that sale, along with any return paperwork. Our guide to winning retail chargeback and return disputes covers which documents carry the most weight.
Sales tax auditors often ask for Z reports first. Sequential Z numbers with no gaps, backed by a grand total that only rises, are the simplest proof that your reported sales are complete. How long to keep these records depends on federal and state tax rules as well as your own exposure. This is general information rather than tax advice, so confirm the retention period with your accountant. Scanning each day's set into a dated folder costs almost nothing and survives a register replacement.
Tonight, compare two times: when your store closes and when your terminal auto-batches. If the batch closes first, change it. Then pull last week's Z reports and batch reports and line up the card totals day by day. Any gap that repeats points to its own fix. If that fix is getting the register and terminal to work together, MannyPay's retail payment options include POS systems and card terminals. A free quote request gets a reply from a MannyPay specialist within one business day.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.
