Enterprise software knows where the money should go. Moving it is the gap
According to TechRadar, ERP software already shapes how businesses spend, but a gap remains between deciding on payments and actually making them.
TechRadar argues in a feature this week that enterprise resource planning software, usually called ERP, has become the central nervous system of many companies. The outlet describes ERP as a centralized system that links core business functions such as finance, human resources, inventory and sales through a shared database.
According to TechRadar, these systems now play a major role in how organizations manage suppliers, approve spending, forecast cash flow and make financial decisions. The piece compares the software to a brain that coordinates the parts of a body so that the whole business runs as one connected unit.
The article's central point is a gap between understanding and acting. TechRadar says an ERP can determine what a business needs to buy and which suppliers it should use, yet the step of actually moving the money is still treated as a separate task. The outlet asks whether that final step is ready to be folded into the same platforms.
The source material does not report a new product launch, a company deal, a survey or specific figures. It does not describe a particular customer or implementation. The discussion is a general argument about where enterprise software is heading, rather than a report on a single event.
Background
Enterprise resource planning grew out of earlier systems for manufacturing planning and inventory control. Through the late twentieth century, large companies adopted integrated software suites in which a shared database stored records for accounting, payroll, purchasing and production. The appeal was consistency: one version of the truth for orders, stock and cash, instead of separate spreadsheets and systems that did not agree.
Over time, many of these platforms moved from servers inside a company's own data center to cloud services delivered through subscriptions. Vendors also added modules for procurement, expense management, supply chain analytics and reporting, often connecting to outside services through application programming interfaces.
Moving money has traditionally been handled somewhere else. Companies typically rely on banks, payment networks, treasury management systems and dedicated accounts payable tools. Payments must be authorized, routed through banking rails, matched against invoices and reconciled once they clear. Each step carries controls designed to prevent fraud, duplicate payments and errors. That separation has been deliberate, since payment authority is one of the most sensitive functions in any organization.
Because of this history, the question of whether ERP software should execute payments as well as plan them touches on long-standing habits in finance departments, banking relationships and internal controls. The debate is less about technical possibility than about where accountability should sit when money leaves a company.
Why it matters
Finance teams already rely on ERP systems as a source of truth, so the idea of connecting planning directly to payment has obvious appeal. If a system can see an approved purchase, the right supplier and the available cash, an extra step of re-entering the same information in another tool looks like wasted effort. Shorter gaps between decision and payment could reduce late fees, improve supplier relationships and make cash forecasts more accurate.
The shift also raises the stakes. A platform that both recommends and releases payments concentrates authority in one place. Access rules, approval workflows and audit trails would need to be strong enough that no single error or compromised account could move funds unchecked. Smaller firms, which often lack dedicated treasury staff, might benefit most from automation, but they may also be the least equipped to supervise it.
For software vendors, the question is commercial as much as technical. Payments carry different economics than licenses and subscriptions, and they bring regulatory and banking obligations. How companies answer this question will influence which vendors become trusted financial infrastructure and which remain planning tools.
What to watch
Watch whether ERP providers describe payment features in concrete terms, including who approves transactions, how exceptions are flagged and how errors are reversed. Clear answers to those questions will matter more than broad promises about efficiency.
Also watch how banks and payment networks respond. Their participation will determine how smoothly software can connect to the rails that actually settle transactions. Finally, pay attention to audit and compliance guidance from finance professionals and regulators, since their standards will shape how much autonomy businesses are willing to give their software.
Viewpoints
Commentary from our columns: three angles on this story.
The Ledger the business angle
Every finance chief knows the frustrating moment when an approved purchase sits in one system while the payment waits in another. TechRadar's framing points at that seam, and it deserves attention. A company that can see what it needs, from whom, and at what cost has already done most of the hard thinking. Stopping short of paying feels like leaving value on the table.
The business case is easy to state: fewer manual handoffs, faster settlement, fewer chances for a payment to drift out of step with the budget. But the economics only work if the savings outweigh the new risks and the cost of building trust. Vendors that add payments will need to justify pricing on outcomes, not features. Buyers should ask what happens when a payment fails and who absorbs the cost. The companies that answer those questions plainly will be the ones that win the contracts.
The Builder the engineer's view
From an engineer's seat, the appeal of connecting planning and payment is obvious. Data already lives in the ERP, so moving an approved invoice to a bank should be a short hop. The hard part is everything around that hop. Idempotency, retries, partial failures, currency rules, bank cutoff times and reconciliation all have to behave correctly when networks fail halfway through a batch.
I would want the payment path designed as its own service with narrow permissions, clear logs and a way to pause without breaking the rest of the system. Keeping the planning core and the money-moving component loosely coupled makes both easier to test and easier to audit. Tight integration sounds elegant until one bad release affects both forecasting and disbursement at once. Good engineering here is mostly about boundaries.
The Skeptic open questions and weak points
It is worth asking why the gap has persisted for so long. Companies have kept planning and payment in separate tools for reasons beyond inertia. Banks, auditors and internal controllers often insist on distinct roles, and that separation is itself a safeguard. An argument that the software can see everything, so it should also act, deserves scrutiny before anyone accepts it.
The open questions are practical. Who is accountable when an automated payment is wrong? How do approval rules survive a vendor update or a staff change? What happens to smaller companies that adopt the feature without a finance team to supervise it? The article raises a fair question, but the answers will decide whether this becomes a convenience or a new point of failure.