Convert a DCU (Digital Federal Credit Union) PDF or image bank statement into a .qbo for QuickBooks Online or Desktop when the credit union feed breaks.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF
Uploading...
When the Digital Federal Credit Union feed in QuickBooks stops updating, keeps asking for a validation code, or tells you the account no longer supports downloading, stop fighting it. Download the DCU 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 after DCU moved to its newer digital banking platform.
The converter takes a PDF or an image (photo or scan) of your DCU 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].
Sometimes, through a credential-based aggregator connection, but DCU has a rocky track record here. When DCU moved to a newer digital banking platform that signs you in with a username and password instead of a member number, the change broke a lot of automated downloads. DCU also stopped supporting Direct Connect, the paid, bank-hosted channel that tends to be the most stable, so the connections that remain are the credential-based Express Web Connect and Web Connect style links that re-authenticate constantly.
In practice, DCU members and their bookkeepers report connections that need a security code every single time, downloads that stop pulling new transactions while newer activity is clearly visible on the site, and setups that finish two-factor authentication and then cannot find the accounts. In QuickBooks Online those surface as error 102 or 105 (the connector cannot read the site), error 103 (credentials rejected even though they work fine on dcu.org), or a feed showing a stale "last updated" date. Some members have seen a message that the account is at a bank that no longer supports downloading.
None of these are fixable from your end. You cannot repair an aggregator connector by clearing your cache. You wait, or you route around it. A statement PDF converted to .qbo posts the same result: dated transactions in For Review, ready to match.
Sign in to DCU Digital Banking at dcu.org or in the DCU mobile app and open the eStatements section. DCU delivers monthly account, mortgage, and credit card statements as eStatements you can view, print, and save as PDF files, and the same eStatements option appears in both the website and the mobile app. Open the month you want and save it as a PDF.
Statements are electronic once you set your eStatement preference, so if you never enrolled in eStatements you may not see much history online. DCU does not publish a fixed number for how far back statements stay available. Check your 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, ask DCU 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 DCU account in your chart of accounts (checking to checking, business card to the credit card account), and confirm. The transactions land in For Review exactly as if the feed had delivered them, and your rules, matches, and suggested categories all still fire.
Two limits are worth knowing. QuickBooks Online rejects files over 350KB and caps a single upload at 1,000 transaction lines. Neither 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 DCU 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. DCU's own online banking has offered QFX, OFX, and CSV exports at various points, and DCU has told members it no longer provides QFX files at all. QFX is the Quicken flavor of the same OFX standard, close enough to look like it should work and different enough that Desktop refuses it. Converting the statement PDF gives you a real .qbo that Desktop accepts on the first try.
DCU runs a real business banking operation. It offers Free Business Checking with no monthly maintenance fee, business savings, money market, CD and IRA options, up to four business Visa debit cards per account, and Business Digital Banking through the app and dcu.org so an owner can manage the accounts, pay bills, and deposit checks. 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), 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 dcu.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 DCU 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 (aggregator connection) | Transactions flow automatically into For Review, no file handling | Usually the last 90 days at setup, then forward only | DCU uses credential-based Express Web Connect and Web Connect style access, not Direct Connect. Repeated validation codes, errors 102, 103, and 105, and stalled downloads are common, and business logins often will not link. |
| Downloading a file from DCU Digital Banking | DCU has offered CSV and Quicken-format exports on some accounts, and has told members it no longer provides QFX. It does not advertise a QuickBooks .qbo export. | Limited by the history window in online banking | Quicken-format and spreadsheet exports are not .qbo. Desktop's Web Connect importer rejects anything else, 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 DCU | 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 for DCU it has often not been, 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 DCU keeps them online for your account, and DCU does not publish a single hard number. Sign in, open the 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 DCU still shows you.
If you need months that have dropped off the list, contact DCU 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.
DCU does not advertise a QuickBooks Web Connect (.qbo) export, and it no longer supports Direct Connect, the channel most banks use to serve QuickBooks files directly. It has offered CSV and Quicken-format files instead. If your account has no .qbo option, convert the statement PDF here.
Errors 102 and 105 mean Intuit's connector could not read DCU's site, usually after a platform change or during maintenance. Error 103 means your credentials were rejected even though they work on dcu.org. None are caused by anything you did, and none are 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 DCU 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 business-login problem specifically, see why a credit union business account will not connect to QuickBooks. Go straight to the PDF to QBO converter, read how the PDF to QBO converter handles a statement, or learn what a .qbo file actually contains. For the step-by-step, follow the walkthrough for importing bank statements into QuickBooks, and if you are on Desktop, see converting a bank statement for QuickBooks Desktop. 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 |
