SoftTech AI Registry
Oracle · Oracle Fusion Cloud Expenses

Expenses Agent

Oracle documents Expenses Agent as the AI agent that orchestrates the Touchless Expenses experience: it receives emailed receipts, extracts expense details, creates and completes expense items, matches them with corporate card transactions, validates them against configured requirements and policies, follows up with employees by email for missing information, groups eligible expenses into expense reports and, where configured and compliant, submits those reports on a scheduled cadence into Oracle's downstream approval workflow.

Recorded characteristics

Function
Oracle states that Expenses Agent "processes receipts, extracts expense details, creates and completes expenses, matches expenses with corporate card transactions when applicable, and requests missing information from employees", and that, depending on configuration, it also supports automatic itemization, spend authorizations, expense allocation, accounting segments, spending limits and cash advance application. Oracle distinguishes Touchless Expenses (the employee experience and business outcome) from Expenses Agent (the AI agent that delivers it). Oracle describes a single orchestrating agent whose release-by-release features are surfaces of that one agent, and the Registry records it as one capability.
Data access
Employee-forwarded receipt emails and receipt images, extracted transaction details, Oracle Expenses expense items and expense reports, corporate card transactions, spend authorizations, cash advances, project and task allocations and configured accounting segments, and administrator-uploaded corporate travel and expense policy documents used to ground policy answers. Oracle states the agent does not use the email subject line to extract or update expense information.
Actions
Can take actions
External actions
Conditional
Human confirmation
Conditional
Permission basis
Not established
Administrative control
Oracle documents agent-specific controls: an opt-in under the Financials offering for existing customers; business-unit enablement, which Oracle states cannot be undone; the FSM opt-in "Email-Based Expense Completion Using Expenses Agent"; the profile option EXM_AGENTIC_EMAIL_PROCESSING set at user level for pilots or site level for wider rollout; a dedicated company email alias and the scheduled process that creates expenses from email receipts; configurable automatic submission; cash advance and authorization policies; key flexfield segments exposed for expense override; spending limits and policy enforcement settings; and uploading and publishing policy documents to the "Get Expense Policy Document" agent in AI Agent Studio. Oracle also documents the profile option ORA_ASE_SAS_INTEGRATION_ENABLED for integration provisioning.
Default state
Conditional
Availability
Documented for Oracle Fusion Cloud Expenses within Oracle Fusion Cloud Financials, delivered in the Redwood experience. Oracle release documentation traces the same agent across 25D (Touchless Mobile Expenses), 26A (expense completion and compliance enhancements), 26B (no promocode required, email-based expense completion, receipt capture and matching, policy inquiry moved into AI Agent Studio) and 26C (cost allocations, cash advance application). Oracle states new customers in 26B have the email-completion opt-in enabled by default while existing customers must enable it.
Licensing
Not established. No Oracle primary document reviewed states a licence, entitlement or additional charge for Expenses Agent.
External model or provider
Not established. Oracle does not identify a model or model provider for Expenses Agent in the documentation reviewed.
Limitations and uncertainty
Oracle does not document the runtime authorization identity of the agent, so permission basis is recorded as not established; administrator setup steps are not evidence of a runtime permission mechanism. Oracle documents that the email subject line is ignored; that issues which cannot be resolved by email require the employee to open Oracle Expenses; that manual merge is needed in rare cases where automatic matching cannot reconcile duplicates; that disputed corporate card expenses cannot be submitted until resolved and aged card charges can block cash expense submission; that cash advances apply at expense report level, not expense line level; that spend authorizations must be created in Standard Expenses rather than in the agent flow; and that business unit enablement cannot be undone. Oracle does not establish that the agent approves expense reports, reimburses employees, creates payments, moves funds, posts accounting entries or overrides policy. Oracle states that uploaded policy documents power self-service policy clarification today, with broader validation and enforcement over time; spending limits and policy enforcement are separately configured rules. Agent-specific audit or observability is not established.

Evidence