← Back home

Team spending

How to set spending limits on team cards linked to a verified account

One verified account, several team cards, one shared balance. Spending limits are what keep that arrangement calm instead of chaotic — here is how to set them so your team can work and your money stays under control.

Two colleagues reviewing a team payment card and spending dashboard

Why limits matter more than trust

A team card linked to a verified account draws from the same balance as the main account. Every cardholder can spend the business's money, which is exactly why the arrangement works — and exactly why it needs guardrails. Trust is a good starting point, but trust is not a control. A control is something that still works on a busy Tuesday when nobody is watching.

Spending limits turn an awkward conversation into a setting. Instead of telling a teammate to be careful with the card, you set a number that enforces itself. The card simply stops at the limit, which protects the balance and protects the teammate from an honest mistake becoming an expensive one. Nobody has to accuse anyone of anything, because the rule applies to every card the same way.

Limits also protect the account itself. A verified account that suddenly shows unusual spending patterns can attract reviews and holds from the platform or the card provider. Steady, predictable spending that matches the account's normal pattern is far less likely to draw attention than a sudden spike from a card that was never meant to spend that much.

What a spending limit actually controls

A spending limit is not one number. Most card programs let you control spending in four different ways, and the best setups use more than one of them at the same time.

The per-transaction cap is the largest single purchase a card can make. This is your first line of defence against a mistyped amount, a duplicate charge, or a subscription that renews at a higher tier than expected. Set it at the largest routine purchase the cardholder genuinely needs to make, not at the largest purchase you can imagine.

Daily, weekly, and monthly totals cap how much a card can spend over a period. A monthly cap is the most useful of the three for most teams, because it matches how budgets and payouts actually work. A daily cap is useful for cards used on the go, where a lost or misused card should not be able to drain much before anyone notices.

Category controls restrict what kinds of purchases a card can make, such as travel, software, advertising, or supplies. Merchant controls go one step further and restrict spending to specific vendors. These two controls matter most when a card is issued for one job — an ads card should not be buying office furniture, and a travel card should not be paying for software subscriptions.

Start with roles, not numbers

The most common mistake is giving every team member the same limit. A limit that is right for the person who pays the monthly software bill is far too high for someone who only buys the occasional courier label, and far too low for the person who books client travel.

Start by listing the roles that need a card. The owner or finance lead usually needs the widest limit, because they handle rent, payroll-adjacent payments, and the unexpected. A manager needs enough room for their team's regular spending, but not the owner's ceiling. Day-to-day buyers need a limit that covers their routine purchases with a little headroom. Field staff and occasional users need the smallest limits of all, because their spending is narrow and predictable.

Write one sentence for each role describing what the card is for. If you cannot describe it in one sentence, the role is too vague and the limit will be too. That sentence becomes the test for every future request: if a purchase does not fit the sentence, it belongs on a different card or needs approval first.

Issue one card per person, never one shared card for a whole team. A shared card makes limits meaningless, because you cannot tell whose spending hit the cap, and you cannot lower one person's limit without lowering everyone's. Per-person cards also make the monthly statement readable, which matters when you reconcile payouts or answer a question from your accountant.

Setting your first limits in four steps

First, look at what the team actually spends. Pull the last three months of card statements and sort the spending by cardholder and by category. The numbers in front of you are a far better guide than any rule of thumb, because they show real behaviour rather than what anyone remembers spending.

Second, set each monthly limit a little above the cardholder's normal month. A limit that sits exactly at the average will be hit in every busy month, which trains the team to treat the limit as a suggestion rather than a rule. A limit set roughly a fifth above the usual month gives room for a busy week without giving room for a spending spree. If a cardholder's spending swings wildly from month to month, use their busiest recent month as the baseline instead of the average.

Third, set the per-transaction cap at the largest routine purchase, not the largest possible one. If the biggest regular purchase is a monthly software bill, the cap should sit just above that bill. Anything larger — a new laptop, an annual plan, a conference ticket — should go through a quick approval, because those purchases are rare enough that a short wait costs nothing.

Fourth, turn on alerts before you turn on limits. An alert when a card reaches most of its monthly limit gives the owner time to raise it, move the purchase, or say no while there is still time to act. A limit without an alert is a surprise decline at a checkout counter, and a surprise decline is how a team learns to work around the system instead of inside it.

Per-card limits vs a shared pool

Some card programs offer a shared pool: a single monthly budget that all team cards draw from, instead of a separate limit on each card. This sounds simpler, and for very small teams it can be, but it hides the same problem as a shared card. One cardholder's busy month eats the whole team's budget, and the person who notices is the one whose legitimate purchase declines at the end of the month.

Per-card limits are clearer for almost every team. Each person knows their own number, the owner can see at a glance who is close to their cap, and raising one person's limit never quietly raises everyone else's. The shared pool still has a place: as an overall ceiling on the account itself, sitting above the per-card limits. That way the account has a hard stop even if several cards all have a busy month at once.

If your provider only offers one of the two, choose per-card limits when you have more than two cardholders, and choose the shared pool only when a single person genuinely manages all the spending. Either way, write the arrangement down somewhere the whole team can see it, so a declined card is a known rule rather than a mystery.

Category and merchant controls

Category controls are worth setting even when the amounts look small. A card issued for advertising spend should not be able to pay for travel, and a card issued for supplies should not be able to pay for a subscription. The point is not suspicion — it is clarity. When every card has a job, the monthly statement reads like a budget instead of a puzzle.

Merchant controls are the most precise tool available, and the most work to maintain. Restricting a card to one or two vendors makes sense for a card that exists for a single recurring payment, such as an ad platform or a software suite. It makes little sense for a general-purpose card, where the list of approved merchants would need updating every week.

Online-only restrictions are a useful middle ground for cards that never need to pay in person. A card that only buys software and advertising has no reason to work at a physical terminal, and disabling in-person use removes a whole category of risk at no cost to the team. The same logic applies in reverse: a field card that pays for fuel and supplies may not need online purchasing at all.

What happens when a limit is hit

A declined card is not a failure of the system — it is the system working. What matters is what happens next. The cardholder should know, before it ever happens, who to contact and how long an increase takes. If the answer is a message to the owner and a same-day adjustment, a decline is a five-minute delay. If the answer is nobody knows, a decline becomes a missed payment and a frustrated teammate.

Agree a simple override process in advance. The cardholder messages the owner with the amount, the vendor, and the reason; the owner raises the limit for that card, or for a single transaction, and notes the change. A temporary increase should always have an end date. A limit raised for one purchase and never lowered again is not a temporary increase — it is the new limit, set by accident.

Watch for repeated declines on the same card. One decline is normal. The same card declining every month means the limit is wrong, the role has changed, or the spending has moved somewhere it should not be. Any of the three is worth a short conversation rather than a quiet habit of topping the limit up each month.

Reviewing and adjusting limits

Limits are not set once and forgotten. Put a monthly review on the calendar, ideally when you reconcile the month's payouts, and spend ten minutes on the card statement. Look for cards that came close to their limit, cards that barely spent anything, and any purchase that does not fit the card's job.

Raise a limit when the role grows. A teammate who takes on a new client, a new channel, or a new category of spending needs a limit that matches the new job, and the change should happen before the first purchase, not after the first decline. Lower a limit when the role shrinks, a project ends, or a card goes unused for a month or two — an unused high limit is risk with no benefit.

Seasonal businesses should plan limit changes the way they plan inventory. A card that handles holiday advertising or a busy season needs its higher limit in place before the season starts, with a note to bring it back down when the season ends. The same applies to one-off events: raise the limit for the week of the event, then return it the following Monday.

When a cardholder leaves the team, remove their card the same day. This is the easiest item on the list and the most commonly skipped. A cancelled card costs nothing to remove and can cost a great deal if it stays active, even with a low limit, because the account remains responsible for whatever it spends.

Mistakes that undo good limits

  • Giving every cardholder the same limit, regardless of role or spending.
  • Setting limits so tight that normal work declines, which teaches the team to bypass them.
  • Turning limits on without alerts, so the first sign of a problem is a declined payment.
  • Raising a limit temporarily and never bringing it back down.
  • Sharing one card across a team instead of issuing a card per person.
  • Never reviewing limits, so a limit set a year ago still governs a role that has changed twice.
  • Forgetting to cancel a card the day its holder leaves the team.

A simple starter setup

  • One card per person, with the person's name on it.
  • A written one-sentence purpose for every card.
  • A monthly limit set a little above each cardholder's normal month.
  • A per-transaction cap at the largest routine purchase.
  • Alerts switched on before the first limit goes live.
  • Category controls matching the card's job.
  • A named person to contact when a card declines, and a same-day override process.
  • A monthly review date on the calendar, next to the payout reconciliation.

Set the limits, switch the alerts on, and tell the team what the numbers are. A limit the cardholder does not know about feels like a trap; a limit they helped set feels like a tool. Review the setup once a month, adjust for the roles as they change, and cancel any card the moment its holder leaves. That is the whole system — and it is enough to keep one verified account, several team cards, and a single shared balance working quietly in the background while the team gets on with its work.

This guide is educational only and is not financial advice. Card features, limits, and controls vary by provider and by account type — check your provider's own documentation before changing any setting on a live account.

One card per person

Every cardholder has their own card, their own limit, and a statement you can actually read.

Limits that enforce themselves

Per-transaction caps, monthly totals, and category controls that work even when nobody is watching.

Alerts before declines

Notifications when a card nears its limit, so a busy month is a conversation, not a surprise.

Ready to buy with confidence?

Every account in our catalog runs through the same 27-point QA before it reaches you. Ask us anything before you order.