Fall '26 edition: Prompt your finance

Join the webinar
Skip to main content
All playbooks

Card and spend-control fit review

Card limits that match reality. The assistant finds the cards that keep hitting their limit, the limits nobody comes near, and the policies spending has outgrown - then makes the change you authorize, on the card when one card is the problem and on the policy itself when a whole group has outgrown it.

How it works

  1. Compares every card's limit and policy against its actual spending pattern.
  2. Flags the mismatches in both directions: blocked spenders and oversized limits.
  3. Applies the change you authorize, on the card or on the policy, and shows how many cards a policy change reaches before it is made.

Common questions

Will it change card limits on its own?

No. It recommends. A limit changes only when you explicitly authorize it, only within your own Payhawk permissions, and the change is previewed first and recorded in the audit trail.

What happens when it changes a policy rather than a card?

A policy governs every card attached to it, so before you authorize anything the preview tells you how many cards the change reaches, names up to ten of them and counts the rest. If a card joins or leaves that policy in the meantime, the authorization stops being valid and you are shown the new picture instead.

Which policy settings can it change?

The spending controls: the budget, the daily and per-transaction limits, and whether cash withdrawals, ATM requests and online payments are allowed. Creating a policy, deleting one, choosing which policy new cards inherit, and the approval, merchant, category, country and time-of-day rules stay in the Payhawk app, and a change made here leaves them untouched.