Overview

The Single Use Activity process provides users with a fast and secure way to complete necessary purchases when a legitimate transaction is unexpectedly declined. It acts as an emergency budget mechanism, allowing users to temporarily access funds while maintaining full approval and compliance control.

How it works

When a transaction is declined, the user receives a notification within the platform.

The notification includes an option to request a Single Use Activity for that specific transaction. 

If the user agrees, the system automatically: 

• Creates a Single Use Activity tied to the declined transaction. 
• Submits it for approval following the organization’s standard workflow. 
• Once approved, the user receives funds equal to the declined transaction amount. 

These funds are temporary and will expire if not used within a few hours.

Criteria for Single Use Activities

Single Use Activities are only created when a declined transaction meets specific criteria.

The system reviews the user’s transaction history and spending patterns to determine eligibility. For example:

• The user has a recent history of purchases at similar merchant categories (e.g., grocery stores). 
• The declined amount falls within a pre-configured threshold defined by the organization.

This ensures that Single Use Activities are only generated when the decline appears to be an isolated error rather than a potential control or policy breach.

Additional Notes

• Regular Should-Be-Business (SBB) expenses do not create additional activities. 
• Approval requests for Single Use Activities include the label “Business Expense” in the notification title, allowing reviewers to easily distinguish them from standard approval flows.