Truist provides statements for personal and business checking, savings and business credit card accounts in US dollars. The reviewed statements include Business Value 500 Checking, Truist Focus Checking and Business Visa statements, one of them a text PDF with an OCR text layer.
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 Truist statements from 2022 to 2025: a Business Value 500 Checking statement, a Truist Focus Checking statement, and two Business Visa card statements. One of the checking statements is a text PDF whose text layer came from OCR, which is common for Truist statements that customers download and re-save, so the page covers both clean and OCR-layer files.
MM/DD with no year. The statement is dated in the header, For 03/27/2025, and the period is the span between "Your previous balance as of 02/27/2025" and "Your new balance as of 03/27/2025", so Truist cycles run mid-month to mid-month and cross the year in December. Card rows carry a transaction date and a post date, both MM/DD, with the year in "Billing cycle 02/08/25 - 03/07/25".-$2,500.00.NC 1340009215548, and again in the account heading. Card statements print only "Account ending in 2362".A Truist checking statement lists "Other withdrawals, debits and service charges" first and "Deposits, credits and interest" after it, often on the next page. Both print positive numbers. A converter that assumes deposits come first, or that reads the amounts without tracking the section, gets every sign wrong. Each section closes with a total line, = $5,976.97, and the Account summary on the first page shows the same totals with their signs, which is the check.
The customer name and address on the first page come through as A N G E L D M I T C H E L L, one space between every letter. This is how Truist prints the mailing block, not an extraction error. It does not affect the transactions, but a converter that reads the account holder name from the statement has to collapse the spacing.
A debit card row reads DEBIT CARD PURCHASE DUNKIN #362563 03-15 843-745-0892 followed by NC and 5070 as separate elements to the right. The state and the last four digits of the card are their own columns. A converter that joins everything after the date into one description gets a payee that ends in "NC 5070" on every card row; one that stops at the description column loses which card was used. The transaction date is inside the description as 03-15 for signature purchases and as 03-16-25 for PIN purchases, while the DATE column is the posting date.
The same text carries INT'L SERVICE ASSESSMENT FEE rows that repeat the merchant of the foreign purchase they belong to, and CONVERTED CHECK - ARC rows for checks the payee turned into electronic debits, which are listed here and not in the Checks section.
The Checks section has three groups of DATE, CHECK#, AMOUNT side by side, so a single row holds up to three checks that are not in date order with each other. A * after a check number marks a gap in the sequence and a • before it marks an electronically converted check, explained in a footnote under the table. Neither mark is part of the number.
One reviewed checking statement is a text PDF, but the text was produced by OCR before the file reached the converter. The signs are doubled spaces inside phrases, DEBIT CARD PURCHASE, spaces inside amounts, 63 .59 and 200 .00, check numbers with junk attached, 2548,--,, a page count read as Page 3 of S, and left edges of the date column that drift by fifty pixels down the page because the scan was skewed. A converter must treat such a file like a scan: normalize spaces inside numbers before parsing them, group rows by position with a wider tolerance, and reconcile every section total.
Card rows have five columns: transaction date, post date, a 23-digit reference number, a description and an amount. The description is padded to fixed widths, merchant, city and state, so the city runs into the state when it is long, PEMBROKE PINEFL, FORT LAUDERDAFL. The reference number is unique per row and is the right transaction ID. Refunds carry a leading minus like payments do. There is no running balance; the check is Total transactions and other debits minus Total payments and other credits equals Balance in the Account summary.
The lower part of the first page is a remittance block marked "For information only, Do not remit payment" on company copies, with the account ending and the balance repeated. It is not a transaction.
The Account summary with its signed totals, the section total lines, the "Average Posted Balance in Statement Cycle" line, the page header with the account number, the page footer split into PAGE, 2, OF, 3, and the notices about fees and services that fill the rest of the last page.
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.