Fifth Third Bank provides statements for personal and business checking, savings and money market accounts in the Midwest and Southeast of the United States, in US dollars. The reviewed documents are twelve consecutive monthly statements of one 5/3 Business Checking account for 2024, which show which parts of the layout change from month to month.
Countries: United States
Supported statement formats: PDF
Supported destinations: QuickBooks Desktop, QuickBooks Online, Quicken, Xero, CSV/Excel
QuickBooks Online can read a PDF statement itself: Banking, Upload transactions, choose the PDF. Try it first. Use ProperConvert when QuickBooks flags the statement for review, stops before the last page, or the account is not in QuickBooks Online.
For a short statement, type the date, memo, and amount into the destination. Reconcile the result to the closing balance.
Open the PDF statement, review the extracted transactions, choose QuickBooks Online, and save the converted file on your computer.
Choose the posted transaction date, supply a missing year from the statement period, and check statements that cross January.
Remove currency symbols from numeric cells, preserve the decimal separator, and verify debit and credit signs against the running balance.
Keep the payee or customer reference that helps identify the transaction, while avoiding repeated headers and unrelated reference numbers.
The following details were checked against twelve Fifth Third statements: every month of 2024 for one 5/3 Business Checking account in Michigan. Twelve consecutive months of one account show which parts of the layout are fixed and which parts appear only in some months: a Checks section that exists only when a check cleared, a notice block that appears in some months and not others, and a page count that swings between two and four. The rules below are the ones that held for all twelve.
MM/DD with no year, 03/01 and 03/28. The period is in the header of the odd pages, "Statement Period Date: 3/1/2024 - 3/31/2024". Each card purchase carries a second date inside the description, ON 022924, the purchase date, which can be in the previous month.1,150.61. The account summary prints debits with a dollar sign outside parentheses, $(58,642.65), and credits with a plain dollar sign, $75,417.44.7914903218, after "Account Number:" in the header and in the heading "Account Summary - 7914903218". The same number is printed twice more on every page in two control lines, described below.The first line of every page reads FTCSTMT051 051 20240331 UDSPDFSTMT 0000000007914903218 DDA and the last line reads PSKEY01|DDA0|01|FTEM|20240331|8|0|S|1|16010|16010|7914903218|0|47741||PSKEY99|. They are print control keys: the statement date, the account number padded with zeros, a page sequence number that increases by one on each page. They are printed in the page margin in the same font as the statement. A converter that treats every line as content sees a twenty-digit number and a line full of pipes on every page, and a user who blacks out the account number in the header still sends it out twice per page.
The statement lists Checks first, then Withdrawals / Debits, then Deposits / Credits, then a Daily Balance Summary. Every section heading carries its own count and total, 44 items totaling $58,612.65, and a section that continues on the next page repeats its heading with "- continued". No row has a sign. The Checks section exists only in months when a check cleared: in the January statement the summary line Checks has no count and no amount, and the section is absent. A converter that expects the sections in a fixed order, or expects the Checks heading every month, breaks in the months without checks; one that reads all rows with one sign gets the ending balance wrong by twice the deposits.
A card row reads 03/01 2.15 DEBIT CARD PURCHASE AT City of Detroit 38, DETROIT, MI ON 022924 FROM CARD#: and continues on a second line with XXXXXXXXXXXX1108. The first date is the posting date; 022924 in the text is the purchase date, February 29 on a March statement. ACH rows end with the same six-digit date, PAYCOR INC. 109463071524007 tax fund 101511143260492 COMPANY NAME TRA 030724. A converter that takes the first six-digit group it finds as a date reads the reference number 109463071524004 as one; one that picks the date in the description over the posting date puts the row in the wrong month. The account has two cards, ...1108 and ...3741, and the card number is on the second line of every purchase.
Payroll rows read PAYCOR INC. 109463141524005 tax fund 208020603241170 COMPANY NAME TRA 031424 and PAYCOR INC. 109463141524003 DD - Fund 122883576457311 COMPANY NAME TRA 031424, two rows per payday with different fifteen-digit references. A lease payment runs to two lines with CO# 01 CUST# 313604 and LEASE# 1166072 TRAN# 000000291 BATCH# 0000158. The account holder's own name is printed inside the description, cut at a fixed width, COMPANY NAME TRA. A converter that keeps the whole description gets a payee that never repeats; one that cuts at the first digit gets PAYCOR INC. for both rows and loses the difference between the tax payment and the direct deposit fund, which the bookkeeper needs. The useful cut is after the second word group, before the reference number, keeping tax fund or DD - Fund as a memo.
The Checks section is a table of Number Date Paid Amount in two groups side by side, with a legend " Indicates gap in check sequence, i = Electronic Image, s = Substitute Check". The number cell reads 0000 i for a check with no number and `1478ifor a check after a gap, with the asterisk and the letter glued to the digits. A converter that reads the cell as a check number produces1478*i`, and one that requires digits only drops the row.
Pages one and three print the customer's name and address, the banking center, the phone numbers and the period; pages two and four print only the control line and the content. The transaction table starts lower on page one than on page two. Some months add a notice block on the first or last page, in capitals, about fee-free ATMs or updated account rules, and the four-page months end with a page that says "This page intentionally left blank." A converter that learns the table position from page one and applies it to page two misses the first rows of page two; one that expects text on every page stops on the blank one.
The Account Summary on page one has the beginning balance, counts and totals per section and the ending balance, with the dates 03/01 and 03/31 in the first column, so it looks like two dated rows. The analysis block below it, Analysis Period: 02/01/24 - 02/29/24, Service Charge withdrawn on 03/12/24 $0.00, refers to the previous month. The Daily Balance Summary prints three groups of Date Amount per line, one balance per business day. A converter that takes every dated line with an amount as a transaction adds the beginning and ending balance as rows and up to three balances per line at the end.
Compare the converted transaction count and totals with the statement, then confirm that the calculated final balance equals the printed closing balance.
Yes. If the PDF statement is readable, its age does not prevent conversion. Confirm the year when transaction rows omit it.
No. Convert posted transactions that contribute to the statement balance. Pending or future-dated items should not be mixed into that reconciliation.
Use the destination-specific settings below, then review the file before import. The destination may require particular columns, dates, account identifiers, or sign rules.
A bank PDF can contain searchable text, scanned page images, or a mixture of both. Searchable text still needs layout analysis because transaction descriptions wrap, columns move, and headers or balances repeat at page breaks. A scanned statement adds OCR uncertainty.
A transaction may begin at the bottom of one page and continue on the next. Continuation pages can omit column headings, repeat an opening balance, or insert footer text and legal pages between transaction pages. A conversion should join split rows and exclude repeated page furniture before it writes the output.
On scanned pages, OCR can turn 0 into O, 1 into l, or 5 into S. It can also lose a minus sign or decimal mark, read two columns in the wrong order, or struggle with skewed and faint pages. The running balance is the best check: a damaged amount or missing row breaks the balance sequence.
Yes. Review the OCR result and reconcile every balance movement. Scans with faint printing, rotation, or handwritten marks need more checking than searchable PDFs.
PDF text stores page positions rather than a spreadsheet table. Wrapped descriptions, repeated headers, and visually aligned columns can paste in the wrong order or into the wrong cells.
Try selecting a transaction description in a PDF reader. If individual words can be selected, the page probably contains text. If the whole page behaves like one picture, it requires OCR.
QuickBooks Online imports bank transactions from a file through Banking, Upload transactions. It accepts QBO, QFX and OFX files, which share the OFX structure, and CSV files. Uploaded rows land in the For Review list, where QuickBooks matches them to existing entries and the user adds or excludes them.
Since 2026 the same upload screen also takes a PDF or an image of a statement (JPG, PNG, HEIC). Intuit's AI reads the pages, and a statement it cannot read with confidence is held for a manual review by Intuit staff. If the account is in QuickBooks Online and the statement is a clean PDF, try that first; it costs nothing. A converted file is the better route when the upload flags the statement or stops before the last page, when there are many statements to catch up, when the bookkeeper wants to see and fix every row before it enters the books, or when a client's statement should not be uploaded to a third party.
Settings that matter:
MM/DD/YYYY or DD/MM/YYYY depending on the company settings, digits only, four-digit years.Use OFX, QFX or QBO when the file can be made in that format. It carries the payee, the memo and the check number and gives QuickBooks a transaction ID for duplicate checks. Use CSV when a spreadsheet is the only source and a single description is enough.
The usual causes are a date column QuickBooks cannot read, an amount with a currency symbol or thousands separator, more columns than the three- or four-column layout, or a file over the size limit. Save the file with dates as digits, amounts as plain numbers, and only the needed columns.
The account was chosen during upload. QuickBooks Online does not read the account name from the file. Exclude the rows, delete them from Excluded, and upload again with the right account selected.
In For Review, select the rows, choose Batch actions, Exclude Selected. Open Excluded, select them again, Batch actions, Delete. The rows are gone and the file can be uploaded again.
QuickBooks Online skips rows whose transaction ID it has already seen and, for CSV, rows it reads as duplicates by date, amount and description. Two genuine identical rows on the same day can be dropped from a CSV. Use an OFX-type file with unique IDs for those.
Yes. The 90-day limit applies to a live bank connection, not to a file upload. Any date range can be uploaded from a file.
For one clean statement of an account that is already in QuickBooks Online, the built-in upload is the shortest path, and this page says so. A converter earns its place when the upload flags the statement for review, when a scanned or multi-year statement does not go through, when the account is in QuickBooks Desktop, Quicken, Xero or Sage instead, or when the statement must stay on your computer. The converted file goes through the same Upload transactions screen as a QBO file, with a transaction ID per row, so re-uploading a period does not double it.