Branch close that doesn’t match the POS and settlements

The workflow

A branch closes for the day, the counted cash and the POS Z-reading and the GCash, Maya, card and aggregator settlements that arrive days later are four different numbers, and nobody reconciles them channel by channel while the day is still fresh.

What happens today

The supervisor counts the drawer, photographs the Z-reading, and posts both to the branch group on Viber. The numbers are typed into a spreadsheet the next morning. Cash is most of it — in a survey of eleven markets, the Philippines had the highest proportion of small businesses taking at least half of their sales in cash, more than three quarters of them — so the count is the day’s control, and it is a control run by hand.

The electronic channels settle on their own clock. GCash, Maya, card and the delivery aggregators pay days later, net of fees, in batches that do not line up with any one day’s sales. A small difference gets a one-word explanation, or none. An accounting firm that works with Philippine restaurants puts it plainly: a variance should be documented and investigated, not adjusted away, and using the till as petty cash is one of the most common sources of end-of-day variances in the first place.

What ordinary rules handle

Most of the close is arithmetic against a calendar, and we build that as ordinary rules, because ordinary rules are cheaper to run, easy to check, and behave the same way next month.

• Splitting the day’s POS sales by channel and subtracting the counted cash from the cash line.
• Holding each electronic channel open until its settlement arrives, then matching the batch to the orders that earned it and to the fee the schedule says to expect.
• Flagging any variance past the threshold the branch was given, and routing it to the supervisor who closed that shift.
• Reminding on a schedule while the explanation is outstanding, and counting the unexplained days at that branch.

Where the assistant follows through

This is the part we call follow-through: the assistant checks the records, prepares the action, routes it, chases the reply, and raises what it cannot settle.

What rules cannot do is read “short kasi may pinambili ng ice, resibo nasa drawer” in a Viber thread and turn it into an explanation attached to the right day and the right channel. AI reads the message and the photographed Z-reading and makes that call, and it is a smaller part of the job than it sounds.

1. The count and the Z-reading become a draft close. The photographed reading is read off and set beside the counted cash. Draft, because nothing has been posted yet.
2. The day is reconciled channel by channel. Cash against the cash line, and each electronic channel held open until its settlement lands and the fee is checked against what was agreed.
3. The variance is flagged with its evidence attached. The Z-reading, the drawer count and the settlement batch travel with the exception, so the next person to look at it is not re-doing the check.
4. The branch is asked for an explanation, and chased. The question goes to the supervisor who closed the shift, in the thread the branch already uses. If it goes unanswered, the reminder goes out on schedule.
5. Repeats are escalated rather than absorbed. A second short in a month at the same branch is raised to the operations manager as a pattern, not filed as two small numbers. If the reading cannot be read, or a settlement matches no day, it is raised rather than guessed at.

Where a person decides

Writing the difference off or opening an investigation is the operations manager’s call, and the assistant cannot take it. It reconciles the day, collects the explanation, and stops there — not because a check failed, but because that is where the line was drawn when the workflow was built.

Money moving is a decision. The write-off is recorded against the day and the channel, and the approval stays on the record with the name of the person who gave it. A quarter later, the question “how much did this branch write off, and who agreed to it” has an answer.