Article
Payments
4 min read
Dondi BlackHead of Industry Advisory for Payments

In brief

  • B2B payment modernization is an adoption challenge: electronic rails exist, but checks persist when supplier workflows are hard to change.
  • Payment decisions increasingly happen in treasury, ERP and AP workflows, so banks need embedded, accessible capabilities.
  • Supplier enablement, connected payment data and reliable reconciliation help electronic payments work for both buyers and suppliers.

B2B payments does not suffer from a shortage of payment rails.

 

ACH is mature. Virtual cards continue to expand. Real-time payment networks are available. Wire capabilities are well established. Commercial payment platforms have become increasingly sophisticated.

 

Yet paper checks remain embedded in many corporate payment processes. That persistence points to a different modernisation challenge: the last mile of B2B payments is increasingly an adoption problem.

 

The recent partnership between Kyriba and Viewpost is a useful example. Rather than asking enterprises to replace their treasury infrastructure, the companies are integrating payment optimisation and supplier enablement into an existing treasury workflow, with the goal of migrating eligible check payments to electronic alternatives.

 

The signal here is the integration strategy: making digital payments easier to adopt where businesses already manage them.

Payment choice increasingly happens inside the workflow

 

For many businesses, payment execution begins long before a bank receives an instruction.

An invoice arrives. It is matched against a purchase order. Someone reviews and approves it. The supplier’s payment preferences are checked. A method is selected, the transaction is initiated and the payment is ultimately reconciled.

 

Treasury management systems, enterprise resource planning (ERP) platforms, accounts payable (AP) automation tools and vertical software increasingly coordinate that journey. They shape how information moves, which approvals are required and what options are presented at the moment a payment decision is made.

 

That changes the competitive position of banks and payment providers. Owning the rail does not necessarily mean owning the payment decision. The organization controlling the workflow can influence which method is used, when the transaction occurs, what information accompanies it and which financial institution executes it.

 

For banks, this means payment capabilities need to work inside the environments their business customers use. A strong rail can still be overlooked if it is difficult to access, poorly integrated or disconnected from the systems that initiate and reconcile payments.

Supplier enablement is part of the payment product

 

Moving a buyer from checks to electronic payments solves only one side of the equation. The supplier still needs to participate.

 

That can mean collecting and validating banking information, setting payment preferences, agreeing to virtual card acceptance, managing remittance details and adapting existing receivables processes. Suppliers may also need confidence that a new method will not create extra fees, delays or manual work.

 

At enterprise scale, those activities become significant operational work. A buyer may have thousands of suppliers, each with different capabilities and preferences. If enrollment is confusing or exceptions are difficult to resolve, teams may fall back on the familiar process—even when electronic options are available.

 

This helps explain why checks can persist after a business has modernized its own payment capabilities. Adoption depends on whether the change works for both parties.

 

Kyriba and Viewpost are addressing this friction by combining treasury workflow with supplier enrolment and payment optimization. The broader lesson for B2B payment providers is clear: supplier adoption should be engineered into the proposition. A faster or more efficient rail creates limited value if counterparties cannot or will not use it.

 

That calls for practical capabilities: straightforward enrollment, clear explanations of payment options, reliable validation of supplier details, support for different preferences and a manageable process for exceptions. Making those steps part of the product can reduce the work required to move a supplier from one method to another.

Reconciliation may matter as much as execution

 

Businesses rarely evaluate payments solely on whether money moved successfully. They also need to know what invoice was paid, which business entity initiated the payment, what fees were incurred, when the supplier received the funds and how the transaction should be recorded.

 

Payment modernization therefore requires data to travel with the transaction. If remittance information is incomplete, finance teams may still need to match payments manually. If data is inconsistent across systems, reporting and reconciliation can become harder even as payment execution gets faster.

 

ERP integration, data normalization, usable remittance details and automated reconciliation can create as much practical value as the payment method itself. They help make digital payments fit the end-to-end business process, from approval through accounting.

 

This is where the next competitive advantage in commercial payments may emerge from orchestrating existing rails around the business process rather than adding another rail. The goal is to make the right payment method usable, understandable and operationally efficient for everyone involved.

Three priorities for banking and payments leaders


  1. 1. Design around the AP and treasury workflow.
    Map where payment decisions actually occur. Identify manual steps, system handoffs and data gaps that prevent electronic adoption. Look at the full journey—from invoice receipt and approval to supplier payment and reconciliation—rather than focusing only on execution.

  2. 2. Treat supplier enablement as infrastructure.

  3. Enrolment, credential validation, payment preferences and exception management should be scalable capabilities, not one-time implementation activities. Track where suppliers drop out of the process and make it easier for them to understand and adopt available options.


  4. 3. Make payment capabilities embeddable.
    Banks should ensure ACH, virtual cards, real-time payments and other commercial services can be consumed inside treasury, ERP and software environments through APIs and consistent data models. Integration should carry the information businesses need to manage and reconcile the payment, not just initiate it.

  5.  

These priorities are particularly important for regional and mid-size banks. Strong payment capabilities can become less visible if customers increasingly interact through third-party treasury and AP platforms. Fragmented products and difficult integrations raise the risk that another provider will shape the payment decision.

Looking ahead

 

B2B payment modernization is entering a different phase. The market has created multiple effective ways to move money electronically. The larger opportunity now lies in making those capabilities easier to adopt inside the workflows businesses and suppliers already use.

For banks, processors and B2B payment platforms, the competitive question is increasingly straightforward: Can your payment capabilities participate naturally in someone else’s workflow?

The next generation of B2B payments will be won by organizations that make electronic payment the easiest operational choice, supported by supplier participation, connected data and reliable reconciliation.

For a broader look at how AI, platforms, workflows and real-time rails can become scalable business capabilities, download our executive guide, Payments at the Operating Core.

FAQs

Payment rails alone do not ensure adoption. Supplier enrolment, payment preferences, fees, remittance details and exceptions can add work, prompting businesses to keep familiar processes.