Help center

Answers

• Getting started
• The balance check
• Scans and photos
• Exports
• Credits and refunds
• Privacy and accounts

How your statement is handled

What the balance check covers, what one conversion can take, and how particular layouts and export formats behave.

What the balance check covers

• Amounts, dates and the running balance. The check is arithmetic: the opening balance plus each transaction has to equal each printed running balance and the closing balance. Rows that break the chain are flagged with the difference.
• What arithmetic can put right, it puts right and says so. A debit read as a credit, or a running balance misread on one line while the amounts around it agree, is corrected from the printed balances and shown as Matched with a note beside the tick. Where the chain still breaks, the row is marked for review in the workbook with the difference beside it. A number we changed is never shown as a number we read.
• Descriptions sit outside the arithmetic. A misread merchant name does not change a total, so the chain cannot see it. Two things are checked instead: a date that falls out of the statement's sequence is marked for review, and a cell the reader itself could not make out is marked for review with the cell named. Read the descriptions where they matter to you.
• Credit-card statements without a per-line balance. Most issuers print a previous balance, the transactions and a new balance, with no running balance on each line. The check ties the totals instead: previous balance plus purchases minus payments has to reach the new balance, and where the statement prints totals for money out and money in, those are tied to the rows as well. Where the totals tie, the badge reads "closing total checked". Where nothing can be tied, the check is marked unavailable and the rows are in the workbook for you to review. Credit-card statements.
• A passed check means the arithmetic ties. Two offsetting errors would tie as well, so treat it as strong evidence of a clean extraction. How the check works.
• Authenticity is a separate question. The check confirms that the export matches the document. It says nothing about whether the document itself is genuine.

The review workbook

A conversion gives you one file: the review workbook (.xlsx). Every format you import comes from it, and producing them uses no pages. The step-by-step guide explains every column and field, and every message you may see.

1. Download the workbook and open it in Excel, Numbers, LibreOffice or Google Sheets. The Transactions sheet holds every row with a Check column and a Note column: a row marked Review has a note saying what to look at, usually one cell against the statement. Rows marked Matched need nothing.
2. Fill in the Statement details sheet. It lists the few facts an accounting import needs, with a description beside each: the opening balance, which every file needs; the account type, which QuickBooks, OFX, Quicken and QIF files need; and the currency, which QuickBooks, OFX and Quicken files need. All three are already filled in from the statement where it prints them; the account type is picked from a drop-down list in its cell, with what each choice means written beside it; the account number, which QuickBooks and OFX files need to tell accounts apart; and optional ones such as the bank code, the bank name, the statement period and the date order for QIF and CSV files. Required fields are marked.
3. Save it as .xlsx and upload it in Step 3 of the converter page, "Upload the review workbook", straight away or any time later. The rows and details are checked again: a required field left blank or a date that cannot be read is listed with its row or cell, and you upload the file again once it is fixed. There is no limit on how many times.
4. Download the formats. Excel, CSV, CSV for import, QBO, OFX, QFX and QIF are produced from the rows and details you confirmed. They carry no marks and no notes: only the data.

Keep the column headings and the sheet names as they are; you may sort, filter, edit any cell and delete or add rows. A format whose details are missing, such as QBO without an account number, is offered as soon as the field is filled and the workbook uploaded again. The CSV for import writes its dates in the order you chose on the Statement details sheet, day first unless the statement is in US dollars.

What one conversion can take

• 100 pages per PDF, 50 MB per file, scanned or not. Split a longer statement across two conversions, and see where to cut it. A scanned page is read the way a photo is, so it takes longer than a typed one, but it goes as deep: 100 pages either way.
• Up to 80 transactions on a page. One reading of a page holds a limited number of rows, and a page with more than 80 transactions can be refused. It is refused only after it has been read, so the pages read count, and converting the same file again gives the same result. Bank statements rarely come close: the densest real statement page we have tested had 57. If yours has more, email us before converting it.
• 100 photos per conversion, under 5 MB each after your browser shrinks them and 50 MB in total.
• One document per conversion. Twelve monthly statements are twelve conversions, run one after another. Bulk upload is on the roadmap.
• Expect about a minute for a scanned or photographed page, and about the same for six of them. A typical native PDF takes 10-60 seconds. Picture pages are read at full resolution, six at a time, so a six-page scan takes about as long as one page and a longer one adds about a minute for every six pages. Keep the tab open: the conversion lives in the open page, and the tab title shows the percentage while you work in another tab. Scans and photos.

Splitting a PDF statement

On a Mac, open the file in Preview, choose File then Print, set the page range for one part, and choose Save as PDF; repeat for the rest. On Windows, open the file in Edge, press Ctrl+P, set the page range, and choose Save as PDF. Convert each part on its own; every format stays available for each conversion separately.

Where you cut matters more than how. If the file holds several statement periods, cut between periods: each part then carries its own opening and closing balance, and the check runs cleanly on both. If you have to cut one statement in half, the second part carries no printed opening balance, so enter the first part's closing balance as the Opening balance on the workbook's Statement details sheet, and the check runs from there when you upload it.

Splitting never drops a row. Everything on the pages you send is read and checked against itself. What a partial upload can lose is the closing check, because the closing balance printed on those pages usually belongs to the whole period rather than to the part you sent.

Layouts that need a decision from you

• Multi-account statements. A single PDF covering several accounts, such as a current account and a savings account or a primary and a supplementary card, is exported as one list in document order. The check flags the rows where one account's balance chain ends and the next begins. Convert the accounts as separate documents when you need them apart.
• Several currencies in one table. A statement is read as a single currency. Mixed columns break the balance chain and those rows come back flagged, which is the signal to split the document by currency before converting.
• Redacted pages. Where the balance column is blacked out, the transactions are still extracted and the check is marked unavailable.
• Dense pages. A page carrying more than 60 rows takes longer, and on a scan it is the most likely place for a flagged row.
• What the converter reads. Bank and credit-card statements. Screenshots, handwritten ledgers and transaction lists pasted into a document carry no statement structure and no printed balance, so they sit outside its scope.

Files the converter turns away

A file refused before anything is read costs nothing: no page is deducted and no credit is spent. That covers a file that is too large, not a PDF or an image, password-protected or damaged, or over the page limit. Some files can only be refused after they have been read: a document that is not a statement, a mortgage or loan statement, and a page with more than 80 transactions. The pages read then count, and the message says so.

• Anything that is not a bank or credit-card statement. If the reader cannot find a transaction table with dates and amounts, it says so instead of handing back an empty spreadsheet. Invoices, receipts, payslips and tax forms are turned away here.
• Pages whose amounts cannot be read. A line with no figure in either column is not a transaction, so it is left out of the export and reported above the table. When every line on a statement is like that, usually a photograph too dark or too skewed to read, the whole conversion is refused and the fix is a better picture rather than a better guess.
• Mortgage and loan statements. On a loan account the balance is money owed and a repayment reduces it, the opposite of a transaction account, so exporting one as a bank statement would reverse every row in your books. The converter recognizes them and turns them away rather than getting it quietly wrong.
• Files that are not PDFs or images. Spreadsheets, Word documents and archives are rejected on their contents, not their file name, before anything is read.
• Password-protected PDFs. Open the file in your PDF reader, save an unlocked copy, and upload that. The converter does not remove passwords, by design.

Languages and dates

• Statements in English and Turkish are supported. Both number conventions (1,234.56 and 1.234,56), accounting-style negatives and CR/DR suffixes are detected from the statement itself, and every export writes a plain decimal.
• Dates. Month names in English and Turkish are read directly. An ambiguous numeric date such as 03/04, on a statement with no day above 12 and no printed period, is resolved from the transaction sequence; where a running balance is printed, the check catches an ordering error that results.
• The interface is in English.

Exports

• Every format comes from the review workbook, after you confirm it and upload it. Excel, CSV, CSV for import, QBO, OFX, QFX and QIF; producing them uses no pages, and the files carry no marks or notes.
• QBO bank identifier. The QBO file carries the identifier you enter on the Statement details sheet; left blank, a generic identifier is written, which manual Web Connect imports accept. Some QuickBooks setups require the bank's own identifier: email us the bank and we tell you what to enter.
• QuickBooks Desktop. Import through QBO Web Connect or CSV. Desktop tells accounts apart by the account number in the file, which is the Account number field on the Statement details sheet.
• Descriptions are exported exactly as printed. No merchant-name cleanup, no categorization.
• Programmatic use. An API, a Google Sheets destination and team workspaces are on the roadmap.

If you are converting your first statement, how to convert a bank statement PDF to Excel walks through it end to end.

Support