Revolut Pro

Revolut Pro logo
Provides a free business banking account and invoicing inside the Revolut app for freelancers.

How to use Revolut Pro

This guide gets you from a fresh Revolut Pro account to a banking layer you can actually run a business on: multi-currency money in, cards and subaccounts that keep your spending legible, and the plumbing that feeds your bookkeeping without manual re-entry. It is written for solo founders and small teams who sell internationally, invoice in more than one currency, and want their banking to behave like infrastructure rather than an app they dread opening.

Getting set up

The first decision is the boundary between you and the business. Revolut Pro sits alongside a personal Revolut profile, so keep the two genuinely separate from day one: business income lands in Pro, personal spending never touches it, and you never blur the line "just this once". That separation is what makes everything downstream (reconciliation, tax, a clean view of runway) painless instead of a quarterly archaeology project.

Next, decide which currencies you actually transact in and hold accounts for those, not for every currency on offer. If you sell in USD, GBP and EUR, hold those three and let the rest convert on demand. Holding a currency means you receive and spend in it without a forced conversion on every transaction, which is the whole point of a multi-currency account, but holding twelve currencies you rarely use just spreads your balance thin and gives you more things to watch.

Read the full guide

Then set up the people and the cards. Add the team members who genuinely need spending power, give each a card (virtual for online and recurring subscriptions, physical only where it is truly needed), and use disposable virtual cards for one-off or risky online payments so a leaked number costs you nothing. Treat the card layer as a permissions system, not a perk.

The setup decision people skip is naming and structure. Decide, before money starts flowing, how you will label accounts and what each card or subaccount is FOR (one for ad spend, one for software, one for client pass-through), because retrofitting that structure once hundreds of transactions exist is the unpleasant part.

How to actually use it

The core loop is: receive, hold, spend in the right currency, then reconcile. Get the order right and the value compounds.

Start with getting paid. Share your account details so clients can pay you in their own currency, and where you operate across borders, use local account details so a client's bank treats it as a domestic transfer (cheaper for them, faster for you, fewer "the payment is pending" emails).

Hold rather than convert reflexively. When a USD invoice lands and your costs are partly in USD, keep it in USD and spend it directly. Convert only when you genuinely need the other currency, and convert deliberately rather than letting every transaction trigger a silent FX hit. This is the single habit that saves the most money over a year.

Spend through the card and account structure you set up, so every payment already carries context. When ad spend goes out on the "ads" card and software on the "software" card, your statement reads itself.

Close the loop with reconciliation. Export or sync your transactions on a fixed rhythm (weekly is a good default), match them against invoices and receipts, and never let it pile up. The discipline matters more than the tool: a banking layer you reconcile weekly tells you the truth about your business, one you reconcile in a panic at year-end tells you a story.

Power moves

Use disposable virtual cards as your default for any new or untrusted online vendor. The number dies after use, so a breach on their side is a non-event for you. Most people never turn this on, and it is one of the strongest fraud defences you get for free.

Lean on local account details in your key markets rather than relying on international transfers. The difference in cost and settlement time on inbound client payments is real and it accrues silently.

Set per-card and per-merchant controls deliberately: cap a subscription card just above the expected charge, restrict categories where you can, and freeze a card the moment a project ends rather than leaving a live number floating. A card you forgot about is the one that gets abused.

Treat FX as something you time, not something that happens to you. Hold balances in the currencies you owe money in, convert in larger deliberate moves when rates suit you rather than in a hundred tiny forced conversions, and watch the actual rate and fee on each conversion rather than assuming it is free.

Where it fits your stack

Revolut Pro is the money layer; its job is to feed clean data into everything above it. The most valuable connection is to your accounting tool: a transaction feed into your bookkeeping system means reconciliation becomes matching rather than typing. Wire that up early, because it removes the most error-prone manual step in your whole finance stack.

Around that, the card layer connects to your spend: link cards to your ad platforms, your SaaS subscriptions, and your contractor payments so each cost centre has a clear source. For invoicing, pair Pro with whatever tool you raise invoices in and use the multi-currency account details as the receiving end, so the invoice currency and the receiving currency match and there is no conversion surprise.

Think of it as the hub between "money arrives" and "money is accounted for". Everything else (forecasting, your P&L, your runway view) reads from the clean record Pro and your accounting integration produce together.

Pitfalls to avoid

The biggest mistake is mixing personal and business money in the same flow because it is convenient in the moment. It quietly destroys the legibility you set the account up for, and you pay for it at tax time.

The second is converting reflexively. Every unconsidered conversion is a small fee, and across a year of international income the small fees are not small. Hold, then convert with intent.

The third is card sprawl: handing out cards without controls, leaving old cards live, and never reviewing them. Every live card is a small open risk. Review them on a schedule and freeze what you do not use.

The fourth is treating banking as something you check rather than something you operate. If you only open the app when something is wrong, you will always be reacting. Reconcile on a rhythm, and the account becomes a source of truth instead of a source of anxiety.

How to automate Revolut Pro

API and webhooks

Revolut documents a Business API and a Merchant API. Check whether they cover Pro accounts before you plan a build, because the Business API is described for Revolut Business accounts. If you need programmatic access to payments and transactions, you may need Revolut Business instead.

Built-in automation

Revolut Pro has payment links, invoices and QR codes inside the app, and your earnings settle in one place. An idea: send every client a payment link at the moment you finish the work, so you do not need to chase invoices later.

No-code automation

Check whether Zapier or Make has a Revolut connection before you plan a flow, and whether it supports Pro accounts. If not, export your transactions on a regular schedule and import them into your bookkeeping tool.