Spend Management for Startups

The best expense process for a startup is one that people barely notice: give teams and individuals a budget, give them a company card, and let software enforce the limits and collect the receipts. Control comes from the budget and the tool, not from a manager approving every purchase. The result is fewer delays, less finance admin and a clearer view of where the money goes.

This guide is for founders and finance leads who want to set that up. It covers why approval queues and reimbursements fail, how to delegate budgets, what spend management platforms do, how to let people pick their own tools safely, and what the accountant needs at the end of the month.

The short answer

1. Trust people with a budget, not with a form. If you let an employee decide what to build or sell, which is where their time goes, you can also let them decide how to spend a small budget on the tools to do it.
2. Delegate in layers. A company budget is split into team budgets, and each team lead can give individuals a small monthly allowance for tools and learning.
3. Use a spend platform. Software such as Ramp or Spendesk (examples) provides cards, limits, approvals, receipt capture and accounting sync in one place.
4. Write a one-page policy. What is allowed, what needs approval, what is never allowed, and who to ask.
5. Make the safe path the easy path. Virtual cards per vendor, receipts attached by photo, spend coded automatically.
6. Guard the few things that matter: security and data in new software, renewals that nobody owns, duplicate tools and large or unusual payments.
7. Review after, not before. Look at spend weekly or monthly against budget, sample the details, and talk to people about outliers.
8. Include the accountant from the start. Receipts, VAT recovery and the monthly close all depend on how clean the spend data is.

Why old-style expense control fails

The traditional process works like this: an employee wants something, asks a manager, the manager asks finance, finance approves, the employee pays with a personal card and months later submits a claim with receipts. Every step costs time, and the process is built for the rare large purchase rather than the many small ones that make up most of a startup's spending.

What it costs

An invented example. A designer needs a EUR 30 monthly software subscription. With a fully loaded cost of EUR 50 an hour (illustrative), the approval chain looks like this:

The process costs more than the thing it controls, and it adds days of delay on top. Multiplied across a team making dozens of small purchases a month, the hidden cost is large, and it falls on the most expensive people in the company.

The problems that follow

• Reimbursements. Employees lend the company money on personal cards, wait weeks to be paid and lose receipts. Foreign currency and card fees land on them. The finance team spends time on claims that should not exist.
• Approval queues. Requests wait for a manager who is travelling or busy. People give up, or find a way around the rule.
• Shadow IT. Staff sign up for tools on personal cards or free trials with company data. The company does not know what it has, what it pays or what data sits where.
• Surprise bills. Annual renewals roll over without notice, trials convert to paid plans, and seat counts creep up as people join and leave.
• Messy books. Missing receipts and uncoded transactions make the monthly close slower and leave VAT unclaimed.
• Mistrust. A process that treats every purchase as suspect signals that the company does not trust its people, and good people notice.

The aim is not to remove control. It is to move control to where it is cheap and effective: the budget, the card limit and the monthly review.

The principle: freedom inside a frame

A startup that hires good people lets them decide what to work on, how to prioritise and how to solve problems. Those decisions move the company's single biggest cost: people's time. It would be odd to trust someone with a month of working time that costs thousands of euros, and then not trust them with a EUR 30 subscription. If people choose how to spend their time, they should also choose and buy the tools that make that time more productive.

The arithmetic of a tool

A tool is worth buying when the time it saves is worth more than it costs. The break-even is simple:

Break-even hours per month = monthly price of the tool ÷ hourly cost of the person

An invented example in euros: an employee costs the company EUR 6,000 a month in total, which is about EUR 35 an hour over roughly 170 working hours (illustrative). A tool costing EUR 30 a month pays for itself if it saves under one hour a month. Even a EUR 300 tool breaks even at less than nine hours a month. The employee knows far better than a manager or the finance team whether it saves that time.

The trap is the opposite one. A process that slows the purchase of a EUR 30 tool by a week costs far more than the tool, as the previous section showed.

What the frame is

Freedom works when its limits are clear and cheap to enforce. The frame has four parts:

1. A budget. Each person or team has a monthly amount they can spend without asking. The budget, not an approval, limits the risk.
2. A few hard rules. Things that are never allowed or always need a second pair of eyes: personal spending, anything involving customer data in an unreviewed tool, payments above a set amount.
3. A tool that enforces it. Card limits, merchant restrictions and receipt requirements live in the spend platform, so people do not have to remember them.
4. A regular review. Finance and team leads look at spend after the fact, ask about anything unusual and adjust the budgets.

When this does not fit

The approach suits most early-stage software and services companies. It needs adjusting in a regulated sector, where tool choice may be restricted for compliance reasons, in a company that handles highly sensitive data, and in a company with very tight cash, where a lower limit and a monthly check are sensible. The principle stays the same; the budgets and the hard rules change.

Delegating budgets to teams and individuals

Delegation starts by splitting spending into two kinds.

• Run costs are owned by finance or the founders: payroll, rent, core infrastructure such as cloud hosting, insurance, legal and tax advice, and contracts the whole company depends on. They are planned centrally.
• Discretionary costs are delegated: software and tools, learning and conferences, small equipment, travel, team events, freelancers and experiments, within a budget.

The delegated part is where speed matters and where the individual knows best, so it is the part to hand over.

Four levels

The amounts are illustrative; set yours from your own budget and risk tolerance.

How to set the budgets

1. Start from the cash forecast. Take the non-payroll cost lines and decide how much of the discretionary part you can delegate without hurting runway.
2. Set budgets per team from headcount and plan. A simple rule is a per-head tool allowance plus a few team-specific lines. An invented example: a team of eight with a EUR 200 per head allowance has EUR 1,600 a month for tools, plus a separate EUR 1,000 for events and learning, so EUR 2,600 in total.
3. Name one owner for each budget. The owner is accountable for staying within it and for explaining outliers. A budget with no owner is not a budget.
4. Decide what happens to unused money. Common options: it does not roll over (simplest), it rolls over for one quarter, or the team keeps a share of savings. Say which, so people do not rush to spend at month-end.
5. Review each quarter. Raise limits for teams that stay within budget and are spending well. Lower them where the money is being wasted. Do it as a conversation, not a punishment.

Commitments versus spend

A one-month subscription and a two-year contract are very different decisions even at the same monthly price. Delegate monthly spend freely. Put the approval on the commitment: the length of the contract, the amount paid up front and automatic renewals. A simple rule is that anything locked in for more than twelve months, or with a total value above a set amount, needs a second approval.

Spend management tools

A spend management platform replaces the pile of personal cards, spreadsheets and email approvals with one system. Ramp and Spendesk are two well-known examples; others exist, and the market changes quickly, so treat any list as a starting point and check current features, countries and pricing.

What these platforms usually do

• Company cards. Physical and virtual cards issued to people, teams or single vendors, each with its own limit.
• Controls on the card. Monthly or one-off limits, merchant or category restrictions, and cards that can be switched off in a click.
• Requests and approvals. A request for a purchase, or for a larger limit, goes to the right approver in a few clicks, and approved requests can issue a card on the spot.
• Receipt capture. Employees photograph a receipt on a phone, or the receipt is pulled from email; the card cannot be used for long without one.
• Automatic coding. Transactions are tagged with a category, a team and sometimes a project, with suggested codes that improve over time.
• Accounting sync. Coded transactions and receipts flow into the accounting system, which shortens the monthly close.
• Bills and reimbursements. Supplier invoices can be approved and paid, and the occasional out-of-pocket claim handled, in the same place.
• Subscription tracking. A list of recurring charges, renewal dates and owners, which prevents surprise renewals.
• Reporting. Spend by team, vendor and category against budget.

How to choose

Compare two or three options on the criteria below, using a trial or a demo with your own accountant in the room.

A practical way to decide: list the ten most common purchases in your company, run each through the trial, and count the clicks, the minutes and the questions from your accountant.

Do you need a platform yet?

A company with five people and a handful of subscriptions can start with a company card from the bank and a shared receipts folder. A platform pays for itself when there are around ten or more people with regular purchases, when reimbursements consume finance time, or when you cannot say what you pay for software each month. It is easier to introduce early than to move a habit later.

Cash back, idle cash and payment speed

A spend platform is also a financial product. The terms on rewards, on the money it holds for you and on how fast payments move change what it really costs, and these are the terms that are easiest to overlook in a demo. They depend on the provider, the country and the type of account, so the points below are questions to ask rather than answers.

Where the money sits matters too: the deposit protection and spreading-cash advice in Banking for Startups applies to balances held on a spend platform.

Cash back and rewards

Many company cards pay a share of spend back as cash back or points. An invented example: EUR 20,000 of card spend a month at 1.5% cash back is EUR 300 a month, or EUR 3,600 a year. That is worth having, but check what sits behind the headline.

• Rate and limits. Is the rate flat or only on some categories? Is there a cap or a minimum spend?
• Fees that cancel it. A foreign-exchange fee or a per-user fee can wipe out the reward, especially if you pay many suppliers abroad. Compare the net, not the headline.
• Form of payment. Cash, statement credit or points that expire? Cash is simplest.
• What the card costs to qualify. Rewards on a credit card may come with a personal guarantee, a deposit or a fee. Prepaid and charge cards may offer none.
• Who receives it. It belongs to the company, not the cardholder.
• Tax and accounting. Depending on the country, rewards may be treated as a reduction of the cost or as taxable income, and the VAT treatment can differ. Ask your accountant how to book them.
• Do not let it drive behaviour. Spending money to earn 1.5% back is a loss. Cash back is a small bonus on spending you would do anyway.

If the card is a credit product, pay the balance in full by the due date. Interest on an unpaid balance is typically far higher than any reward.

Idle cash

Money waiting to be spent, for example a prepaid balance that funds the cards, or cash held in the platform account, can sit idle for days or weeks. Whether it earns interest depends on the provider.

An invented example: EUR 500,000 earning 2% a year is EUR 10,000 a year, about EUR 830 a month. That is useful, but it is small next to the downside of losing access to the money or of the provider failing. For a startup, cash safety and access come first, yield second. Keep the money you need for the next few months in an easily accessible, protected account, and consider the rest separately with your accountant or bank. The cash forecast tells you how much is which.

Payment speed

Speed matters when a tool is blocked because a card was not funded in time, or a supplier is waiting for a transfer.

A useful rule is to pay suppliers on the due date rather than early, unless there is a discount, because cash kept for longer is runway. Payment scheduling in the platform makes that easy.

Making it easy

A policy that people follow has to be short, and the tool has to make the right behaviour the quickest one. The goal is that buying a tool, paying a supplier or booking a trip takes a minute and leaves a clean record without anyone thinking about the accounts.

A one-page policy

A sample you can adapt. Amounts are illustrative.

Spending policy (sample)

Principle. Spend company money as carefully as your own, and on things that help us do the work.

What you can buy without asking. Software, tools, books, courses and small equipment for your work, up to your monthly allowance of EUR 200. Use your company card.

What needs a second approval.

• A new tool that will hold customer or personal data (ask security and finance first)
• Any contract longer than 12 months, or over EUR 5,000 in total
• Any single payment over EUR 1,000
• Anything that renews automatically for more than EUR 500 a year

What you must not do.

• Spend on personal items or use the card for private costs
• Split a purchase to stay under a limit
• Share a card or its details

Every purchase. Add the receipt within 7 days (a photo is fine) and a one-line reason if it is not obvious.

Questions. Ask in the finance channel. If unsure, ask before buying, not after.

Features that remove friction

1. One virtual card per subscription. Each recurring vendor gets its own card with its own limit. When someone leaves or a tool is cancelled, the card is closed, and the vendor cannot charge more than agreed.
2. Cards issued in a minute. A new joiner gets a card and an allowance on day one. A team lead can raise a limit, within their budget, without a ticket.
3. Receipts by photo or email forwarding. The simplest rule is a short reminder when a receipt is missing, and a card that is paused if receipts stay missing after a few reminders.
4. Auto-coding. Transactions arrive with the team, category and VAT code filled in from rules, so that finance reviews exceptions only.
5. Mobile first. Approvals, requests and receipts should work from a phone in a couple of taps.
6. Visible budgets. People see their budget and spend in the app, so they self-correct without being asked.
7. One place to ask. A finance channel or an inbox with a promised response time, such as one working day, for questions and requests.

What to remove

• Paper claim forms and spreadsheets for expenses.
• Approvals for amounts below the individual allowance.
• Second approvals for people who are within budget and have a clean record.
• Separate systems for cards, bills and receipts if the platform can do all three.

Letting people choose their tools

Letting people pick the tools they work with has real benefits: they know the job, adoption is higher, the best ideas for a better workflow tend to come from the person doing it, and the company signals trust. It also has real risks, which are specific and manageable: data security, tools that overlap, contracts nobody owns and costs that creep. The answer is a light set of guardrails, not a ban.

Three tiers

Sort a purchase by what it could damage, and give each tier a different level of oversight.

The questions behind the tiers

A short checklist anyone can run before buying:

1. Does it touch data? Customer, employee or confidential information changes the tier to red. If personal data of people in Europe is involved, a data processing agreement is generally required.
2. Do we already have something that does this? A quick look at the tool list avoids paying twice. If two tools overlap, say which one the team uses.
3. How do people log in, and how do we remove access? Single sign-on or a shared admin account lets the company close access when someone leaves.
4. Who owns it? Every tool needs one named owner who knows the renewal date, the cost and who has seats.
5. How long are we locked in? Prefer monthly terms until the tool has proved itself.
6. What happens to the data if we stop? Check that you can export it.

Keep a tool list

A simple register of every tool the company pays for makes all of this workable. The spend platform's subscription list is a good start.

Housekeeping that makes it work

• A quarterly tool review. Each owner confirms the tool is used and worth its cost; unused seats are removed.
• Offboarding. When someone leaves, their tools are reassigned or cancelled and their cards are closed on the last day.
• Sharing what works. A short note in a team channel when someone finds a good tool, so that others can use it instead of buying a second one.
• A way to say yes. If a red-tier tool is requested, the answer should arrive within a day or two. A slow review pushes people to buy on their own.

Controls that do not slow people down

Trust does not replace control. It changes where control sits: from permission before the purchase to limits built into the card and review afterwards. A good control is cheap for honest people and expensive to get around.

The layers

A light review routine

1. Weekly, 15 minutes. The finance lead scans the largest transactions, new vendors and anything unusual, and asks the owner a question when it is not clear.
2. Monthly. Compare each team's spend with its budget, review missing receipts, check the subscription list for new items and upcoming renewals.
3. Quarterly. Sample a small number of transactions in detail: does the receipt match, is the amount right, is the purpose business-related? Share what you find with the teams; patterns matter more than individual cases.

What to watch for

• Split purchases. Several payments just under a limit to avoid an approval. The platform can flag the same vendor or the same day.
• Personal spend. Usually accidental, handled by repayment and a reminder; repeated cases are a conversation with the manager.
• Duplicate subscriptions. Two teams buying the same tool.
• Zombie subscriptions. Charges for tools nobody uses after a project ends or a person leaves.
• Unusual vendors or locations. A merchant that does not fit the business, or a payment at an odd time.
• Fraud and card theft. Instant freezing, one card per vendor and alerts on large payments limit the damage.
• Rounded or repeated amounts without a clear receipt.

Principles for dealing with problems

• Start with the assumption of a mistake. Most problems are errors or misunderstandings. Ask first.
• Be fair and consistent. The same rule applies to everyone including founders. Founders who spend casually undermine the entire policy.
• Fix the system, not only the person. If many people forget receipts, change the reminder, not the people.
• Act on deliberate abuse. If personal spending or falsified receipts are intentional, treat it as a serious conduct matter and follow your employment procedures.

Accounting and tax

Delegated spending is only safe if the books stay clean. Most of the accounting and tax work depends on what is captured at the moment of purchase, so the platform should collect it then. The points below are general; your accountant will know the local rules. The Tax 101 guide in this series covers VAT and records in more detail.

For VAT, deductibility and the wider tax picture, see Tax 101 for Startups.

What the accountant needs for each transaction

• the receipt or invoice, with supplier name, date, net amount, VAT and total;
• the company's name and VAT number on the invoice where the law requires it;
• the category (software, travel, meals, equipment, and so on);
• the team or project, if you report costs that way;
• the business reason, in a line, for anything not obvious;
• the supplier's country and VAT number, for purchases from abroad.

VAT on purchases

1. A valid invoice is usually needed to reclaim VAT. A card slip or a bank record is generally not enough. Make sure online tools bill the company, not the individual: set the company name, address and VAT number in the account's billing details.
2. Foreign suppliers. Many software and service suppliers are abroad. In the EU, purchases of services from a supplier in another EU country by a business are normally handled through the reverse charge, where the company accounts for the VAT itself. Correct coding of the supplier's country makes this automatic for the accountant.
3. Non-deductible items. Some costs, such as certain meals, entertainment or private use, have limited or no VAT recovery. Coding them correctly avoids a claim that will later be reversed.

Corporate tax and benefits

• Deductibility. Costs must be business-related and supported by documents. Meals, gifts and entertainment are often limited or disallowed.
• Allowances and perks. A tools or learning allowance is usually a business cost, but equipment that can be used privately, home office payments and some perks can count as taxable benefits for the employee in some countries. Check before launching a perk programme.
• Travel. Many countries have rules for daily allowances, mileage and foreign trips. Keep the purpose and dates of each trip.
• Rewards and cash back. Card rewards can be taxable income or reduce the cost of the purchases, depending on the country. Ask your accountant.

Withholding tax certificates. Sometimes a payment is made net of tax withheld at source: interest on a deposit, a royalty or a service fee from a foreign customer. The payer should give you a certificate showing how much was withheld, and you need it to claim a credit against your own tax or to apply for a refund. Spend platforms are built mainly for outgoing payments, and I cannot say whether a given one handles these certificates specially. Ask the vendor. In most cases the practical answer is to attach the certificate to the related invoice or bank entry as an ordinary document, or to store it in the accounting system, with a note of the amount withheld and the country. Name one person who requests the certificate when the payment arrives, because they are much harder to get later and credits can expire.

Subscriptions and the books

A tool paid annually in advance is a prepayment: the cash leaves on day one but the cost belongs to the next twelve months. Your accountant should post it that way, which is why the spend platform's renewal dates and amounts matter. Monthly plans avoid the issue and are easier on cash, as the runway guide explains.

Keeping the close fast

1. Transactions and receipts sync from the platform to the accounting software daily or weekly.
2. Anything missing a receipt or a code is listed and chased before month-end.
3. The platform's balance and card statements are reconciled to the bank.
4. Any unusual spending is explained in the monthly report pack.

With these in place, expense processing stops being a monthly scramble and the close can finish within a few days of month-end.

Rolling it out

A 30-day plan

Metrics to watch

• Receipts matched. The share of card transactions with a receipt within seven days. Aim for well over 90%.
• Time to close. Working days from month-end to a finished close.
• Spend per head and by category. Software, travel and learning per person, compared month to month.
• Budget versus actual by team. And the number of teams that go over.
• Subscription count and unused seats. Fewer tools doing the same job, and no seats nobody uses.
• Approval time. For purchases that need one, the median time from request to decision. Aim for within a working day.
• Employee satisfaction. Ask directly whether the process is easy.

Common mistakes

1. Copying a big-company policy. A thirty-page policy at a ten-person company is ignored.
2. Delegating without a tool. Budgets and trust need limits that software enforces.
3. Allowances set too low. If people must ask constantly, nothing has changed.
4. No owner for each budget or tool. Nobody then notices the renewal.
5. Letting founders be the exception. The behaviour of the founders sets the culture.
6. Ignoring the accountant. A beautiful workflow that produces data the accountant cannot use wastes the effort.
7. Rolling out without explaining why. Tell people the reasoning: speed, trust and clean books.
8. Never reviewing. Delegation without review turns into drift. Keep the weekly and quarterly routines.

Starter checklist

• Run costs and delegated costs separated in the budget
• A per-person monthly allowance and team budgets set, each with a named owner
• Approval rules written for commitments, new data-handling tools and large payments
• A spend platform chosen, connected to the bank and the accounting software
• Company details and VAT number set as billing details on all tools
• Virtual cards in place for recurring subscriptions
• A one-page policy shared and discussed with the team
• A tool register with owners, costs and renewal dates
• A weekly 15-minute review and a quarterly tool review scheduled
• The accountant has confirmed what they need for each transaction

A note on sources and numbers

This guide is written from general practice rather than from a specific publication, vendor document or law.

• All example figures (the approval cost, the break-even hours, the allowances and limits, the team budget) are invented for illustration.
• Ramp and Spendesk are named as examples of spend management platforms. Check each vendor's current features, pricing, country coverage and card terms yourself.
• Statements about VAT, benefits in kind, deductibility, data protection and record keeping are general and differ by country. Confirm them with your accountant or tax adviser before relying on them.
• Thresholds, such as the 12-month contract limit, the 90% receipt target and the response times, are suggestions, not standards.