A sales day creates more than a total: there are transactions to reconcile, payments that need an explanation, refund requests, and payout records that finance needs to trust. Strawberry can turn the SumUp screens you opened into a clear review queue across sales history, transaction state, customer follow-up, and payout checks.
01
A payment total is not a settlement check.
Have a companion inspect the sale and payout screens side by side.
It can separate ordinary timing differences from records that need finance to investigate, so the close starts with exceptions rather than a manual hunt.
02
Refund work needs the original sale in view.
A refund request can look straightforward until the payment status, item, and customer conversation tell a different story. Bring those tabs together and get a concise case brief before anyone changes a transaction.
03
The receipt request belongs with the transaction.
Instead of copying reference numbers into a separate message, use the visible SumUp record as the starting point for a customer-ready response or an internal receipt task. The details stay attached to the payment they describe.
04
A daily payment check catches problems while the evidence is fresh.
Turn the end-of-day review into a SumUp skill, then schedule a 17:30 pass that groups failed, refunded, and unsettled transactions for finance. That cadence lands after the trading day without touching a charge, a refund, or a payout.
It can organise the sales, transaction states, refund cases, payout records, and related browser material you choose into a reviewable payment-work queue.
Review the original transaction, amount, reason, and customer impact before authorising a refund-related action.
Yes. Capture your finance team’s exception rules in a skill and set a weekday cadence that prepares the check after trading closes.
No. SumUp remains the payment system; Strawberry helps make the work around the signed-in account easier to review.
SumUp Strawberry