How to Reconcile POS Tender Settlements

Processor deposits never match the day’s card or wallet total

SumUp or a bank partner pays two days later, net of fees, sometimes combining several days. Finance books the deposit as sales and understates revenue by the fee forever.

Without per-tender clearing, nobody can say which till method the deposit belongs to when three processors land in one bank account.

Duplicate CSV imports of the same payout create double bank debits if references are not unique.

Why this happens

• Posting non-cash sales straight to bank before money arrives.
• Ignoring fees until year-end tax time.
• No external reference uniqueness on settlements.
• Leaving clearing balances to age without Attention alerts.

Biznsbook addresses this through tender settlements, clearing reconciliation, stale clearing Attention Center when the POS module is licensed — terminal and back-office checkout share unified SaleBill posting.

Finance teams lose days each month reconciling versions that should never have diverged. Naming Biznsbook screens as the system of record — and closing periods when agreed — prevents silent edits that auditors flag immediately.

Step-by-step: Reconcile POS Tender Settlements

Built for retailers who need a fast till, float discipline, and the same INV-* sale bill in stock and GL — not a standalone cash register.

1. Confirm tenders and clearing. Each processor-backed tender should already have its clearing account from Payments → Tender types.
2. Create a settlement. Payments → Tender settlements → create. Choose tender, bank account, arrival date, gross, fee, net, and external reference from the processor statement.
3. Let posting derive a penny if needed. If gross is off net plus fee by one cent, Biznsbook derives gross to keep the journal balanced within ledger tolerance.
4. Post when the period is open. The settlement posts via APS with SourceType TenderSettlement. Closed periods fail the open-period check rather than posting silently.
5. Open Reconcile. Compare amounts taken on the till for that tender, amounts settled, and the clearing account balance.
6. Watch Attention Center. Stale clearing older than StaleAfterDays (default 7) can raise an Attention item so uncleared processors are not forgotten.

Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.

Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.

Common mistakes to avoid

• Mistake 1: Posting non-cash sales straight to bank before money arrives. Repeating this each month usually shows up first in cash reconciliation and till speed.
• Mistake 2: Ignoring fees until year-end tax time. Repeating this each month usually shows up first in cash reconciliation and till speed.
• Mistake 3: No external reference uniqueness on settlements. Repeating this each month usually shows up first in cash reconciliation and till speed.
• Mistake 4: Leaving clearing balances to age without Attention alerts. Repeating this each month usually shows up first in cash reconciliation and till speed.

Track recurring exceptions in month-end notes; each should map to a control above.

Best practices that hold up as you scale

• Confirm tenders and clearing — Each processor-backed tender should already have its clearing account from Payments → Tender types.
• Create a settlement — Payments → Tender settlements → create.
• Let posting derive a penny if needed — If gross is off net plus fee by one cent, Biznsbook derives gross to keep the journal balanced within ledger tolerance.
• Post when the period is open — The settlement posts via APS with SourceType TenderSettlement.
• Open Reconcile — Compare amounts taken on the till for that tender, amounts settled, and the clearing account balance.

Teams that open on a named register, park holds, and close with expected cash keep variance disputes short.

How Biznsbook supports this workflow

tender settlements is documented in Biznsbook POS capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

clearing reconciliation is documented in Biznsbook POS capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

stale clearing Attention Center is documented in Biznsbook POS capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

Sessions, barcode, split tender, X/Z reports, and receipt branding are covered in Docs/POS — use Help Center for click-level screens.

Suggested implementation timeline

1. Week 1: Document current process gaps and configure tender settlements with finance owner sign-off.
2. Weeks 2–3: Pilot on one month or one entity; post all test transactions through Biznsbook; freeze parallel spreadsheet journals.
3. Week 4: Run first trial balance or report tie-out; fix mapping and permission issues.
4. Month 2–3: Roll out to full team; add approvals and period close cadence from this guide.
5. Ongoing: Monthly review using pair with stripe when both exist and leadership dashboard.

Related guides and help articles

Help Center: open a POS session. Industry: retail POS ERP. Module: POS software.

Restaurant-adjacent (not this pillar): transition from standalone POS, Toast alternative.

Journal shape to remember

Tender settlement posting mirrors Stripe payouts: debit Bank for net, debit Payment Processing Fees for fee, credit the tender clearing account for gross. SourceId is the settlement id string for APS idempotency. FailureReason is stored when posting cannot complete so finance can fix bank mapping or period status without inventing a second journal.

Session X/Z and terminal Z tender breakdowns show till activity; settlements show bank activity. Both are required to explain why cash in the bank is not equal to yesterday’s non-cash Z line.

Import profiles store column mapping JSON so recurring SumUp or bank CSV formats do not need remapping every week. Always keep ExternalReference filled — it is the duplicate guard that protects the bank account from a second debit of the same payout.

If clearing stays stale past StaleAfterDays, Attention Center can surface it on read, similar to Stripe attention items. Treat that as a cash-office task list item, not a night-time Hangfire dependency.

Metrics to track monthly

• Open sessions with a selected POS terminal
• Cash sales with ClientRequestId retries that stay single INV-*
• Parked bills resolved before close
• X-reports run mid-shift without closing
• Terminal Z generated per register/day

Start with three metrics; trend direction matters more than a single point-in-time snapshot.

Spreadsheet / manual books vs integrated ERP

Compare typical manual finance work with Biznsbook tender settlements and related capabilities.

Pair with Stripe when both exist

If you use Stripe Terminal and a SumUp tender, keep Stripe on Card payout reconciliation and SumUp on Tender settlements. Mixing them in one report would blur processor fees and arrival dates.

Document this in your finance SOP and revisit each quarter as transaction volume or entity structure changes.

Frequently asked questions

How this differs by industry