Every growing startup hits the same wall: company spending is scattered across personal cards, a shared founder card and a spreadsheet nobody trusts. People front their own money, lose receipts, and wait weeks for a reimbursement. Finance spends Friday afternoons chasing line items instead of closing the books. For a lean EU team, that is real time and real cash flow leaking away.
Per-employee virtual expense cards fix the problem at the source. Instead of reimbursing spend after it happens, you control it before it happens, with a card scoped to each person and each purpose. This guide explains how expense cards work for European startups, what to look for, and how to roll them out without adding admin.
Why reimbursements break down as you scale
Reimbursement-based spending works when you are three people. It stops working fast. The cracks usually look like this:
- Cash-flow strain on staff. Junior team members shouldn't carry hundreds of euros of company spend on a personal card until payday.
- No real-time view. You only learn what was spent when expense reports come in, often a month late, long after the budget call mattered.
- Receipt chaos. Matching receipts to bank lines by hand is slow and error-prone, and it gets worse at quarter-end.
- Weak controls. A shared card has one limit and one PIN. Anyone with the number can spend, and you can't cap a category or a person.
The deeper issue is that a spreadsheet records the past. It can't enforce a limit, can't be frozen, and can't tell you what is happening right now.
How per-employee virtual cards work
With 2card you hold one euro balance on a single EU IBAN and issue a dedicated virtual Visa card to each employee, team or project. Each card draws on the same balance, so there is one pool of money to top up and reconcile, but spending is split cleanly by card.
Because the cards are virtual, you can create one in seconds, add it to Apple Pay or Google Pay, and use it online or in person the same day. No plastic to post, no branch visit, no waiting. A new hire on day one can have a marketing card or a travel card before lunch.
Hard limits, set per card
Each card carries its own hard limit you set, the kind that simply declines once the cap is hit, rather than a soft target someone can blow past. Give the SaaS card a monthly ceiling, cap a travel card for one trip, or set a small standing limit for office supplies. Spending can't exceed what you allow, so a mistake or a compromised number is contained to one card.
Merchant whitelists for tighter scope
For predictable spend, merchant whitelists let a card pay only approved merchants. A subscriptions card that works at your tools and nowhere else removes a whole class of misuse and makes month-end review trivial.
Real-time visibility and cleaner books
The biggest day-to-day win is that you see spending as it happens, not weeks later. Every transaction lands against a named card the moment it clears, so finance always knows the live position against budget.
That changes how you close the month. Instead of reconstructing what happened from a pile of reports, each card is effectively its own pre-sorted ledger: this card is marketing, that one is travel, this one is software. Export to CSV and the categories are already there. You move from forensic reconstruction to a quick review.
The point of an expense card isn't just convenience, it's that control and visibility happen before the spend, not after.
Instant freeze when someone leaves
Offboarding is where shared cards and lingering reimbursements get dangerous. With per-employee cards, the moment someone leaves, or loses a phone, you freeze or replace the card instantly. No reissuing a shared PIN to the whole team, no window where an old credential still works. Access ends cleanly with the card.
The same applies to contractors and short-term staff. A freelancer joining for a two-month project gets a capped card for the engagement, and you freeze it on the final day. If most of your spenders are non-employees, our guide to payroll cards for contractors covers that pattern in depth, and the dedicated payroll and contractor cards page shows how it fits together.
Funding it all from one EU IBAN
Behind every card sits a single EU IBAN with full SEPA support, including SEPA Instant and Direct Debit. You top up the balance from your main business account by ordinary SEPA transfer, in euros, with no currency conversion across the eurozone. From there, money flows out to whichever cards your team is using.
For European startups this keeps things simple and compliant: euro in, euro out, one IBAN to mention to your accountant, one statement to reconcile. Issuing in bulk is straightforward too, via API or CSV, so spinning up cards for a new cohort of hires doesn't mean clicking through one form at a time.
A note on who holds the money. 2card is a marketing partner of myTU, an EU-licensed Electronic Money Institution supervised by the Bank of Lithuania; myTU provides the IBAN, the Visa issuing and the safeguarding of funds. 2card is not a bank. Under EU EMI rules your balance is safeguarded and segregated rather than lent out, which is a different protection model from a bank deposit, explained in our piece on how EU EMIs safeguard your money.
Rolling it out without adding admin
You don't need a finance team to run this well. A simple, repeatable setup works for most startups:
- One card per recurring purpose (software, ads, travel, office) plus a personal card per employee who needs one.
- Sensible hard limits on each, sized to a realistic month, so the card itself enforces the budget.
- Whitelists on the predictable cards, left open on the genuinely variable ones like travel.
- A freeze-on-exit step baked into your offboarding checklist.
Done once, this runs itself. New spend slots into an existing card, new people get a card on day one, and leavers are handled with a click. The spreadsheet, the reimbursement backlog and the shared-card anxiety simply go away. 2card is in early access now; you can request access from the 2card homepage while we finalise availability for EU teams.