Validation and Testing

After completing the setup, validate your configuration.

Note:

You can approach testing in one of two ways depending on your rollout strategy:

• Entire BU testing (all users): Enable the feature for all business units and validate behavior across all users.
• Pilot testing (selected users): Enable the feature for a subset of users within a business unit to validate in a controlled manner before broader rollout.

Configure Testing Notifications

During a pilot rollout, pilot notifications are the automated emails that Expenses Agent sends as part of the touchless expense workflow. These notifications aren’t application alerts or BPM approval notifications. They include:

• Receipt processing results: Confirms that a forwarded receipt was processed successfully or explains why processing failed (for example, an unsupported format, unreadable image, or file size limit).
• Requests for missing expense information: Conversational emails asking employees to reply with information such as the business purpose, cost center, or attendees.
• Credit card charge notifications: Alerts that a new corporate card transaction is available for matching.
• Overdue expense reminders: Reminds employees that a corporate card transaction hasn’t been submitted within the configured time frame.
• Autosubmission confirmations: Confirms that a completed expense report was submitted automatically.

Configure a designated test email address to redirect these notifications to a single mailbox during pilot testing. This allows administrators to validate notification content, delivery, and workflow behavior from a single mailbox instead of relying on individual pilot users’ inboxes.

Note: This redirect applies only to Expenses Agent-generated notifications. Standard BPM approval notifications continue to use your existing approval routing and aren’t affected by this configuration.

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

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.

If you configured a pilot rollout using the EXM_TOUCHLESS_EXP_DOCIO profile option, remove any associated site or user-level values after pilot testing is complete and they’re no longer needed. This prevents the pilot configuration from continuing to control user scope or navigation. See Configure a Pilot Rollout.

Test Prerequisites

Before testing, confirm:

• Expense templates and supported expense types are configured.
• E-receipt setup is complete
  • Configure receipt forwarding to the designated email address.
  • Schedule the required processing jobs.
  • Follow receipt forwarding best practices, including:
    • Use clear, supported receipt attachments.
    • Send one receipt attachment per email unless multi-attachment processing is enabled.
  • Verify that expenses are created and notifications are received.

• Pilot users have a valid email address configured in their user profile.

  Expenses Agent uses the email address to send workflow notifications. If a user doesn’t have a configured email address, notification-dependent scenarios, including automatic submission, can’t be fully validated.

• If using corporate cards:
  • Verify that the corporate card program exists.
  • Review MCC mappings to ensure transactions default to correct expense types.

Testing Without a Corporate Card Feed

If your test environment doesn’t have an active corporate card feed, you can still validate the following Expenses Agent capabilities:

• Email receipt forwarding and receipt processing.
• Email-based expense completion, including conversational replies and missing field updates.
• Out-of-pocket reimbursable expense creation (cash and personal card).
• Expense policy inquiries using AI Agent Studio.
• Automatic submission and approval routing.

Corporate card matching scenarios require corporate card transactions or representative test data.

Test Automated Expense Creation

Validate that Expenses Agent creates an expense automatically from a forwarded or uploaded receipt.

1. Upload or forward a valid receipt.
2. Verify that the receipt is processed.
3. Verify that the receipt information is extracted automatically.
4. Verify that an expense item is created.
5. Verify that the expense is added to an expense report.

See Enable Automatic Expense Submission.

Test Email-Based Expense Completion

Validate the complete email workflow:

1. Forward a valid receipt.
2. Verify that an expense is created.
3. Verify that Expenses Agent requests any missing required information.
4. Reply with the requested information.
5. Verify that the expense is updated.
6. Repeat until the expense is complete.
7. Verify that the expense is marked Ready to Submit or automatically submitted, depending on your configuration.

Also verify that unsupported updates direct employees to Oracle Expenses.

See How Email-Based Expense Completion Works for details.

Functional Testing Checklist

Verify that:

• Completed expenses are included in a report without manual intervention.
• Expense types match the expected MCC mappings for corporate card transactions.
• Submission timing aligns with user preferences.
• Notifications are delivered as expected.
• Approval workflows behave correctly for automatically submitted expense reports.
• Required descriptive flexfields (DFFs) have been deployed successfully.
• The Expenses search index returns the expected results.