Guaranty Bank & Trust provides statements for personal and business checking and savings accounts in Texas, in US dollars, and moved to the Glacier Bank statement layout in early 2026. The reviewed documents are a January 2026 statement in the old Guaranty layout and a March 2026 statement in the new one, for the same business checking account.
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 two Guaranty Bank & Trust statements for one business checking account of a restaurant in Texas: January 2026 and March 2026. They do not look like statements from the same bank. The January statement is the old Guaranty layout, with separate sections for credits, debits and checks and no running balance. The March statement is a "Statement of Account" on the Glacier Bank system, with one running table, signed amounts and a Glacier privacy notice at the back. The January statement itself announces the change in a box on page one, and a converter set up on one of the two layouts stops working on the other.
MM/DD with no year on both layouts, 01/02 on the old one and 3/02 without the leading zero on the new one. The old period reads "Statement Period 1/1/2026 TO 1/31/2026"; the new one reads "Statement Dates 3/02/26 to 3/31/26 (30 days)". Check image captions carry the full date, 1/16/2026 on the old layout and 03/02/26 on the new.1,409.43, and takes the sign from the section. The new layout prints a dollar sign on every amount and a leading minus on debits, -$9,143.10, in a Debits column and unsigned credits, $2,846.60, in a Credits column, with a running Balance column.XXXXXX5218, and printed in full in the old summary block, Business Checking 13235218, and in every old check image caption. The new layout prints it masked in the product line, "TOTALLY FREE BUSINESS CHECKING - XXXXXX5218".The January statement carries a notice about a move to new systems, and the March statement is printed by them: the same account, the same masked number, a different page size, a different header, different columns and a different sign convention. Page two of the March statement lists the Glacier Bank divisions, and the privacy notice at the back is Glacier Bank's, with Guaranty Bank & Trust as one division. A converter that was set up for the January layout finds no DEPOSITS AND OTHER CREDITS heading in March, and one set up for March finds no Debits column in January. Both layouts have to be recognised, and the account number, which does not change, is the link between them.
The January statement lists DEPOSITS AND OTHER CREDITS first, then WITHDRAWALS AND OTHER DEBITS, then CHECKS, each with a DATE AMOUNT DESCRIPTION header and unsigned amounts. The CHECKS table prints two groups of DATE CHECK NO AMOUNT side by side, sorted by check number and not by date, with an asterisk glued to the number to mark a gap, 2361*. A DAILY BALANCE INFORMATION table with three groups of DATE BALANCE follows, and a SUMMARY OF OVERDRAFT AND RETURNED ITEM FEES with dollar signs. There is no running balance on the rows, so the only checks are the summary block on page one and the daily balance table. A converter that reads any dated line with an amount takes the daily balances as thirty deposits.
On the March statement the text of each row comes out of the PDF in the order date, debit or credit, balance, description, so a converter that reads the elements in file order sees 3/02 $2,846.60 $121,048.60 DDA Regular Deposit and takes the balance for the amount. Sorting by position fixes it. Check rows read CHECK and the number in a separate cell, CHECK 2347, and some read CHECK alone, -$4,200.00 with no number at all. The SUMMARY BY CHECK NUMBER table at the end has the same rows, with an asterisk in its own cell next to a number that is out of sequence and a note " Denotes checks out of sequence", and the rows without a number have an empty check number cell. A converter that requires a check number on a check row drops those, and one that takes the asterisk as part of the number produces `2347`.
A supplier payment reads ACH Ben E. Keith Com 1000 ISA*00* *00* *17*121000562 and continues on a second line with *17*111915608 *260102*011 on the old layout. On the new layout the same payment reads Ben E. Keith Com 1000 CTX 0000261412 091000015170382 ISA*00* with a second line *00* *17*121000562 *17*111915 608 *260302*0132*U*00401*. These are pieces of the EDI envelope that the sender put in the addenda, and the routing and trace numbers change on every payment. An Uber payout ends with REF*TN*ESRDM1DKWQ\, a backslash included. A converter that keeps the full description gets a payee that never matches twice; one that cuts at the first star, or at the ACH class code (PPD, CCD, CTX), gets Ben E. Keith Com.
The old layout is numbered "1 OF 4" but the file has five pages: page two is the back of the first sheet, a reconciliation worksheet with CHECKS OUTSTANDING, BALANCE BROUGHT FORWARD and $ ____________ boxes, unnumbered, and it sits between page 1 and page 2 of the statement. The old check image pages carry captions 13235218 $763.36 1/16/2026 2331, account, amount, date and check number, two per line. The new layout has eight pages: transactions on pages one, three and four, a list of Glacier divisions with addresses and phone numbers on page two, image pages with captions Date 03/02/26 Check No Amount $2,846.60 that include deposit slips as well as checks, and a two-page privacy notice whose own page numbers restart at "Page 2". Each new page also carries a short string of symbols in the top right corner, !NqHV)]mn"7T"|+`, which is a barcode printed in a barcode font. A converter that reads every page as transactions takes the worksheet, the captions, the division list and the barcode as data.
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.