Match card charges to your bills

1. Match card charges to your bills

   Compare what the card reader actually charged with the card payments posted on your bills, and optionally with SumUp's own history. Settle every unmatched charge while it is still traceable, so a missing or double card payment never becomes an unexplained shortfall.

2. Compare and export

   Compare with SumUp fetches SumUp's own transaction list for the range (only when SumUp is connected in Integrations). Export CSV downloads the register rows matching your filters, and View changes the table row density.

3. Date range and filters

   Pick a from and to date or a quick preset, then narrow by transaction state, for example Needs attention. Search by bill code, reference or cashier, or enter a reader ID, and press Apply filters.

4. Card charges by state

   Amount and count for each state in the range. Booked to bills is the card figure the Z report uses. Captured, not on a bill means a guest was charged but no bill carries the payment, so post it or refund the guest.

5. SumUp comparison

   Shown after you press Compare with SumUp: how many successful charges SumUp holds for the range and how many of them are in your register. If the list cannot be fetched, that is not proof that nothing is missing.

6. Mismatches

   Four checks: charges captured by the reader but missing on the bill, card payments on a bill the reader never saw, amounts that differ, and charges known only to SumUp. Matching uses the transaction reference only, never amount or time.

7. Card reader register

   Every card reader transaction in the range with its time and shift, state, bill, reader amount, the payment on the bill (shown in red when it differs), reference and cashier. Charged but unmatched rows are tinted red.

8. Settle a charge

   Only the moves allowed for that row appear: Post to bill, Mark as not charged, Refund guest or Refund via bill. Each one asks for a reason that is kept in the audit log, and a refund to the card cannot be undone.