Oracle Fusion Expenses Agent: How Touchless Expense Reporting Actually Works

Nobody enjoys filling in an expense report. Oracle's Expenses Agent aims to remove the form entirely: charge the expense, forward the receipt, and let the agent do the rest. Here is what it genuinely does, what you have to configure first, and where human review still belongs.

Expense reporting is one of those processes everybody agrees is broken and nobody prioritises fixing. Employees delay submitting because the form takes twenty minutes they do not have. Finance chases them. Approvers rubber stamp reports they have not really read. Auditors sample a handful and hope the rest were fine. Meanwhile card charges age quietly in the background.

Oracle's Expenses Agent is aimed directly at that cycle. It is part of what Oracle calls Touchless Expenses, and it became generally available for Oracle Fusion Cloud ERP in Release 26B alongside the Ledger Agent, Payables Agent and Payments Agent.

This article covers what it actually does, how the email flow works, what has to be switched on first, and where finance still needs to keep a hand on the wheel.

The basic idea: no form at all

Oracle describes the intended employee experience simply. You charge the expense and you forward the receipt. That is the whole task.

From there the agent extracts the key details from the receipt, matches it to the corresponding corporate card charge, validates the expense against policy, and moves it toward reimbursement. It flags only what looks like a genuine exception, and it keeps the employee updated on status.

The significant part is that an employee can complete an expense without logging into the application at all. For people who travel constantly and treat expense reporting as an unwelcome administrative tax, that is a meaningful change.

How email based expense completion works

This is the part worth understanding properly, because it is where most of the practical value sits.

An employee emails a receipt, a restaurant bill or a flight ticket for example, to the Expenses Agent. The agent processes it and creates the expense. If something required is missing, it does not simply fail. It replies by email asking for the specific detail it needs.

The information it can request and capture through that email conversation includes attendee names and emails, delegates, merchant name, dates, justifications, project, task, company, cost centre and spend authorisation. The employee replies to the template with the missing details and the agent adds them to the expense. Once everything is present, the expense is marked ready to submit, or submitted automatically if that has been enabled.

There are sensible limits documented by Oracle that are worth knowing before you promise the world to a client:

• Receipts should be clear attachments in JPEG, PNG or PDF format, with a maximum of 4 MB per receipt.
• Expense instructions should sit at the top of the email body, above signatures and forwarded chains, using clear wording such as setting the expense type to Meals.
• Text only emails with no real receipt attached are not the intended use.
• A maximum of two guided reply turns is supported, so the conversation is short by design.
• If the situation is genuinely complex, for example tax codes or project and cost centre validation issues, the agent directs the employee to the user interface to finish manually.
• The email subject becomes the default expense description if the body does not specify one.

That last group of points matters in a rollout. The agent is built to handle the ordinary majority quickly and hand off the awkward minority, rather than pretending it can resolve everything.

What else sits inside Touchless Expenses

The email flow gets the attention, but several supporting capabilities do the quieter work of keeping expense data clean and compliant.

• Projects: employees can allocate expenses to projects, provided the expense types are enabled for projects and the user has the right project privileges.
• Manual merge: a guided two item merge for duplicates, used when automatic matching does not catch that a card swipe and an e-receipt are the same transaction.
• Corporate card dispute management: employees can mark an expense as disputed, and a disputed expense cannot be submitted until it is resolved.
• Corporate card aging controls: administrators set age limits on card charges and can block cash expense submissions until overdue card charges are submitted, which reduces improper payments.
• Mark as cash: converts a cash e-receipt into a cash expense, from mobile or desktop.
• Policy enforcement: administrators set daily and single instance limits for meals, entertainment, accommodation, car rental and miscellaneous, with warning and error tolerances.
• Push notifications: employees are notified when corporate card charges are uploaded and when expenses are auto personalised.

Read that list again from a controls perspective rather than a convenience one. Aging controls, dispute handling, duplicate merging and policy limits are the mechanisms that stop touchless from meaning unsupervised.

What you need to enable first

This is where implementations go wrong, because the email experience depends on foundations being in place.

Touchless Expenses, the base Expenses Agent capability, must be enabled first. Expense policies and their related validations need to be configured, because the agent validates against them. Only then does email based completion make sense.

For the email capability specifically, Oracle documents a clear enablement path: opt in to the feature for email based expense completion using the Expenses Agent, then configure the associated profile option so it is enabled and updatable with the value set appropriately. You can set the profile at user level to run a controlled pilot with a selected group, or at site level for an organisation wide rollout.

Usefully, Oracle states that no new access requirements apply beyond standard Expenses application access. Enabling project allocation and changing policy configuration do require the appropriate implementation role.

The pilot path is the one to recommend. Running at user level first with a group of frequent travellers tells you quickly whether your receipt quality, policy configuration and card feeds are actually ready.

Where the business value really comes from

It is tempting to sell this as employee convenience. That undersells it.

The genuine finance value is timeliness. Expense processes fail not because reports are wrong but because they are late. Late submissions distort accruals, delay cost visibility, create a rush at period end and leave card charges aging. If forwarding a receipt takes ten seconds instead of twenty minutes of form filling, submissions arrive closer to the date the cost was incurred.

The second area is consistency of compliance. A policy applied by an agent on every single expense is applied more consistently than a policy applied by a busy approver on a Friday afternoon. That does not remove the need for review, but it changes what review is for.

The third is exception focus. If routine expenses progress automatically, the auditor spends time on the ones that genuinely look unusual rather than reading through hundreds that do not.

This is the same pattern we described for the general ledger in the Ledger Agent and continuous financial control. Move the routine along automatically, and give people back the time to think about the exceptions.

Where you still need controls

Automating expense capture does not remove the reasons expense fraud controls exist.

• Approval workflow still applies. Decide explicitly what auto submission means in your organisation and where approval remains mandatory.
• Policy configuration becomes the control. If your daily limits and tolerances are wrong, the agent will consistently apply the wrong rule.
• Duplicate handling needs attention. Automatic matching handles most cases, but the manual merge exists because it does not handle all of them.
• Audit sampling should not disappear. It should shift toward the exceptions the agent flags, plus a sample of what it passed.
• Receipt quality drives accuracy. Extraction from a clear PDF and from a crumpled photograph are not the same thing.
• Data privacy deserves a thought. Receipts arrive by email and may contain personal information, so consider how that mailbox is governed.

What this means for consultants

The Expenses Agent does not replace Expenses configuration knowledge. It depends on it.

Somebody still has to design expense types, policy limits and tolerances, corporate card programmes and feeds, project allocation rules, approval routing, and the accounting behind it all. The agent sits on top of that configuration and applies it faster and more consistently.

What changes is the shape of the conversation with the client. Instead of walking through screens, you are asking how the policy should behave, what should auto submit, what must always be reviewed, and how the organisation will audit an automated flow. That is a more senior conversation, and it is worth being ready for it.

If you are learning Oracle Fusion Financials, Expenses is a good module to understand deeply for exactly this reason. It is small enough to master and it now demonstrates the full pattern of an agent working on top of solid configuration.

Frequently Asked Questions

The bottom line

The Expenses Agent is one of the easier agents to justify, because the pain it addresses is universal and the measure of success is obvious. Are expenses submitted sooner, are policies applied more consistently, and do reviewers spend their time on the items that deserve it.

It is also a good reminder of how these agents work in general. The agent is only as good as the policy configuration, card setup and approval design underneath it. Touchless does not mean unmanaged, and the organisations that get the most from it will be the ones that treated the configuration seriously before switching the agent on.

Our Oracle Fusion Financials training covers Expenses alongside the wider Financials stack, with live sessions and real implementation scenarios.

Sources

Agentic AI in ERP, four agents you can use today, Oracle Fusion Insider, June 2026.

What is Expenses Agent and what problem does it solve, Oracle Help Center.

Expenses Agent for Email-Based Expense Completion, Oracle Fusion Cloud Financials 26B What's New.

Note: Oracle updates these capabilities every quarter. Confirm the exact behaviour, opt in steps and prerequisites for your own release before planning a rollout.

Official reference: Oracle Fusion Cloud Financials (official)