1. Detailed Adoption Guidance: Expenses Agent
  2. Validation and Testing

Validation and Testing

After completing the setup, validate the configuration.

Configure Pilot Users

Here's how you can create and run a pilot program in a test environment before enabling Expenses Agent for all users.

  1. In the Setup and Maintenance work area, go to the Manage Profile Options task.
  2. Create the EXM_TOUCHLESS_EXP_DOCIO profile option used for pilot testing and ensure it’s enabled and updatable at site and user levels.
  3. Add it to the ORA_FND_AUTH_REST_ACCESS profile category.
  4. In Manage Administrator Profile Values, set:
    • Site to N
    • User to Y for specific pilot users (bulk import supported)
  5. Save your changes.

Configure Testing Notifications

Here's how you can configure a test email so pilot notifications don’t reach real users:

  1. In the Setup and Maintenance work area, go to the Manage Standard Lookups task.
  2. Create a new lookup type as follows:

    • Lookup Type: EXM_AUTO_APPROVAL_PREF

    • Meaning: Test email setup

    • Description: Lookup type configuration for test email setup

    • Module: Expenses

    • REST Access Secured: Secure

  3. Add lookup code as follows:
    • Lookup Code: DIGEST_TEST_EMAIL
    • Meaning: (your designated test email address)
  4. Save your changes.

Test Prerequisites

Before testing, confirm:

  • Expense templates and supported expense types are configured.
  • E-receipts setup is complete
    • Configure receipt forwarding to the designated email address.
    • Schedule the required processing jobs.
    • Follow best practices (for example, clear image resolution and one receipt per email).
    • Verify that expenses are created and notifications are received.
  • If using corporate cards:
    • Verify that the corporate card program exists.
    • Review MCC mappings to ensure transactions default to correct expense types.

Test Automated Expense Creation

  1. A pilot user uploads a receipt using the mobile application.
  2. The system processes the receipt.
  3. Receipt information is extracted automatically.
  4. An expense item is created.
  5. The expense is added to an expense report.

Functional Testing Checklist

Verify:

  • Completed expenses are included in a report without manual intervention.
  • Expense types match expected MCC mappings (for corporate card).
  • Submission timing aligns with user preferences.
  • Notifications trigger and approval workflows behave correctly for automatically submitted expenses.

Related Topics