This article answers common questions about Submission Policies in Float, including how they work, how they're assigned, and what happens when a transaction doesn’t meet policy requirements.
Who sets up Submission Policies?
How many Submission Policies can we have?
Can Spenders choose a Submission Policy?
What do “Required,” “Not Required,” and “Hidden” mean?
Can we limit which vendors or GL codes cardholders can select?
What is an amount threshold?
What happens when a transaction is non-compliant?
What notifications do Spenders receive?
Can Submission Policies be changed after a card is issued?
Do policy changes affect past transactions?
Who sets up Submission Policies?
Only Float Administrators can create and manage Submission Policies. These are usually members of your Finance, HR, or IT teams.
Admins define which information (e.g. receipts, descriptions, GL codes) is required for each transaction type and can assign different policies to different teams, cardholders, or spend categories.
How many Submission Policies can we have?
It depends on your Float plan:
-
Essential Plan: Supports one default Submission Policy for the entire account
-
Pro Plan: Allows multiple Submission Policies that can be applied to different teams, cardholders, or spend types
If you're on the Essential Plan and would like to enable more flexibility, contact support@floatfinancial.com to learn about upgrading.
Can Spenders choose a Submission Policy?
Yes, if your organization is on the Pro Plan and your Admins have enabled it. When submitting a Spend Request, Spenders may see a list of available Submission Policies and be asked to choose the most appropriate one based on their upcoming expense.
If you’re not sure which policy to select, we recommend reaching out to your Float Administrator for guidance.
What do “Required,” “Not Required,” and “Hidden” mean?
Each transaction field in a Submission Policy can be configured in one of three ways:
-
Required – The Spender must complete this field for the transaction to be considered compliant
-
Not Required – The field is optional but available to fill in
-
Hidden – The field won’t appear to the Spender at all
Can we limit which vendors or GL codes cardholders can select?
Yes. Administrators can apply field restrictions in Submission Policies to control which values are available to cardholders. See Submission Policy Field Restrictions for more details.
What is an amount threshold?
Admins can set thresholds to make certain fields required only for transactions above a specific amount.
For example, you might configure the policy to require a receipt only if the transaction is over $75. Transactions under that amount won’t need the receipt to be considered compliant.
What happens when a transaction is non-compliant?
A transaction is non-compliant if it’s missing one or more required fields for more than 24 hours. These transactions:
-
Are flagged in the system
-
Appear with a grey compliance icon
-
May cause the associated card to be automatically paused (if the Submission Policy includes auto-pause settings)
What notifications do Spenders receive?
Spenders receive notifications in Float when:
-
Their transaction is non-compliant
-
Their card has been paused due to policy violations
-
Their card is unpaused after compliance is restored
-
Their assigned Submission Policy has been updated
Notifications help ensure that cardholders are aware of any issues and can take corrective action quickly.
Can Submission Policies be changed after a card is issued?
Yes. Admins and Managers can change the Submission Policy assigned to any card at any time. Once changed, the new policy will apply to all future transactions on that card.
See : Changing the Submission Policy for an Existing Card
Do policy changes affect past transactions?
No. Updating a Submission Policy affects new transactions going forward. It does not retroactively re-validate or re-flag past transactions.