Float gives Administrators and Managers flexible tools to manage company spending before, during, and after it happens. Understanding how Approval Policies, Submission Policies, and Transaction Review Policies work together, is key to building efficient controls without slowing teams down.
Each policy type serves a different purpose in the spend lifecycle:
1. Approval Policies: Control before spend
Approval Policies are used to control spend before it happens. You can create Approval Policies for new card and limit requests, Reimbursement requests and Bill submissions. This ensures that requests are approved before funds are made available.
These policies define who needs to sign off on card or limit requests based on conditions like:
[we mention card or limit requests here but not Reimbursement or Bills]
-
-
Team
-
Spend amount
-
Request type (recurring or temporary)
-
For example:
You can set up a policy where any travel request over $2,000 from the Sales team needs approval from a Director and a Finance Manager.
Approval chains can be simple or multi-step and can include:
-
-
Fixed approvers (specific individuals)
-
Dynamic approvers (based on the requestor’s manager or department)
-
Once a request is approved, the user can access their card or limit and make purchases.
Learn how to create Approval Policies by viewing the article Approval Policies Overview.
2. Submission Policies: Ensure required details are submitted
Submission Policies define what information users need to submit after a card transaction is made.
You can require:
-
-
Receipts
-
Descriptions
-
Vendor name
-
GL codes
-
Custom fields (like customer or project)
-
Tax Codes
-
Admins can choose how strict the policy is. For example, you might pause cards automatically if users miss a set number of submissions.
These policies help keep your reporting clean and accurate, especially when syncing with your accounting integration.
Learn how to create Submission Policies by viewing the article Creating and Editing Submission Policies.
3. Transaction Review Policies: Review spend after it happens
Transaction Review Policies allow Managers and Administrators to review settled transactions after the spend has occurred.
You can configure rules to trigger reviews based on:
-
-
Transaction amount
-
Team
-
These reviews are done after the transaction settles and are separate from submission tasks. Managers can review and approve transactions directly in Float, helping to catch unusual spend patterns or ensure policy alignment.
Note: Refunds, pending charges, and credits are not included in review workflows.
Learn how to create Transaction Review Policies by viewing the article Configuring Transaction Review Policies.