Fintech baropaper 2026
Returning research
That's the core of it. Responsibilities are fragmented, the outlook rarely extends beyond a few weeks and the same operational bottlenecks resurface year after year. The reason: ownership and mandate are not clearly defined. Whoever spots the signal isn't authorised to act on it. Whoever is authorised to act sees the signal too late.
In 30 seconds: what this report shows
Who actually owns DSO?
Chapter1
Who owns DSO?
- Finance/ credit management
- CFO
- Operatiations teams/ the business
- no one explicitly
The cost of role ambiguity
Who bears responsibility when DSO targets are not met?
How often does unclear DSO ownership lead to internal discussion or decision-making delays?
- Always
- Frequently
- Occasionally
- Never
Explaining cash flow versus managing it
Chapter 2
How often are you forced to explain cash flow retrospectively rather than managing it proactively?
How far ahead can you today confidently plan expected cash-in?
Where organisations get stuck
What gets in the way of managing cash flow at the level the board expects?
From data to insight to action
Conclusion
Whoever maintains that architecture holds a governance responsibility, not an operational one. The CFO who wants to project confidence to the board no longer explains what happened. They show where the organisation will be in thirty days, what risks that picture contains and why the measures in place are working.
That doesn't require a better dashboard. It requires a deliberate design choice: around ownership, around the end-to-end process, around governance of something that has been labelled "operational" for far too long.
Best practies: what data tells us
- Don't manage blindly to a DSO score
Start by mapping the causes. DSO is an outcome; its drivers are not. Identify the five biggest contributors to your payment delays and assign a named owner to each one. Accountability without that level of precision just moves the blame around. - Define your early warning signals before you need them.
Agree in advance which thresholds call for action: a growing overdue balance, a spike in disputed invoices or a failed payment arrangement. Locking in those signals now (before DSO starts moving) is the difference between managing and explaining. - Map the process clearly before you automate it.
You can scale a problem, but you can't scale a solution that doesn't exist yet. Structure first, software second. Automating an undefined process is a guaranteed path to digital sprawl. Agree what happens at each stage and who has sign-off authority before you configure a single credit management tool. The tool makes your process faster; it doesn't design it for you.
About the research
Every year, Onguard investigates how financial professionals view current trends and developments, such as financial technologies, digital transformation, AI and new payment methods. This study, entitled the FinTech Barometer, was conducted for the first time in 2017, surveying every year around 300 finance professionals. Of these, 200 work in financial management and 100 as financial employees.
About Onguard
Managing receivables across multiple entities, ERPs, and markets: no single system was built for that. Onguard Credit Management helps credit and finance teams automate reminders, collections, and order-to-cash across every entity and market, without relying on outside consultants or adding headcount. Solving these challenges since 1992, trusted by hundreds of companies across 40+ countries. The result: customers get paid faster, DSO down by up to 30%, collection costs cut by 15-30%.)
