To get a Tide bank statement to Excel, export a CSV from the Tide app or the web app, choosing a CSV type such as Standard, which lists cleared transactions with the running balance after each one. Or download a PDF statement and convert it. The CSV opens in Excel as it is. The PDF has to be turned into rows first.
The PDF route comes with three rules. According to Tide's guide to downloading statements and transactions, a custom date range statement covers up to 6 months per document, its end date must be at least 3 days ago, and a statement with more than 2,000 transactions is sent as a secure download link by email rather than as a direct PDF.
So for an account you or your client can still log in to, the CSV export usually does the job and nothing needs converting. A PDF has to be converted when it is what you have: the statements a client emails instead of giving you access, a full year that arrives as two or more custom-range PDFs (or as an emailed link on a busy account), the transaction history Tide emails when an account closes, and any job that needs the statement's own opening and closing balances. Those PDFs convert to Excel or CSV with one row per transaction.
Downloading Tide PDF statements: monthly, custom range and the 2,000-transaction link
Tide produces two kinds of PDF statement, and they suit different requests.
Monthly statements are "issued on the 4th of each following month, in-app", so the March statement appears on 4 April. Additional accounts get their own monthly statements on the same day. In the app, go to the Profile icon, then Bank account, then Account statements, select the month or months you need, and tap Share to save or send the PDFs. Tide's help centre gives no web path for monthly statements, so a client working on a laptop will usually find it easier to request a custom range.
Custom date range statements cover whatever dates you set, within the rules. In the app, tap your initials (top left), then Bank account, Statements and documents, Account Statements and Custom date range. On the web, open Account details (the 'i' icon, top right), then Statements, Statement type and Custom range. Additional accounts follow the same path.
The rules shape what a year of statements looks like in practice:
- A 12-month year is at least two documents. For a company with a 31 March year end, that is one statement for April to September and another for October to March. A catch-up job covering two years means four or more.
- The end date has to be 3 days in the past. A client asked on 31 March for statements to 31 March can't produce one until 3 April. Either wait, or take the custom range to an earlier date and pick up the last days from the CSV.
- A busy account's six months can come as a link. Over 2,000 transactions, Tide sends a secure download link by email instead of the PDF. If a client says the statement "didn't download", check their inbox before asking them to try again, and make sure the link reaches whoever is collecting the statements.
Monthly statements suit a client who will send one PDF a month as part of their routine. Custom range suits a year-end request, a lender's three or six months, or a catch-up.
The statement header differs by business type, which matters when you file statements for several clients or send one to a lender. A registered business's statement shows its legal name, trading name and registered address. A sole trader's shows their personal name, the business legal name, the trading name and the trading address. On a folder of PDFs from different clients, the header is what tells you whose account each one is.
Tide's CSV export: the Standard type, its running balance and what it leaves out
The CSV export sits with the transactions rather than with the statements. In the app, go to Pay, then View more, set your filters, tap the Share icon, choose a CSV type and tap Export. On the web, open Accounts, choose the account, click the Funnel icon, then Apply Filter and Export. The filters cover date, category, type and status, so you can cut the export to a VAT quarter or a tax year before it is made rather than deleting rows afterwards.
Tide asks you to pick a CSV type, and there is more than one. The type its help centre names is Standard: "Standard - Cleared only (including running balance)" in the app, "Standard (Cleared transactions only)" on the web. On the web you can also include attachments, which brings the receipts saved against transactions out with the export.
Tide's help centre mentions no OFX, QIF, QBO or Excel file, no date limit on the CSV, and no column list. The export is a CSV, which opens straight in Excel and goes into accounting software through its CSV import.
It is sometimes said that Tide's export is a bare list of transactions with no balance. The Standard type carries the running balance after each cleared transaction, so the balance is there. What the CSV lacks is the statement's frame:
- No statement period. The file covers whatever your filter selected, and nothing in it says which statement it corresponds to.
- No printed opening or closing balance. You can read the first and last running balances, but there is no figure issued by the bank to reconcile them against.
- Cleared transactions only. Anything still pending when you export is left out of the Standard type.
The PDF statement carries the period and both balances, which is why auditors, lenders and year-end files ask for statements rather than an export. Starling makes the same distinction between its CSV and its True Copy PDF statements, as the guide to getting Starling statements into Excel explains.
For a live account, though, a Standard CSV per period is the quickest way into Excel, and an accountant who can ask a client for a CSV instead of PDFs should. Other app-first business accounts set their own export rules. Monzo, for one, exports PDF, CSV or QIF for any range you choose, as the guide to converting Monzo bank statements to Excel sets out, and Revolut has its own routes, covered in Revolut Business statements to Excel.
Tide's accounting feeds and their start dates
Through Open Banking, Tide feeds transactions to Sage, FreeAgent, Coconut, KashFlow, QuickBooks, Crunch, Clear Books and Reckon One, as listed on Tide's accounting integrations page. Xero has a page of its own, which describes the Xero Connector, an enhanced sync costing £6.99 + VAT a month and included on the Smart, Pro and Max plans.
What Tide says about each feed is uneven. FreeAgent receives cleared transactions every 24 hours. QuickBooks imports daily. For the others Tide gives no frequency, so check the feed in the accounting software rather than assume it is current to yesterday.
The detail that decides how much history a feed brings is its start date. Sage and FreeAgent ask for one when the feed is set up, and Tide states no limit on how far back it can reach. Whatever that date is, the feed carries transactions from it onwards and nothing before it. That leaves gaps in some common situations:
- A client who moved to new accounting software partway through the year. The feed starts on the switch date, and the months before it are still part of the year's accounts.
- A feed connected late. A client who opened a Tide account in May and connected FreeAgent in October has five months the feed never saw unless the start date was set back.
- A catch-up job on a year that had no feed at all, such as unfiled Self Assessment for a sole trader who kept nothing in software.
Those months come from the CSV export if someone can still log in, and from the PDF statements if not. Whichever it is, end the uploaded history on the day before the feed's first transaction. Overlap the two and the same payment lands twice.
After closing a Tide account: the history Tide emails, and how to ask for it again
Once an account closes there is no app to export from, and the record that remains is what Tide sends. Within 10 days of closure, Tide emails "a copy of your full transaction history for all of your Tide accounts, except your Cash Register account". If that email has gone, the history can be requested up to 5 years after closing, and Tide emails it within 7 days of the request (Tide's account closure page sets out both).
Tide does not say what format the history arrives in. If it comes as a spreadsheet file, it is already rows and opens in Excel. If it comes as a PDF document, it converts like any other statement.
Two gaps are worth catching before a client closes, while there is still access:
- The Cash Register account is left out. A business that took payments through it needs that account's statements or export saved separately, because the closure history will not include them.
- Monthly statements have to be saved before closing. The closure history gives the transactions, but the monthly PDFs, with their printed opening and closing balances, are downloaded from the app, so the time to save them is before the account closes. A client who saved them has a ready check on the history; one who didn't has the history alone.
The years still matter after the move. HMRC expects a sole trader to keep business records for at least 5 years after the 31 January submission deadline of the tax year they relate to, and a limited company to keep its records for 6 years from the end of the financial year they cover. Tide's 5-year request window is measured from the closure date, so it can close before either duty ends. Save the closure email and whatever it contains with the client's permanent records on the day it arrives, rather than counting on requesting it again.
Which Tide route fits which job
| The situation | The route |
|---|---|
| A live account you or the client can log in to | A Standard CSV export, one per period |
| Ongoing bookkeeping in Xero, FreeAgent, QuickBooks or Sage | The accounting feed, from its start date |
| Months before the feed's start date | The CSV export, or the PDF statements if nobody can log in |
| A client who sends PDFs instead of access | Convert the PDFs |
| A full year for year-end accounts or a catch-up | Two or more custom-range PDFs, or the CSV |
| An auditor, a lender or an HMRC enquiry asking for statements | The PDF statements, which carry the period and the balances |
| A closed account | The closure history, plus any monthly statements saved before closing |
When you ask a client for a Tide statement for your records, ask for both if they can manage it: a Standard CSV for the period, which gives you the transactions as rows, and the PDF statements, which give you the opening and closing balances to check them against. If a client will only send PDFs, take the PDFs. Another round of export instructions to a client who won't export often costs more time than converting what arrived.
Sole traders bring one more consideration. Making Tax Digital for Income Tax, which from April 2026 covers sole traders and landlords with qualifying income over £50,000, requires digital records kept in compatible software. For a Tide sole trader, the Making Tax Digital for Income Tax records can come from the feed or a regular CSV import, with converted statements filling the months the feed missed.
Converting Tide PDF statements to Excel or CSV
Once the statements are PDFs, none of Tide's own routes turn them back into rows. With Invoice Data Extraction you upload them as they arrived and convert Tide PDF statements to Excel or CSV: monthly statements, custom-range statements, the closure history if it came as a PDF, and additional accounts' statements alongside the main account's, all in one task. A task takes up to 6,000 files, and a single PDF can run to 5,000 pages, so a long custom-range statement or a full closure history goes in as one file.
You say what the spreadsheet should be in plain words. That can be a list of fields (date, description, money in, money out, balance), or the job the data is for, such as "I'm reconciling bank statement transactions against our invoices". The ready-made bank statement prompt asks for one row per transaction and is a starting point you can add to. When several statements go in together, two additions are worth making:
- A statement period column, so every row says which statement it came from, and the sheet can be checked against each statement's opening and closing balance.
- An account column, so a main account's rows and an additional account's rows can be told apart and filtered.
The download is Excel, CSV or JSON. In Excel, amounts come through as numbers and dates as dates, so totals, filters and pivot tables work straight away. After your columns come two more. Source File gives the file and page each row came from. Review Needed flags a value or a row the panel of AI agents cannot agree on, with what to check. In the results viewer, clicking the file name on a row opens the statement page beside it.
The output is a spreadsheet, not an OFX or QIF file. The CSV or Excel file is what goes into the accounting software, through its CSV import.
Worked example: a client who has left Tide
A joinery company with a 31 March year end banked with Tide until June 2026, when it moved to a high-street bank and closed the Tide account. Its accountant still has the accounts for the year to 31 March 2026 to finish, and the months from April to closure to bring into the new books. The director hands over what he has: 24 monthly Tide statements saved from the app, April 2024 to March 2026, and the closure history Tide emailed, which in this case arrived as a PDF.
All 25 PDFs go into one task with this prompt:
One row per transaction. Date as DD/MM/YYYY, description, money in, money out, balance. Add a Statement column with the statement month as YYYY-MM, or "Closure history" for the closure history. Add the opening and closing balance printed on the statement to each row, blank if the document shows none.
An invented extract of what comes back, from the end of the March 2026 statement and from the closure history around the year end:
| Date | Description | Money in | Money out | Balance | Statement | Opening | Closing |
|---|---|---|---|---|---|---|---|
| 26/03/2026 | CARDIFF TIMBER SUPPLIES LTD | 1,846.50 | 14,032.94 | 2026-03 | 12,480.20 | 12,268.34 | |
| 30/03/2026 | HMRC VAT | 3,214.60 | 10,818.34 | 2026-03 | 12,480.20 | 12,268.34 | |
| 31/03/2026 | R ADEYEMI | 1,450.00 | 12,268.34 | 2026-03 | 12,480.20 | 12,268.34 | |
| 31/03/2026 | R ADEYEMI | 1,450.00 | 12,268.34 | Closure history | |||
| 01/04/2026 | SCREWFIX CARD PAYMENT | 86.40 | 12,181.94 | Closure history | |||
| 02/04/2026 | WEST BAY HOMES LTD | 4,200.00 | 16,381.94 | Closure history |
The two R Adeyemi rows are the same payment. The closure history repeats every transaction the monthly statements already carry, so the sheet holds those two years twice. The Statement and Date columns make this a quick filter: keep the monthly statements' rows for April 2024 to March 2026, and keep the closure history's rows only from 1 April 2026. Everything up to the year end now comes from documents with printed balances, and the closure history supplies only the months nothing else covers.
Then the check, the same one used when reconciling a bank statement against the books, applied across 24 statements at once:
- Each statement's last row lands on its printed closing balance. In the extract, March's final balance of 12,268.34 matches the Closing column.
- Each month's closing balance is the next month's opening. A pivot table by Statement, with Opening and Closing set to Max, shows all 23 joins in month order.
- The join between the two documents holds. The first closure history row kept, Screwfix on 1 April, takes the balance from 12,268.34 to 12,181.94, carrying on from March's closing figure.
A break in any of these points to a missing month or a missing page, and the Source File column names the PDF and page behind the rows either side of it. With the balances carrying through, the year to 31 March 2026 is ready for the accounts, and the rows from April go to the new accounting software as the opening months of the next year.
Importing the Tide sheet into Xero, FreeAgent, QuickBooks or Sage
Xero, FreeAgent, QuickBooks and Sage all take a bank statement as a CSV file, whether it came from Tide's export or from converted PDFs. The file is imported into the bank account in the software; nothing posts there directly. The steps for Xero are in the guide to importing bank statements into Xero, and the other three follow the same pattern: choose the bank account and upload a CSV in the layout the import asks for.
A few points save rework at that last step:
- Shape the columns before you convert. Some imports want separate money in and money out columns, others one signed amount. The prompt can ask for either, for example a single Amount column with payments as negative numbers. A Structured Prompt fixes the exact headers in the exact order, and the Source File and Review Needed columns can be left out in Preferences when the file has to carry nothing but the import's columns.
- Keep the statement columns out of the import. Statement, Opening and Closing did their work in the reconciliation. Delete them from the copy you upload.
- Mind the feed. If a Tide feed is or was connected to the same software, import only the dates before its first transaction, or after it stopped, so no payment appears twice.
- One import per bank account. An additional Tide account's rows go to its own bank account in the software, which is where the account column from the conversion earns its place.