Convert a Patelco Credit Union PDF or image bank statement into a .qbo for QuickBooks Online or Desktop when the California credit union feed breaks.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF
Uploading...
When the Patelco Credit Union feed in QuickBooks stops updating, keeps asking you to reconnect, or throws an error the day after a platform change, stop fighting it. Download the Patelco statement PDF, run it through the converter at the top of this page, and import the resulting .qbo straight into QuickBooks. That is the fastest path back to a reconciled month, whether the feed died this morning or went dark during the platform work that followed Patelco's 2024 outage.
The converter takes a PDF or an image (photo or scan) of your Patelco statement and produces a QuickBooks Web Connect file, the .qbo format QuickBooks was built to read. PDF and image are the only inputs it accepts. Before it hands you the export, it adds up every transaction it read and compares its running total against the closing balance printed on your statement. If the two disagree, you get told, not a silently wrong file. The same parsed data can also come out as Excel or CSV for your working papers.
Last updated July 2026.
Built for the statements US banks actually send, checked before it exports.
The converter adds up the transactions it parsed and matches that to the statement 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.
OCR runs before parsing, so a scanned or photographed paper statement comes out the same as a digital PDF.
Bulk upload for catch-up and cleanup work. Each file gets its own reconciliation check and its own exports.
Enter the password on upload. Multi-column and multi-page statement layouts are parsed too.
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 PDF, a scan, or a phone photo. Password-protected and multi-page files are fine.
Every transaction is extracted and checked against the statement total. You see the parsed 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, email [email protected].
Often it does, but not always cleanly. Patelco is a large California credit union with roughly 500,000 members, and QuickBooks can reach it through Intuit's aggregator connections. Members and bookkeepers, though, report the usual credit union pattern: reconnect prompts, downloads that stall, and setups that authenticate and then pull nothing. When any of that hits, the PDF route keeps the books moving.
QuickBooks reaches a bank through one of four channels. Direct Connect is a bank-hosted, often paid link (the credit union sets any fee, so never assume it is free). Web Connect is the manual path where you download a .qbo and import it. Express Web Connect and Express Web Connect+ are the credential and token based aggregator links that re-authenticate constantly and throw errors 103, 105, and reconnect prompts. Patelco members have historically used Quicken and aggregator connections, and some have had to re-add the institution under a Web Connect variant of the name to get downloads flowing. Do not assume any one channel is available for your account until you confirm it inside QuickBooks.
None of the aggregator failures are fixable from your end. You cannot repair a screen-scraping connector by clearing your browser cache. You wait for Intuit and the credit union to sort it out, or you route around it. A statement PDF converted to .qbo posts the same result: dated transactions in For Review, ready to match.
Patelco was hit by a ransomware attack in 2024 that took its banking systems offline from June 29 to about July 15, 2024. Online banking, the mobile app, transfers, statements, bill pay, Zelle, and card functions were all down for roughly two weeks. The systems were later restored, but the episode is a textbook example of why a working QuickBooks feed suddenly stops.
When a credit union rebuilds or hardens its digital platform after an incident like this, the aggregator connectors that QuickBooks relies on frequently have to be rewritten and re-certified. In the meantime, feeds go stale, logins get rejected, and members see reconnect prompts that never resolve. The California Department of Financial Protection and Innovation later issued a consent order in connection with the event, including a $100,000 penalty tied to cybersecurity findings. The point for a bookkeeper is simple: the systems came back, but events like this are exactly what knock a feed offline and force you to import statements by hand for a while. Converting the PDF to .qbo is how you stay current without waiting on the connector.
Sign in to Patelco Online banking at patelco.org or in the Patelco mobile app and open the Statements or eStatements section. Patelco delivers monthly statements you can view and save as PDF files, and the same option is available on the website and in the app. Open the month you want and save it as a PDF to your computer.
Statements are electronic once you set your eStatement preference, so if you never enrolled you may not see much history online. Patelco does not publish a single fixed number for how far back statements stay available. Check your Statements or eStatements section and see what is actually there before promising a client two or three years of cleanup. If the history you need is gone, contact Patelco and ask for archived statements.
Save each month as its own PDF, and if the file is password protected, remove the password first. Scans and photos work too, as long as the page is flat and the amounts column is in focus.
Convert the PDF to .qbo, then in QuickBooks Online go to Transactions, then Bank transactions, then Upload from file. Pick the .qbo, map it to the Patelco account in your chart of accounts (checking to checking, business card to the credit card account), and confirm. The transactions land in For Review just as if the feed had delivered them, and your rules, matches, and suggested categories all still fire.
Two limits are worth knowing. QuickBooks Online's Upload from file tool accepts QBO, QFX, and CSV, rejects files over 350 KB, and caps a single upload at 1,000 transaction lines. Neither limit bothers one month of a small business checking account. Both bite when you catch up a busy year in one go. The fix is boring and reliable: convert and upload one statement month at a time, and tick each month off against its own printed closing balance.
In QuickBooks Desktop, go to Banking, then Bank Feeds, then Import Web Connect File, and select the .qbo you produced. Desktop asks which account the file belongs to. Point it at the Patelco account and work the transactions through the Bank Feeds Center.
Here is the part that trips people up every year. Desktop's Web Connect importer reads .qbo and nothing else. Not .qfx, not .ofx, not CSV. If Patelco online banking or a Quicken export hands you a QFX or CSV file, Desktop will refuse it. QFX is the Quicken flavor of the same OFX standard, close enough to look like it should work and different enough that Desktop rejects it. Converting the statement PDF gives you a real .qbo that Desktop accepts on the first try.
Patelco runs a real business banking operation. It offers Business Checking and Business Interest Checking, plus Business Money Market, business credit cards, and merchant services, all managed through Patelco Online and the mobile app. All of that is legitimate, and none of it guarantees a clean QuickBooks feed.
Credit unions frequently build business digital banking on a different platform from the retail one. Same brand, same phone number, but underneath they can be separate systems with separate sign-in flows and separate multifactor prompts. QuickBooks treats the institution as the unique thing it connects to, not the credential set. You search the credit union by name, you get one entry (sometimes two or three that look nearly identical, including a Web Connect variant), and the connector behind it was written against one specific platform. If your business credentials belong to the other one, the failure is not helpful. It refuses your password, or accepts it and returns nothing, or asks for a security code that never arrives.
Symptoms to watch for: your login works on patelco.org but QuickBooks reports error 103; the connector links your personal accounts but not the business ones; or the connection authenticates and pulls zero transactions because the aggregator cannot read the business platform behind it. Call Patelco and ask which digital banking platform your business account sits on and whether third-party aggregator access is supported for it. Meanwhile, convert the statement PDF and keep the books moving.
| Route | What you actually get | How far back | Typical friction |
|---|---|---|---|
| Live bank feed (Direct Connect or aggregator connection) | Transactions flow automatically into For Review, no file handling | Often the last 90 days at setup, then forward only, but the window varies by institution | Any Direct Connect access is bank enrolled and the credit union sets any fee. Aggregator links throw reconnect prompts and errors 103 and 105, and business logins often will not link. Platform work after an outage can break all of it. |
| Downloading a file from Patelco online banking | Export formats have historically included Quicken and spreadsheet style files. Patelco does not advertise a QuickBooks .qbo export. | Limited by the history window shown in online banking | Quicken-format and CSV files are not .qbo. Desktop's Web Connect importer rejects anything but .qbo, and a CSV has to be mapped by hand every time. |
| PDF statement converted to .qbo (this page) | A QuickBooks Web Connect file with dates, descriptions, and amounts, plus optional Excel or CSV copies | As far back as you have statement PDFs, including archived ones from Patelco | One statement at a time. The upside is a balance check against the printed closing figure before export. |
When the feed is healthy, use it. When it is not, and around a platform disruption it often is not, the PDF route is the only one that hands QuickBooks a file it accepts natively.
It depends on when you turned on eStatements and how long Patelco keeps them online for your account, and Patelco does not publish a single hard number. Sign in, open the Statements or eStatements section, and look at the actual list before you commit to a cleanup scope. Anything you can open as a PDF, you can convert here, no matter how old, so the real constraint is what Patelco still shows you.
If you need months that have dropped off the list, contact Patelco and ask for archived statements. Paper or PDF, once you have the pages you can run each one through the converter and check it against its own closing balance.
Patelco does not advertise a QuickBooks Web Connect (.qbo) export. It has historically supported Quicken connections and spreadsheet style downloads instead. If your account has no .qbo option, or the aggregator feed is down, convert the statement PDF here and import the .qbo directly.
Error 105 means Intuit's connector could not read Patelco's site, usually after a platform change or during maintenance. Error 103 means your credentials were rejected even though they work on patelco.org. Neither is caused by anything you did, and neither is fixable from your side. Import a converted statement to stay current.
Yes. Images are accepted alongside PDFs. Photograph or scan the full page, keep it flat and in focus, and include the header with the closing balance. The converter needs that printed balance to check its own arithmetic before it produces the .qbo file.
Not if you disconnect the bank feed first, or only convert months the feed never delivered. QuickBooks does deduplicate on transaction IDs, but the safest habit is one source per date range. If duplicates do appear, exclude them from the For Review tab rather than deleting posted entries.
Yes. Any Patelco statement you can download as a PDF converts the same way, business or personal, checking or card. This matters most for business accounts, since credit union business platforms are the ones QuickBooks feeds are least likely to connect to in the first place.
Upload a PDF, get a QuickBooks-ready .qbo back in seconds. No card to try it.
This pattern repeats across every credit union client you take on, so the credit union statement to QuickBooks guide is worth reading once for the shared playbook. For the business-login problem specifically, see why a credit union business account will not connect to QuickBooks. Go straight to the QBO converter, learn how the PDF to QBO converter handles a statement, and remember that our bank statement to QBO converter treats every US bank and credit union statement the same way: PDF or image in, QuickBooks-ready .qbo out.
Same converter, tuned for the layout each bank uses. Find yours:
From the same family of tools
For one bookkeeper running monthly close.
USD
per month
billed as
$288 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
For an accounting firm or finance team with steady volume. Adds QuickBooks .qbo export and bulk conversion.
USD
per month
billed as
$888 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
For lenders, audit firms and analysts running thousands of statements a month.
USD
per month
billed as
$ yearly
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
