Skip to content
Theme
OnDevice Tools

GadgetsLaptops & PCs

ERP payments could close the gap between approving and moving money

A contributed piece for TechRadar Pro argues that enterprise resource planning systems should handle payment execution, not just financial oversight, so that approvals and transfers happen in one place.

Illustration of a finance dashboard inside an ERP system approving an international supplier payment

Key takeaways

  • A TechRadar Pro Perspectives article argues ERP systems should execute payments, not just approve and track them.
  • The author is the president and chief commercial officer at TransferMate Global Payments, a cross-border payments provider.
  • The piece says staff often leave the ERP to send funds through several bank portals and manage currency exchange separately.
  • It claims embedded payment and reconciliation tools would cut manual matching work and reduce pressure to add headcount.
In this article
  1. The news in brief
  2. Where the payment step still happens
  3. What embedded payments would change
  4. The cost of fragmented finance
  5. Why the argument matters

The news in brief

Enterprise resource planning software has become the hub that ties finance, HR, stock and sales into one shared database. A contributed article published by TechRadar Pro on 20 November 2026 argues that these systems still stop short of the moment money actually leaves the business.

The piece appears in TechRadar Pro's Perspectives channel, which carries arguments from industry figures rather than reported news. Its author is the president and chief commercial officer at TransferMate Global Payments, a cross-border payments provider. The central claim is that ERP payments should be built into the platform finance teams already use every day.

Where the payment step still happens

According to the article, an ERP is good at showing a business what it intends to spend, which vendors it relies on and which invoices have cleared approval. It can also forecast how a transfer will affect cash flow. The difficulty starts afterwards, when staff have to leave the system to carry out the instruction.

The writer describes a typical case. A finance leader signs off an overseas supplier payment inside the ERP, then switches to one of several banking platforms to send the funds, arrange the currency exchange and watch for completion. The record sits in one place while the transaction happens in another, which the author compares to a brain that has to hand its decisions to a second body before anything can be done.

What embedded payments would change

The proposal is to place payment execution and reconciliation inside the ERP itself. Rather than only flagging what needs to happen, the system would let finance staff complete the transfer without leaving the environment where the approval was given.

The argument is that this is a logical next step for software that started as accounting tooling and expanded into a platform for wider business processes. The more of the financial workflow an ERP covers, the more firmly it sits inside an organisation, and the fewer disconnected steps its customers have to manage themselves. The author frames this as a change in expectations rather than a new category of product.

The cost of fragmented finance

Illustration: banking, price, wallet, calendar and the labels Embedded Payments, Erp, Teams

Much of the piece focuses on the hidden workload created when payment instructions and bank activity live outside the main system. Teams spend time matching transactions, checking figures and chasing discrepancies, and the effort grows with each additional banking relationship and currency route.

As volumes rise, that burden can lead to extra hiring simply to keep pace, which pushes costs up alongside revenue. Connecting payment activity to financial data already held in the ERP, the author suggests, would cut repetitive manual work and allow operations to scale without expenses rising at the same rate. The case is presented as strongest for cross-border payments, where the underlying plumbing is complex but the experience for finance staff need not be.

Why the argument matters

For finance teams, the practical question is how many separate systems and logins sit between a decision and a completed payment. Fewer handoffs mean less reconciliation and a clearer view of where money is going and when. That is the benefit the article sets out, though it is presented as an argument rather than a demonstrated result.

Readers should note the source. TransferMate sells global payment services, so embedding payments in ERP software aligns with its commercial interests. TechRadar Pro states that Perspectives articles reflect the views of their authors and not necessarily those of the publication or Future plc. The piece contains no product launch, pricing, availability or performance figures.

Sources

  1. ERP has spent decades managing money. Is it time to start moving it?TechRadar

Tags

Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.