You finished the close. The client wants to see the numbers. Do you send a PDF, an Excel, a QBO file, or a dashboard link? The wrong format is the difference between a happy client and a 6-email back-and-forth.
The deliverable format is the #5 pain point for bookkeepers. This page covers the 4 deliverable formats, who wants which, the 4-tab Excel structure, and the recon cutoff tool’s per-period export.
The 4 deliverable formats: PDF (read-only), Excel (editable), QBO file (QBO-only), live dashboard (read-only online). Most clients want Excel. Some clients want the live QBO dashboard. The recon cutoff tool’s per-period export creates the exact file structure clients want: summary tab, transaction list tab, reconciliation tab, and (if applicable) 1099 report tab.
The format choice is about the client’s next step. If the client will edit the numbers, send Excel. If the client will just look at the numbers, send a dashboard link. If the client will send the file to their tax person, send Excel. The recon cutoff tool’s per-period export creates all 4 formats from the same source.
For the broader bookkeeper workflow, see the bank statement workflow for bookkeepers pillar. For month-end close (the step before delivery), see the month-end close guide. For multi-entity (delivering per-entity), see the multi-entity guide.
The 4 Deliverable Formats
The 4 deliverable formats cover every client need. Each format has its own use case. The recon cutoff tool emits all 4 from the same converted source.
What most guides miss about Excel conversion 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.
Format 1: PDF (Read-Only)
PDF is the read-only format. The client can view it but not edit. PDF is the right format when the client wants a snapshot of the books for their records, or when the client will print the report. PDF is also the right format for legal or tax purposes where the file should not be modified.
The recon cutoff tool’s per-period export generates a PDF from the converted Excel. The PDF includes the summary tab, the transaction list tab, and the reconciliation tab.
Format 2: Excel (Editable)
Excel is the editable format. The client can view, edit, and forward. Excel is the right format when the client will do further work on the numbers, or when the client will send the file to their tax person. Excel is the most common deliverable format for bookkeepers.
The recon cutoff tool’s per-period export generates an .xlsx file with 4 tabs: summary, transactions, reconciliation, 1099. The 4-tab structure is what clients expect. The 1099 tab only appears if the client has 1099 contractors.
Format 3: QBO File (QuickBooks-Only)
QBO is the QuickBooks Web Connect format. The file imports into QBO as a native bank feed. QBO is the right format when the client is on QBO and wants the data integrated into their QBO file directly. QBO is less common as a deliverable because most clients don’t run their own QBO file.
The recon cutoff tool’s per-period export generates a .qbo file. The file imports into QBO with payee matching and de-duplication working out of the box.
Format 4: Live Dashboard (Read-Only Online)
Live dashboard is the read-only online format. The client gets a link to a secure web page that shows the books. Live dashboard is the right format when the client wants to see the numbers without opening a file. Live dashboard is becoming more common as bookkeepers move to cloud-based delivery.
The recon cutoff tool doesn’t generate a live dashboard directly. The QBO file or Excel file goes into a third-party dashboard tool (e.g., Fathom, Spotlight Reporting) that generates the live dashboard. The dashboard tool handles the access controls and the visual design.
Who Wants Which Format
The format choice depends on the client’s next step. The 4 client types and their preferred format.
The owner who just wants to see the numbers. Live dashboard. The owner logs in once a month, looks at the summary, and closes the tab. No file management needed.
The owner who sends the file to their tax person. Excel. The tax person opens the file, does the tax prep, and sends it back. Excel is the standard format for tax prep.
The owner who runs their own QBO file. QBO file. The owner imports the QBO file into their QBO, which becomes part of their QBO data. QBO is the right format when the owner is hands-on with the books.
The owner who keeps paper records. PDF. The owner prints the PDF and files it. PDF is the right format when the client wants a permanent snapshot.
From PDF to Excel in one click
Forget retyping line by line. Upload any bank statement, get a spreadsheet you can actually use. Your files are never stored, and you can test the converter with 3 free conversions.
Try it freeThe 4-Tab Excel Structure
The 4-tab Excel structure is what clients expect. Each tab has a specific purpose. The recon cutoff tool’s per-period export creates all 4 tabs.
Tab 1: Summary. The summary tab shows the income, expenses, and net income for the period. The summary also shows the comparison to the prior period (if available) and the year-to-date totals. The summary is the first thing the client looks at.
Tab 2: Transactions. The transaction list tab shows every transaction for the period. The columns are date, description, amount, balance, category, and payee. The transaction list is searchable and sortable. The client uses this tab for the detail work.
Tab 3: Reconciliation. The reconciliation tab shows which transactions matched the bank feed and which didn’t. The recon cutoff tool’s reconciliation worksheet generates this tab. The client uses this tab to verify the books match the bank statement.
Tab 4: 1099 (if applicable). The 1099 tab shows the payee rollup for the year. The 1099 tab only appears if the client has 1099 contractors. The recon cutoff tool’s year-end export generates this tab.
The File Naming Convention
The file naming convention is consistent across deliverables. The 4-part pattern: client name, entity, period, format.
Example: AcmeLLC_LLC1_2024-03.xlsx. The 4 parts are: client name (AcmeLLC), entity (LLC1), period (2024-03), format (xlsx). The recon cutoff tool’s per-period export uses this naming convention automatically.
The Delivery Workflow
The delivery workflow runs in 5 steps. The recon cutoff tool’s per-period export compresses the file generation step from 30 minutes to 2 minutes.
Step 1: Choose the Format
Choose the format based on the client’s preference. The choice is usually Excel (most common) or live dashboard (cloud-first clients). The recon cutoff tool’s per-period export generates both.
Step 2: Generate the File
The recon cutoff tool’s per-period export generates the file. The export takes 2 minutes per client. The 4-tab Excel structure is created automatically.
Step 3: Verify the File
Open the file and verify the numbers match the books. The recon cutoff tool’s verification step takes 1-2 minutes per file.
Step 4: Deliver
Send the file via email, secure portal, or cloud share. Email is the most common. Secure portals (e.g., Liscio, TaxDome) are becoming the standard for bookkeepers serving regulated industries.
Step 5: Archive
Archive the file in the client’s cloud folder. The recon cutoff tool’s archive feature stores the deliverable alongside the original PDF and the converted file. The archive is the audit trail.
The Common Mistakes
3 mistakes bookkeepers make on deliverables.
Sending the wrong format. Sending Excel when the client wants PDF, or vice versa, is the most common complaint. The fix: ask the client what format they want, or default to Excel + PDF.
Sending files with no tab structure. A single-tab Excel with 1000 rows of transactions is unusable. The fix: the 4-tab Excel structure with summary, transactions, reconciliation, and 1099 tabs.
Skipping the verification step. Sending a file with wrong numbers is the most damaging mistake. The fix: always open the file and verify before sending. The recon cutoff tool’s verification step takes 1-2 minutes per file.
For the broader bookkeeper workflow, see the bank statement workflow for bookkeepers pillar. For month-end close, see the month-end close guide . For multi-entity, see the multi-entity guide . For the related bookkeeper client deliverable: bank statement format and audit prep page, see the linked article. 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.
More on the broader cluster
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.
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.
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 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.
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.
Turn PDF Bank Statements Into Workable Spreadsheets
Your bank statement is a mess of numbers, but your books shouldn't be. Use our converter to get Excel, CSV, or QBO files — ready for QuickBooks.
Try It Free Now
