How to find till variance and reconcile POS takings
Who it is forGrocery chain branch managers, till supervisors, finance and accounting teams, loss prevention and internal audit
When the till does not balance at the end of the day, the first question asked is where the money went. Most of the time the answer is not money but a record: a receipt keyed as cash instead of card, a return posted to the next day, an amount the bank credited after deducting commission, or a sale that never reached the ERP. This guide covers how to find a till variance, how to run three-way reconciliation between the cash register, the bank's POS and the ERP, the typical causes of a variance and how to close each one with a cause code, using a worked example. The formula and threshold for the till variance rate are covered separately on the till variance rate KPI page.
What till variance and a till shortage are
Till variance is the difference between the takings counted at the end of the day and the takings the records say there should be. If the counted amount is lower there is a till shortage; if it is higher there is a till overage. Both are matters for the record; an overage is not the good news version of a shortage, it is usually the same error in the other direction.
Expected takings rest on the cash register. Under the Turkish Revenue Administration's guide to new generation electronic cash registers, the daily closing (Z) report is the record of one day, that is of sales between 00.00 and 24.00, and it is taken every day; a business still open after midnight takes its Z report at closing time and the turnover is posted to the previous day. On card payments, the information on the cash register receipt and the bank's POS transaction slip are combined, and a taxpayer required to use an electronic cash register may not take payment through a desktop POS terminal independent of it. The card total on the Z report and the bank's POS end-of-day total should therefore show the same transactions.
The variance is calculated by payment type: cash, debit and credit cards, meal cards, gift vouchers. Looked at as one total, a shortage in cash and an overage on card cancel each other out and two separate errors look like zero. Shortages and overages are also held in separate columns; netting a variance hides its cause.
- Till variance (by payment type)
Takings counted − Takings expectedA negative result is a till shortage, a positive result a till overage.- Cash that should be in the till
Opening float + Cash takings per the Z report (net of returns) − Cash drops during the day − Documented payments out of the till- Till variance rate
|Till variance| ÷ Takings expected × 100
How the end-of-day cash count is done
The order of the count prevents a good part of the variance in the first place. A Z report taken while a receipt is still open pushes the sale into the next day; a count made before the POS end-of-day is run cannot see a shortage or overage on card; and cash drops that are not deducted with their dockets make money that is not in the till look like a shortage.
On the bank side, the end-of-day is a separate operation and it starts the transfer of funds into the account. As the Ziraat Bank merchant questions explain, an end-of-day run through the POS terminal reaches the account one day later where there is no holdback period, and the day after the holdback period ends where there is one. The end-of-day report is therefore an attachment to the till count record.
- Close open receiptsCheck that no suspended or pending receipt is left. A sale whose goods have left but whose receipt was never closed shows as missing both in the till and in the ERP.
- Run the POS end-of-dayThe bank's POS end-of-day report is printed and attached to the count record; card takings are compared against it.
- Take the Z reportThe Z report is taken every day; a store that closes after midnight takes it at closing time. The payment type breakdown on the report is the expected takings.
- Count cash by denominationTwo people count, the opening float is set aside and a denomination record is completed. Cash drops made during the day are deducted with their dockets.
- Gather the documentsCard and meal card slips, gift vouchers, return and void documents and documented payments out of the till are brought together.
- Record the variance by payment typeFor each payment type the expected amount, the counted amount and the variance are recorded; the record is signed by the cashier and the person counting. An explained variance is recorded with its cause code, an unexplained one with a separate code.
A mistaken receipt cannot be corrected afterwards; the fiscal memory of an electronic cash register cannot be erased or changed. Under the Revenue Administration's guide, the original of a mistaken receipt is voided and kept attached to its copy on the record roll held at the business, and a new receipt is issued for the real amount. A void whose document is not kept comes back as an unexplained variance in the count.
How POS reconciliation works: matching the till, the bank and the ERP
POS reconciliation checks whether three sources tell the same story about the same day with the same amount. The cash register's Z report is the fiscal record and gives the payment type breakdown. On the bank side there is the POS end-of-day report and the amount credited to the merchant account. The ERP is the accounting and stock record of the sale. All three can be internally correct and still fail to agree; the job of reconciliation is to separate an expected difference from an unexplained one.
Matching starts with totals and ends at the receipt line. If the totals agree the day is closed; if they do not, the variance is hunted line by line using the receipt number, the time, the amount and, on card transactions, the bank's authorisation code. Most of a card total variance usually comes down to a single receipt.
The amount credited by the bank is not equal to the end-of-day total, and that is not a shortage. Merchant commission is deducted and the money arrives on the value date. In the definition used in the Garanti BBVA POS guide, the value date is the period between the day of the sale and the day the payment reaches the account, and many banks do not count weekends and public holidays as business days. Ziraat Bank likewise advises checking the end-of-day slip first when less than expected has been credited, and asking the bank about whatever is still missing after commission has been deducted.
- Card reconciliation
Z report card total − POS end-of-day total = 0- Amount expected to be credited
POS end-of-day total − Merchant commission (on the value date)- ERP reconciliation
Z report sales total − Sales posted to the ERP = 0
| Comparison | Matching key | Expected difference | Unexplained difference |
|---|---|---|---|
| Cash counted ↔ Z report cash | Till, business day | None | Till shortage or overage |
| Z report card ↔ POS end-of-day | Receipt number, time, amount, authorisation code | None | Wrong payment type, a transaction voided on the POS but left on the till |
| POS end-of-day ↔ amount credited | End-of-day date, merchant number | Commission, holdback period, value date, public holidays | Whatever is still missing after commission has been deducted |
| Z report ↔ ERP sales | Store, business day, receipt number | The day cut-off on sales made after midnight | A receipt that was never posted, or posted twice |
What causes till variance, and how cause codes are assigned
Most till variance is not theft but a difference of record and timing. The order of investigation is therefore fixed: timing first (value date, day cut-off), then the record (payment type, returns, voids, posting), and counting and change last. Whatever unexplained variance remains after that elimination goes to investigation.
Every variance line is written with the same fields: store, till, business day, payment type, amount, direction (shortage or overage), cause code, evidence (receipt number, authorisation code, document) and the person closing the record. The code list is kept short; a long list does not get completed in the field and everything ends up under the other code. There is a separate code for unexplained variance too, and it is never left blank.
| Code | Cause | How it shows | Check |
|---|---|---|---|
| PTY | Wrong payment type | A shortage on one payment type and an overage of the same amount on another | Authorisation code match at receipt line level |
| RTN | A return not keyed into the till or posted to another day | Cash short; the return is in the ERP but not on the Z report, or the reverse | The return document against the return line on the Z report |
| VOI | Undocumented void | The receipt was voided, the money left the till | Is the original of the void receipt on the record roll |
| COM | Merchant commission | The amount credited is lower than the end-of-day total | Recalculate at the rate in the agreement; instalment transactions separately |
| VAL | Value date and holdback | The amount is not in the account on the expected day | Whether the merchant works with or without a holdback period, business day calendar |
| CUT | Day cut-off difference | Sales after midnight posted to another day in the ERP | The Z report date against the ERP business day rule |
| OPN | Open receipt | The goods have left, the receipt was never closed | The end-of-day open receipt list |
| PST | Posting error | A difference in receipt count between the Z report and the ERP | Continuity of receipt numbers |
| MEA | Meal card, gift voucher | An amount collected through a separate channel recorded as cash | Separate coding of the payment type |
| CHG | Change and counting error | Small amounts, in cash, direction varies | Denomination record, second count |
| UNX | Unexplained variance | None of the other codes fits | Cashier, time and the pattern of voids and returns; camera event |
The codes are examples; adapt them to your own till and ERP structure. What matters is that every variance is tied to a code and to evidence, and that unexplained variance is visible separately.
Can a till shortage be deducted from an employee's pay?
This question rests on three statutory provisions. Under Article 400 of the Turkish Code of Obligations, an employee is liable for any damage caused to the employer through their own fault; in determining that liability, the nature of the work and the employee's qualities known or which ought to have been known to the employer are taken into account. Article 407 of the same Code provides that the employer may not set off a claim against the employee with the wage debt without the employee's consent; a claim arising from damage the employee caused intentionally and established by a court judgment may be set off up to the attachable portion of the wage.
The wage deduction penalty in Article 38 of the Labour Law is a separate matter. It may only be imposed for reasons set out in a collective agreement or the employment contract, must be notified to the employee immediately with its reason, may not exceed two days' wages in a month, and the money deducted does not stay with the employer; it is paid into an account opened in the name of the Ministry for the training and social services of workers. That penalty therefore does not cover the shortage.
For operations, the conclusion is this: before a variance is attached to a person, the timing and record causes are eliminated, evidence is gathered for whatever is left unexplained (the receipt, the POS record, the pattern of voids and returns and, where needed, the camera event), and the process is kept in writing.
This section is general information, not legal advice. Any decision on deduction, set-off or compensation depends on the circumstances of the specific case and should be assessed with an employment lawyer.
What a daily till and POS checklist should look like
The checklist has two parts: what is done in the store at the end of the day, and what is done at head office the next morning. The store counts and documents; head office matches against the bank and the ERP. If the two jobs land on the same person, both the control and the separation of duties disappear.
- End of day: no open receipts; the POS end-of-day and the Z report have been taken and both attached to the count record
- End of day: cash counted by denomination by two people, the opening float set aside, cash drops deducted with their dockets
- End of day: card, meal card and gift voucher amounts compared against the payment types on the Z report
- End of day: every return and void documented; the originals of voided receipts attached to the record roll copy
- End of day: the variance recorded by payment type, with a cause code, and the count record signed
- Next day: the Z report matched to the sales posted to the ERP on receipt count and amount
- Next day: the POS end-of-day matched to the bank movement, taking commission and the value date into account
- Next day: unexplained variance assigned to an owner; variances recurring on the same cashier or the same till flagged separately
The list stays short and is worked in the same order every day. Small variances that recur on the same till carry more information than one large one-off variance; the pattern is tracked even when no threshold is breached.
How till variance and POS reconciliation are tracked in Mindpera
On the Store Reconciliation screen in Mind Ops, the gap between the till and the system is listed as unmatched POS rows with a cause code and an amount; which row failed to match and why is not hunted for, it is written down. Events in the till, entrance and shelf areas are recorded with a timestamp and every event is linked to the relevant sales record. A till event that does not match a transaction raises an alert and lands, with its record, on its owner.
Every item opened carries an owner, a deadline and an outcome; it is tracked until it closes and escalates step by step if it does not. On the Mind Cam side, the till variance record and the camera event at the same moment are placed side by side, so an investigation starts from the matching event rather than from scanning footage.
- Mind Ops, Store Reconciliation: unmatched POS rows with a cause code and an amount
- Mind Ops, camera event tracking: events are recorded with a timestamp and linked to the sales record
- Mind Ops, Action Centre: owner, deadline and outcome; an item that does not close escalates step by step
- Mind Cam, till matching: the till variance record side by side with the camera event at the same moment
Where the till, the POS and the ERP run on different day cut-off rules, they are brought under one rule during installation. The data protection side of camera recording is covered in the store camera recording guide.
Frequently asked questions
- What is POS reconciliation?
- POS reconciliation is the check of whether the card takings on the cash register's Z report, the bank's POS end-of-day report, the amount credited to the account and the sales posted to the ERP agree with one another. If the totals agree the day is closed; if they do not, the variance is hunted line by line using the receipt number, time, amount and authorisation code. Commission and value dates are expected differences; whatever remains after they are deducted is the variance that needs explaining.
- Can a till shortage be deducted from an employee's wages?
- Under Article 407 of the Turkish Code of Obligations, an employer may not set off a claim against an employee with the wage debt without the employee's consent; only damage caused intentionally and established by a court judgment may be set off, up to the attachable portion of the wage. The employee's liability depends on fault (art. 400). The wage deduction penalty in Article 38 of the Labour Law is paid into a Ministry account and does not cover the shortage. The specific situation should be assessed with a lawyer.
- Why do the Z report and the POS end-of-day not agree?
- The most common cause is the wrong payment type: a receipt paid by card was keyed as cash on the till, or the reverse. In that case one payment type shows a shortage and another an overage of the same amount. Other causes are a transaction voided on the POS but left on the till, the POS end-of-day being run at a different time from the Z report, and a split payment recorded under a single type. The variance is found by matching at receipt line level with the bank's authorisation code.
- When does money taken on a POS terminal reach the account?
- It depends on the merchant agreement. According to Ziraat Bank, an end-of-day run on the POS reaches the account one day later where the merchant works without a holdback period, and the day after the holdback period ends where there is one. In calculating value dates, many banks do not count weekends and public holidays as business days. The amount credited is net of commission; in reconciliation the gross end-of-day total and the net amount are kept on separate lines.
- What should be done when the till is over?
- It is recorded exactly like a shortage: amount, payment type and cause code. An overage is usually the counterpart of a shortage on another payment type, such as a receipt closed under the wrong payment type or change given short to a customer. An overage is not netted against a shortage, because two separate errors then look like zero. An overage whose source cannot be found is tracked as unexplained variance and investigated if it recurs on the same till.
- What goes into a till count record?
- Store, till number, date and time; the opening float; cash counted by denomination; cash drops during the day; the Z report amount, the counted amount and the variance by payment type; the number of return and void documents; the cause code and explanation for the variance; and the signatures of the cashier and the person who counted. The record is kept together with the Z report and the POS end-of-day report, and goes into head office reconciliation the next day.
Sources
- Turkish Revenue Administration, Guide to the Use of New Generation Electronic Cash Registers (YN ÖKC) — 2025
- Ziraat Bank, POS and merchant frequently asked questions — 2026-09
- Garanti BBVA POS, what the value date means on POS terminals — 2025-07-09
- Turkish Code of Obligations No. 6098 (consolidated text), art. 400 and art. 407 — 2011-02-04
- Labour Law No. 4857 (consolidated text), art. 38 — 2003-06-10