Finance leaders are rethinking cash. Once treated primarily as a back-office asset to be reconciled, protected, and reported, cash is now a performance lever. In a market shaped by higher capital costs, liquidity pressure, and faster decision cycles, the way an organization moves, monitors, and governs cash can influence resilience, investment capacity, and overall financial performance.
Yet many treasury operating models were not built for that reality. Organizations have modernized ERP environments, standardized finance processes, and improved reporting, but the workflows that actually execute payments and manage liquidity often remain outside ERP. Cash positioning, bank connectivity, approvals, payment release, and reconciliation may still run through banking portals, third-party tools, spreadsheets, and manual handoffs. That fragmentation limits treasury’s ability to optimize overnight interest earnings and savings through automated cash sweeps on business days, and automated fund transfers to keep accounts aligned to the target balances.
That separation creates a gap between financial insight and financial action. ERP may show what has happened or what is scheduled to happen, while execution takes place elsewhere. Treasury teams can spend valuable time reconciling information across systems, validating approvals, managing exceptions, and trying to understand current liquidity positions. The larger and more complex the payment ecosystem becomes, the more that friction affects performance.
There’s also a governance gap. Treasury policy, compliance controls, and execution logic are often distributed across documents, workflows, banking systems, and institutional knowledge rather than embedded directly into operational systems.
The cost of that friction is no longer limited to operational inefficiency. Idle balances, delayed transfers, inconsistent payment routing, and manual exception handling can affect interest income, borrowing costs, risk exposure, and forecasting accuracy. At the same time, CFOs and treasurers are being asked to strengthen controls, reduce fraud risk, and make faster decisions without adding complexity to the finance operating model.
This is why the traditional bank-centric treasury architecture is being reconsidered. Banks will always remain critical execution partners, but the enterprise needs stronger orchestration across banks, payment types, policies, and ERP-driven financial data. When financial data lives in one environment and executions are managed across many others, treasury loses the real-time context needed to optimize decisions. Organizations are increasingly looking for AI-driven bank statement processing across all banking relationships using same-day and previous-day data to improve real-time cash positioning and fund transfer decisions. Treasury teams also need real-time alerts on funding needs and fund balancing based on projected inflows and outflows. Compliance controls are shifting earlier into the process as well, with compliance alerts (like OFAC, workflows, control limits, etc.) and recommendations being applied at the system source level before bank transfers occur rather than through labor-intensive after-the-fact review.
A more effective model brings treasury and payment execution closer to ERP. In an ERP-centric approach, the ERP environment becomes more than the system of record. It becomes the operational control center for payments, liquidity visibility, approvals, policy management, and financial execution. This gives treasury teams a more centralized view of cash and payment activity while giving finance leaders stronger control over how policies are applied.
The shift is not simply about automation. Automating disconnected workflows can make legacy processes faster, but it does not necessarily make them more strategic. The greater opportunity is to connect financial data, treasury policy, and execution workflows so organizations can make better decisions at the point where cash is actually moving.
Policy-driven orchestration is central to that model. Treasury policies governing approvals, payment routing, liquidity thresholds, bank selection, exception handling, and risk controls often sit in static documents or institutional knowledge. When those policies are embedded directly into operational workflows, they can be applied more consistently across business units, banks, and payment methods.
This foundation enables treasury teams to operate with proactive, real-time, policy-driven intelligence rather than reactive after-the-fact controls. AI-driven capabilities can help identify anomalies, support fraud detection, recommend payment timing, improve cash positioning, and surface liquidity trends. As organizations move toward more autonomous and agentic treasury operations, governance becomes even more important. Policy-driven AI agents must operate within real-time compliance, approval, and auditability frameworks so that automation strengthens financial control rather than bypassing it. In AI-driven treasury environments, policy guidance, alerts, and recommendations must evolve continuously alongside operational conditions rather than relying on periodic manual reviews and after-the-fact validation.
For treasury teams, ERP-centric payments and treasury stakeholders can change the day-to-day operating model. Teams gain better visibility into cash and liquidity positions, reduce manual reconciliation, streamline approvals, and improve payment lifecycle control. They can also respond faster to exceptions, funding needs, and shifting market conditions because execution is connected more directly to the data that informs financial decisions.
For CFOs, the impact is broader. Better treasury orchestration can improve working capital discipline, reduce operational risk, strengthen governance, and create more confidence in liquidity decisions. In high-interest-rate environments, it can also help organizations better manage the relationship between idle cash, borrowing needs, and investment opportunities.
Technology is evolving to support this transition. ERP-centric treasury and payment platforms are helping organizations centralize execution, improve visibility, and connect payment workflows more directly to enterprise systems. Solutions such as 22nd Century Technologies’ Payment Gateway platform, built on native Oracle Cloud technologies, reflects this direction by supporting payment visibility, bank connectivity, secure processing, reporting, AI-enabled fraud detection, and policy-driven treasury operations within an ERP-centric model.
ERP transformation has already modernized how finance teams record, report, and analyze financial activity. The next phase is modernizing how organizations execute and govern financial operations in real time. Those that integrate ERP-centric execution with policy-driven, AI-governed treasury operations will be better positioned to optimize liquidity, strengthen control, and operate with greater financial agility. This would extend native cash management capabilities directly into the ERP environments where finance teams already work – Oracle Fusion, Oracle EBS, NetSuite, PeopleSoft, Workday, SAP, and others – reducing reliance on standalone treasury systems.
By Dinesh Kumar, President, ERP Practice, 22nd Century Technologies
