Enable Email-Based Expense Completion and Expense Policy Inquiry

Existing customers with environments created before 26B must enable the Email-Based Expense Completion Using Expenses Agent opt-in to use the following Expenses Agent capabilities. In 26B and later environments, this opt-in is enabled by default.

• Email-based expense completion, which allows employees to complete expenses through email conversations with Expenses Agent.

  See How Email-Based Expense Completion Works for details.

• Expense policy inquiry, which enables employees to ask natural language questions about corporate expense policies.

  See Upload Policy Documents for details.

You can enable these capabilities for a pilot group or for all users. Oracle recommends validating the configuration with a small group of users before enabling it organization-wide.

Prerequisites

Before enabling these capabilities:

• Complete the Expenses Agent configuration described in Core Configuration Steps.
• If you’re an existing customer, enable Touchless Expenses Using Document IO Agent for Expenses.
• If you plan to use enhanced policy inquiries, upload your policy documents to AI Agent Studio.

Enable the Required FSM Opt-In

Go to the Functional Setup Manager and enable Email-Based Expense Completion Using Expenses Agent.

Configure the Email-Based Expense Completion Profile Option

1. Sign in with the Application Implementation Consultant role.
2. Navigate to Setup and Maintenance.
3. Create the following profile option if it doesn’t already exist.

   Field	Value
   Profile Option Code	EXM_AGENTIC_EMAIL_PROCESSING
   Profile Option Name	EXM_AGENTIC_EMAIL_PROCESSING
   Application	Expenses
   Module	Expenses
   Start Date	5/1/2026

4. Save your changes.
5. Configure the profile option levels:
   • Enable the User level and make it updatable.
   • Optionally, enable the Site level if you plan to enable the capabilities for all users.

Configure Profile Values

1. Navigate to Manage Administrator Profile Values.
2. Search for EXM_AGENTIC_EMAIL_PROCESSING.
3. Configure the profile value based on your rollout approach:

   Rollout	Configuration
   Pilot rollout (recommended)	Enable the profile option at the User level and assign only selected pilot users.
   Organization-wide rollout	Enable the profile option at the Site level. Individual user assignments aren’t required.

4. Save your changes.