Match every store deposit to the bank, every week

Why weekly, and why per store

A monthly bank reconciliation tells you whether the company's books balance. It doesn't tell you which store's Tuesday deposit never made it to the bank, and by the time the month closes, the person who made that deposit may not remember it.

A weekly, per-store match keeps every gap small and recent. A missing deposit found on Monday is a phone call. The same deposit found five weeks later is an investigation.

Three numbers for every store-day

Reconciliation is matching three records that should describe the same money:

• What the POS reported. Cash sales and card sales for the business day, from your POS's end-of-day or sales summary. For cash, use the expected deposit after any paid-outs and the drawer's own over/short, not gross cash sales.
• What the store deposited. The deposit slip amount the manager recorded, ideally with the slip number and a photo. For cards, this is the batch the POS or your card processor settled.
• What the bank credited. The actual deposits and card settlements on your bank statement or activity feed, with their posting dates.

Cash and card need separate matches. They move on different timelines, fail for different reasons, and land in the bank as different lines.

Timing gaps you should expect

Most mismatches in a given week aren't mismatches at all. They're money in transit. Know your normal lags before you start chasing anything.

• Weekends. Saturday and Sunday cash often goes to the bank Monday, and may post Monday or Tuesday. Expect two or three business days to arrive together.
• Holidays. A bank holiday adds a day to everything. Keep the bank's holiday calendar next to your own store hours.
• Card batch settlement. Card sales are usually settled in a nightly batch and credited a business day or two later, often as one deposit per batch, sometimes net of processing fees. A batch that didn't close at night may merge with the next day's.
• Deposit cutoffs. Cash dropped after the bank's daily cutoff posts the next business day.
• Courier or armored pickups. If a service collects deposits, the deposit date is the pickup date, not the business day.

Write down each store's expected lag for cash and for cards. A deposit is only "late" once it's past that lag.

Short and over thresholds

Not every difference deserves a call. Set thresholds so small, explainable differences are noted, and real ones get worked.

• A small tolerance for rounding, coin, and minor drawer differences. Log these, but don't chase them one at a time.
• A review threshold above which the store manager explains the difference within a set number of days.
• An escalation threshold above which an area manager or the owner looks at it directly.
• A pattern rule. Several small shorts at the same store in the same few weeks get reviewed as a group, even if each one is under tolerance.

For example, say a store's expected cash deposit for a day was $1,240 and the bank credited $1,140. A $100 gap is too round to be rounding. Look for a second deposit, a split bag, or a slip that was written up wrong before you assume anything else.

The weekly routine

1. Pull the week

For each store, pull the POS cash and card figures by business day, the deposit log, and the bank activity for the week plus a few days on either side to catch lags.

2. Match the easy ones

Match each expected deposit to a bank credit with the same amount within the store's normal lag. Most lines clear here.

3. Match combined and split deposits

Look for one bank credit that equals two or three days of expected deposits, or two credits that add up to one day. Weekends and missed bank runs produce both.

4. Work what's left

Anything still unmatched past its lag goes on the exception list with the store, the day, the expected amount, and what the bank shows. Send each manager only their own store's list.

5. Carry open items forward

An item that's still in transit at week's end stays open on next week's list. Never close it just because the week did.

6. Record the resolution

For every exception, record what it turned out to be, who confirmed it, and the evidence. That record is what makes next month's close quick.

Mismatch types and likely causes

Common failure modes

• Matching totals instead of days. A week that balances in total can hide a missing deposit offset by a combined one.
• Treating every lag as a shortage. Chasing Monday's weekend deposit on Monday morning trains managers to ignore you.
• Mixing cash and card. One store's card fees can quietly offset another day's cash short.
• Closing items at week's end. In-transit money that's dropped from the list stops being looked for.
• No slip evidence. Without a slip number or photo, every disagreement is one person's word against the bank.
• Gross cash instead of expected deposit. Paid-outs and drawer differences make good deposits look short.
• Waiting for month-end. The evidence is still there; the memory isn't.

What to measure

• Match rate: share of expected deposits matched within their normal lag, per store
• Days to deposit: business day to bank posting, for cash and for cards
• Open exceptions: count and age, carried week to week
• Net short/over: per store, over a rolling period, alongside the count of small shorts
• Unexplained items at month-end: the number that should trend toward zero

Weekly checklist

• Every store-day has an expected cash deposit and an expected card settlement
• Each one is matched to a bank credit, or is still inside its normal lag
• Combined and split deposits are matched to the days they cover
• Every difference over tolerance has a store owner and a due date
• Last week's open items are either resolved or carried forward
• Card credits tie to processor settlement detail, fees included
• Each resolution has evidence and a name next to it

Keeping it weekly

This routine runs fine in a spreadsheet. What breaks it is store count: each store adds a column of days, two kinds of money and its own lags. Poros Ops runs this reconciliation for multi-unit operators, matching POS figures, deposit logs and bank activity each week and handing each manager their own short list of exceptions. It reads and matches only; it doesn't move money.