Pro
For people who manage the books every week.
500 pages / month
See planTurn PDF bank statements into clean Excel and CSV files in seconds. Built for thousands of banks worldwide, no sign up to try.
Drag a file in, or pick one. You see the rows first, then you save.
PDF, CSV, TXT, TSV, IIF, OFX, QBO, QFX and QIF files. Everything runs in this page. Your file never leaves your device.
| Date | Description | Amount | Balance | Category |
|---|
Pick a pair and the tool at the top is set for you. Drop your file in and save in the new kind.
Save your statement as Excel and the workbook carries a second sheet: a ready-made dashboard of your money. No setup, no formulas to write - open the file and the numbers are there.
| Salary | 52% | |
| Rent | 24% | |
| Groceries | 15% | |
| Other | 9% |
Tap a star and tell us how it went.
Tap a star:
Loading ratings... out of 5 · ratings
Your stars help us make it better.
One rating per device on this site for now. One rating per IP needs a server step, and it is not live yet, so a second device can rate again. This stops casual double votes, it does not prove who a person is.
No app to add. It takes a few secs.
Tap Pick Files, or drag your file in.
The converter finds the date, the description and the amount in each row.
You see a green tick when the sums add up.
Save as Excel or CSV. Pro also saves for QuickBooks and Xero.
Files from 1,000+ banks work here
Older tools need a fixed template for every bank. This converter reads the layout of each page and adapts, the way a careful bookkeeper would.
Reads any bank layout. No template, no set up.
Reads scanned PDFs and phone pics too.
Joins split lines. Fixes dates and sums. Drops junk rows.
First sum plus all rows must match the last sum.
Tags each row: pay, rent, food, fuel and more.
Finds rows that show up two times.
Keeps $, €, £ and more, just as in your file.
Maps rows to the right QuickBooks and Xero columns.
Start free. Pay only when you need more pages.
For people who manage the books every week.
500 pages / month
See planFor teams handling many files.
1,500 pages / month
See planFor firms with very high volume.
5,000 pages / month
See planFor firms that need more than Enterprise.
Custom pages
See planAll plans are page based: 500 pages for $12, 1,500 pages for $29, and 5,000 pages for $49 a month. Pay by year to save half.
The API is for Business plan users, and access is by request only. Ask here, and we set up access for your team if your plan fits.
Tell us who you are and what you want to build. We read each ask and reply by email.
Tell us. We will look at it.
The converter reads the layout, finds each row, cleans it, tags it, and checks the totals. You just drop the PDF in.
Most banks. See the bank list above. If yours is not there, try it. The converter adapts to most layouts.
Excel and CSV on all plans. Pro adds QuickBooks and Xero files.
Through Lemon Squeezy, our payment provider. Card, PayPal, and Apple Pay are supported, and VAT is calculated by Lemon Squeezy.
Yes, with Pro. Text PDFs work on all plans.
One page of your PDF counts as one page.
Start free. Pay only when you need more pages.
For people who manage the books every week.
per month
$0.024 a page.
500 pages / month
Secure checkout by Lemon Squeezy.
For teams handling many files.
per month
$0.019 a page.
1,500 pages / month
For firms with very high volume.
per month
$0.0098 a page.
5,000 pages / month
Secure checkout by Lemon Squeezy.
For firms that need more than Enterprise.
Tell us your volume and we will set a fair price together.
Custom pages
Custom pricing. We reply within one business day in most cases.
All plans are page based: 500 pages for $12, 1,500 pages for $29, and 5,000 pages for $49 a month.
Pay by year to save half: the same plan costs less per month, and your plan simply runs without monthly renewals.
Tap a plan to see what it includes
| What you get | Free | Pro · $12 | Business · $29 | Enterprise · $49 | Custom · Contact |
|---|---|---|---|---|---|
| Pages you get | 1 to 5 / day | 500 / month | 1,500 / month | 5,000 / month | Contact |
| Excel and CSV | ✓ | ✓ | ✓ | ✓ | ✓ |
| Smart layout detection | Basic | ✓ | ✓ | ✓ | ✓ |
| Auto cleanup and balance check | No | ✓ | ✓ | ✓ | ✓ |
| Auto tags and duplicate check | No | ✓ | ✓ | ✓ | ✓ |
| Batch: up to 25 files at once | No | ✓ | ✓ | ✓ | ✓ |
| QuickBooks and Xero formats | No | ✓ | ✓ | ✓ | ✓ |
| Batch, 25 files at once, ZIP save | No | ✓ | ✓ | ✓ | ✓ |
| Files up to 50MB, PDFs with a code word | No | ✓ | ✓ | ✓ | ✓ |
| Team seats | 1 | 1 | 5 | 5 | Custom |
| API, by request only | No | No | ✓ | ✓ | ✓ |
| One click download | ✓ | ✓ | ✓ | ✓ | ✓ |
| Every output format included | No | ✓ | ✓ | ✓ | ✓ |
| Files processed in your browser, never uploaded | No | ✓ | ✓ | ✓ | ✓ |
| Bulk file upload | No | ✓ | ✓ | ✓ | ✓ |
| Global bank support | ✓ | ✓ | ✓ | ✓ | ✓ |
| Nothing is stored after you close the tab | No | ✓ | ✓ | ✓ | ✓ |
| 24/7 Email Support | No | ✓ | ✓ | ✓ | ✓ |
| Priority email support | No | No | ✓ | ✓ | ✓ |
| Large file support (10MB+) | No | No | ✓ | ✓ | ✓ |
| VAT invoices and billing by Lemon Squeezy | No | No | ✓ | ✓ | ✓ |
| Process PDFs with over 100 pages | No | No | ✓ | ✓ | ✓ |
| Priority Support | No | No | No | ✓ | ✓ |
Last updated: October 24, 2026 · Written by Joseph Adam
Joseph Adam
Founder and developer of Bank Statement Converter
Hi, I am Joseph Adam, and I built this tool for one reason: I was tired of retyping bank statements by hand. For years I have worked with bookkeeping data, bank exports, and accounting file formats like OFX, QBO, QFX, and IIF. Again and again I watched the same story: a client sends a statement as a PDF, and someone spends an evening typing rows into Excel, hoping no digit gets dropped. One mistyped number in a ledger can cost hours to find later, so I decided to build a converter that gets the rows out cleanly and shows them to you before you save anything.
The converter reads your PDF directly in your browser. It detects the layout of each page, finds the date, description, amount, and balance in every row, cleans up split lines and junk rows, and then runs the check that matters most: opening balance plus the rows should equal the closing balance. When the totals line up you see a clear signal, and you always get to review every row before you save the file. Nothing is perfect, which is exactly why the preview comes first: you are the final check, and the tool does the typing.
Your statement file never leaves your device. There is no upload step, no server that stores your rows, and no copy of your data anywhere. That is a deliberate choice, not a marketing line. You can read it again in the Privacy Policy, and you can verify the behavior yourself: open your browser network tools, convert a file, and watch that no statement data is transmitted.
Three things. First, honesty about limits: text-based PDFs convert well, and you should always review the rows before you trust them, because your books deserve that check. Second, your data stays yours: files are processed in your browser and never uploaded. Third, straight answers: if a statement does not convert the way you expect, write to me through the contact form and I will look at it personally.
If you have one file now and then, the free plan may be all you need. If you process many statements each month, Pro or Business gives you more pages and the accounting file formats. Either way, I hope this tool gives you back the evenings you used to spend typing.
Last updated: October 24, 2026
These terms are the rules for the use of Bank Statement Converter. When you use this site and tool, you agree to these terms. If you do not agree, please do not use the tool.
Bank Statement Converter turns PDF bank statements into Excel and CSV files. The converter reads rows automatically, cleans them, and checks the totals. The tool is a help for your own work. It is not a bank, and it is not a bookkeeper or tax adviser.
You can try the tool with no account for a small number of pages. A free account gives you more pages each day. Paid plans need an account so we can track your pages and seats. Keep your login safe. You are in charge of work done through your account.
Free plan: 1 page a day with no account, and 5 pages a day with a free account. Each count is per 24 hours. Pro plan: $12 per month for 500 pages per month. Business plan: $29 per month for 1,500 pages per month, with API access on request. Enterprise plan: $49 per month for 5,000 pages per month, with all Business features. Pay by year and you save half: Pro is $72 a year, Business is $174 a year, and Enterprise is $294 a year. Custom plan: price and page count are set by agreement, for more than 5,000 pages per month, through the contact form. Page counts, file types, and tools in each plan are shown on the pricing page. One page of your PDF counts as one page.
We may change plan prices or page counts in the future. If we do, we will show the new figures on this site before they apply to a new billing period.
Paid plans are billed in advance for each billing period, month or year, and they renew automatically at the end of each period unless you cancel. Payments are handled by Lemon Squeezy as the merchant of record. Card, PayPal, and Apple Pay may be used where Lemon Squeezy supports them. Tax, such as VAT, is calculated and added by Lemon Squeezy where the law requires it.
You can cancel at any time from the Lemon Squeezy customer portal. The link to that portal is in the invoices Lemon Squeezy emails you. When you cancel, your paid plan stays active until the end of the period you have paid for, and then it stops. It does not renew after that.
Refunds are handled through Lemon Squeezy, under their rules and the law that applies to your sale. If a file cannot be read and we cannot fix it, tell us through the contact form soon after the job, and we will provide a fix or a refund for that job. Refund requests for a past period that was fully used may not be granted, except where the law requires it.
Your bank files and the sheets you make from them are yours. You give us only the short right we need to read a file and make your sheet when you ask us to. You are in charge of keeping your own copies of your files and sheets.
Automated reading is good, but it is not perfect. A faint scan, a torn page, or an odd bank layout can produce a wrong row or amount. You must check your sheet with care before you use it, and you must check that the sums match your bank file. Do not file tax, send a loan form, or make a pay choice based on a sheet you have not checked. See our Disclaimer for more on this point.
In short: the tool is provided as is. We work hard to keep it accurate and online, but we do not promise it will never fail, never be slow, or fit every need. To the fullest extent the law allows, we are not liable for lost profits, lost data, or costs that come from using a file you did not check, or from downtime. Where the law does not allow a limit, that limit does not apply. Nothing in these terms takes away rights you have by law that can not be taken away.
Bank names and marks shown on this site are the marks of their owners. We show them only to say which bank files the tool can read. That is not a sign that a bank backs or approves this tool.
We may update these terms from time to time. The new terms will be shown on this page, with a new date at the top. If you keep using the tool after a change, that means you accept the new terms for your new use.
Use the contact form for any ask about these terms. We reply within 1 business day in most cases.
Last updated: October 24, 2026
This page tells you what data Bank Statement Converter takes in, how it is used, and what rights you have. We keep this short and plain. If a part is not clear, ask us through the contact form.
When you use the tool, your file is read in your browser on this page, and we never receive it. If a future paid feature ever needs server processing, this policy will be updated first and your consent asked for.
If you tap a star in the rating band, we store your star count, from 1 to 5, a device id, and a hash of your IP address. The hash is made in your browser with SHA-256. We never store your raw IP address. One IP keeps one rating, and a new tap updates that same rating. If the IP lookup fails, the device id is used and the rating band says so. Ratings are stored in Supabase. We use the stars only to show the true average score and the count of ratings.
If you send a note through the contact form, we get your name, your email, the subject, and your message. We use them only to reply to you and to fix the point you raised.
If you sign in with Google, or with email and a password, Supabase Auth holds your name, email, and a hash of your password for login only. Only login facts are held there. Bank statement files, rows, balances, and account numbers are never sent to Supabase and never stored there.
Pay is handled by Lemon Squeezy, not by us. We do not see or store your full card number. Lemon Squeezy tells us whether a plan is paid, stopped, or past due, so we can set your plan correctly.
Like most sites, our host may keep short logs of page views, such as the page shown, the time, and the kind of browser. We use these only to keep the site safe and to fix breaks.
Files read in your browser stay in your browser. Nothing is uploaded and nothing is stored on a server. Files you save are saved by you, on your own device. Keep your own copies in a safe place. Do not send us bank files by email or through the contact form. The contact form is for words only.
This site uses a small number of cookies and like stores in your browser. Some are needed for the tool to work, such as to keep your device id for ratings, and to keep your language picks. You can clear or block cookies in your browser at any time. If you block the needed stores, some parts, such as ratings and language picks, may not work as they should.
Each of these firms has its own privacy rules. We pick firms with care, but their use of data is set by their own terms.
We may show ads on this site, and we may use Google AdSense to do so. This part tells you how ads use cookies.
We do not sell your bank files, and we do not use the rows in your bank files to pick ads for you.
If you are in the UK or in the EEA, you have rights under GDPR. In short form, you may ask to see the data we hold on you, ask us to fix it if it is wrong, ask us to delete it, ask us to limit how we use it, ask for a copy you can move, and say no to some uses. We will reply to a valid ask in the time the law sets, in most cases within one month.
If you are in California, or in a US state with a like law, you may ask to know what data we hold on you, ask us to delete it, and ask us not to sell it. We do not sell your own data. We will not treat you in a worse way for using your rights.
To use any of these rights, send a note through the contact form. Tell us which right you want to use, and the email tied to your account or rating, so we can find the right rows.
This tool is for grown ups who do book work. It is not made for kids under 13, and we do not knowingly take in data from kids under 13. If you think a kid under 13 has sent us data, tell us through the contact form, and we will delete it.
Contact notes are kept only as long as we need them to reply and to keep a short record of the fix. Ratings are kept while the rating band is live, so the score stays true. Account facts are kept while your account is live, and for a short time after that where the law or tax rules ask us to keep them.
We may update this page from time to time. The new text will be shown here, with a new date at the top.
Use the contact form for any privacy ask. We reply within 1 business day in most cases. Please do not put bank files, card facts, or login codes in your note.
Last updated: October 24, 2026
This page sets out the limits of Bank Statement Converter, in plain English. It sits with our Terms of Service and our Privacy Policy.
The tool reads your PDF automatically and builds a sheet. It checks totals as part of the job, but no tool of this kind is right every single time. A faint scan, a low quality image, a torn or bent page, handwritten marks, or a new or odd bank layout can all lead to a wrong date, description, or amount, or to a row that is missed or shown twice.
The sheet you save is a draft for your own work. It is not the bank file itself, and it does not take the place of your bank file.
You must do this check before you use the sheet for tax, for a loan, for a court or form, for pay, or for any choice where a wrong sum could cost you or others. If a sum does not match, fix the sheet by hand, or run the file once more, and check again.
This tool does not give money, tax, law, or book advice. It does not tell you how to file, what you can claim, or how to run your books. For that kind of help, talk to a trained bookkeeper, tax helper, or adviser who knows your case.
Bank names, logos, and marks on this site belong to their owners. We name banks only to say that files from those banks can be read by the tool. That is a note on fit only. It is not a sign that a bank backs, approves, or is tied to this tool, and it is not a sign that we are tied to that bank.
Files made for QuickBooks, Xero, Sage, and FreshBooks are made to fit the import rules those tools publish. Those firms may change their rules at any time. Check the import screen in that tool with care before you finish an import, and keep a back up of your books first.
Have a file we can not read, a billing ask, or a note on how the tool works? Send us a note with the form below. That form is the best way to reach us.
We reply within 1 business day in most cases. Please use the form. Do not send bank files, card facts, or login codes in your note. If a file will not read, tell us the bank name, the file type, and what went wrong, in words.
Your email app should have opened with your message ready to send. If it did not open, write to us directly and we will reply within 1 business day in most cases. If your question is about a payment or a plan, the Lemon Squeezy invoice email holds the link to the customer portal where you can cancel or change your card.
Your account, your usage, and your local history in one place.
Sign in with Google or with email to get 5 pages every 24 hours, your usage history, and this dashboard. As a guest you still get 1 page every 24 hours.
Pro member
500 pages a month · every save format · 25 files per batch · insights dashboard in your Excel download.
Guest
Current plan: Free
Thanks for being on a paid plan! Every save format and the big batch are unlocked on this account.
Payments run on Lemon Squeezy. A paid plan starts only after Lemon Squeezy confirms the payment through a signed webhook. This page never grants a plan by itself.
You have not rated the tool yet.
This list lives only in this browser. It holds the file name, date, formats, and page count. No rows, no balances, no account numbers, and nothing here is sent to Supabase.
No conversions in this browser yet. Convert your first statement and it shows up here.
Clear my local data wipes the conversion list and the page count in this browser. Delete my account removes your email, plan, and usage from the server right away, after you confirm. Statement files are read in your browser only and are never uploaded to Supabase or to any other company.
Short, practical guides on bank statements, spreadsheets, and accounting tools. Every guide is written and maintained by Joseph Adam, who builds and runs this converter.
October 24, 2026
What a bank statement is, what it shows, why you may need one, and the easy ways to get it from your bank.
Read this postOctober 24, 2026
The last 4 digits are the final 4 numbers of your account number. See where to find them, and how to stay safe.
Read this postOctober 20, 2026
Drop in your PDF, check each row, and save a clean Excel file. A step by step guide, plus the checks to run before you trust the sums.
Read this postOctober 18, 2026
Make the right file type, map the columns in the right way, and import with no stray rows. Plus what to do if QuickBooks says no.
Read this postOctober 15, 2026
Use the Xero file type, set dates and signs in the right way, and check the import screen with care before you finish.
Read this postOctober 12, 2026
The one sum check that tells you if a sheet is sound. How to do it by hand, and what a gap in the sums is trying to tell you.
Read this postOctober 9, 2026
Turn 12 monthly files into one workbook for the year. Keep the order right, drop the rows that show two times, and keep a clean trail.
Read this postOctober 6, 2026
Scans and phone pics can be read, but the grade of the pic sets the grade of the sheet. Light, flat, and sharp wins each time.
Read this postOctober 20, 2026 · Blog
A PDF is made for reading on a screen or on paper. It is not made for work. In a PDF, the rows sit still. You can not sort them, you can not add them up with one click, and you can not move them into a book tool with ease. When you turn the same rows into Excel, each date, each note, and each sum sits in its own cell. Then the sheet can sort, add, and search for you.
Think of a shop owner who wants to know what she spent on stock in March. In a PDF, she must read each row by eye and write the sums down by hand. In Excel, she can sort the rows by name, pick the stock rows, and see the total at once. The same is true for fees, rent, pay, and tax sums. A clean sheet saves hours, and it cuts the slips that come from typing rows by hand.
Excel is also the form most helpers ask for. A tax helper, a bookkeeper, or a loan officer can open a sheet, check it, and use it at once. A PDF makes them do the manual work first. So the first step in most bank work is to turn the PDF into a sheet you can trust.
You need three things. First, the true PDF from your bank for the full span you want to work on. Second, a tool that can read the PDF and lay the rows out as a sheet. Third, ten quiet minutes to check the rows with care when the sheet is made. The check is part of the job, not an extra. A sheet you did not check is a sheet you can not yet trust.
Pick the period with care. For tax work, that may be a full month, a full three months, or a full year. For a loan form, it may be the last three or six months. Make sure the period in the PDF starts on the first day and ends on the last day, with no gap in the middle. If a day is missing, the sums will not add up, and the gap can be hard to spot later.
It helps to name the file at the start. Use the bank name, the year, and the month, such as Bank Name 2026 March. A clear name means you can find the file in a week or in a year, and you can match it to the sheet you make from it.
Log in to your bank on their site or in their app. Open the account you need, then look for a part named Statements, Documents, or Downloads. Pick the month you need and save the PDF to your device. Steps vary a bit from bank to bank, but the path is much the same in most banks. Save the file as it comes. Do not print it and scan it back in if you can help it.
A PDF that comes from the bank has true text in it. The words and sums sit in the file as text, so a tool can read them in a clean way. A scan or a photo has no true text. The tool must guess the text from a pic, and a guess can be wrong when the print is faint. That is why the bank PDF is the best start, on all plans, each time you can get one.
Check the PDF before you move on. Open it and make sure all the pages are there, from the first page to the last page. Make sure the first balance and the last balance are both shown. Those two sums are the key to the big check at the end, so a file with no end balance is a file you should swap for a full one.
Open the tool on the home page of this site. Drop your PDF into the box, or tap Pick Files and pick the file from your device. If you need the sheet words, dates, or sums in a tongue that is not English, pick that tongue in the sheet tongue bar first. That pick sets the sheet only. It does not change the words of this site.
The tool then reads the file and finds the date, the words, and the sum in each row. It lays the rows out in a table on the screen, so you can see them before you save a thing. This look first step matters. You can spot a row that looks cut, a sum with the wrong sign, or a date that looks off, while the fix is still quick and easy.
When the rows look right, save the file. Tap the Excel key to save an Excel file, or save as CSV if you want a plain text file that most tools can open. Open the saved file in Excel or in a like sheet tool, and give it one last look. The job for one month of rows should take less than a minute once you have done it a few times.
Start with the big sum check. Take the balance at the start of the period. Add all the rows, with money in as plus and money out as minus. The total should match the balance at the end of the period, to the last cent. Our tool runs this check as part of the job and shows a tick when the sums add up. If the sums do not match, stop. Do not use the sheet yet.
Next, spot check a few rows by eye. Pick the first row, one row in the middle, and the last row. For each one, set the date, the words, and the sum in the sheet side by side with the same row in the PDF. They should match in full. A spot check takes one minute, and it can catch a flaw that a sum check alone can miss, such as two rows with swapped words.
Last, scan the sheet for rows that look odd. Look for blank dates, sums with no sign where a sign should be, sums that are far too big, and the same row shown two times. Sort a copy of the sheet by date and look down the list. Odd rows stand out when the rest of the sheet is neat and in order.
Do not fix the sheet by guess work. Go back to the PDF and read the true row there. If the date is wrong in the sheet, type the date from the PDF. If the sum is wrong, type the sum from the PDF, with the right sign. If a row is missing, add it in the right date place, with the words and the sum just as the bank shows them. Each fix should come from the bank file, not from your head.
If a whole page looks wrong, the cause may be the file, not the sheet. A faint scan, a page at a slant, or a page with a shade across it can all make a bad read. In that case, get a fresh bank PDF if you can, or take a new, clear pic of that page in good light, and convert that page once more. One fresh read can save a long list of hand fixes.
When you have made your fixes, run the sum check once more from the start. The start balance plus all the rows must match the end balance before you move on. Then spot check the rows you fixed. Only when both checks pass is the sheet ready to use for books, tax, or a form.
Keep the bank PDF and the sheet side by side in one folder. Give the sheet the same name as the PDF, plus the word sheet at the end. For one month, a name such as Bank Name 2026 March Sheet is clear. For a year book, add the word Year. Clear names sound like a small thing, but they save real time when a helper asks where a sum came from months later.
Save in the form your next step needs. Excel is best for work you will do in a sheet, such as sort, tag, and add up. CSV is best as a plain form that many tools can take in. If the next step is QuickBooks or Xero, pick that file type in the tool, which is part of Pro, so the columns land in the places those tools look for.
Keep a back up copy that you do not edit. Work on a copy, and keep the first saved sheet as it came out of the tool. If a sort or a fix goes wrong later, you can start again from the clean copy, and you still have the bank PDF as the true base for all of it.
With a checked sheet, most bank jobs get fast. You can sort rows by name to group all the buys from one shop. You can add up a month of fees and see if a fee is new. You can tag rows by kind, such as stock, rent, wages, and tax, and get a clear view of where the money went. You can also find one payment in a snap with search, in place of reading page by page.
You can send the sheet to the tools and people who need it. Book tools such as QuickBooks and Xero can take in the rows, so you do not type them by hand. A tax helper can work from the sheet at once. For a loan or a visa form, the bank PDF is still the proof they ask for, and the sheet is the work file that sits next to it.
Keep the habit for each new month. Get the bank PDF, convert it, check it, name it, and file it in the same folder. Ten minutes a month beats a long, hard week at tax time, when a year of rows must be found, checked, and added up all at once under time stress.
Try the tool on the home pageAll blog postsOctober 18, 2026 · Blog
QuickBooks can take in bank rows from a file, so you do not have to type each row by hand. That saves time and cuts typing slips. But QuickBooks trusts the file you give it. If a date is wrong, a sum has the wrong sign, or a row shows two times, QuickBooks will take that flaw into your books. Then your books will be wrong in a way that can be hard to find weeks later.
A clean file means three things. Each row has a true date that QuickBooks can read. Each row has clear words, so you can tell what the payment was. Each sum is a plain sum, with money in and money out shown in the right way. When those three things are right, the import is smooth, and the rows sit in the bank feed ready for you to sort and tag.
The time to clean a file is before the import, not after it. Fixing ten rows in a sheet takes minutes. Hunting for one wrong row in a month of booked rows, after you have tagged and matched them, can take an hour. A short check first is the cheap path, each time.
Use the QuickBooks file type in the tool, which is part of Pro. That kind lays the date, the words, and the sum out in the columns QuickBooks looks for when it reads a bank file. A plain Excel sheet may look fine to your eye, but if the columns sit in the wrong places, QuickBooks may put the words in the sum field, or fail to read the file at all.
If you start from a plain sheet, keep the columns plain and few. One column for the date, one for the words or payee, and one for the sum is the base shape most imports want. Take out title rows, total rows, and blank rows at the top and foot of the sheet. Those extra rows are for reading by eye. In an import file, they turn into stray rows or errors.
Keep sums as sums, not as text. A cell that shows a money sign and commas as typed text may look like a sum, but QuickBooks may read it as words and skip it. In a good import file, the cell holds a true sum, and the money look comes from the cell style, not from typed signs in the cell.
Convert your PDF first, then run the big sum check. The balance at the start, plus all the rows, should match the balance at the end. Do not import a sheet that fails this check. Fix it first, while the rows are still in a small sheet where a flaw is easy to spot and easy to fix by hand from the bank PDF.
Look down the date column and the sum column with care. Dates should all be in one style, such as day, month, year, in the same order from the first row to the last. Sums should have one clear rule for signs: money in is plus, money out is minus, or the split your file type uses. Mixed styles in one column are the top cause of a bad import.
Make a back up of your QuickBooks books before any bulk import, as you should with any big change. A back up means a bad import is a small slip you can undo, not a long fix. Save the back up, save the import file, and keep the bank PDF in the same folder, so all three parts of the trail sit in one place.
In QuickBooks, go to the bank feed or import part, pick the bank account the rows belong to, and pick the file you saved. QuickBooks will show a map screen. This screen is where you tell it which column in your file is which field in QuickBooks. Take your time here. A right file with a wrong map still lands in the wrong way.
Match the date column to the date field. Match the words column to the memo or payee field, as your QuickBooks set up names it. Match the sum column to the sum field. Then check the date style shown on the screen. If your sheet puts the day first and QuickBooks reads the month first, a date such as 03 04 can land in the wrong month, and that kind of flaw is hard to spot at a glance.
Read the first few rows on the map screen as if they were in your books. Does the date look true? Does the payee name sit in the right field? Does money out show as money out? If one of those looks off, stop, fix the map or fix the file, and start the import once more. Do not push a flawed map through and plan to fix the rows later.
If this is your first import, or your first import for a new bank, bring in one month first. One month is a small set of rows, so you can check them all by eye in a few minutes. If the month lands well, you can import the rest with trust. If it lands in a wrong way, you have a small set to clear out, not a full year to undo.
After the test import, pick three rows in QuickBooks and check them against the bank PDF: the first row of the month, one row in the middle, and the last row. Check the date, the words, and the sum for each. Then check the month total in QuickBooks against the sum check from your sheet. The two should tell the same tale.
When the test month is right, keep the same steps for the rest. Use the same file type, the same map, and the same date style for each month. A steady way of work means each new import feels the same, and a flaw stands out at once, since it breaks the pattern you know well.
When QuickBooks turns a file down, it is most often for a small, plain cause. A blank row at the end of the sheet is a top cause. A sum with a money sign typed in the cell is an other. A date in a style it can not read is a third. Open the sheet, look for those three things first, clear them, save the file once more, and try the import again.
If the error note names a row or a line, go to that row in the sheet and read it with care. Look for a sum in the date cell, words in the sum cell, or a row where two bank rows were joined into one. Fix that row from the bank PDF, not by guess work. Then save and try again. Most files pass on the next try once the named row is clean.
If the file still fails, make the file smaller. Split it by month and import one month at a time. A flaw that hides in a year of rows will show up fast when you test month by month, since the bad month will be the one that fails while the rest pass. That split turns one big hunt into one small one.
When the rows are in, open them in QuickBooks and sort by date. The first date should be the first date of your period, and the last date should be the last date. A row far out of span, such as a date in the wrong year, is a sign the date style was read in the wrong way. Catch that now, before you tag and match the rows.
Check the sums once more in QuickBooks. The total of money in and the total of money out for the period should match the totals from your sheet and from the bank PDF. If a total is off by the size of one row, look for a row shown two times or a row that did not come in. If a total is off by twice a row, look for a row with the wrong sign.
Only then sort, tag, and match the rows in your normal way. Tag each row to the right book code, match rows that link to bills or sales, and leave a note on any row you fixed by hand. A short note now saves a long search later, when you or your helper asks why that row looks the way it does.
A clean trail means you can walk from any row in QuickBooks back to the row in the bank PDF in a minute or less. Keep the bank PDF, the import file, and a note of the import date in one folder for each account and each period. Name all three in the same way, so the link is clear at a glance, with no need to open each file to guess.
Do not edit rows in QuickBooks in a way that hides the bank truth. If a bank row must be split, such as one payment that covers two costs, use the split tool in QuickBooks and leave a note that says what you did and why. The bank row stays as the base, and your split sits on top of it as your book choice, in clear view.
This care pays off at tax time and in any check of your books. When a helper can see the PDF, the file, and the books agree, they can trust the work and move fast. When the trail is messy, each sum needs a hunt. A few minutes of neat work each month is what keeps the trail clean all year.
Make a QuickBooks file on the home pageAll blog postsOctober 15, 2026 · Blog
Xero is strict in a good way. It wants a bank file with clear dates, clear words, and sums with the right sign. When you give it that, the import is smooth, and the rows sit as bank lines ready for you to match and tag. When the file is messy, Xero will stop the import, or take the rows in with flaws that flow into your books.
The strict rules guard your books. A bank line with a wrong date can land in the wrong month and move a tax sum. A bank line with the wrong sign can turn a cost into pay. Xero stops what it can at the door, so the fix takes place in the file, where it is quick, and not in the books weeks later, where it is slow and hard to trace.
So treat the rules as help, not as a block. A file that passes the Xero checks is a file with plain dates, plain words, and true signs. That is the same file you would want for your own checks, even if no tool asked for it. Make the file right once, and both Xero and you gain from it.
A good file has few, clear columns. One column holds the date of each row. One holds the words or payee name from the bank. One holds the sum, with money in and money out shown by sign. Some files split money in and money out into two columns. Both shapes can work, as long as you pick one shape and keep it the same from the first row to the last row.
The rows should be bank rows only. Take out title rows, page heads, total rows, and blank rows. Each row in the file should be one bank row, on one date, for one sum. A row that joins two bank rows into one line will break the sum check and will be hard to match in Xero, since no bank row on its own looks like it.
Dates should sit in one style all the way down. Sums should be true sums in the cells, not text with money signs typed in. Words should be the bank words, kept whole, not cut short. When a file looks plain and steady like this, the import screen in Xero is quick to map, and the check after import is quick to pass.
Start from a checked sheet. Convert your bank PDF first, run the sum check, and look at the rows. The start balance plus all the rows should match the end balance. If that check fails in the sheet, it will fail in your books too, so fix the sheet first, from the bank PDF, row by row if you must.
Then pick the Xero file type in the tool, which is part of Pro. That kind sets the columns and the date style in the way Xero wants, so you do not have to rebuild the shape by hand. Save the file with a clear name that holds the bank name, the account, and the period, so you can tell at a glance which account and which month the file is for.
Keep your bank PDF near by when you import. If Xero flags a row, you can read the true row in the PDF at once and fix the file with the true date, words, and sum. Work from the bank truth at each step. Never fix a flagged row by guess work, since a guessed sum can pass the import and still be wrong in the books.
In Xero, open the bank account the rows belong to, pick the import choice, and load the file. Xero will show you the first rows and ask you to map the fields. Match your date column to the date field. Match your words column to the payee or memo field. Match your sum column to the sum field. Read each match with care before you move on.
Check the date style on the import screen. Banks and tools do not all write dates in the same order. If your file puts the day first and the screen reads the month first, rows can land in the wrong month with no clear sign of the flaw. The first rows on the screen should show dates you know are true from the PDF. If they look off, stop and fix the style.
Read the words field too. The payee or memo should hold the bank words for the row, in full. If the words field shows a sum, or the sum field shows words, the map is wrong. Go back one step, fix the map, and look at the first rows once more. A minute on this screen saves a long clean up in the bank lines later.
In most bank files, money out is a minus sum and money in is a plus sum. That sign is how Xero knows which way the money moved. If the signs are lost, all your sums can show as money in. Your costs then look like pay, your bank total climbs when it should fall, and the books tell a tale that is the flip of the truth.
Signs get lost in plain ways. A sheet may hold money out in its own column with no sign, and the import may read all sums as plus. A PDF may show money out in a set of marks, and a weak read may drop the mark. That is why you check signs in the sheet before import, row by row for a few rows, and not just the totals at the end.
A fast sign check is to pick one row you know well, such as rent out or wages in, and trace it through each step. Find it in the PDF, find it in the sheet, then find it in Xero after import. The sign should say the same thing in all three places. If it flips at any step, find where it flipped and fix the file at that step.
Xero shows you the import in steps, and the last look before you finish is your best chance to catch a flaw while the fix is still one click back. Read the count of rows. It should match the count of bank rows in your period. A short count means rows were skipped. A high count means rows were split or shown two times on the way in.
Read the totals on the screen too. The total of the file should match the change from the start balance to the end balance in the bank PDF. If the file total is off, the flaw is in the file, and it is far better to go back, fix the file, and load it once more than to finish the import and hunt for the flaw among live bank lines.
If all looks right, finish the import, then do one more check in the bank account. Sort the new lines by date, and check the first line and the last line against the PDF. Check a few lines in the middle too. This last look takes two minutes, and it is the look that lets you match and tag the rows with full trust.
A row can show two times if you import the same span twice, or if two files overlap by a few days. In Xero, that means the same bank row sits as two bank lines. If you match both, your books count the money twice, and your bank sum in Xero will not match the true bank sum. So clear spare rows out as soon as you spot them, before you match a thing.
To spot a spare, sort the bank lines by date and sum, and look for two lines with the same date, the same words, and the same sum. But take care. Some like rows are real. Two buys at the same shop on one day, for the same sum, do take place. Check the bank PDF before you delete. If the PDF shows the row once, one line is a spare. If it shows it twice, both lines are real.
Delete the spare line in Xero, then check the period total once more. The start balance plus the bank lines should now match the end balance. Keep a note of the date you cleared the spare and why, in your work notes. If the same flaw comes back next month, look at your periods. An overlap of a day or two at the seam is the most common cause.
Once the check is done, you can match, tag, and clear the rows in your normal way. Match bank lines to bills, sales, and transfers where they link. Tag each line to the right book code, so your tax sums build up in the right places as you go. Work in date order, from the start of the period to the end, so no line hides in the middle of a long list.
Leave the bank words as they are on each line. If you need to add a note, add it in the note space, not by writing over the bank words. The bank words are part of the trail back to the PDF. A line whose words still match the bank, with your note next to them, is a line any helper can check in a snap, months from now.
Keep the trail whole. Store the bank PDF, the import file, and a note of when you imported and checked it, in one folder per account. With that trail, a clean Xero import is not just fast. It is proof, in three parts, that the rows in your books are the rows the bank sent, checked by you, in full.
Make a Xero file on the home pageAll blog postsOctober 12, 2026 · Blog
It is a plain sum check that tells you if a bank sheet is whole. Take the balance at the start of the period. That is the opening sum. Add all the rows in the period, with money in as plus and money out as minus. The total should be the balance at the end of the period. That is the closing sum. Opening plus rows should equal closing, to the last cent.
Say a statement starts at 1,000. In the month, 2,300 comes in and 820 goes out. The rows add up to plus 1,480. Add that to the start sum and you get 2,480. If the bank says the end sum is 2,480, the sheet is whole. If the bank says 2,430, there is a gap of 50, and a row in the sheet is wrong, missing, or shown two times.
The check works for any span. It works for one month, for three months, and for a full year. It works in Excel, in CSV, and on paper with a hand sum. As long as you have the true start sum, the true end sum, and all the rows in the period, this one check can prove the set is whole, or prove that it is not.
A sheet can look neat and still be wrong. Rows can sit in clean cells, in date order, with clear words, and one row can still be missing. Your eye will not spot a row that is not there. The sum check will. It counts the money, not the look of the page, so it catches the flaws that a quick read by eye will miss each time.
The check also guards all the work that comes next. If you import a sheet into QuickBooks or Xero, tag rows for tax, or add up costs by kind, each of those jobs builds on the rows in the sheet. If the rows are short by one, each job that follows will be short too. One check at the start guards the whole chain of work that comes after it.
Best of all, the check is fast. For most sheets, the sheet tool adds the sum column for you. You need the start sum and the end sum from the bank file, and one minute of care. Few checks give you this much trust for this small a cost, which is why our tool runs it as part of each job.
The opening sum sits near the start of your bank statement. Banks name it in their own ways. It may say balance at start, sum brought forth, opening balance, or the balance on the first date of the period. It is the balance just before the first row of the period. Write it down just as the bank shows it, with its sign and its cents.
The closing sum sits at the end of the statement. It may say balance at end, closing balance, or the balance on the last date of the period. It is the balance just after the last row. Make sure you take it from the last page, not from a page in the middle. A mid span balance will make the check fail even when the sheet is right, since it is the wrong end point.
If your period covers more than one statement, take the opening sum from the first statement and the closing sum from the last statement. The rows in the period are all the rows in all the statements in date order. The check still holds: the first start sum plus all the rows should match the last end sum, with no gap and no overlap in the rows.
In Excel or a like sheet tool, click the first cell of the sum column, then pick all the sum cells for the period, down to the last row. The tool shows the sum of the cells you pick at the foot of the screen. That sum is the net move of the period: all the money in minus all the money out, in one sum. Write it down with care, plus or minus sign and all.
Add that row sum to the opening sum. Use the same sums the bank uses, to the cent. Do not round to whole units at this step, since a round step can hide a small gap or make a false gap. If your sheet holds money in and money out in two split columns, add the in column, take away the out column, and that net sum is the one you add to the opening sum.
Set your total side by side with the closing sum from the bank. If they match to the last cent, the check passes. If they do not match, write down the size of the gap and its sign. A plus gap and a minus gap point to flaws in flip ways, and the size of the gap is your first and best clue in the hunt that comes next.
The size of the gap is a clue, and at times it names the flaw at once. If the gap is the same size as one row in the sheet, that row may be shown two times in the sheet, or a row of that size may be missing from it. Search the sheet for rows of that size first. Check each one against the bank PDF to see if it is real, spare, or lost.
If the gap is twice the size of a row, that row may have the wrong sign. A money out row read as money in moves the total by twice its size: once for the out that was lost, and once for the in that was wrongly added. Search for a row half the size of the gap, and check its sign against the PDF. This is one of the most common causes of a big gap.
If the gap is small, such as a few cents or a few units, a sum may have been read with one digit wrong. Digits that look alike, such as 6 and 8 or 1 and 7, are the usual cause in a scan or a faint print. A gap of 9, or 90, or 900 can point to two digits swapped in place. Use the size of the gap to aim your hunt, and it will be far shorter.
Split the period into parts and check each part on its own. Check the first half of the rows against the balance at the mid point of the statement, then check the next half. The half that fails holds the flaw. Split that half again, and check each part once more. In a few splits, you can cut a month of rows down to a small group where the flaw must sit.
Work in date order, in small groups, and tick each group off as it passes. For each group, the balance at the start of the group plus the rows in the group should match the balance at the end of the group, which the bank shows in the balance column next to the last row of the group. That balance column is a gift for this hunt. Use it at each step.
When the group is small, read each row in it against the PDF, one by one. Check the date, the words, and the sum, and the sign of the sum. The flaw will be in this group: a missed row, a spare row, a wrong sign, or a wrong digit. Fix it from the PDF, then run the full check once more from the start to prove the whole span now passes.
Fix the row from the bank PDF, and from the bank PDF only. If the sum is wrong, type the sum the bank shows. If the sign is wrong, flip it to the sign the bank shows. If a row is missing, add it with the true date, words, and sum. If a row is a spare, take it out. Each fix makes the sheet match the bank truth a bit more, till the check passes in full.
Do not plug the gap with a made up row. It can be tempting to add a row for the size of the gap so the sums match. That makes the check pass on the page, but the sheet now holds a row the bank never sent, and the words on that row will be wrong. A plugged sheet will fail later, at tax time or in a bank check, in a worse way than a sheet with an open gap.
Note each fix you make, in a short list next to the sheet. Write the date of the row, what was wrong, and what you set it to. If a helper later asks why that row was changed by hand, your note tells the tale in a line or two. Honest notes are part of a clean trail, and they take less than a minute to write while the work is fresh.
You can trust a sheet when two checks both pass. The first is the sum check: opening plus rows equals closing, to the last cent, for the full span. The second is a spot check by your own eyes: a few rows from the start, the middle, and the end of the sheet match the bank PDF in date, words, sum, and sign. A sheet that passes both is a sheet built on proof, not on hope.
Our tool runs the sum check as part of each job and shows a tick when the sums add up. That tick is a good sign, and it saves you the hand sums. Still do the spot check your self. The tool can prove the money adds up. Your eyes prove the words sit on the right rows. The two checks guard two kinds of flaw, and you want both kinds caught.
Keep the proof with the sheet. Save the bank PDF, the sheet, and a note that the check passed, with the date you ran it, in one folder. Then the sheet is ready for your books, your tax work, and your forms, and if any one asks how you know the sums are right, you can show the check, not just say it.
Convert a file and see the sum checkAll blog postsOctober 9, 2026 · Blog
At tax time, one workbook for the whole year is far more use than 12 files in a heap. In one workbook, you can sort all the rows of the year at once. You can add up a full year of costs by kind, such as stock, rent, or fees, with one pass. You can find any row of the year with one search, in place of opening file after file and searching each one on its own.
A year book also makes gaps plain. In 12 split files, a missing month can hide for a long time. You may not see it till a tax sum looks low and a long hunt starts. In one book, sorted by date, a missing month shows as a clear hole in the dates, and an overlap shows as rows that seem to come twice at a seam. The shape of the year tells on itself.
Most helpers would rather take one year book too. A tax helper can check it, sort it, and tag it in one place. A bookkeeper can match it to the books with no need to open 12 files in turn. One clean year book, with its 12 bank PDFs in the same folder, is the form that saves time for each person who works on it.
Name each monthly PDF in date order at the start. Use the year and the month as numbers at the front of the name, such as 2026 01, 2026 02, and so on to 2026 12. Number names sort in the right order on their own in a folder, so the first file is the first month and the last file is the last month, with no need to guess from bank file names.
Use the months of your tax year, not just the months of the year on the wall. If your tax year starts in April, your first file is April and your last is March of the next year. Name them in tax year order, from month 01 of your tax year to month 12, and add a note in the folder that says which tax year the set is for. That one note stops a mix up a year from now.
Keep the set whole as you build it. If a month is not yet in the folder, leave its place clear in your list and note that it is still to come. Do not merge a part year and call it a year. A year book with a quiet gap in it is worse than 12 honest files, since the gap will flow into each sum the book is used for.
Convert each month on its own first, and check each month with the sum check. For that month, the start sum plus all its rows should match its end sum, to the last cent. A month that passes on its own is a sound brick for the year book. A month that fails will fail inside the year book too, where its rows sit among hundreds of others and the flaw is far harder to find.
Fix a failing month while it is still small. In one month of rows, the hunt for a missed row, a spare row, or a wrong sign is a short job with the split and check steps. In a year book of more than a thousand rows, the same hunt can take an hour. The rule is plain: no month joins the year book till its own check passes in full.
Note the start sum and the end sum of each month as you check it, in a short list. That list is gold at the seam check that comes next. The end sum of one month should be the start sum of the next. With the list in hand, you can check all 11 seams in a minute or two, before you join a thing.
Put the checked months into one book in date order, first month at the top and last month at the foot. On Pro, you can add many files at one time in a batch and save the year as one book. Keep one head row at the top of the book, with the date, words, and sum heads. Take out the head rows of the months that follow, so the book has one head, not 12 heads down its length.
Keep one row per bank row as you join. Do not add total rows for each month inside the year book, since those totals are not bank rows and they will break the year sum check. If you want month totals, make them in a copy of the book, or on a split page in the same file. The main year book should hold bank rows only, in date order, from the first day to the last.
When the join is done, sort a copy of the book by date and scan it from top to foot. The dates should climb in a steady way, with no jump back in time in the middle. A jump back is a sign that a month was pasted in the wrong place. Fix the order in the main book, then run the seam check and the year check before you use the book for any sums.
The seam is where one month ends and the next starts. It is the weak point of a year book, so check each seam with care. The end sum of one month should be the start sum of the next month. If the two sums are not the same, stop. A month may be missing, two months may overlap, or a month may sit in the wrong place in the order.
Check the dates at the seam too. The last date of one month and the first date of the next should sit side by side in the right order, with no day shown in both months and no day lost in the gap. Some banks end a month on the last work day and start the next on the first work day, so the seam dates may not be the 1st and the 31st. What matters is that no bank row is in the book twice, and none is left out.
If a seam fails, go back to the two monthly files at that seam and read them against the bank PDFs. The flaw is almost always in that pair: a wrong month file, a month used twice, or a month that was checked on a period that was a few days too long or too short. Fix the pair, rejoin from that point, and check the seam once more.
Sort a copy of the year book by date, then by sum, and scan for two rows with the same date, the same words, and the same sum, side by side. That shape is the mark of a row shown two times. It most often comes from an overlap at a seam, where the last day of one file and the first day of the next file hold the same bank rows.
Take care before you delete a row. Some like rows are real. A shop may charge the same sum twice on one day. A wage may match a fee by chance. The bank PDF is the judge. If the PDF shows the row once for that account and date, one copy in the book is a spare and should go. If the PDF shows it twice, both rows are real and both should stay.
When you take a spare row out, run the seam check and the sum check for that month once more. The month should pass on its own again with the spare gone. Note the fix in your list: the date, the sum, and why the row was a spare. That note keeps the trail honest, and it helps you spot the same overlap habit in the next year set.
The year check is the same sum check, at year size. Take the start sum of the first month. Add all the rows in the year book, money in as plus and money out as minus. The total should match the end sum of the last month, to the last cent. If it matches, the year book is whole: no row is missing, no row is spare, and no sign is wrong, in the whole year at once.
If the year check fails but each month passed on its own, the flaw sits at a seam. Check the seams in order with your list of month start and end sums. Find the first seam where the end sum of one month is not the start sum of the next. The gap at that seam, and the dates near it, will point to the missing or spare rows that break the year.
When the year check passes, spot check the book by eye too. Pick a few rows from the start, the middle, and the end of the year, and match them to the bank PDFs. Then the year book has passed both kinds of proof: the money proof of the sum check, and the eye proof of the spot check. That is a book you can hand to a tax helper with trust.
Keep the year book and all 12 bank PDFs in one folder, named for the tax year and the account. The folder is the whole trail in one place: the bank truth in the PDFs, and the work file in the year book. If a sum is ever asked about, you can open the folder, find the row in the book, and find the same row in the PDF, in a minute or two.
Keep a clean copy of the year book that you do not edit. Do your sorts, tags, and sums in a work copy. If the work copy gets in a mess, you still hold the clean book that passed the year check, and you can make a fresh work copy from it. Store a back up of the folder in a next place too, such as a cloud drive, so a lost device does not mean a lost year.
Add one short note file to the folder. Note the date you built the book, that the year check passed, any rows you fixed by hand, and any spare rows you took out, with their dates and sums. That note is the tale of the book in one page. A year from now, it will tell you, or your helper, all you need to know to trust the book at once.
Start your year book on the home pageAll blog postsOctober 6, 2026 · Blog
A text PDF holds its words and sums as true text. A tool can lift that text as it is, so the read is clean and true. A scan or a phone photo holds no true text at all. It holds a pic of the page. The tool must look at the pic and guess what each word and sum says. That guess work is where flaws creep in, most of all with faint print and alike digits.
Think of digits that look much alike in a pic. A 6 and an 8, a 1 and a 7, a 3 and a 5 can swap in a soft or dim pic. A comma and a dot can swap too, and that can move a sum by a lot. In a text PDF, those swaps do not take place, since the sum is stored as a sum. In a pic, the grade of the pic sets the grade of the guess, each time.
That does not mean scans and pics are of no use. With Pro, the tool reads the pic with care, and a good pic reads well. It means the work you do before the read, on light, flat, and sharp, and the checks you do after the read, matter far more for a pic than for a text PDF. This post shows both parts, step by step.
The best pic is flat, sharp, well lit, and whole. Flat means the page lies smooth, with no curl at the edge and no fold across the rows. Sharp means the words are crisp when you zoom in, not soft or blurred. Well lit means even light across the whole page, with no shade from your hand or your phone. Whole means all four edges of the page and all its rows are in the frame.
A scan from a home scanner is often the best of all. Set the scan to a mid to high grade, in grey or black and white, and save it as a PDF. A scanner holds the page flat, lights it in an even way, and keeps it straight, which takes out the three top flaws of phone pics at once: slant, shade, and curl.
If a phone pic is what you have, treat it like a scan job, not a snap. Take the pic for the read, not for speed. One page at a time, in good light, with a check of the pic before you move on. The next parts of this post show that way of work in full, and it takes less than a minute a page once it is a habit.
Put the page on a flat table near a window or a bright lamp, in the day if you can. Smooth the page with your hand so it lies flat, and weigh a curled edge down if you must, with the weight clear of the rows. Make sure no shade falls across the words. Your own shade, as you lean over the page, is the shade that spoils most pics, so stand to the side of the light.
Hold the phone right above the page, so the page fills the frame and its edges look straight, not wide at one end and thin at the other. A page shot at a slant squeezes the rows at the far end, and squeezed rows are hard to read. If your phone has a scan mode in its camera or notes app, use it. Scan mode finds the edges, straightens the page, and lifts the light, all in one step.
Tap the screen to focus on the rows in the middle of the page before you take the pic. Then hold still for a beat as the pic is taken. A pic taken while the phone still moves will be soft, and soft pics read in a poor way. Take the pic, then zoom in on it at once. If you can read the sums with ease at zoom, the tool can read them too.
Take one page in each pic. A pic of two pages side by side makes each page small in the frame, and small words are the first thing a read gets wrong. One clear pic per page gives each row its full size, and it gives you a clean link too: pic three is page three, so a flaw on one page is easy to find and easy to fix with a fresh pic of that page alone.
Keep the order as you go. Name or sort the pics in page order at once, while the pages are still in front of you. Page order matters for the sum check, since the check walks the rows in date order from the start sum to the end sum. A set of pics in a mixed order can make a right read look wrong, and waste your time on a hunt for a flaw that is not there.
Make sure the start sum and the end sum are in the pics. The first page holds the start sum, and the last page holds the end sum, and the sum check needs both. If a pic cuts off the top or the foot of a page, that sum may be lost. Check the first and last pics with the most care of all, and retake them if an edge row is cut or dim.
Zoom in on the pic and read three spots: the top rows, the rows in the middle, and the last rows. In each spot, read a sum in full and look at its digits one by one. If the digits are crisp and clear to your eye, they will be clear to the tool. If you must squint at a sum, the tool will have to guess at it, and a guess is a risk you do not need to take.
Look for lines and marks that are not part of the rows. A fold line, a pen mark, a stamp over a sum, or a dark edge from the table can all be read as part of a word or a sum. Smooth the page and retake the pic if a mark sits on a row. If a bank stamp sits on the page in ink, note the rows it touches, so you can check those rows by hand with the most care after the read.
Check that the pic is not too dim and not blown out by a flash. A flash can turn the middle of the page white and wash the sums out, while the edges stay dim. Even light with no flash reads best. If the pic fails any of these checks, retake it now. A retake takes ten ticks of the clock. Fixing ten wrong rows by hand takes far longer.
Check a sheet from a scan or pic with more care than you would for a text PDF. Run the sum check first, as always. The start sum plus all the rows should match the end sum. For a pic read, this check is not a nice extra. It is the main proof that the guesses the tool made add up to the bank truth, and it will catch a wrong digit that your eye may miss.
Spot check more rows than usual, and spread them out. Check a few rows from each page of the statement, not just the start and the end. Look with care at sums with alike digits, such as 6 and 8 or 1 and 7, and at sums where a comma or a dot sets the size of the sum. Those are the sums a pic read can mix up when the print is faint, so they earn the closest look.
Read the words on a few rows too. A pic read can swap a letter in a name while the sum stays right, and the sum check alone will not catch that. For book work, the words set the tag the row gets, so a wrong name can send a cost to the wrong place. A two minute read of words and sums, page by page, is the right cost for a pic based sheet.
If one page reads in a poor way twice, do not sit and fix a long list of rows by hand. Take a new pic of that page in better light, flatter and sharper, and convert that page once more. A fresh pic fixes the cause of the flaw. Hand fixes treat one row at a time, and the next page from the same bad set up will have the same flaws all over again.
If the page is a scan, scan it once more at a higher grade and check the new scan at zoom before you convert it. If the print on the page is faint in ink, a grey scan may read it in a better way than a black and white scan, since grey keeps the faint marks that a harsh black and white scan can drop. Try the next set up, check at zoom, and use the best pic of the page you can make.
If a few rows are still wrong after a good new pic, fix those rows by hand from the paper page, then run the sum check for the whole span once more. Note the rows you fixed. A page that needs many hand fixes, month after month, is a sign to change the source, which is the point the next part takes up.
If your bank gives text PDFs in online banking or in the app, that is the best source, each time. A text PDF takes the guess work out of the read, cuts the check time down, and gives the cleanest sheet. If you have been sent paper by post, or pics from a helper, it is worth a short hunt in your bank app for the PDF form of the same statement.
Ask the bank if you can not find it. A branch or a phone call can get most banks to send a PDF, or to turn on online statements for your account. Some banks charge for paper copies but give PDFs at no extra cost in the app. One ask can end the scan work for good, for this account, for all the months that follow.
Keep pics and scans for the times when they are all you have: an old paper file, a closed account, or a statement from a bank you no longer use. For those, the steps in this post will get you a checked, trusted sheet. Just give the pic the care it needs at the start, and give the sheet the full checks at the end, and the result will serve you well.
Try a scan with Pro on the home pageAll blog postsOctober 24, 2026 · Blog
A bank statement is a list your bank gives you of all the money that moved in and out of your account in a set span of time. Most banks make one for each month. It is the bank own record of your account, made by the bank, with the bank name on it. That is why firms, schools, and loan staff take it as proof, in a way they do not take a note you wrote your self.
Think of it as a report card for one account, for one period of time. It starts with the sum you had at the start of the period. It then shows each payment in and each payment out, in date order. It ends with the sum you had at the end of the period. If you add the start sum and all the rows, you should land on the end sum. That link is what makes a statement a true record, not just a list.
A statement is not the same as the live view in your bank app. The app shows your account as it is now, and it can change while you look at it. A statement is fixed for its span. Once the bank has made it, the rows in it do not change. That fixed form is why a statement works for tax, for forms, and for checks that take place months after the period has ended.
At the top, it shows the name of your bank, your name, and the details of your account, usually with most of the account number hidden and only the last 4 digits shown. It shows the start date and the end date of the period it covers. Some banks also show your home address as they hold it, and a number for the statement, such as statement 12 of the year.
The main part is the rows. Each row shows the date of a payment, a short note on what it was, the sum that moved, and the balance of the account after that row. Money in may sit in its own column, and money out in its own column, or the sums may sit in one column with plus and minus signs. The shape varies by bank, but the parts are the same in most banks.
At the start and at the end, it shows the two key sums: the balance at the start of the period and the balance at the end. Some banks add a short sum part too, with the total money in and the total money out for the period. Those totals give you a fast check: start sum plus total in, minus total out, should match the end sum. If it does, the statement is whole.
For tax work, a statement shows your pay and your costs in a clear, dated way. It backs up the sums in your tax form with bank proof. For a loan, a bank or lender looks at your statements to see if you earn in a steady way, what your bills look like, and if you can pay back. A clean set of statements, with no gaps, makes that check fast and calm.
For a visa form or a rent form, a statement can show you hold funds for your trip, your stay, or your rent. For a new job or a school place, it can serve as proof of address or proof of funds in some cases. In each case, the point is the same: the bank made the record, so the reader can trust it more than a claim you make on your own.
For your own books, a statement is the base you match your work to. It helps you spot a fee you did not know about, a payment that went out twice, or pay that did not land. Many people only look at their balance in the app. A read of the full statement, once a month, is how you catch small flaws while they are still small and easy to fix.
Log in to your bank site on a computer. Open the account you need, then look for a part named Statements, Documents, or Download. The words vary by bank, but the part is usually near the account home or under a menu with the account name. Pick the month you need from the list of past statements the bank holds for you.
Save the statement as a PDF when the bank gives you the choice. A PDF is the best kind to keep, to send, and to convert into a sheet, since it holds true text that a tool can read in a clean way. Save it with a clear name, such as the bank name, the year, and the month, so you can find it later with ease and match it to the period it covers.
Most banks hold past statements in online banking for a long span, usually a year or more, and some hold them for far longer. If you need an old month, look in the same list before you call the bank. If the month you need is not there, the branch and post paths in the parts below can still get it for you, though they take more time.
Open your bank app and tap the account you need. Look for a part named Statements, Documents, or Account papers. It may sit under a menu with three dots or lines, or under the account details. Pick the month you need from the list. Most apps show the same list of past statements as the bank site, since both read from the same bank store.
Tap Download or Share, and save the PDF to your phone, or send it to your email so you have it on your computer too. If you plan to convert it, the PDF from the app is just as good as the PDF from the site. It is the same bank file, with the same true text, so it will read in the same clean way in the tool.
If you can not find the part in the app, use the search or help part in the app and type the word statement. Most apps will point you to the right screen. Apps vary a bit in their layout, and banks move parts from time to time when they update the app. The path is still much the same in most apps: account, then statements, then month, then save.
You can walk into a branch with your ID and ask for a printed statement for the period you need. Take proof of who you are, such as a card the state gave you or a passport, and the bank card or account details for the account. The bank may print the statement on the spot, or ask you to come back, or post it to you if the period is long.
Some banks charge a small fee for paper copies, most of all for old periods that must be looked up. Ask about the fee first, so there is no shock. A branch print may come with a bank stamp or a signed note on it. Some forms and some loan checks ask for that stamp, so if your form asks for a stamped copy, say so at the start of your visit.
You can also call the bank and ask them to post a statement to the home address they hold for you. Post takes a few days, and the bank will send it to the address on the account only, for your safety. If you have moved home, update your address with the bank first, then ask for the post copy, so it goes to the right home and not to a past one.
Most banks make a statement once a month for an account that is in use. The span usually runs from the first day of the month to the last day, though some banks run it from the date you opened the account each month. Your statement date stays much the same from month to month, so you learn when to look for the new one.
Some banks give a statement once each three months if the account is quiet, with few or no rows. If no money moved at all in a period, some banks skip a statement for that span or show one with the start and end sums the same and no rows in the middle. That is normal for a savings account you do not touch, and it is not a flaw.
In online banking and in the app, you can usually see past statements for many months back, and save any of them when you need. That store is there all the time, day and night. So for most needs, you do not have to wait for the post or for a branch to open. You can get the month you need in a few minutes, at the time you need it.
Check the period first. The statement should cover the full span you need, from the first day to the last day, with no gap at the start or the end. Check the account too: the last 4 digits at the top should match the account you meant to use. It is an easy slip to save a statement for the wrong account when you hold more than one at the same bank.
Make sure you have all the pages, from page one to the last page. A missing page means missing rows, and the sums will not add up. Check that the first balance and the last balance are both shown. You need them for the sum check: the first balance plus all the rows should match the last balance. If a page is missing, go back and save the full statement once more.
When your statement is ready, you can use it as it is for a form or a loan, or drop the PDF into the tool on the home page to turn it into a sheet. You get clean Excel or CSV rows in seconds, ready for tax, books, or a form. Keep the bank PDF with the sheet you make, side by side, so the proof and the work file stay linked for any check that comes later.
Convert your statement on the home pageAll blog postsOctober 24, 2026 · Blog
Your bank account number is a long number that is yours alone. The last 4 digits are just the final 4 numbers at the end of it. If your full account number ends in 4821, then 4821 is your last 4. That is all it means. When a page, a form, or a bank staff member asks for the last 4 digits of your bank account, they are asking for those final 4 numbers, and for no more than that.
Banks and forms ask for the last 4 as a way to name your account in a safe, short way. A full account number is long, and most staff do not need the whole thing to find your account on a list or to match a payment. The last 4, with your name, are usually enough to point to the right account. That is why you see the last 4 on so many pages, bills, and apps.
You will usually see the last 4 shown with stars in front of them, like this: ****4821. The stars stand for the part of the number that is hidden. The hidden part stays hidden on the page, but you and your bank hold the full number. The stars plus the last 4 form a label for the account that is safe to show on a screen or on paper that others may see.
They are not the last 4 digits of your bank card. Your card number is a new number, made for the card, and it is not the same as your account number. Its last 4 will usually be unlike your account last 4. This mix up is very common. If a form asks for the account last 4 and you give the card last 4, the form may fail to match your account, since the bank looks for the account number, not the card.
They are not your sort code or branch code. That code tells which bank and which branch an account sits at, and many accounts at one branch share the same code. It does not name your own account. They are also not your PIN, your password, or a code sent to your phone. You do not use the last 4 to log in, and no bank will ask for your PIN in a form that asks for the last 4.
They are not the full account number, and they do not work in its place for a payment. To pay money into an account, the payer needs the full account number and the bank code, in the form your bank uses. The last 4 alone can not take a payment in or send one out. That limit is part of what makes the last 4 safe to show and safe to give when a form asks for them.
Banks hide most of your account number and show only the last 4 so you can tell which account a page or a bill is about, with no risk of the full number being seen by others. It is a safe label for your account. If a full number were shown on each statement, each app screen, and each bill, far more eyes could see it, copy it, and try to use it in ways you did not ask for.
The last 4 strike a fair line. They are enough for you to know the account is yours, and enough for a bank to match a form to your account when you also give your name. They are not enough, on their own, for a stranger to get into your account or take money from it. That is why banks, card firms, and many other firms all use the same last 4 way of work.
You will see the same idea in other places too. A card is shown by its last 4 on a bill. A phone number may be shown by its last 2 or 3 digits when a code is sent to it. In each case, the firm shows just enough for you to know it is yours, and hides the rest. Your bank account last 4 are one case of that same, plain safety rule.
On your bank statement, look at the top of the first page. Most banks show your account there, as stars plus the last 4, near your name and the dates of the period. Some banks show it on each page, in the head or the foot of the page. Read the final 4 numbers of that masked number. Those are the last 4 of that account, for that statement.
If your statement shows more than one account, such as a main account and a savings account on one set of pages, take care to read the last 4 from the part of the page for the account you need. Each account has its own number and its own last 4. A fast way is to match the balance: find the end balance for the account you need, then read the last 4 shown with that part of the statement.
On a paper statement sent by post, the place is the same: the top of the first page, with your name and the period dates. If the print is small, look for a set of stars or a run of hidden marks with 4 clear digits at the end. If you still can not find it, the app and online banking paths in the next part show the same last 4 in a bigger, clearer way.
In online banking, log in, open your account, and look in the account details part. The masked account number there ends with your last 4. Some banks put the details under a tab or a menu with the account name. The last 4 you find there are the ones to use on a form, since they come from the bank own record for that account.
In your bank app, tap your account, then tap a details or info part. The account number is shown masked, with the last 4 in clear view next to the account name. This is the fastest path for most people, since the app is on your phone and the details are two taps away. If you hold more than one account, tap into each one in turn and read its own last 4 in its own details.
On a cheque, if you have a cheque book, your account number is printed at the foot of the cheque, in the row of numbers there. Its final 4 numbers are your last 4. Take care to read the account number part, not the cheque number or the bank code part. Most people will not need this path, since the statement, the site, and the app all show the last 4 in a clearer way.
Many people hold a main account, a savings account, and a joint account at the same bank. Each one has its own account number, and its own last 4. The last 4 are the tag that tells them apart on a page that shows more than one. A bill, a form, or a statement that shows **** and 4 digits is talking about the one account whose number ends in those digits, and no other.
Make a small list for your self and keep it in a safe place. For each account, write the name you use for it, such as Main, Savings, or Joint, and its last 4. Do not write the full account numbers on that list. The last 4 are enough for the list to do its job, and a list of last 4 tags is far safer to keep than a list of full numbers.
Then, when a form or a page shows a masked number, match its last 4 to your list in a snap, and you know which account it is. If a last 4 on a page is not on your list at all, stop and check. It may be an old account, a card and not an account, or a page that is not from your bank. A last 4 you do not know is a sign to slow down and look with care.
The last 4 digits alone are not enough for a person to take money from your account, and banks show them for that reason. Forms ask for them, bank staff ask for them, and bills print them, all in the open. In those normal cases, giving the last 4 is fine, and it is part of how banks check they are talking about the right account when they talk to you.
Still, share them with care, as you would with any bank detail. Give them on a form from a firm you know, or to bank staff on a call you made to the bank own number. Be slow to give any bank detail on a call that came to you from a number you do not know, or on a page that a strange email or text sent you to. The last 4 are low risk, but the habit of care guards the high risk details too.
Keep your full account number, your card PIN, and your passwords far more close. Never share your full details with a person you do not know. Never type your bank password on a page that did not come from your bank. No true bank will ask for your full PIN or your full password on a form, in an email, or on a call. A bank that seems to ask for those is a fake, and you should stop at once.
If a form says the last 4 you gave do not match its records, check the plain causes first. The most common cause is the card mix up: you gave the last 4 of your bank card, not of your account. Go back to your statement or your app, read the account last 4 from the account details, and try once more with those. The next most common cause is the wrong account: you gave the last 4 of your savings account for a form about your main account.
Check the digits them self too. Read them one by one from the bank page as you type, in the same order. A swapped pair, such as 4821 typed as 4812, will fail a match but looks right at a fast glance. If the form still fails, look at which account the form is about. Some forms hold an old account from a past use, and the bank can update it when you call them.
If no plain cause fits, call your bank on the number on their own site or on your card, and ask them to check the account the form points to. Do not keep trying at random, and do not give more bank details to a page you are not sure of. Your bank can tell you the last 4 they hold for each of your accounts, and that ends the guess work in one call.
Try the tool on the home pageAll blog postsFor the site owner only. This page has no link in the menu or footer. Open it by typing #/admin in the address bar.