{"id":8276,"date":"2026-06-11T14:04:03","date_gmt":"2026-06-11T14:04:03","guid":{"rendered":"http:\/\/version1.thinktankdev.org.uk\/en-us\/?p=8276"},"modified":"2026-07-21T15:15:39","modified_gmt":"2026-07-21T15:15:39","slug":"unlocking-value-using-oracle-erp-ai-agents-2","status":"publish","type":"post","link":"https:\/\/version1.thinktankdev.org.uk\/en-us\/blog\/unlocking-value-using-oracle-erp-ai-agents-2\/","title":{"rendered":"Unlocking value using Oracle ERP AI Agents\u00a0"},"content":{"rendered":"

Following on from our previous webinar, \u2018Unlocking the power of Oracle AI: transforming Oracle HCM and SCM with next-generation agents<\/a>\u2019, we\u2019re now turning our attention to the opportunities Oracle AI Agents can unlock across ERP.<\/p>\n

In this blog,\u00a0key takeaways\u00a0will be shared\u00a0from our latest webinar, \u2018Unlocking Value with Oracle ERP AI Agents<\/a>\u2019, including an overview of the five new AI agents introduced in Oracle Fusion 26B and what they could mean for finance teams seeking greater efficiency, visibility and value.<\/p>\n

During\u00a0the\u00a0session, we ran a poll\u00a0asking which of those agents was most valuable to attendees.<\/p>\n

The Ledger Agent came top with 31% of votes, closely followed by the Expenses Agent (27%) and Payables Agent (25%). Cash and Payments Agents rounded out the rest.<\/p>\n

\"\"<\/p>\n

That spread tells its own story. Finance teams\u00a0aren’t\u00a0excited about one narrow use case.\u00a0They’re\u00a0looking at AI across the whole ERP landscape, from how invoices land in the system to how the general ledger gets\u00a0monitored\u00a0and queried.<\/p>\n

Here’s what the five agents do:<\/h2>\n

The Expenses Agent<\/h3>\n

The promise here is straightforward: no more form of filling. An employee makes a purchase and forwards the receipt. The agent then reads it, extracts the details, if a corporate card was used, it matches it to the charge, checks it against policy, and emails back if anything’s missing. The whole thing runs through a conversation rather than through a submission screen.<\/p>\n

I\u2019ve watched an Oracle colleague submit an expense for lunch from start to end before they’d reached the top of an escalator. That’s not a demo scenario, that’s the product being used in real time.<\/p>\n

One thing to note: although the Expenses Agent is available in 26B, email-based conversations still require a Service Request (SR) to be raised with Oracle first.<\/p>\n

The Payments Agent<\/h3>\n

Payments traditionally meant \u2018invoices come in, payment runs go out\u2019. The Payments Agent adds intelligence to that mechanical process.<\/p>\n

It comes with three assistants:<\/p>\n

The Payment Options Assistant looks at outstanding invoices alongside programmes like dynamic discounting and virtual cards, then calculates the financial benefit of each based on payment terms and cash position<\/p>\n

The Supplier Offer Assistant identifies where dynamic discounting makes sense for a specific supplier, drafts the offer, sends it and tracks responses<\/p>\n

The Payment Execution Assistant handles scheduling, monitors for failures and surfaces exceptions before they become problems<\/p>\n

Core features are available out of the box in 26B. More advanced insights still require a SR to Oracle.<\/p>\n

The Payables Agent<\/h3>\n

The Payables Agent focuses on making invoice processing as touchless as possible. Invoices arrive by email, PDF or e-invoicing channel. The agent then reads them, extracts the key data, defaults missing attributes like cost centers or general ledger (GL) accounts, and flags anomalies in real time. Accounts Payable (AP) teams move away from processing every invoice individually and focus instead on the exceptions the agent surfaces. This one isn’t generally available yet. It’s still an early adoption programme, so Oracle needs to be contacted to access it.<\/p>\n

The Cash Agent<\/h3>\n

The Cash Agent does the same pattern-recognition trick, but for bank statements and remittance advisers. It reads documents, creates receipts, matches payments to invoices and highlights where it can’t make a clean match. Focus can shift to exceptions rather than line-by-line processing.<\/p>\n

This was a late addition to 26B and is early adoption only \u2013 so, again, there\u2019s a need to contact Oracle to access it.<\/p>\n

The Ledger Agent<\/h3>\n

This is the one that came top of the poll, and it’s not hard to see why.<\/p>\n

The Ledger Agent sits across GL and works across three areas. Proactive monitoring uses configurable AI-based alerts to surface anomalies and unusual movements as they occur, rather than waiting for someone to run a report. Insights take those alerts and add a narrative (not just what has changed, but why). Natural language inquiry lets users ask questions in plain English across GL, payables and receivables data, without the need to navigate to separate screens.<\/p>\n

The Ledger Agent is available out of the box in 26B with no formal opt-in, though configuration is required to set up roles and access controls.<\/p>\n

Pricing:\u00a0what\u2019s\u00a0changing<\/b><\/h2>\n

Oracle announced a pricing\u00a0restructure\u00a0at AI World London in March. The formal start date\u00a0hasn’t\u00a0been confirmed, but\u00a0it’s\u00a0expected\u00a0in\u00a0June 2026.<\/p>\n

Under the old structure,\u00a0customising\u00a0an out-of-the-box agent made it a custom agent and therefore chargeable. That created a strange incentive\u00a0where\u00a0organisations\u00a0avoided the\u00a0customisation\u00a0they\u00a0actually needed.<\/p>\n

The new structure is simpler. Pricing is driven purely by the LLM you use:<\/p>\n