Getting Started with Oracle Payables Agent: Inbox to Invoice, Touchlessly

Oracle’s been moving quickly with its agentic finance capabilities, and the Payables Agent is one of the more practical outcomes so far. If you’re looking after accounts payable or running a shared services function, it’s worth taking a closer look at what it can do and what’s involved in getting up and running.

The Payables Agent is focused on the day-to-day reality of accounts payable, helping with invoice intake, compliance and control. It works to take invoices from wherever they come in and move them through to payment-ready with as little manual handling as possible. It sits alongside a wider set of Oracle AI agents across Payments, Expenses, Ledger and Customer Payments, each one aimed at a specific finance outcome.

At the heart of it is Document IO, which handles invoice ingestion across different channels and formats. It routes everything through a consistent process and flags anything that needs a closer look, so exceptions can be picked up and dealt with quickly.

Document IO works a bit differently to traditional approaches. It reads the whole invoice rather than picking out individual fields, then extracts and maps the information straight into the right attributes in Oracle Fusion. It can handle different formats, multi-page documents and multiple languages without needing templates set up for each supplier, and you don’t have to change how invoices are sent in, as your existing email channels can stay as they are.

The Streams UI gives you a single place to keep on top of everything, bringing together all your active invoice streams. You can quickly see what’s coming in, what’s already been processed, and what needs attention. Out of the box, there are two streams available. The first covers invoice image documents, handling supplier invoices sent by email in different formats, across multiple pages and languages. The second is partner e-invoice integration, which connects to e-invoices via Thomson Reuters. That one does require a commercial agreement with Thomson Reuters to get started.

Converged streams bring your existing channels into the same view as well, including bulk uploads and manual entry. It means you get a single, consistent way of seeing and managing every invoice type in one place.

For suppliers with a consistent invoice layout and high volumes, document training makes things even smoother. You set the format up once, the system extracts the data using GenAI, you check and save it, and that format is then recognised going forward. After that, every invoice in the same layout is processed automatically, without the need to retrain.

All of that is handled automatically in the background, with policy-driven validation, anomaly detection, PO matching, approval routing and budget checks applied to every invoice. A full audit trail is maintained throughout. Anything that needs attention is surfaced in the Invoice List UI, giving you a single place to manage invoices, handle exceptions and respond to queries. It means your team can focus their time where it really matters, rather than working through everything manually.

So, how do you get started? The Document IO Agent is already switched on by default, so there’s nothing you need to enable. From there, it’s really about setting up three key areas: where your invoices are received, how your streams are connected into the Streams UI, and, for higher-volume suppliers, putting a bit of time into training the system to recognise their invoice formats.

The best way to approach it is to take things in stages. Start with getting your invoice ingestion set up, then bring in converged streams and training, and finally test and refine at scale across different formats and volumes.

Stepping back, this is really about making day-to-day accounts payable that bit easier. A lot of the routine work is taken care of in the background, so your team can spend more time on the things that genuinely need their input. If you’re already using Oracle Fusion, it’s definitely worth exploring what this could look like in your own environment and where it might take the pressure off your team.

Please note all screenshots are the property of Oracle and are used according to their Copyright Guidelines

Oracle Expenses Agent: The Touchless Future of Employee Expense Management

With Release 26B, the Oracle Expenses Agent is now generally available to all customers. There are no promo codes or pilot requirements to worry about. If you are using Oracle Fusion Cloud Expenses, you can start using it straight away. The Expenses Agent is part of a much broader set of Oracle-built agents embedded across Fusion Applications, alongside Oracle AI Agent Studio for building your own agents, AI Workflows, and an AI Agent Marketplace for partner solutions. It is included as part of your existing Fusion Cloud Expenses licence and is updated by Oracle each quarter, so you continue to benefit from ongoing enhancements without additional effort.

Across the Financials suite, Oracle has introduced a range of agents covering Payables, Expenses, Accounting Operations, Payments and Cash Processing. Each is designed to streamline processes, cut down cycle times and reduce the level of manual effort required from finance teams.

At its core, the Expenses Agent is designed to deliver a touchless experience. An employee simply makes a purchase and forwards the receipt by email, and the agent takes it from there. It reads the receipt, extracts the key details, matches it to the card transaction, creates the expense line, and submits it for approval. If anything is missing, it reaches out to the employee directly. Where everything is complete and compliant with policy, it moves straight through without any manual intervention. Employees can also interact with the agent using natural language to ask questions about policies and processes, making it much easier for infrequent travellers to find the information they need without unnecessary friction.

Oracle reports a 70-80% reduction in the effort required to create and submit expenses, along with 99% accuracy when matching card transactions. Just as importantly, compliance checks happen upfront rather than after submission. In a traditional process, approvers often have to send non-compliant claims back for correction. With the agent, expenses are checked before they reach the approver, helping to avoid rework and keep the process moving smoothly.

I have seen the Expenses Agent in action first hand, and it really brings the experience to life. Recently, I was out for lunch with an Oracle colleague who showed me how they submitted the expense. They simply took a photo of the receipt and, by the time we had walked up the escalator, the expense had already been checked against company policy and confirmed as compliant. It was then automatically matched to the corporate card transaction. It is a small moment, but it shows just how quick and effortless the process can be in practice.

The 26B release broadens support across all corporate cards and personal expense types, building on earlier versions that were limited to J.P. Morgan Chase corporate cards. It also introduces a number of enhancements, including email-based expense completion, the ability to query policies through Oracle AI Agent Studio, automatic receipt itemisation, mobile attachment of pre-approved spend authorisations, and more detailed location information within the Expenses page.

One point to be aware of is that the Expenses Agent uses a non‑premium large language model by default, so there is no additional cost to use it. If you find that performance does not fully meet your requirements, you do have the option to switch to a premium model. This can enhance capability, but it does come with a cost based on token usage.

Oracle recommends a structured, four-stage approach to adoption. It starts with laying the right foundations by simplifying expense types, refining policies and encouraging the use of corporate cards, as cleaner and more consistent data improves automation accuracy. From there, organisations can move to a phased rollout by business unit, typically starting with a pilot group before expanding more widely, supported by auto‑provisioning of the ERP Self Service role. The next step is to focus on employee experience and adoption, ensuring users are comfortable with receipt forwarding and interacting with the agent in natural language. Finally, it is about embedding operational best practices, such as enabling auto‑submission and using line-level attachments to support a smooth, efficient process.

There are a few practical points to be aware of before going live. If Touchless Expenses is not visible on the configuration page, you will need to opt into the relevant FSM feature before enabling it at business unit level. If you encounter a blank page after configuration, or the interface falls back to the classic landing page, it is worth reapplying any custom theme, checking the root menu configuration for stray spaces, and running the Retrieve Latest LDAP Changes and Import User and Role Application Security Data processes. If emailed receipts are not being processed, make sure the Create Expenses from Email Receipts process is scheduled to run at regular intervals, as it does not trigger automatically.

Looking ahead, the 26C release will introduce further enhancements, including support for Cost Allocations and Additional Information such as monthly and yearly limits, along with Cash Advance Applications and email-based completion for Classic Expenses customers who have not yet moved to Touchless. Beyond that, Oracle has outlined plans for a new Redwood Expenses page for employees and delegates, an Audit Workspace Agentic application, and expanded agent capabilities covering Cash Advance Requests, Mileage, Per Diem and more advanced attendee requirements.

If you have not yet looked at the Expenses Agent, it is worth starting with the basics. Taking time to simplify policies and increase corporate card adoption will deliver immediate improvements to your current process, while also setting you up to get the most value from the agent when you choose to enable it. If you would like to understand what this could look like in your organisation, now is a good time to start the conversation and explore how to get value from it early.

Please note all screenshots are the property of Oracle and are used according to their Copyright Guidelines

Oracle ERP Cloud Financials 26B

Don’t worry, I haven’t abandoned the world of HCM for ERP just yet. My enthusiasm for Oracle AI is very much alive, and with four new AI agents landing in Financials this release, I simply couldn’t ignore it. I’d never claim to be a Financials expert, but I do know how long ERP users have been asking for meaningful AI capabilities, and this release feels like a real response to that demand. Oracle has clearly leaned in, and there’s plenty here worth getting excited about.

The long awaited Ledger Agent brings an intelligent, AI‑powered experience to General Ledger, helping finance teams work more efficiently and proactively. It continuously monitors balances, journals, and transactions using configurable prompts, surfacing clear, contextual insights only when attention is needed. Accountants can ask natural language questions about balances, variances, journals, and process statuses, and receive precise, easy‑to‑understand explanations backed by correlated ledger and subledger data. By combining proactive monitoring, root‑cause insight, and seamless access to related ledger actions in a single guided experience, the Ledger Agent reduces time spent navigating multiple screens or compiling information manually, supports earlier detection and resolution of issues, and helps teams maintain accurate, up‑to‑date financial positions while respecting existing security and access controls.

The Payables Agent delivers a modern, AI‑driven approach to invoice processing, helping organisations move towards a truly touchless Payables experience. It automates invoice ingestion, compliance, and control across multiple sources and formats, using GenAI to reduce manual effort, improve data accuracy, and surface only the exceptions that need attention. With unified capture, automated attribute defaulting, intelligent anomaly detection, and a single, streamlined view for managing invoices, teams gain full visibility and control across the invoice‑to‑pay lifecycle. The result is faster processing, stronger compliance, reduced risk of errors or fraud, and improved supplier satisfaction, allowing Payables to shift from a reactive cost centre to a value‑generating function that supports better financial outcomes.

The Payments Agent introduces a smarter, more strategic approach to supplier payments by helping organisations optimise how and when they pay, rather than simply executing scheduled runs. Using AI‑driven insights and conversational guidance, it supports users across the full payment lifecycle, from evaluating payment options such as dynamic discounting and virtual cards, through creating and managing supplier offers, to executing and monitoring payments securely. By assessing the financial impact of different payment programmes in real time and translating decisions seamlessly into action, the Payments Agent improves cash flow, generates incremental financial benefits, and strengthens operational control. The result is a more proactive, insight‑led Payables function that reduces manual effort, highlights exceptions early, and enables finance teams to focus on working capital optimisation and stronger supplier relationships.

The Expenses Agent simplifies expense reporting by allowing employees to complete and submit expenses entirely through email, using natural language. Employees can forward receipts directly to the agent, which automatically creates the expense and prompts for any missing details, such as justifications, attendee information, or cost centres, via a simple email reply. Once all required information is captured, the expense is ready for submission or can be auto‑submitted in line with company policy. This conversational, email‑based approach reduces manual data entry, minimises errors, and cuts down on back‑and‑forth, accelerating reimbursements while improving compliance and delivering a far more intuitive experience for both employees and finance teams.

To wrap up, this has been my first step into writing about ERP Cloud Financials, and I’ve genuinely enjoyed exploring what Oracle is doing in this space, particularly around AI. I’d really welcome your feedback on this post, whether it’s what resonated, what you’d like to see more of, or where I could go deeper. If there’s interest, I’d be more than happy to write further blogs on Financials and continue sharing my perspective as these capabilities evolve.