One of the things many organizations underestimate is just how difficult they sometimes make it for money to move.
From an executive perspective, revenue can appear relatively straightforward. A customer is billed, the customer pays, and the organization receives the money. We measure the result through receivables, collections, days outstanding and other financial metrics, so naturally that is where much of the attention goes.
But those numbers only tell us what happened. They do not always tell us why.
What interests me much more is what happens between the point when a customer is ready to pay and the point when the organization actually receives the money. That is where the real operational story exists, and in many organizations, it is far more complex than leadership realizes.
This matters because we often treat revenue problems as collection problems when, in reality, some of them begin much earlier as flow problems.
A customer may fully intend to pay, but the process available to them creates friction. Perhaps they need to call during business hours. Perhaps they have to navigate an online experience that is difficult to use. Perhaps the payment process requires an employee to get involved. Perhaps information must move through several disconnected systems before the transaction is truly complete.
None of those things necessarily looks like a major problem on its own. In fact, most of these processes probably work exactly as they were designed to work and in fact, that is part of the problem.
Organizations can become very good at operating around friction. Employees learn the workarounds. Customers adapt. Finance teams reconcile the exceptions. Contact centres absorb the calls. Accounts receivable teams follow up when payments do not arrive. Eventually, the friction becomes normalized.
And once that happens, leadership may see the cost of the process without necessarily seeing the process itself.
Revenue does not move in a straight line
When I speak with organizations about payments, one of the most useful exercises is simply to follow the money.
Forget the technology for a moment. Forget the payment product. Start with the customer.
The customer receives a bill or realizes that a payment is due. What happens next?
Can they pay immediately? Can they pay using the channel they prefer? What happens if they have a question? What happens outside normal business hours? What happens if the digital channel does not work for them? Does someone need to take the payment manually? Once the payment is completed, where does the information go? How much additional work is required internally before the transaction is fully processed and reconciled?
When you start asking those questions, the payment process often stops looking like a transaction and starts looking like a journey.
That distinction is important.
The transaction itself may take seconds. The journey around it may involve multiple systems, departments, people and decisions. That is where money flow starts to slow down.
Looking at the Wrong End of the Problem
In my experience, many organizations spend too much time looking at what happens after revenue becomes a problem.
They look at overdue balances. They look at collection activity. They look at reminder strategies. They look at staffing requirements. They ask how theycan collect faster or improve accounts receivable performance.
Those are all legitimate questions.
But I think an equally important question is: what happened before the payment became overdue?
Was the customer actually given a simple opportunity to pay when they were ready?
- Could they pay after hours?
- Did they have to wait for an employee?
- Was there unnecessary friction in the process?
- Did they try to pay and abandon the experience?
- Did the organization even know that happened?
That last question is especially interesting because some of the most important payment friction is invisible.
If a customer encounters an error, gives up and comes back three days later, the organization may never record that as a failed payment. If someone wantsto pay at 9:30 at night but there is no available process for doing so, then there will be no system event showing that revenue was delayed.
Nothing technically failed.
The money just did not move.
That is why looking only at completed transactions gives organizations an incomplete picture of payment performance.
Operational Friction Eventually Becomes Financial Friction
One of the reasons I have become increasingly focused on payment flow is that operational inefficiency and financial performance are much more closely connected than they sometimes appear.
Consider something as simple as a payment being taken by an employee over the phone.
That process may work perfectly well. The customer pays. The transaction is successful. The organization receives the revenue.
But now look at the broader flow.
An employee had to be available. The customer may have waited on hold. The interaction took several minutes. Payment information needed to be handled securely. The whole transaction process may have created PCI compliance considerations, in addition to additional reconciliation or system updates.
Multiply that across thousands of transactions and suddenly what looked like a simple payment method becomes a meaningful operational process.
This is where executives need to be careful about defining success too narrowly.
A successful transaction does not necessarily mean an efficient payment flow.
The same principle applies to digital payments, reminders, recurring payments and virtually every other payment channel. The important question is not simply whether the technology works. It is whether the entire process allows money to move with the least unnecessary friction possible.
Complexity Usually Develops Slowly
Organizations do not deliberately build complicated payment environments.
Most complexity accumulates over time.
A department adopts one solution because it solves an immediate problem. Another business unit uses something different. A manual process is added to handle exceptions. A new payment channel gets introduced. An acquisition brings another system into the environment. A workaround that was supposed to be temporary becomes permanent.
Each decision may be perfectly reasonable on its own.
The problem appears when you look at all of them together.
You may now have multiple ways of collecting money, different processes for different departments, employees performing tasks that customers could complete themselves, and systems that do not communicate particularly well with one another.
From inside the organization, everyone understands their piece of the process.
From the customer’s perspective, however, there is only one question: how easy is it for me to pay you?
That gap between the internal view and the customer view is where a lot of payment friction lives.
This is Where Payment Flow Intelligence Becomes Useful
The idea behind the Payment Flow Intelligence Framework™ is relatively simple: before trying to optimize a payment technology, understand how the money is actually moving.
That means looking across the entire process rather than evaluating individual payment channels in isolation.
Where does the customer start? Where do they encounter friction? Where does an employee become involved? Where does information move manually? Where are there delays? Where are the security or compliance considerations? Where do exceptions occur? And what happens after the transaction is completed?
The objective is not to eliminate every human interaction or automate everything simply because automation is available.
It is to understand which parts of the process are genuinely creating value, and which parts exist primarily because that is how the organization has always operated.
That difference matters.
Good payment modernization should not begin with technology. It should begin with understanding payment flow.
Revenue Preservation
This is an area I think deserves much more attention.
Organizations spend enormous effort trying to recover revenue once it becomes overdue. There are collections teams, reminder programs, outbound calls, letters and increasingly sophisticated digital engagement strategies.
But some percentage of that effort may have been avoidable if the customer had been able to complete the payment more easily earlier in the journey.
That does not mean every overdue payment is caused by friction. Clearly, it is not.
But I think executives should be asking whether their payment environment is doing everything possible to capture customer intent at the moment it exists.
If somebody is ready to pay, the goal should be to make that transaction as easy, secure and immediate as reasonably possible.
The longer the distance between intent and payment, the greater the possibility that something gets in the way.
That is why ayment modernization is a revenue preservation strategy, not simply a technology strategy.
Follow the Money First
If I were advising an executive team on where to begin, I would not start with a product discussion.
I would take one common payment journey and follow it from beginning to end.
Start with the moment the customer decides to pay. Then look at every interaction that follows. How many steps are required? How many systems are involved? How many people touch the process? Where does the customer need help? Where does the organization perform work that could potentially be eliminated? What happens when something goes wrong?
Most importantly, ask why each step exists.
Some steps will absolutely be necessary. Others may have existed for so long that nobody has questioned them in years.
That exercise can reveal something financial reporting alone rarely shows: the places where revenue is being slowed down by the way the organization operates.
That is the broader opportunity.
Understanding how money moves is not simply about payments. It is about understanding the operational journey between customer intent and realized revenue.
Once you can see that journey clearly, you can start identifying where money gets stuck, why it gets stuck, and what the organization can do to help it move more securely, efficiently and intelligently.
To learn more about 24/7 IVR payments, automated payment processing and Datatel’s Payment Flow Intelligence Framework™, visit Datatel Systems or speak with our team about where payment friction may exist within your current customer journey.