Team Money
When you are the only person who can spend money, you are also the only person who can unblock work. This hub is about designing spending permissions deliberately: budgets, thresholds, approval routes, evidence requirements and the controls that keep it safe.
Reviewed by a qualified professional
James Whitfield — FCCA, Chartered Certified Accountant — 18 years advising UK SMEs on employment costs, payroll and business finance. Reviewed 5 August 2026.
Last updated 2 August 2026
Where are you stuck?
Overview
Why spending controls need designing, not just limiting
When the founder is the only person who can authorise spending, they are also the only person who can unblock work, which quietly recreates a bottleneck every time someone needs a subscription renewed or a supplier paid.
A spending limit on its own only tells someone how much they can spend. It does not tell them what the money is for, what evidence is expected, or what happens if something goes wrong — which is why policy has to come before the card or the number.
Designing this deliberately, rather than defaulting to 'ask me every time' or the opposite extreme of an unmonitored shared card, is what allows a small team to move quickly without creating real financial risk.
The order to work through it
Start with budgets: give a role or a project a number to work within, rather than leaving spending as an open-ended question that always needs a founder's judgement call.
Next, set permissions and thresholds — who may view, initiate, approve and release payments, ideally never the same person for all four, and a value band below which no approval is needed at all for budgeted, routine purchases.
Only after budgets and thresholds exist does it make sense to choose the mechanism: named cards, purchasing controls for recurring subscriptions, and a reconciliation routine that captures evidence at the point of purchase rather than chasing it weeks later.
Common failure modes
In Kayley's experience, the most common failure is a shared card and shared login, which makes it impossible to know who spent what, and turns every discrepancy into a guessing game rather than a quick check of a named account.
A second failure is setting a threshold without writing the policy behind it, so people know the number but not what it is meant to cover, which leads to inconsistent and sometimes unfair decisions about what gets approved.
A third is treating reconciliation as a monthly confrontation about missing receipts, rather than building capture into the moment of purchase, when it is genuinely easy to do.
What to write down
Write a simple purchasing approval matrix: value bands, who approves each band, what evidence is required, and how exceptions are handled when something urgent falls outside the normal rules.
Document who has account and card access, at what level, and set a monthly review point so access does not quietly outlive the reason it was granted.
Note your separation-of-duties principle explicitly — for example, the person who approves a payment should not also be the only person who can release it — so the control survives a change of staff, not just a change of habit.
What "done" looks like
Routine, budgeted purchases below your threshold happen without anyone waiting on you, and every card or account has a named owner rather than a shared login.
Reconciliation is a quiet monthly review of clearly evidenced transactions, not a chase for missing receipts, because capture happens at the point of purchase.
You can say, without checking, roughly who can spend what and who approves anything above it — and that answer has been reviewed within the last few months, not set once and forgotten.
The five-minute action
Subtopic map
What this hub covers
Team and project budgets
Giving a role or a project a number instead of an open question.
How to Set Team and Project Budgets (10 min read)Financial permissions
Who may view, initiate, approve and release payments — never the same person for all four.
How to Set Financial Permissions for a Small Team (10 min read)Approval thresholds
Value bands that decide whether anyone needs to be asked at all.
How to Create a Team Spending Policy (11 min read)Purchasing controls
Preferred suppliers, recurring subscriptions and one-off purchases.
How to Set Purchasing Controls for a Small Team (9 min read)Account and card access
Role-based access instead of a shared password.
Business Debit vs Credit Card for Employees (10 min read)Fraud prevention
Separation of duties, payee verification and card controls.
How to Prevent Fraud in a Small Team (11 min read)Receipts and reconciliation
Evidence rules that make month-end quiet.
How to Reconcile Team Spending Every Month (9 min read)Subtopic map
Guides in this hub
Each guide answers one question in full and ends with something you can write down today.
How to Create a Team Spending Policy
Write down who can spend what, up to which limit, with what evidence, before you hand out any card or account access — a one-page policy that names roles and thresholds prevents mo…
Read (11 min read)Business Debit vs Credit Card for Employees
A business debit card spends only money the business already has and never extends credit, while a business credit card gives employees a spending line backed by the company's cred…
Read (10 min read)How to Set Team and Project Budgets
A team or project budget is a fixed amount of money allocated to a role, team, or piece of work for a defined period, so that spending decisions can be made without returning to th…
Read (10 min read)How to Set Financial Permissions for a Small Team
Financial permissions are the four separate access levels — view, initiate, approve, and release — that control who can take each action on a business bank account, and which shoul…
Read (10 min read)How to Set Purchasing Controls for a Small Team
Purchasing controls are the written rules that govern how a small team buys goods and services — covering preferred suppliers, approval thresholds, and evidence requirements — so t…
Read (9 min read)How to Prevent Fraud in a Small Team
Fraud prevention for a small UK team is a set of proportionate internal controls — primarily the separation of who initiates and who approves payments — that make both accidental m…
Read (11 min read)How to Reconcile Team Spending Every Month
Monthly spending reconciliation is the process of matching every transaction on a business account and card statements to stored receipts and invoices, on a fixed date each month, …
Read (9 min read)Featured tool
Team Spending Controls Builder
Builds your spending policy first — roles, thresholds, approval routes, evidence rules and leaver controls — and only then discusses mechanisms.
Use the Team Spending Controls BuilderTemplate
Purchasing Approval Matrix template
Value bands, who can approve, what evidence is required and how exceptions are handled.
Use the template online or print a copy for your team. No email address is required.
Founder stories
If you have moved from approving everything to a threshold system, tell us where you set the numbers and what changed.
Contribute your storyTools for team access and employee spending
Policy first, product second. These are partner products and we may be paid if you use them. Read the risks and the alternatives before the offer.
Tide
Once your permissions and thresholds are written down, you need an account that can express them: role-based access for a bookkeeper and debit cards that cannot spend money you do not have.
Tide is relevant once you need someone other than you to see, spend or reconcile business money: role-based Team Access for a bookkeeper, debit Expense Cards for employees, receipt capture and transaction organisation.
This page describes a Tide referral campaign. If you open an account through a tracked link on this site we may receive a referral payment, and you may receive a reward if you meet the campaign conditions. This does not change what we recommend or what we tell you about the product.
Read the full offer record, risks and eligibilityCapital on Tap
If your business is an eligible UK company that genuinely needs credit alongside per-card limits and real-time visibility, a business credit card is one option — with the risks set out in full.
Capital on Tap is relevant to eligible UK companies that need business credit alongside controlled employee cards: individual limits, virtual cards, real-time visibility, receipt capture and accounting integration.
This page describes a Capital on Tap campaign. If you apply through a tracked link on this site we may receive a payment. This does not change the eligibility rules, the risks or the alternatives we set out.
Read the full offer record, risks and eligibilityFrequently asked questions
What should the first spending threshold be?
Pick a value where the cost of your attention exceeds the cost of the mistake. For many small businesses that is somewhere between £50 and £250 for routine, budgeted purchases. Write it down, then review after a quarter.
Should employees have their own cards?
If they buy things regularly, yes — a named card with an individual limit is safer and cleaner than a shared card or a reimbursement queue. If purchases are rare, reimbursement may be simpler.
How do I reduce the risk of misuse?
Individual named cards, per-card limits, a written policy that people have acknowledged, monthly review of every transaction, and prompt removal of access when someone leaves.