First Citizens .qbo downloads throw OL-222 in QuickBooks because of malformed transaction types. Export your CSV and build a clean, OFX-compliant .qbo here instead.
No account needed for your first conversions. We never store your bank login.
Short answer: If a First Citizens Bank download will not import into QuickBooks, or it throws Error OL-222, the file the bank gave you is malformed, not your QuickBooks setup. Export your First Citizens activity as a CSV and convert it here, and the converter builds a clean, OFX-compliant QuickBooks Web Connect (.qbo) file with every deposit, withdrawal, and card charge signed correctly. QuickBooks Online imports the .qbo directly, and QuickBooks Desktop reads it through File, Utilities, Import, Web Connect Files.
First Citizens has absorbed several banks in recent years, including CIT Bank and the former Silicon Valley Bank, and each conversion moved customers onto the First Citizens platform. Those conversions are when feeds and downloads tend to break. Business customers have reported connection failures and .qbo imports that QuickBooks rejects. Converting your own CSV to a properly formed .qbo gives you a file QuickBooks accepts on the first try, no matter what the bank download does.
Built for the CSV and Excel exports US banks and cards actually send, checked before it exports.
The converter adds up the transactions it parsed and matches that to your file total before you export, so nothing is silently dropped.
Valid OFX 1.02 with QuickBooks Web Connect headers. Online and Desktop import it as a standard bank feed.
Date, description, and amount are detected for you, so you skip QuickBooks' strict 3-column and 4-column CSV layout.
Bulk upload for catch-up and cleanup work. Each file gets its own reconciliation check and its own exports.
Mixed date formats, currency symbols, and stray commas that break a raw CSV import are cleaned up before the .qbo is built.
One conversion, three files: the .qbo for QuickBooks, an XLSX to review, and a CSV for everything else.
Three steps. No column-mapping wizard.
Drag in a CSV, XLS, or XLSX export from your bank, credit card, or accounting tool. Any column order is fine.
Every transaction is parsed and checked against your file total. You see the rows before exporting.
Download the .qbo and import it as a Web Connect bank feed. Excel and CSV are in the same download.
The specifics that decide whether the import is clean. If your case is not here, message us in chat.
Because the .qbo First Citizens hands you is not fully compliant with the OFX standard QuickBooks requires. The most reported cause is the transaction-type coding: the bank writes values QuickBooks does not accept, such as spelling out DEPOSIT where QuickBooks expects the short code DEP, and stray invalid characters in the file. QuickBooks then refuses the import and returns Error OL-222. Some users hand-edit the bank file in a text editor to fix it, but building a clean .qbo from your CSV avoids the malformed download entirely.
It can, but the connection has been unreliable through the recent platform conversions. Business customers report connection errors such as Banking error 102 and downloaded Web Connect files that fail on import. First Citizens itself tells customers to disconnect their old bank feed before reconnecting to the First Citizens platform, which is a sign of how disruptive the conversion is. When the feed or download will not cooperate, exporting a CSV and importing a converted .qbo keeps your books moving.
Export your First Citizens checking, savings, or credit card activity as a CSV, then upload it in the converter at the top of this page. The tool detects the date, description, and amount columns, normalizes the dates, strips dollar signs and commas, and writes each transaction type using the short codes QuickBooks accepts, so the OL-222 problem never appears. It totals the parsed rows against your file before it writes the .qbo. Download the .qbo and import it into the matching First Citizens account.
Sign in to First Citizens Digital Banking, open the account you want, and go to its transaction history. Choose a date range or a specific statement period, then select the download or export option and pick the CSV or spreadsheet format. If a view only offers a PDF statement, download that and turn it into a spreadsheet first, then convert that file here. Pull each period you still need, since the on-screen history only reaches back so far.
Given that the bank .qbo has been triggering OL-222, a converted .qbo built from your CSV is the most reliable file. This table compares the options for a First Citizens account and what each means for your import.
| File or method | Works with First Citizens? | Reliability | Best for |
|---|---|---|---|
| Bank .qbo download (Web Connect) | Available, but often throws OL-222 | Fails on malformed transaction types | Only when it imports cleanly |
| Express Web Connect (aggregated feed) | Unreliable through conversions | Drops and duplicates | Not dependable for clean books |
| Raw CSV upload to QuickBooks Online | Yes, but forces column mapping | Manual, capped at 350 KB | Small, one-off imports |
| CSV export, convert to .qbo (this page) | Yes, every First Citizens account | Clean, OFX-compliant every time | Bookkeeping and clean reconciliation |
Yes. First Citizens business checking, business savings, and credit card accounts all export activity as a CSV, and accounts moved over from CIT Bank or the former Silicon Valley Bank export the same way once they are on the First Citizens platform. Convert the exported CSV to a .qbo and import it into the matching account in QuickBooks. For a credit card, set the account up as a Credit Card type so purchases and payments carry the right signs.
Add the account with the correct type before importing: checking and savings as Bank accounts, and any First Citizens card as a Credit Card account. In QuickBooks Online, open the Chart of Accounts, add a new account, choose the type, and name it for the First Citizens account. Then import the converted .qbo into that account. Setting the type first keeps the running balance matching your statement and prevents sign errors during reconciliation.
In QuickBooks Online, open Transactions, then Bank transactions, select the matching First Citizens account, and upload the .qbo file. In QuickBooks Desktop, go to File, then Utilities, then Import, then Web Connect Files, and choose the .qbo. Because the converter writes compliant transaction types and clean characters, the file imports without the OL-222 error the bank download produces, and the transactions post straight to the register.
QuickBooks Online caps a raw CSV upload at 350 KB, roughly a thousand rows, so a long history has to be split into several files. A .qbo import is not held to that limit, so converting lets you bring a full year of First Citizens activity into QuickBooks in one file. To process several statements at once, the bulk CSV to QBO converter handles them in a single batch.
Yes. Before the .qbo downloads, the converter totals every transaction it parsed and compares that against your First Citizens file, so a missing or misread row shows up in the preview rather than during reconciliation. The tool only reads the transaction rows, date, description, and amount, to build the file, and never asks for your First Citizens login.
Upload a CSV or Excel export, get a QuickBooks-ready .qbo back in seconds. No card to try it.
Related guides: convert any bank or card file with the CSV to QBO converter, understand the file format in the QuickBooks Web Connect file converter guide, avoid the retiring bank feed with the Direct Connect alternative, and follow the steps to import a QBO file into QuickBooks or fix a QuickBooks Web Connect import error.
For the solo bookkeeper running a monthly close in QuickBooks.
USD / month
billed $288 yearly
For a firm or finance team converting across many clients and currencies.
USD / month
billed $888 yearly
For multi-bookkeeper firms managing many client books at scale.
USD / month
billed $2,988 yearly