Bookkeeper Workflow for Monthly Bank Imports in QuickBooks
No account needed for your first conversions. We never store your bank login.
A clean monthly bank import is the difference between a two-hour close and a two-day mess. The bookkeepers who close fast do not treat each client as a fresh puzzle; they run the same repeatable sequence every month: pull the statements, export the data, convert what needs converting, import once, reconcile against the statement total, then review. This is that workflow, written so you can hand it to a junior or follow it yourself across a dozen clients without missing a step.
The goal is a process that does not depend on any single bank feed staying alive, because feeds break and Intuit is retiring Direct Connect on October 30, 2026. A file-based import you control is the backbone; the feed is a shortcut you use only when it happens to work.
What is a good monthly bank import workflow for bookkeepers?
A good workflow is a fixed sequence you repeat for every client: collect each account's statement, export the transactions as a CSV or QBO, convert any CSV-only accounts to QBO, import one file per account, reconcile to the statement closing balance, then review uncategorized and duplicate transactions. Standardizing the order means every client closes the same way, so a missed step is obvious and a new team member can follow it.
How do I import a full month of bank transactions at once?
Export the entire statement period from the bank as a single CSV or QBO file, then import that one file rather than importing week by week. In QuickBooks Online use Transactions, Bank transactions, Upload from file. QuickBooks Desktop imports only QBO files through File, Utilities, Import, Web Connect Files. Importing the whole month in one file makes reconciliation a single check against the statement instead of a running tally.
Step by step: the monthly close import
Work each client account in the same order every month:
| Step | Action | Why it matters |
|---|---|---|
| 1 | Gather every account's statement for the period | Fixes the target closing balance up front |
| 2 | Export each account as CSV or QBO | One file per account keeps reconciliation clean |
| 3 | Convert CSV-only accounts to QBO | QuickBooks Desktop will not import raw CSV |
| 4 | Import one file per account | Avoids mixing accounts in one register |
| 5 | Reconcile to the statement closing balance | Confirms nothing is missing or duplicated |
| 6 | Review uncategorized and duplicate lines | Catches feed gaps and double imports |
How do I handle a client whose bank only gives a CSV?
Convert the CSV to a QBO file before importing. Many banks, and QuickBooks Desktop in particular, will not take a raw CSV into a register, so a CSV-only client stalls the whole close until the file is converted. Run each CSV through a CSV to QBO converter to get a reconciled QBO, then import it the same way you import every other account.
How do I avoid duplicate transactions during import?
Import each period once, from one file, and never re-import an overlapping date range. Duplicates usually come from importing a file that overlaps a range the bank feed already pulled, or from importing the same statement twice after a failed close. Reconcile immediately after each import so a doubled balance shows up right away, and if you do see duplicates, remove them before you categorize rather than after.
How long should a monthly bank import take per client?
Once the workflow is standardized, a straightforward client with two or three accounts takes about 15 to 30 minutes to import and reconcile. Clients with many accounts, high transaction volume, or CSV-only banks take longer, mostly in the review step. The time sink is almost never the import itself; it is chasing missing transactions from a broken feed, which is exactly what a full file-based import eliminates.
Should I still use the bank feed in this workflow?
Use the feed as a convenience, not the backbone. When a client's feed is reliable, let it pre-fill the register and treat your file import as a verification. When the feed is flaky or the account is on a connection Intuit is retiring, skip it and import the file directly. Building the process around files rather than feeds means a dead connection never stops a close.
How do I keep the workflow consistent across many clients?
Document the six steps as a checklist and store each client's export settings, account list, and closing-balance targets in one place. Consistency is what lets you scale from three clients to thirty without quality slipping. When every client follows the same import and reconcile sequence, you can delegate the mechanical parts and reserve your attention for the judgment calls in the review step.
What if a client has both feed accounts and CSV-only accounts?
Split the client's accounts into two lists and treat each list consistently. For accounts with a reliable feed, let it pre-fill and verify against the statement. For CSV-only accounts, convert each export to a QBO and import it. Keeping the two groups explicit in your checklist stops the common error of assuming an account is feeding when it is actually a manual one, which is how a whole account gets missed at close.
How do I onboard a new client into this workflow?
On the first month, spend the extra time to record each account's export path, file format, and typical transaction volume, and confirm the opening balances tie to a known statement. That one-time setup is what makes every following month a 20-minute routine. Get the account list and export settings right up front and you never have to rediscover how a client's bank exports its data.
What tools do I need for this workflow?
You need access to each client's bank to export statements, QuickBooks Online or Desktop, and a reliable CSV to QBO converter for the accounts that only export CSV. That is genuinely it. The workflow deliberately avoids depending on fragile automatic feeds or extra connected apps that store client banking credentials, because every added connection is one more thing that can break the day before a deadline.
How do I keep a clean audit trail with manual imports?
Save each source export and each converted QBO file in a dated client folder, named by account and period, before you import. That archive means you can always prove where a transaction came from and re-run an import if a close has to be reopened. Auto feeds leave no such trail; the transactions just appear. A file-based workflow gives you a paper trail for free, which matters the moment a client or an auditor questions a figure.
How do I handle a client who is months behind?
For a back-dated catch-up, export the entire outstanding range from each account as one file and import it in a single pass rather than reconstructing month by month from a feed that only reaches back so far. Convert any CSV-only accounts to QBO first so the whole history lands cleanly, then reconcile each completed month against its statement in order. One large, complete import beats a dozen partial feed pulls when you are rebuilding a neglected book.
For the mechanics of the conversion step, see how to convert CSV to QBO and the CSV to QBO converter built for accountants and bookkeepers. If a client's feed has gone dark, the Direct Connect alternative workflow keeps their imports running. When onboarding a messy new client, pair this with the QuickBooks cleanup checklist. If the source arrives as scanned statements, you can convert those statements to a clean data file before you start.