Expected transactions

From scattered commitments to a living view of the next 30 days

Period:
2025–2026
Platforms:
Web, iOS, Android
Role:
research, product design, design mentorship, specs, qa

Key question

How might we make the near future actionable?

Context

SME owners could see today’s balance, but future cash was fragmented across invoices, bills, direct debits, subscriptions, transfers, financing, and spreadsheets. Qonto already held many of those signals; the opportunity was to turn them into a coherent, trustworthy view, informing next payment decisions.

Assemble

Bring future commitments together

Expected Transactions consolidates invoices, bills, direct debits, subscriptions, scheduled transfers, financing instalments, and manual entries into one view.

The Expected transactions screen on web, a projected-balance chart above a list of commitments drawn from invoices, transfers, subscriptions and predictions
The same view on mobile, Overdue and Upcoming tabs above the chart
Rows naming the source each item came from — client invoice, approved quote, Pay Later instalment, predicted transaction

Understand

Show the impact on cash

A 30/90-day chart and projected balance connect individual commitments to the overall trajectory. Chart and list remain synchronised so customers can move from shape to detail.

Hovering a bar in the chart names the commitment behind it and its date
A day selected on the mobile chart, showing the projected balance for that date
The list below the chart, synchronised with the day selected on it

Act

Unload the future, decide with confidence

This screen is not about “keeping it clean.” It is a place to offload what is coming next and turn it into decisions.

  • Choosing when to pay a bill: schedule it and preview how each timing option affects the projected balance.
  • A client will pay late: reflect the new expected date so your near-future view stays true to reality.
Rescheduling a supplier invoice: the date picker open on its row, the chart previewing the trajectory that timing would produce
A row's action menu — schedule the transfer, mark it paid, open the invoice, or remove it
Changing an expected date on mobile, with the reason the original date was predicted

Control

Automation with oversight

The system assembles the first picture, then gives customers the levers to make it true: add missing items, edit dates and recurrence, hide noisy sources, and manage overdue separately—kept out of the default timeline, but always reachable via its own filter and counter.

Adding a missing commitment by hand and setting its recurrence, beside the invoice sources that populate the view automatically
The overdue filter switched on, its late items dated in red
The mobile Overdue tab, prompting new dates to move late items back into upcoming

Plan

Connect live reality to intent

Expected now sits beside Actual, Overdue, Target, and Forecast. Customers can see not only what is coming, but whether it supports or threatens their plan.

A month's inflows opened beside the forecast — actual against forecast, and the expected items behind the figure
Actual, forecast and target on one bar, with expected and its overdue count beneath
The expected items for the month the forecast is built from

Retention

+100,000

recurring visitors each month

Action

10,000

unique users managing their overdue

Metric

TBD

TBD

How to push further

Be transparent towards prediction expectations

The value comes from assembling what Qonto knows; trust comes from showing confidence, preserving control, and making every item’s transition into reality understandable. But expressing candidly what are the Qonto current boundaries is not only mitigating the delivered promise, but is a first guidance on what our users might to add to reach a good enough accuracy.