Converted a bank statement with ChatGPT or Claude? Check it before you import

Some accountants and owners now drop a month of bank or card statements into a general AI chat assistant, such as ChatGPT or Claude, and ask for a spreadsheet or a ledger. It can save typing. But what comes back is the assistant's reading of the PDF, not a copy of it, and nothing in the chat proves that every row made it across.

People who tried it have described the problems in public. One user on Reddit wrote that a few transactions were dropped, one entry was split into two rows and some amounts were slightly off across three months of statements (Reddit, April 2026). Another found rows in the output that were not on the statement at all, while real ones were missing (Reddit, 2024). Both posts were written by people who now sell converters, so read them as examples of what can go wrong, not as measurements of how often it happens.

The fix is the same check you would run on any converted file. It takes a few minutes per statement-month and needs only the numbers printed on the statement.

What to check, in order

1. Every page went in. Find "Page X of Y" on the statement and confirm the assistant was given every page. Long PDFs are where rows most easily go missing, so one statement-month per chat is easier to check than a whole year.
2. The month ties. Take the opening and closing balances from the statement itself, not from the assistant's answer. Total the deposits and the withdrawals in the spreadsheet yourself. Opening + deposits − withdrawals should equal the closing balance to the cent.
3. The totals match the summary box. Many statements print total deposits, total withdrawals and sometimes item counts. Compare your totals and row counts with them. That tells you which side is short.
4. No invented rows. A file can tie and still be wrong if one made-up row cancels a missing one. Check the largest few items, and the first and last days of the period, against the PDF line by line.
5. No split or merged rows. Look for two rows with the same date that add up to one statement line, or one row that combines two.
6. Signs are right. Deposits positive and withdrawals negative (or in the right column). Card statements run the other way; see credit card statement PDF to CSV.
7. Dates and years are right. Statements often print dates without a year. Check months that cross December into January, and that every date sits inside the statement period.
8. Only transactions came across. Running-balance figures, page headers, "continued" lines and summary totals should not appear as transactions.
9. The months join up. Each month's closing balance should equal the next month's opening balance.
10. Do the arithmetic outside the chat. Asking the same assistant to confirm its own work is not an independent check. Add the columns in a spreadsheet, or use our free tie-out checker, which runs in your browser and shows the row where a CSV stops balancing.

The full method, with a worked example of a missing page and a missing month, is in check a bank statement PDF is complete before you import it. Don't post a balancing entry to force a month to tie; find the cause first.

Get the layout right for the import

• QuickBooks Online: a CSV needs 3 columns (Date, Description, Amount) or 4 (Date, Description, Credit, Debit), all dates in one format, and the file must be 350 KB or less with up to 1,000 lines per upload (Intuit). QuickBooks Online can also read a statement PDF itself; see importing a PDF statement into QuickBooks Online.
• QuickBooks Desktop: bank transactions come in as a Web Connect .qbo file, not a CSV. See convert a PDF bank statement to a QBO file.
• Xero: a CSV needs at least a Date and an Amount column, and Xero recommends OFX, QFX or QuickBooks files where your bank offers them (Xero Central). See importing bank statements into Xero.
• If the account already has a bank feed, import only the dates before the feed starts. See duplicate transactions after a bank upload.

Date errors on import are common with assistant-made CSVs: QuickBooks CSV date format errors.

Before you paste a client's statement into a chat assistant

A statement carries account numbers, balances and the names of everyone the business pays. Settings differ by product and plan, and they change, so check your own account. What the vendors' own help pages said when we read them on 24 Oct 2026:

• Redact what the conversion doesn't need: full account numbers, the account holder's address, check images. Dates, descriptions, amounts and the opening and closing balances are enough.
• Check that your engagement letter allows outside tools to process client records. If it is unclear, ask the client first.
• The same questions apply to any converter, including us: questions to ask before uploading client bank statements.

Where LedgerReady fits

If you'd rather not run these checks on every month yourself, LedgerReady is done for you. For each statement-month you get a QBO file, a Xero CSV, a plain CSV and a tie-out sheet showing opening balance + net activity = closing balance, with any difference shown. It costs $15 per statement-month, and we aim to deliver within 12 hours. If the output doesn't reconcile to the statement's opening and closing balances and we can't fix it, you don't pay for that statement. LedgerReady is AI-assisted and run by an automated operator; we are not CPAs, and you should still review categories before you rely on them.

Bank menus change; labels here were accurate to our knowledge in Oct 2026, so check your bank's help pages if something differs.