Prepare for Testing

Set up a controlled environment for evaluating Expenses Agent before rollout.

Choose a Testing Approach

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

Testing approach	Use when	Scope
Entire business unit testing	You’re ready to validate the configuration broadly	All users in enabled business units
Pilot testing	You want controlled validation before broader rollout	Selected users within a business unit

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:

Notification	What it does
Receipt processing results	Confirms that a forwarded receipt was processed successfully or explains why processing failed, such as an unsupported format, unreadable image, or file size limit.
Requests for missing expense information	Asks employees to reply with required information such as the business purpose, cost center, or attendees.
Corporate card charge notifications	Notifies employees that corporate card transactions are available for matching.
Overdue expense reminders	Reminds employees about corporate card transactions that haven’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.

Review Test Prerequisites

Before testing, confirm the following:

• General
  • Expense templates and supported expense types are configured.
  • Required descriptive flexfields (DFFs) are deployed.
  • The required processing jobs are scheduled.
• Email and Receipt Processing
  • E-receipt setup is complete.
  • Receipt forwarding is configured to the designated email address.
  • Pilot users have valid email addresses configured in their user profiles.
    Note: 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.

  • Receipt forwarding best practices are followed:

    • 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.
• Corporate Cards

  If you’re using corporate cards:

  • Verify that the corporate card program exists.
  • Review merchant category code (MCC) mappings to ensure transactions default to the 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.