Category: Use-case

  • What to Do When a Client Emails You 14 PDF Bank Statements

    Every bookkeeper knows the email: “Here you go!” with fourteen PDF bank statements attached and zero context. When you have to process multiple PDF bank statements at once, the instinct is to open the first one and start typing — which is exactly how a half-day intake turns into a three-day slog. Here’s the intake workflow I use to turn a pile of attachments into a clean import without keying a single transaction by hand.

    First, triage the attachments

    Before you touch the accounting file, do a two-minute intake check:

    • Sort by account. Fourteen PDFs are usually two or three accounts across several months, not fourteen separate accounts. Group them.
    • Sort by date and check for gaps. Put each account’s statements in period order. A missing month between two statements is the single most common reason a catch-up won’t reconcile, so flag it now and request the gap before you do any work.
    • Confirm they’re statements, not check images. Occasionally a client sends deposit slips or screenshots. You need the actual statement periods with running balances.

    This triage is the entire reason catch-up intake goes smoothly or sideways. Five minutes here saves hours later.

    Don’t retype — batch convert

    Once the statements are sorted and gap-free, the bottleneck is data entry plus categorization. I batch convert bank statements instead of keying them: I run all the PDFs through Bookmonstic, which reads every transaction across every statement, categorizes them with AI, and exports a single QuickBooks “batch transactions import file” or a Xero “precoded import file.” Fourteen statements become one import file instead of fourteen typing sessions, and because it works straight from the PDF there’s no bank feed or API to set up. (Disclosure: I’m a CPA and Bookmonstic is my own tool.)

    If you want the mechanics of getting that file into QuickBooks, this walkthrough on converting a PDF bank statement to QuickBooks Online covers it step by step.

    Review exceptions, then import multiple statements at once

    With the import file built, you’re not reviewing fourteen statements — you’re reviewing the handful of transactions the AI flagged or that need a judgment call. Sort by category, scan for outliers, fix the few that need it. Then bring the multiple statements into QuickBooks as one import and reconcile each period against its ending balance, in date order. Tying out month by month keeps any discrepancy isolated to a single statement instead of hidden in a year of activity.

    Reply to the client like a pro

    Once you’ve triaged, send one reply: confirm which accounts and date ranges you received, list any missing periods, and give a realistic turnaround. That single message sets expectations and prevents the client from drip-feeding you more attachments mid-engagement.

    Frequently asked questions

    How do I process multiple PDF bank statements without entering each one by hand? Batch convert them. Instead of keying transactions statement by statement, run all the PDFs through a tool that reads and categorizes them and outputs one import file. You go from manual data entry to reviewing exceptions.

    Can I import multiple statements into QuickBooks at once? Yes. If the statements are converted into a single batch transactions import file, you bring them in as one import rather than one statement at a time, then reconcile each period separately.

    What’s the first thing to check during catch-up intake? Gaps between statement periods. A missing month is the most common cause of an unreconcilable cleanup, so identify and request it before doing any work.

    What if the statements are PDFs and not CSV or Excel? PDFs are fine. A PDF bank statement is a complete record and can be converted into an import file just like a CSV, so you’re never blocked by the format the client sent.


    Written by the founder of Bookmonstic, a practicing CPA. Bookmonstic turns PDF/CSV/Excel bank statements into AI-categorized, import-ready files for QuickBooks and Xero — no rules to build, no API. Try it free →

  • The CPA’s Catch-Up Bookkeeping Workflow (Free Checklist)

    A repeatable catch-up bookkeeping workflow is the difference between a profitable cleanup engagement and a black hole that eats your margin. After enough of these, I stopped improvising and built a fixed sequence: scope, gather, import, reconcile, close. Below is the bookkeeping checklist I actually use, in order, so you can scope catch-up engagements accurately and finish them without the late-night surprises that make cleanup work so dreaded.

    Step 1: Scope before you quote

    Most cleanup engagements lose money because they were priced before anyone knew the size of the mess. Before you commit to a fee, answer four questions:

    • How many months of backlog? Count the unrecorded statement periods, not the calendar months the client mentions.
    • How many accounts? Each bank and credit-card account is a separate import and a separate reconciliation.
    • Are the accounts open and connected? Closed or non-connected accounts mean no bank feed — you’ll be working from PDF/CSV/Excel statements.
    • What’s the current state of the file? A brand-new file is easier than one with months of miscoded transactions you have to unwind.

    Write the answers down. That’s your scope and your price.

    Step 2: Gather the source documents

    Request every bank and credit-card statement for the full date range, plus any loan and payroll records. Confirm there are no gaps between statement periods. A missing month is the most common cause of a cleanup that won’t reconcile, and it’s far cheaper to catch it now.

    Step 3: Import instead of keying

    This is the step that breaks the cleanup-workflow bottleneck. Rather than entering months of transactions by hand, I convert the PDF/CSV/Excel statements into an import file. I run them through Bookmonstic, which reads and categorizes every transaction with AI and exports a QuickBooks “batch transactions import file” or a Xero “precoded import file” — no rules to build and no bank feed required, which matters because cleanup accounts are often closed or non-connected. (Disclosure: I’m a CPA and Bookmonstic is my own tool.) For the QuickBooks side specifically, this guide on importing bank statements into QuickBooks walks through the import options.

    Step 4: Reconcile period by period

    Reconcile each statement period in date order against its ending balance. Don’t import everything and reconcile once at the end — that lets small errors compound. Tying out each month keeps every discrepancy contained to a single period.

    Step 5: Review, adjust, and close

    Once the periods reconcile, review the categorizations for judgment calls (owner draws vs. distributions, capitalizable vs. expense), book any adjusting entries, lock the period, and document what you did. That closing memo is your protection if the client questions the work later.

    The one-page checklist

    1. Scope: months, accounts, connected status, file condition 2. Gather: all statements, no gaps, supporting docs 3. Import: statements to batch/precoded import file, review exceptions 4. Reconcile: period by period to ending balance 5. Close: adjusting entries, lock periods, document

    Frequently asked questions

    How do I price a catch-up bookkeeping engagement? Price after scoping, never before. Once you know the number of months, number of accounts, and the file’s condition, you can estimate hours honestly. Quoting before scoping is the number-one cause of unprofitable cleanups.

    What slows down a cleanup workflow the most? Manual data entry and manual coding. Converting statements into a batch transactions import file or precoded import file removes that bottleneck so your time goes to judgment calls and reconciliation instead of typing.

    Should I reconcile at the end or as I go? As you go. Reconciling each statement period in order keeps errors from compounding and makes any discrepancy easy to isolate.

    What if the client only has PDFs, not CSVs? That’s fine. A PDF bank statement is a complete record and can be converted into an import file just like a CSV, so you’re never blocked by the file format the client happens to have.


    Written by the founder of Bookmonstic, a practicing CPA. Bookmonstic turns PDF/CSV/Excel bank statements into AI-categorized, import-ready files for QuickBooks and Xero — no rules to build, no API. Try it free →

  • Catch-Up Bookkeeping: Clearing Months of Backlog from PDF Statements

    Doing catch-up bookkeeping from PDF statements is the most common cleanup job I take on, and it is almost always the same situation: a client has six, nine, or twelve months of unrecorded activity, the bank feed only reaches back 90 days, and the only complete record is a stack of PDF bank and credit-card statements. The fastest way to clear that backlog is to stop treating each statement as a manual data-entry task and start treating the whole pile as one import. Here is the workflow I use to clear bookkeeping backlog without burning a weekend on line-by-line coding.

    Why the bank feed won’t save you

    The bank feed is great for ongoing work, but it is the wrong tool for catch-up. Most banks expose only 60-90 days of history through the feed, and if the account is closed or was never connected, you get nothing. That leaves you with the PDF (or CSV/Excel) bank statement as your source of truth. The temptation is to key transactions in by hand or rebuild them from memory, but for months of activity that is slow and error-prone. You want to import months of statements as data, not retype them.

    The workflow: statements in, import file out

    When I do catch-up bookkeeping with batch import, the steps are consistent:

    1. Collect every statement. Gather the full date range — bank and credit card — as PDF, CSV, or Excel. Confirm there are no gaps between statement periods, because a missing month creates an unreconcilable balance later. 2. Convert and categorize in one pass. I run the PDF/CSV/Excel statements through Bookmonstic, which reads every transaction and assigns a category using AI, then exports a QuickBooks “batch transactions import file” or a Xero “precoded import file.” This is where the time savings live — the data-entry and the coding happen together instead of as two separate manual jobs. (Disclosure: I’m a CPA and Bookmonstic is my own tool.) 3. Review the exceptions, not everything. Sort by category and scan for the handful of transactions the AI flagged or that look off. You are reviewing judgment calls, not entering data. 4. Import and reconcile by statement period. Bring the file in, then reconcile each month against the statement’s ending balance.

    For the import mechanics specifically, this walkthrough on importing bank statements into QuickBooks covers the three methods and which one fits catch-up work.

    Reconcile as you go, not at the end

    The single biggest catch-up mistake is importing everything and reconciling once at the finish. Reconcile each statement period in order. If month three is off by $47, you fix it before month four compounds the problem. Because your import file came straight from the statements, the ending balance should tie out cleanly — and when it doesn’t, the discrepancy is contained to one month instead of buried in a year of activity.

    Frequently asked questions

    How far back can I do catch-up bookkeeping from PDF statements? As far back as you have statements. Unlike the bank feed’s 90-day window, a PDF or CSV statement is a complete record. If the client can pull or request every statement period, you can rebuild the full history.

    Do I have to enter each transaction by hand? No. The reason catch-up takes so long is manual data entry plus manual coding. If you convert the statements into a QuickBooks batch transactions import file or a Xero precoded import file, both steps happen at once and you only review exceptions.

    What if a few months are missing? Stop and request them before importing. A gap in statement periods will leave a balance you can’t reconcile, and it’s far cheaper to wait for the missing PDF than to chase a phantom discrepancy later.

    Does this work for credit-card backlogs too? Yes. Credit-card statements are usually messier than bank statements — more merchants, more categories — which makes batch categorization even more valuable for clearing the backlog.


    Written by the founder of Bookmonstic, a practicing CPA. Bookmonstic turns PDF/CSV/Excel bank statements into AI-categorized, import-ready files for QuickBooks and Xero — no rules to build, no API. Try it free →