Matching TURPAK Sales with Bank Payments: A Step-by-Step Guide
Automation records card sales, but confirming those sales reached the bank is a separate step. This guide walks through the practical way to match sales data from systems like TURPAK against bank-confirmed payments.
Why matching is needed
A sales total that is never compared against bank confirmation may look consistent inside automation yet still not reflect reality. Matching guarantees that every card sale rests on a bank-confirmed record.
The step-by-step match
- Open the shift and load the relevant automation (TURPAK/Asis) sales data.
- List the card and cash sales on the ERP/automation side.
- Compare bank-confirmed payments side by side.
- Correct any misclassified payment types (cash ↔ card).
- Create allocations and resolve the remaining amount.
- Record each step with its reason, reviewer and timestamp.
Common cases
- A sale entered as cash that was actually paid by card.
- A bank-confirmed partial card amount with the remainder in cash.
- A payment that belongs to a neighboring shift but shows in the wrong one.
The outcome
Once matching is done, every amount traces to a bank-confirmed record or an explained cash entry. Shift Tracker automates this flow. Contact us for a demo.