Blog

Payment volume grew 74%. Complexity grew faster.

Payment volume per Kyriba customer has grown 74% since 2019. On a dashboard, that number updates automatically and reads clean. It also tells only part of the story. Volume adds. Complexity multiplies.

The growth itself comes from business decisions layered onto the payment calendar: headcount growth becomes payroll volume, expansion becomes cross-border transactions, new debt becomes wire volume, and M&A creates new banking relationships overnight. Other factors contribute too, including e-invoicing's push toward real-time, individually settled payments instead of bundled batch files.

None of that complexity shows up in the volume count. It shows up in the operational work underneath it: a wire gets keyed in by hand because there's no time to route it through the normal queue, or a file gets rejected because the bank required a piece of information that wasn't there.

Payment complexity compounds faster than payment volume

Add a new banking relationship and payment volume ticks up by however many transactions that bank handles. That relationship also brings its own file format, whether a regional standard like EBICS or a bank-specific flat file, its own cutoff times, a distinct approval hierarchy, and its own fraud exposure profile. A single new entity, rail, or acquisition can multiply the number of ways a payment run can fail well before it changes the number on the volume dashboard.

Payment complexity outpaces payment volume right there. A finance team that scales headcount to match rising volume is solving the wrong problem. The exceptions that actually break a payment run, a rejected file, a mismatched beneficiary account, a format nobody translated correctly: those come from complexity, not volume.

Kyriba’s payment hub is built around that distinction. It consolidates every banking relationship, format, and approval layer into a single governed environment, so a new rail or entity extends the same control structure rather than creating a new one to govern separately. That structure plays out concretely at scale.

Fewer human touches, same amount of control

Şişecam, which runs one of the more complex payment environments in Kyriba's customer base, now processes 95% of its payments through Kyriba with no human touch at all. What matters is where the remaining 5% goes. Kyriba's straight-through processing is built to catch what shouldn't go through: an unusual beneficiary, a format exception, a sanctions hit. Only those are routed to a person, and getting that filtering wrong turns small exceptions into real losses.

Payment disruption is most expensive when volume peaks

Kyriba's CFO Risk Radar research puts a number on what happens when payments complexity goes unmanaged: 60% of finance leaders say a payment infrastructure disruption would directly damage financial performance.

That's the cost of the gap: volume and complexity both climbing, while only one of them shows up on the dashboard. Peak season pushes both numbers up together. The businesses least prepared are the ones treating volume as the only metric that matters, watching a dashboard that says everything is fine right up until it isn't.

Complexity shows up one exception at a time

Payment volume will keep climbing. That part is easy to predict; volume has increased for years. What's harder to predict is whether the complexity riding underneath that volume gets caught before it breaks a payment run, or after.

Ask it plainly: when the last payment exception surfaced, did your team fix the root cause so it can't recur, or just accept the reject and re-enter the payment through the bank portal?

Complexity does not announce itself the way volume does. It shows up in the exception queue, one payment at a time, and whether a team catches it there or downstream determines how much control they actually have over their own payment operations.

Liquidity and the 2028 debt maturity wall are rising just as fast. See the full picture at Ride the Waves.


Written By

Guillaume Metman

Guillaume Metman

VP Product Management - Payments & Bank Connectivity

Guillaume Metman is VP of Product Management for Payments & Bank Connectivity at Kyriba, where he drives product strategy across payment processing, bank connectivity, and fraud prevention. With more than 20 years of experience in software development, product management, and IT operations, Guillaume brings deep expertise in payments, Agile transformation, and enterprise-scale solution delivery. A recognized payments expert and thought leader on topics such as ISO 20022 migration and cross-border transaction banking, he is focused on building scalable, secure payment infrastructure that meets the evolving needs of global treasury and finance teams.

Related resources

Success Story

FLSmidth gains greater payment control and global cash visibility with Kyriba

Learn more
Blog

The invisible infrastructure that wins (or loses) corporate banking relationships

Learn more
Blog

Fraud is scaling faster. Payment fraud screening has to match.

Learn more