How to Convert Revolut Statements to Excel

To convert a Revolut statement to Excel, start with the simplest question: does Revolut's own export already give the exact account, currency, date range, and columns you need? If it does, use the native PDF, Excel, or CSV file first. If it is split by currency, mixes local and base-currency amounts, or does not preserve the formal statement trail you need, convert the PDF statement or consolidate multiple exports into one structured spreadsheet.

For bookkeeping, the useful output is not just "a spreadsheet". It is a transaction table with typed dates, descriptions, currency, amount, balance where available, and a source reference that lets each row trace back to the statement. That matters because Revolut is not a traditional bank statement layout with one predictable monthly file. Personal accounts, Business accounts, card activity, currency wallets, and merchant reports can all produce data in different shapes.

The right route depends on the job the file has to do. A single-currency CSV may be enough for a quick import. A Revolut bank statement PDF to Excel workflow is better when the formal statement is the record your accountant, lender, HMRC, Revenue, or auditor expects to see. A multi-currency business account may need both: the official statement as evidence and a cleaned workbook that separates original currency, base-currency amount, exchange rate, fees, balances, and references.

Invoice Data Extraction can help when the native export is close but not accounting-ready. You can upload Revolut PDF statements, describe the columns and currency treatment you want in a natural-language prompt, and download the result as Excel or CSV. The important part is deciding the target layout before you start cleaning the file.

When Revolut's own export is enough

Revolut's own export is usually the best first option when you need a simple file from a known account, in a known currency, for a defined date range. If the export gives your accountant the transaction date, description, money in, money out, balance, and currency in the shape they asked for, there is no virtue in converting the same data again.

That is especially true for simple single-currency work. A sole trader using one Revolut GBP or EUR account may be able to download a CSV or Excel file, tidy the column names, and send it straight to a bookkeeper. If you are comparing options across banks, the same first-principles test applies to most general bank statement to Excel methods: use the native export when it is complete, readable, and acceptable as the working file.

The complication is that "Revolut export" can mean several things. A Revolut Personal statement, a Revolut Business statement, an expenses or card export, and a merchant reconciliation report are not interchangeable records. They may cover different account activity, different metadata, and different reporting needs. A Revolut Business export to Excel for an accountant should normally be chosen from the business account area and checked against the exact entity, currency, and period being prepared.

The formal PDF statement still matters when the spreadsheet is not enough evidence on its own. Accountants, lenders, auditors, and tax authorities may ask for proof that the transactions came from the account record, not just a cleaned table. In those cases, keep the original PDF statement with the workbook, even if the spreadsheet is the file you actually analyse or import.

Why Revolut exports become messy for bookkeeping

The awkward part of Revolut bookkeeping is not reading a date or an amount from a file. It is deciding which amount belongs in the ledger when the account has more than one currency. A transaction can have an original currency amount, a base-currency amount, a fee, an exchange component, and a running balance. Those fields are useful, but only if the spreadsheet keeps them distinct.

Per-currency activity is another common source of confusion. If one month has GBP spending, EUR receipts, and USD subscriptions, the native exports may not naturally become one clean ledger. Older periods or separate currency wallets may also need to be pulled as separate files rather than one neat history. Combining them by hand can introduce duplicate rows, mismatched date ranges, and descriptions that no longer make it clear which currency wallet or account the transaction came from.

Accounting software adds another constraint. Some imports expect one signed amount column. Others allow separate debit and credit columns. Multi-currency records may require a currency code, but not a second converted amount column. If the Revolut CSV includes both local and base-currency values, a careless import can double count the transaction or put the wrong amount into the bank feed. Before shaping a Revolut CSV for Xero, check the destination file against the Xero bank statement import requirements rather than assuming every exported column should be imported.

For UK self-employed readers, the evidence trail is also part of the job. GOV.UK guidance on self-employed business records says self-employed people need to keep records of sales, income and expenses, make sure records are accurate and identifiable as business transactions, and keep proof including bank statements. That is why a cleaned spreadsheet should not erase the link back to the statement page, file name, account, currency, or reporting period.

The best spreadsheet model depends on the purpose. A simple bookkeeping import may need one amount column and a description. A multi-currency reconciliation workbook may need original currency, original amount, base-currency amount, exchange rate, fees, and balance. An accountant review file may need fewer columns than the export provides, but stronger references back to the source statement.

The spreadsheet layout that works for Revolut statements

A good Revolut workbook starts with the columns the accounting job actually needs. For most statement conversion work, that means date, description, original currency, original amount, base-currency amount where relevant, exchange rate when shown, balance, account or currency wallet, and a source reference such as statement file, page, or line context.

Do not preserve Revolut's visual layout just because it appears on the PDF. Bank statement conversion is useful because it turns a human-readable record into structured data. Typed dates, consistent currency codes, signed amounts, and stable source references matter more than keeping the rows in a shape that looks like the original statement.

Collapse to a single amount column when the destination requires it. That is common for simple single-currency bookkeeping imports, accountant-requested CSV files, or software routes that reject separate local and converted values. In that model, the workbook should make the chosen currency explicit and avoid leaving a second amount column that could be imported by mistake.

Preserve original and base-currency values when reconciliation matters. Cross-border subscriptions, foreign-currency card spending, supplier payments, and exchange transactions are easier to review when the sheet keeps the original amount, the converted amount, and the exchange rate or fee information where it appears. The same principle applies across bank-specific workflows, whether you are building a Revolut sheet or following an AIB bank statement to Excel workflow: design the output around the accounting use case, not the source layout.

For accountant handoff, add a short notes or category column only if someone will actually use it. Over-structuring the file can slow review down. A compact workbook with reliable dates, amounts, currencies, descriptions, balances, and source references is usually more valuable than a wide export full of card metadata that never maps into the accounts.

How to convert Revolut PDFs or exports into one clean workbook

Start by collecting the source files before opening a converter. Save the formal Revolut PDF statements for the right account, entity, currency, and date range. If you also have native CSV or Excel exports, keep them in a separate folder so you can compare totals and date ranges without mixing working files with source evidence.

Then define the workbook before extraction. A useful instruction might ask for one row per transaction, date as a true date field, description, original currency, original amount, base-currency amount where shown, exchange rate where shown, fees in a separate column, balance, and statement page or file reference. For a simple import, the instruction should say which single amount column to produce and which currency it represents.

Invoice Data Extraction fits this point in the workflow when the PDF is the source record and the native export does not give the layout you need. The product is built to convert financial documents into structured spreadsheets: you upload the Revolut PDF statement, describe the columns and currency treatment in a prompt, and download the result as Excel or CSV. For larger jobs, the same prompt-based workflow can process batches of files, so several months of statements can be converted with a consistent output structure.

If you are consolidating multiple months or currencies, keep source context in the output. Add columns for statement month, source file, account or currency wallet, and page reference. That makes later review much easier when a row looks duplicated, a balance does not reconcile, or an accountant asks where a transaction came from.

Before importing the workbook anywhere, run basic checks. Compare the statement period to the extracted date range. Scan for duplicated months. Check that debit and credit signs are consistent. Review currency totals separately before looking at the base-currency total. Where the statement includes opening and closing balances, use them as a reasonableness check, not as a guarantee that every row has been categorised correctly.

Preparing the file for Xero, QuickBooks, FreeAgent, or your accountant

The cleaned Revolut workbook should be shaped around its destination. A file for accountant review can carry more supporting columns than a file for software import. A file for Xero, QuickBooks, or FreeAgent usually needs a tighter structure: date, description, amount, currency where supported, and enough account context to map the transactions correctly after import.

Date format is the first thing to normalise. Use one format throughout the workbook and check that Excel recognises the values as dates, not text. Amount signs matter just as much. A debit shown as a positive number in one export and a negative number in another can break reconciliation if the files are combined without a rule.

Descriptions should be cleaned carefully, not aggressively rewritten. Bookkeepers often need merchant names, references, card details, or payment notes to decide the category. If a Revolut export includes more metadata than the accounting package will accept, keep the extra detail in a review workbook and create a narrower import version from it.

For Xero or QuickBooks, decide whether the import should use one amount column or separate money-in and money-out columns before you export the final CSV. For FreeAgent or an accountant handoff, confirm whether they want original currency values preserved or only the base-currency amount. The answer may differ between a simple domestic account and a Revolut Business account with cross-border payments.

The same handoff discipline applies to other bank statement projects, including the Bank of Ireland statement conversion guide: preserve the source statement, keep the working spreadsheet readable, and do not remove fields that explain how a transaction should be reviewed. VAT and self-assessment preparation depend on organised records, but the categorisation and tax treatment still need professional judgement where the facts are not obvious.

Choose the route based on the job the statement has to do

Use Revolut's native export when the work is simple: one account, one currency, one date range, and a CSV or Excel file that already matches the bookkeeping destination. Keep the PDF statement alongside it if the file may be needed as evidence.

Convert the PDF statement when the formal record is the source of truth. That is the safer route for accountant review, lender requests, HMRC or Revenue record keeping, audit support, or any job where the spreadsheet must trace back to the official statement rather than a manually edited export.

Consolidate multiple exports when the problem is spread across currencies, months, cards, or accounts. In that case, the goal is a controlled Revolut multi-currency statement to spreadsheet workflow, with source file, currency, original amount, base-currency amount, and reference fields kept visible.

Preserve dual-currency values when reconciliation matters. Collapse to a single amount column only when the import route requires it and the chosen currency is clear. The useful result is not just a Revolut statement to CSV or Excel file, but a spreadsheet that matches the accounting task: import, review, evidence, reconciliation, or accountant handoff.