Organizations seeking more flexibility and sophistication in devising transaction fee and commission structures are increasingly turning to rules-based fees engines. Billing systems are designed to handle invoicing and collect payments, but they are limited in their ability to help companies create new fees and commissions.
Rules-based fees engines allow payment processors to stay competitive and profitable, enabling them to offer new value-added services, develop creative incentive programs, create new revenue streams, and respond quickly to market shifts. In a recent PaymentsJournal podcast, BHMI’s Chief Technology Officer Mike Meeks and Senior Program Director Cheryl Fitzgarrald spoke with James Wester, Co-Head of Payments at Javelin Strategy & Research, about the advantages of rules-based fees engines and who benefits from them.
Developing the Solution
Rules-based engines allow fees and commissions to be configured from any combination of attributes, such as the payment method used, the amount, the merchant category, and the time of day the transaction occurs. Unlike traditional billing systems, a rules-based fees engine provides the ability to measure and test the financial viability of new fees and commissions before they are implemented.
“Back in 2004, we were approached by one of the country’s largest debit networks, which was not able to introduce new products or new pricing strategies without long software development cycles,” said Meeks. “All of their rules for how they price things were embedded in code, which made it very slow and costly to roll out new structures and to respond to what their sales teams were asking them to do in a timely manner.”
“They needed a solution that was flexible and could meet unforeseen future requirements,” he said. “That’s what drove us to the concept of a rules-based engine and the kind of open-ended capabilities it would provide. For more than 20 years now, we’ve been implementing these solutions for companies all over the world.”
This solution gives companies the ability to be creative and innovative, supporting any business opportunity, client relationship, or product offering that marketing and sales bring to the table. It also speeds up time to market, as new fee and commission structures can be quickly configured and implemented.
“Research is showing that there is a requirement now in payments for companies to be able to pivot quickly, to be able to bring products to market quickly and to not necessarily be held hostage by those development cycles,” Wester said.
A modern rules-based fees engine should have the flexibility to create any type of fee or commission on any type of payment transaction. This includes card-based transactions as well as account-to-account and real-time payments. It should also have no limitations on the types of fees or commissions that can be configured and should allow for additions and modifications without requiring software changes or downtime.
Another important factor is that the system must be able to access payments data in real time, applying the appropriate fees or commissions while the transaction is still in flight. Finally, rules-based fees engines should provide companies with a real-time view of fee revenues, enabling them to analyze the financial impact of those revenues and easily determine if adjustments are needed.
Under the Hood
A rules-based fees engine integrates data from multiple sources. The most common way to access data from these sources is real-time APIs, but in some cases, automated file-based mechanisms are required, depending on what is supported by the originating data source.
“The typical sources that we see are credit and debit card transactions that an authorization system is writing to a transaction log file, a clearing system that creates a clearing file for POS dual message systems, and a card network that creates a settlement reconciliation file,” said Meeks. “A modern rules-based fees engine can use data from any and all of those sources to assess fees and commissions as a transaction is being processed.”
Once that data is collected, companies have discovered a wide variety of use cases for the technology. “The possibilities are unlimited,” said Fitzgarrald. “Some common use cases would include things like calculation of gateway fees, processing and service fees, and recurring fees. They are also used to calculate many different types of commissions. If you think about it, a commission is just like a fee, but the money goes the opposite way.”
Opening Up Creativity
Rules-based fees engines have allowed companies to be more creative with their services and pricing structures. Fees can vary based on time sensitivity, such as higher fees during peak business hours and lower ones during off-hours. Companies can also introduce fee models tied to loyalty programs or specific merchant partnerships, incentivizing behaviors that increase transaction volumes or customer loyalty.
Once a company implements a rules-based fees engine, the infrastructure allows them to better analyze and address important questions like which fees bring in the most revenue, which commissions provide the most incentive, and whether a particular service can be expanded or rolled out to other customers.
“One of the amazing parts of this is the approach to testing,” said Wester. “Testing is very difficult and time consuming. The idea that you can test a product or a fee, and pull it back if it doesn’t work, gives you a tremendous amount of flexibility.”
Any company that processes transactions and has a need to calculate fees and commissions can benefit from this technology. “Probably the single most important reason that I’ve heard for people adopting rules-based fee engines is that they are money makers,” said Fitzgarrald. “They allow the company to rapidly configure creative fee and commission models and let them pivot quickly in response to changing market conditions. All of this Is done without the cost and delay of code changes.”
Learn more about maximizing your pricing and fee structures.
The post How Rules-Based Fees Engines Drive Innovation appeared first on PaymentsJournal.
