The setting
's combines in-store hardware with cloud software. Cafes, shops, bars and hair salons use it to take payments and manage orders, inventory and staff.
Confirmed cancellations are colliding with a billing run that still treats accounts as active.
Merchants need charges to stop when service ends, while valid subscription collections must continue without interruption.
Who you’d be doing this for
“I cancelled before the renewal date, and now I’m spending my morning chasing a charge instead of opening up.”
Azar Abbasi · Café Owner · a character in this brief
Runs a small café using POS Plus and manages the monthly operating bills personally.
What is at stake
Approved cancellations are still producing subscription charges for restaurant merchants. You have to protect merchant trust without blocking legitimate recurring collections.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- merchant trust vs valid subscription collection
- fast exclusion vs audit-ready evidence
- queue efficiency vs accurate case classification
- automation signals vs verified payment status
Why SumUp
POS Plus restaurant merchants rely on predictable operating costs while using subscriptions alongside daily payment acceptance.
Written with these in mind
Not your kind of problem? 38 more at SumUp, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at SumUp. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Senior Financial Analyst – Revenue Streams (opens in a new tab)
- Take ownership of complex reconciliations within one of SumUp's revenue streams such as lending, e-money or merchant banking
- We combine deep accounting knowledge with SQL queries, AI-assisted reconciliation tools, and advanced data analytics to understand not just what was recorded, but why and how our business operates financially.
- CoreOps Manager · no longer posted
- Partner closely with Finance and Accounting to ensure operational costs, settlements, and reconciliation are accurately reflected in financial reporting and P&L.
- Exposure to non-payments products such as digital accounts, subscriptions, invoicing, or lending.
- Junior Credit Management Analyst w/ Italian (opens in a new tab)
- You'll be the dedicated point of contact for the Italian market, working closely with Sales, Customer Success and Customer Care teams to resolve overdue payments and keep customer accounts on track.
- In Italy, growth in subscription sales and the launch of "Installment from the Shop", our new self financing option for hardware purchases, has significantly increased the number of open payments that need active follow up.
- Junior Credit Management Analyst w/ French (opens in a new tab)
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about money moving incorrectly, late, or twice.
A retry is causing 0.8% of settled refunds to reduce cardholder balances twice.
You have to protect fast refund recovery without letting a delayed response create another adjustment.
Duplicate refunds reached 0.34% of canceled orders during a six-hour spike.
You have to weigh a quick workflow change against preserving every valid payment retry.
Unmatched payments reached 3.1% of posted collections for three straight days.
You need to weigh rapid correction against protecting valid payment posting.
The same setting, from another role
Each is set around SumUp’s Point-of-sale systems, written for a different role. They’re separate briefs, not the same scenario.
Pilot records are losing the operating detail that makes a POS follow-up relevant to the merchant.
You must decide how much of the move from a visit note to a sourced Salesforce field and a next step the AI drafts, and where the seller steps in to confirm what the owner said.
Retail owners are comparing hardware quotes while stock costs keep rising.
You must weigh a simple partner offer against the proof needed to make introductions convert.
An 18-location restaurant group may renew its incumbent because finance and operations reject different parts of the same deal.
You have to weigh a durable rate commitment against the cutover dates that keep service moving.
Other problems with a similar purpose
In each of these, as in this one, the aim is to make complex payment systems feel dependable in the exact real-world moment someone needs to complete one.
Some New York refunds miss the lender statement window, leaving shopper balances open after a merchant approves the return.
You have to weigh a simpler merchant handoff against controls that prove every refund record arrived on time.
Approved agent purchases with changed prices are failing during authentication.
You have to weigh faster completion against a control path that bad actors could exploit.
Approved reimbursements can remain pending after an employee changes bank details.
You must weigh faster routing against sending money using stale account information.
