MILabs
Integrations

Payments reconciliation integration for SumUp

Match SumUp sales to bank deposits and ledger entries with a payments reconciliation build that flags gaps for a person to review.

Updated 2026-06-23

Payments reconciliation with SumUp

A SumUp account keeps a record of each card and contactless sale taken at the counter, on a phone or online, with its time and amount. The harder work starts when those takings need to agree with the bank deposits, the cash count and the books kept by an accountant. A payments reconciliation build for SumUp reads the exported transaction records, matches each sale to the deposit it belongs to, and lists what fails to line up, such as a short payout or a refund that appears twice. The matching rules are written with the owner, so they follow how that business handles tips, split tills and returns. Anything the rules cannot place goes to a review queue, where a bookkeeper makes the decision. MILabs builds the link between SumUp exports and the ledger in Xero, so the team keeps control of every unclear entry.

How it works

  1. Pull a sample transaction export from the SumUp dashboard and check its column names, dates and currency fields before any matching rule is written.

  2. Agree the matching keys with the owner, such as sale time, amount and deposit date, and note how tips and split payments appear in the file.

  3. Schedule imports of new SumUp records so each reconciliation run picks up everything since the last import, with card details removed first.

  4. Match each sale to its bank deposit and ledger entry, and send anything unmatched, such as a short payout or a repeated refund, to a review queue.

  5. Post confirmed matches to Xero, and leave refunds and disputes inside SumUp's own tools for a person to approve.

good questions, straight answers

Frequently asked questions

What happens if SumUp changes?
SumUp may change its dashboard, export columns, plans or API details, and any of these can affect the import. Each change is checked against a sample file before the next reconciliation run, and the matching rules are adjusted to suit. Features also differ by country and plan, so the team confirms them in the account first. The build only reads records, so a change in SumUp leaves the bank and the ledger untouched until someone has reviewed the output.
Who owns a payments reconciliation built around SumUp?
The business owns the build, its matching rules and every record it produces. SumUp's platform and the transaction data in its account remain under its own terms. MILabs designs and delivers the integration, documents how the matching works, and leaves the configuration with the team so they can run it. The owner keeps administrative access to the SumUp account and can remove any connection they no longer want.
How does a payments reconciliation hand work to a person when SumUp data is unclear?
Any sale the matching rules cannot place goes into a review queue with its SumUp amount, time, payment method and the nearest candidate deposit or ledger entry. A bookkeeper opens the item, decides whether it matches, and records the reason beside it. Confirmed matches are then posted to Xero, and the rule stays unchanged until the team agrees to change it. Refunds and disputes are never actioned by the system, so the person keeps the final say.
Can a payments reconciliation work with SumUp data exports?
Yes. A transaction file downloaded from the SumUp dashboard can be imported on a schedule, once its columns have been checked on the day of export. A file is only as current as the moment it was pulled, so a live feed depends on an API connection that someone builds and maintains. Card numbers and personal details should be removed before anything reaches a model. Exports show only what was recorded, so a sale rung up on another till will not appear.
What should I back up in SumUp first?
Before the build starts, export a full set of transaction records for a recent period and store the copy apart from the reconciliation tool. Save the bank statements, cash counts and ledger export for the same dates, so every match can be checked against an untouched original. Keep a written note of account settings and the names of users with access. A backup holds records only, so it does not replace the exports that SumUp keeps in its own dashboard.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.