All posts

Virtual cards for teams: one card per person, project or vendor

Per person, per project or per vendor. How to pick limits, name cards so the statement reads itself, and run approvals without approval software.

Virtual cards for teams: one card per person, project or vendor

The company card is where small-team spending goes wrong. One card, shared by everyone, with one statement at the end of the month that nobody can explain. Virtual cards replace that with a card per person, per project or per vendor, each with its own limit and its own history. Here is how teams set it up, what to decide first, and the habits that keep it tidy.

Three ways to split cards

Per person

Each team member gets a card with a monthly allowance for the tools and small purchases their role needs. Overspend is impossible: the card declines at the limit. The allowance is reviewed with the person, not discovered on the statement.

Per project or client

The project's budget goes on one card. Every tool, ad spend and one-off purchase for that project is charged to it. When the card is empty, the project is at budget. The transaction list is the cost report, ready without a spreadsheet.

Per vendor

A card for each supplier or subscription, loaded with the contracted amount. A vendor that invoices more than agreed gets a decline and a phone call rather than an unnoticed overcharge. A departing vendor is switched off by closing the card.

Most teams end up with a mix: per-person cards for discretionary spend, per-vendor cards for recurring services, per-project cards for campaigns.

Deciding limits

Start from what was actually spent last quarter, not from what feels right. Set each card's limit at that figure plus a modest buffer, then let declines tell you where the number is wrong. A card that hits its limit every month is a budget that needs a conversation. A card that never gets close is money sitting idle that could go back to the pool.

Naming

Name cards so the statement reads itself: "Client A ads", "Design tools for Sara", "Main site hosting". Six months later, when someone asks what a charge was for, the card name answers before anyone has to look.

Reloading and returning money

Per-person cards are reloaded on a schedule, usually the first of the month. Per-vendor cards are loaded with the next invoice. Per-project cards are loaded once at the start. When a project ends or a person leaves, close the card and the unspent balance flows back to the shared wallet the same day. Nothing is stuck on a card nobody uses.

Approvals without a workflow tool

Small teams do not need approval software. The limit is the approval. Anything inside a card's limit is pre-approved by the fact that the limit was set. Anything beyond it requires the person to ask for a raise, which the manager does from the dashboard in seconds. That is the whole approval process, and it leaves a record.

Visibility

Turn on transaction alerts for the cards that matter. A manager who sees every charge on the ads cards as it happens does not need a weekly report. The team member who sees their own card's balance does not need to ask how much is left.

Security for teams

  • Card numbers are revealed to the person who needs them, behind two-factor authentication, never pasted into a shared chat.
  • A card that leaks affects one vendor or one person, and is closed in a tap.
  • When someone leaves, their cards are closed the same day. No shared card to reissue.
  • Only whoever manages the wallet needs to sign in. The person using a card needs the card details, not the account.

What to look for in a provider

Enough active cards for the way you split them, instant limit changes, a transaction list per card, alerts, and a funding method that fits how the company holds money. If the company is paid in stablecoins or moves money across borders, a provider that accepts crypto deposits removes a bank transfer and a conversion from every top-up.