Auto-pause is a compliance feature in Float that can temporarily suspend a card if the cardholder fails to submit required transaction details. This FAQ covers how it works, how it's triggered, and how Admins and users can respond.
What is auto-pause?
Auto-pause is a setting within Submission Policies that allows Float to automatically pause a card when the number of non-compliant transactions exceeds the allowed limit.
A non-compliant transaction is one that is missing required information—like a receipt, vendor, or GL code—for more than 24 hours.
What does “Spend Compliance Policy Violation” mean?
This is the reason that appears when a card is paused due to exceeding the number of policy violations allowed in the Submission Policy. It's a signal that the cardholder needs to complete outstanding transaction details.
Does auto-pause affect both virtual and physical cards?
Yes. If a card—whether virtual or physical—is assigned a Submission Policy with auto-pause enabled, it can be paused if it exceeds the violation threshold.
How is the violation threshold defined?
The threshold is set in the Submission Policy by an Administrator. For example, a policy may allow up to three violations before a card is paused. Admins can adjust this threshold or disable auto-pause entirely.
Who can configure auto-pause?
Only Administrators can enable or modify auto-pause settings. This is done within the Submission Policy settings.
See Auto-Pausing Cards for instructions on how to set it up.
Will users be notified when their card is paused?
Yes. When a card is paused, the user will:
-
See a message in Float on their Overview screen
-
Be shown an action item telling them how many transactions are missing required details
-
Be directed to resolve those transactions in order to get their card unpaused
Can the card unpause automatically?
Yes. Once the cardholder brings their number of non-compliant transactions below the allowed threshold, the card will automatically become active again. No manual steps are needed once compliance is restored.
What if a transaction can’t be edited?
If a transaction has already been exported to the company’s accounting system, it may no longer be editable by the cardholder. In that case, the cardholder will need to contact their Administrator to update or mark the transaction as compliant.
Can an Administrator manually unpause a card?
Yes. Admins have a few options:
-
Turn off auto-pause for a specific card
-
Raise the violation threshold for that card
-
Manually resolve or mark exported transactions as compliant
These actions can bring the card back into compliance, which will automatically unpause it.
Can we override auto-pause for just one card?
Yes. Admins can apply an override to a specific card without changing the Submission Policy itself. This is useful when a single card needs an exception.
For steps, see Overriding Auto-Pause on a Specific Card.
Is auto-pause enabled on all cards by default?
No. Auto-pause must be enabled by an Admin in the Submission Policy assigned to the card. If it’s not enabled, the card will not be paused for policy violations, even if it has missing information.
Can Managers use auto-pause?
Managers can view paused cards and help users resolve violations, but only Administrators can configure or override auto-pause settings.