Month-End Close Workflow for Bookkeepers: The 7-Step Process

It’s the 5th of the month. You have 12 client closes to do. The bank feeds are 60% reliable. The rest is PDF statements, and the client wants the books by the 10th.

The month-end close is the 7-step process bookkeepers run every month. This page covers the 7 steps, where the time goes, and how the recon cutoff tool’s period-end split compresses the close from 8 hours to 3 hours.

Most bookkeepers find that collection and conversion eat a disproportionate share of month-end time, leaving the actual accounting work compressed. The recon cutoff tool’s period-end split plus the batch upload handle 80% of the time sink. The remaining 20% is the review and adjust step, which is where the actual accounting happens.

The 7 steps: collect, convert, reconcile, review, adjust, deliver, archive. The first 2 steps (collect and convert) take 60% of the time. Steps 3-5 (reconcile, review, adjust) take 30%. Steps 6-7 (deliver, archive) take 10%. The 60/30/10 split is consistent across bookkeepers regardless of client count.

For the broader bookkeeper workflow, see the bank statement workflow for bookkeepers pillar. For client onboarding (the month before close), see the client onboarding guide. For multi-entity, see the multi-entity guide.

The 7-Step Process

The 7 steps run in order each month. The first 2 steps (collect and convert) eat about 60% of the time. Steps 3-5 are the actual accounting. Steps 6-7 are the wrap-up.

What most guides miss about this workflow is that the quality depends on the mechanism, not on the tool. Two tools that look different on the surface often run the same 4-step process underneath: read, find, parse, verify. The difference is in how well each step handles edge cases (merged cells, missing balances, non-standard date formats, scanned vs digital input).

Choosing between tools based on UI alone misses the actual quality lever.

Step 1: Collect

Collection is asking the client to send the bank statement. The format request is PDF (the bank’s official statement) plus, when available, OFX or QFX (the raw data feed). The request goes out on the 1st of the month for most clients.

The recon cutoff tool’s archive feature tracks which statements you’ve received and which are still pending. The collection step is done when every account for every client has a statement.

Step 2: Convert

Conversion is turning the PDF (or OFX or QFX) into a structured file. For QBO, the format is .qbo or .csv. For Xero, the format is .qbo, .csv, or .ofx. The recon cutoff tool’s batch upload handles 50 statements in one go. The conversion step takes about 30 seconds per statement once the workflow is set up.

The per-period split is the key. Pre-cutoff transactions go to the current period. Post-cutoff transactions are marked OUTSTANDING. This eliminates the manual date-filtering that used to take 5-10 minutes per statement.

Step 3: Reconcile

Reconciliation is matching each converted transaction against the books. The match is automatic for the 80% of transactions that are clean. The 20% that don’t match need a manual review.

The recon cutoff tool’s archive feature stores the converted file, the source PDF, and the reconciliation worksheet. The reconciliation worksheet shows which transactions matched and which didn’t, so the manual review is targeted at the 20%.

Step 4: Review

Review is the judgment step. The bookkeeper looks at the 20% of unmatched transactions and decides: is this a duplicate? A transfer? A categorization error? A new vendor? Each decision takes 30-60 seconds. The recon cutoff tool’s reconciliation worksheet speeds this up by showing the source PDF beside the converted transaction.

Step 5: Adjust

Adjustment is the journal entry step. For each category error, transfer, or new vendor, the bookkeeper records a journal entry in QBO or Xero. The recon cutoff tool’s per-period split means adjustments are recorded in the right period, with post-cutoff transactions marked OUTSTANDING.

Step 6: Deliver

Delivery is sending the result to the client, the tax software, or both. The format depends on the recipient. Most clients want Excel or a live dashboard link. The recon cutoff tool’s per-period export creates the file structure clients want. For the full deliverable workflow, see the deliverable format guide.

Step 7: Archive

Archiving is storing the original PDF, the converted file, the reconciliation worksheet, and the client deliverable. The recon cutoff tool’s archive feature handles all four in a consistent structure. The archive is what protects the bookkeeper if the client gets audited 2-3 years later.

Where the Time Goes

The 60/30/10 time split is consistent across bookkeepers regardless of client count. The fix is to compress the 60% (collection and conversion) using the recon cutoff tool’s batch features.

Collection and Conversion: 60% of Month-End

Collection takes about 20% of month-end. The bookkeeper sends the request on the 1st, follows up on the 3rd, and most clients respond by the 5th. The slow clients add 1-2 days to the close. The fix: send the request earlier (on the last day of the month) and use a templated email.

Conversion takes about 40% of month-end. Without the recon cutoff tool, conversion is a manual process: download each PDF, open the converter, upload, wait, download the result, import to QBO or Xero. Each statement takes 5-10 minutes. For 12 clients with 3 accounts each, that’s 6-12 hours.

The recon cutoff tool’s batch upload compresses the conversion to 30 seconds per statement. The same 36 statements take 18 minutes instead of 6-12 hours. The per-period split is automatic, eliminating the manual date-filtering step.

Reconcile, Review, Adjust, Deliver, Archive: 40% of Month-End

Reconciliation, review, and adjustment take a meaningful share of month-end, though the exact split varies by bookkeeper. This is the actual accounting work, and it doesn’t compress the same way. The recon cutoff tool’s reconciliation worksheet helps by showing which transactions need manual review, but the review itself is judgment work.

Delivery and archiving take about 10% of month-end. The recon cutoff tool’s per-period export creates the client deliverable. The archive feature stores everything in a consistent structure.

Compressing the Close

The recon cutoff tool’s period-end split plus the batch upload compress the close from 8 hours to 3 hours for a typical bookkeeper with 12 clients. The compression comes from 3 places: faster conversion, automatic per-period split, and reconciliation worksheet.

Faster Conversion

The recon cutoff tool’s batch upload handles 50 statements in one go. The conversion step takes 30 seconds per statement. For 12 clients with 3 accounts each (36 statements), the conversion takes 18 minutes. The same 36 statements without the tool would take 6-12 hours of manual work.

Automatic Per-Period Split

The per-period split is automatic. Pre-cutoff transactions go to the current period. Post-cutoff transactions are marked OUTSTANDING. The bookkeeper doesn’t have to manually filter by date, which used to take 5-10 minutes per statement.

Reconciliation Worksheet

The reconciliation worksheet shows which transactions matched and which didn’t. The manual review is targeted at the 20% that don’t match, not the full transaction list. The review step goes from 30 minutes per client to 10 minutes per client.

The Month-End Calendar

The month-end calendar sets the close dates for each client. The 3 common patterns.

Calendar-month close on the 5th. Most common. The books close on the last day of the month. The bank statement cycle varies. The recon cutoff tool’s per-period split handles the gap.

Calendar-month close on the 10th. For bookkeepers who want a buffer. The extra 5 days allow for late client statements.

Bank-cycle close. Rare. The books close on the same day as the bank statement. The recon cutoff tool’s per-period split isn’t needed because the bank cycle is the close date.

The Common Mistakes

3 mistakes bookkeepers make during month-end.

Waiting until the 5th to start collection. Send the request on the 1st or even the last day of the previous month. The early request catches the slow clients before the close date.

Manually filtering by date. Use the recon cutoff tool’s per-period split. The manual filtering is the single biggest time sink, and the tool eliminates it.

Skipping the archive step. The archive is what protects you if the client gets audited 2-3 years later. Skipping it is the most common cause of audit failure.

The 12-Client Close

A typical bookkeeper has 12 SMB clients. The 12-client close takes 3 hours with the recon cutoff tool and 8 hours without. The 5-hour difference is the conversion step (6 hours saved) plus the per-period split (1 hour saved).

The 12-client close happens once a month. The 5-hour savings, multiplied by 12 months, is 60 hours per year. That’s a full work week of time saved, every year, for one bookkeeper.

For the broader bookkeeper workflow, see the bank statement workflow for bookkeepers pillar. For client onboarding, see the client onboarding guide . For multi-entity, see the multi-entity guide . The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.

The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.

Related:

This topic is part of the bookkeeper-resource cluster on this site. The consolidated hub, covering onboarding, monthly close, year-end, client deliverables, and multi-entity workflows, lives in the complete bookkeeper workflow guide.

For related reading on the broader clusters, the
covers credit-card-side mechanics, and the
covers bank-account-side mechanics. The expanded bank statement anatomy is a useful primer.

Decision framework for this topic

For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.

Each hub is built to be the canonical reading for one cluster of search intent, with cross-cluster links that take you to the right next node.

When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal. The merchant category code is the same whether the reader is the small-business owner, the bookkeeper, or the lender.

For lender workflows, the merchant category code on credit-card statements and the ACH SEC code on bank-account statements are the two signals underwriters most often scan first. Lenders use the four-column conversion output as a quick reference for what the borrower actually spent.

Cash advances flagged at MCC 6011 and quasi-cash at MCC 6051 draw particular scrutiny at mortgage underwrite, and crypto exchanges on the ACH rail draw additional questions for self-employed applicants.

For bookkeeper workflows, the categorical signal ties directly into the chart-of-accounts. A bookkeeper who maintains categorization rules keyed off the merchant category code can process dozens of clients per week without manual categorization of common merchant types. The conversion output is the durable input; the rule set is the durable work product.

Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored. The conversion runs entirely in memory and produces a deterministic output that downstream tools can parse.

The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes. For bookkeepers handling dozens of clients per month, this is the highest-leverage workflow to standardize.

Related reading and broader clusters

For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.

Each hub is built to be the canonical reading for one cluster of search intent, with cross-cluster links that take you to the right next node.

When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal. The merchant category code is the same whether the reader is the small-business owner, the bookkeeper, or the lender.

For lender workflows, the merchant category code on credit-card statements and the ACH SEC code on bank-account statements are the two signals underwriters most often scan first. Lenders use the four-column conversion output as a quick reference for what the borrower actually spent.

Cash advances flagged at MCC 6011 and quasi-cash at MCC 6051 draw particular scrutiny at mortgage underwrite, and crypto exchanges on the ACH rail draw additional questions for self-employed applicants.

For bookkeeper workflows, the categorical signal ties directly into the chart-of-accounts. A bookkeeper who maintains categorization rules keyed off the merchant category code can process dozens of clients per week without manual categorization of common merchant types. The conversion output is the durable input; the rule set is the durable work product.

Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored. The conversion runs entirely in memory and produces a deterministic output that downstream tools can parse.

The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes. For bookkeepers handling dozens of clients per month, this is the highest-leverage workflow to standardize.