Citibank provides checking and savings statements and Citi issues personal, business and co-branded credit cards, all in US dollars. The reviewed statements include a Citi Priority checking statement, Citi and CitiBusiness card statements with several cardholders, a Costco Anywhere Visa statement and an older card statement with unreadable fonts.
Full name: Citibank
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 Citi statements from 2021 to 2026: a Citi Priority checking statement, Citi and CitiBusiness credit card statements with several cardholders, a Costco Anywhere Visa statement, and an older personal card statement whose PDF fonts cannot be read by text extraction. Citibank checking and Citi credit cards use two unrelated layouts, so the first step is to tell them apart: a checking statement has Amount Subtracted, Amount Added and Balance columns; a card statement has Sale Date, Post Date, Description and Amount.
MM/DD/YY. Card rows carry two dates, MM/DD sale date and MM/DD post date, with no year; the year comes from the billing period in the header, 08/12/25-09/09/25, and a December statement holds both years. Card purchases on checking statements embed a second date and a time in the description, Debit Card Purchase 01/01 01:06p #0613, and that date can belong to the previous year on a January statement.On card statements the negative sign in front of payments and credits is a glyph that text extraction returns as the word minus: minus$5,315.05. A converter that tests for - sees a positive payment; one that reads the amount with a regular expression for digits sees 5,315.05 and drops the sign. Treat the literal text minus before a dollar sign as a negative sign.
An older personal card statement extracts its labels and dates but not a single amount: the embedded fonts for the amount column are in a format the PDF library rejects, and the amounts come back empty even though the page is text, not a scan. The only way to convert such a file is to treat it as a scan and OCR the rendered page. A statement whose extracted text has dates and merchants but no amounts is this case, not an empty statement.
A checking row starts with a transaction type in the main font, ACH Electronic Debit, Debit Card Purchase 01/01 01:06p #0613, Mobile Purchase Sign Based, Bill Payment, Debit PIN Purchase. The merchant detail follows in a smaller font, either on the same line to the right or on a second line below, and card purchases add a third line with the merchant category, Specialty Retail stores, Misc Business Services, Contractors. The type line is the same for hundreds of rows; the payee is on the detail line; the category line is a free hint for categorizing that no other bank prints. A converter must keep the three lines together and take the payee from the second one.
The detail line ends with a state and five digits, CA 22002. The digits are not a ZIP code; they are the year and day of year of the transaction, 22002 being January 2, 2022.
The first page of a Citi Priority or Citigold statement carries Value of Accounts, Earnings Summary and Bank Loans Utilized tables with Last Period and This Period columns, balances and interest, followed by a page of fee explanations and messages. The transactions start on the second or third page under "Checking Activity", with an "Opening Balance" row that has a balance and no amount. None of the first-page figures are transactions.
The Cardholder Summary lists each cardholder with a "Card ending in" number, a spend limit and New Charges. The transaction list then repeats the cardholder name as a heading, Standard Purchases under it, and No Activity for cardholders with nothing to show. Payments, Credits and Adjustments come first, with a post date only. Purchases follow per cardholder, with a sale date and a post date. Assigning rows to a card means tracking the last cardholder heading.
A foreign purchase prints the merchant on one line, the original amount and currency on the next, 17,000.00 COSTA RICAN COLON, and Subject to Foreign Fee with the billed dollar amount on the third. The dollar amount is not on the merchant line, and the foreign amount is large and unsigned. A converter that takes the first number after the merchant as the amount reads 17,000.00 instead of $33.85.
On the Costco Visa layout a long merchant name wraps with part of it printed above the row that holds the dates and part below, so grouping by vertical position alone attaches the first part to the previous transaction.
$0.00 (D) style amounts, and year-to-date totals of fees and interest.+$37.45 style amounts.Continued markers on checking pages.Checking statements have a balance on every row; each subtraction or addition must move the previous balance to the printed one. Card statements have no running balance; use Previous balance minus Payments and Credits plus Purchases plus Fees plus Interest equals New balance, and the New Charges per cardholder against the rows under that cardholder.
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.