Core Configuration Steps

Use this section as your sequential implementation framework to configure Expenses Agent from feature enablement through user access. The tasks are arranged in the required execution order, from feature enablement and business unit readiness to security provisioning, technical prerequisites, and user navigation.

Following this order helps ensure prerequisites are completed before downstream features depend on them, reducing configuration issues and application errors.

Along the way, you’ll also complete required technical tasks, including deploying descriptive flexfields (DFFs) and creating the search index, to help ensure the Expenses Agent pages load correctly and expense items appear in search.

Key Considerations

• Customer type entry point: New customers typically have Expenses Agent enabled by default. Existing customers must opt in to the feature within the Financials offering.
• Business unit enablement: Expenses Agent is enabled for each business unit. This supports phased deployments but requires verifying the readiness and configuration of each business unit before activation.
• Receipt processing: Employees forward receipts by email instead of creating expense items manually. Users must register their forwarding email addresses in their user preferences so Expenses Agent can associate incoming receipts with the correct user.
• Security prerequisites: Administrators must enable the required integration profile option before configuring security roles.
• Technical dependencies: Deploy the required descriptive flexfields (DFFs) and create the search index before user testing to prevent blank pages or missing search results.

The following sections walk you through each configuration task in the order it should be completed.