Mid-Year Bookkeeping Document Checklist

A mid-year bookkeeping document request usually covers bank and credit card statements, sales and merchant reports, outstanding invoice and vendor support, payroll records, tax confirmations, loan statements, inventory records when relevant, and documents for unusual or unresolved transactions. The exact list should match the client’s systems, reporting period, and bookkeeping engagement. The goal is to collect and review the supporting records needed for the first half of the year and prepare unresolved items before Q3 and year-end work becomes more difficult. Not every client needs every item, and this checklist is not a substitute for monthly bookkeeping.

Jump to checklist

Browse the resources hub

Copy-ready request checklist

Mid-year bookkeeping documents for [Client / Period]

Copy this request for one client and review period, then remove the groups that do not apply. Keep each requested supporting record as a separate item for client response and staff review.

1. Bank, credit, and financing records

Request the records needed to understand cash, borrowing, and payment activity for the review period.

Business bank statements and transaction detail for the requested period.
Business credit card statements and transaction detail.
Loan and line-of-credit statements, including current balances when requested.
Merchant account, processor, and payout records.
Digital wallet records used for business activity.
Details for new or closed accounts during the period.
Support for unusual deposits, withdrawals, transfers, or fees.
Prior-period statements when they are needed to resolve an opening balance or carryover item.

2. Sales and revenue records

Match the request to the client’s actual sales channels and the level of support used in the engagement.

Sales summaries for the requested period.
POS, ecommerce, marketplace, or other sales-platform reports.
Merchant payout reports and settlement detail.
Customer invoices, credits, refunds, and discount support when requested.
Cash sales logs or deposit support when applicable.
Explanations for deposits that are unclear, combined, or do not match the sales records.

3. Accounts receivable support

Use this group to gather the evidence needed for an AR review and to identify items that still need follow-up.

Current outstanding invoice list or AR aging.
Customer statements when they are part of the review.
Support for unapplied payments.
Credit memos, disputes, and deposit records needing allocation.
Explanations for invoices that remain open, disputed, or otherwise need review.
These records support AR review. CollectCue does not write off balances, adjust the ledger, or determine collectibility.

4. Accounts payable and vendor support

Collect vendor-side support only to the extent it is relevant to the agreed bookkeeping review.

Open vendor list or AP aging.
Vendor statements and unpaid bill support.
Vendor credits and purchase-order support when used by the client.
Employee reimbursement support.
Contractor invoices and W-9 records only within the engagement scope.
Support for stale, disputed, duplicate, or unclear vendor items.
Accounting corrections and vendor-master changes are outside CollectCue’s request workflow.

5. Payroll and contractor records

Ask for payroll evidence that fits the client’s provider, pay cycle, and bookkeeping scope.

Payroll register or period summary.
Payroll-provider reports for the requested period.
Time, hours, or payroll-input support when it is part of the review.
Provider filing confirmations when requested.
Payroll payment confirmations when requested.
Contractor records, bonuses, reimbursements, and correction support when applicable.

6. Sales tax and other tax support

Request confirmations and source reports without making tax determinations in the collection workflow.

Sales-tax reporting from the client’s system.
Filed-return, client, or tax-professional confirmations when requested.
Tax payment confirmations.
Marketplace tax documents when relevant.
Exemption or resale documentation when it is in scope for the engagement.
Prior correspondence about unresolved tax support.
Quarterly estimate confirmation only when requested.
CollectCue does not determine nexus, filing frequency, taxable treatment, liability, or filing obligations.

7. Inventory and fixed-asset support

Use this section only for clients whose workflow includes inventory, equipment, leases, or financed assets.

Inventory counts and adjustment support.
Equipment purchase records and invoices.
Disposal, sale, lease, and financing records.
Support that distinguishes repairs from improvements when the engagement requests it.
Records for new assets placed into service during the period.
CollectCue does not determine inventory value, depreciation, capitalization, or cost of goods sold.

8. Unusual and unresolved transactions

Keep exceptions visible so they can be resolved or intentionally carried forward instead of disappearing into the next period.

Missing receipts or invoices.
Unusual deposits, withdrawals, and transfers.
Mixed business and personal activity.
Possible duplicate charges or payments.
Refunds, loan activity, and owner contributions or withdrawals when evidence is requested.
Items posted in the wrong period.
Unreadable, incomplete, or wrong-period files.
Short explanations for transactions that need context before review can continue.

How the checklist changes around mid-year

The checklist remains a document-collection tool. Adjust the period, supporting records, and unresolved-item handoff without changing the underlying bookkeeping scope.

Q2 supporting records

For bookkeeping teams, Q2 close normally means reviewing supporting records through June 30, not preparing visa documents or public-company reporting materials.

•June bank and credit card statements.
•Q2 merchant and sales reports.
•Payroll quarter-end support.
•Quarterly tax confirmation when requested.
•Open AR and AP support.
•Loan and inventory records when relevant.
•April through June unresolved items.

July bookkeeping documents

This is a copyable variation for July bookkeeping documents, not a separate route or a fixed due-date rule.

•June or July statements according to the reporting cycle.
•Credit card and merchant payout reports.
•Sales reports and AR support.
•Vendor invoices and AP support.
•Payroll and tax confirmations when requested.
•Inventory or financing records when they apply.
•Unresolved first-half exceptions.

Q3 preparation

Prepare the next period without making Q2 and Q3 work indistinguishable.

•Carry only unresolved items, their contacts, and next actions.
•Keep Q2 and Q3 records in separate requests or sections.
•Make the current item list and due dates visible.
•Add new accounts, cards, payroll providers, marketplaces, or loans.
•Close completed Q2 items before starting new-period reminders.
•Avoid duplicate reminders for work that is already resolved.

Second-half file organization

Use a simple organization rule that preserves the request context for each source record.

•Keep client and reporting period visible on the request item.
•Retain original source files when available.
•Distinguish a replacement file from a rejected or superseded file.
•Keep unresolved items visible instead of mixing them with completed work.
•Do not mix records from different clients.
•Preserve the link between each file and its request item.
•Keep outputs separate from the source documents that support them.

Documents to request vs reports produced after bookkeeping

Supporting documents are evidence used in the work. Reports are outputs that may help review, but no output replaces the source documents. CollectCue requests and tracks documents; it does not perform reconciliation, tax filing, payroll reconciliation, journal entries, cleanup, or accounting work.

Supporting records a client may provide

Statements, invoices, payout records, payroll reports, confirmations, asset records, and explanations support the bookkeeping review.

Reports normally produced or reviewed after bookkeeping

Profit and loss statements, balance sheets, cash flow reports, trial balances, AR aging, AP aging, reconciliation work, and management reporting are separate outputs or work products.

A financial statement, trial balance, or aging report may be useful during review, but it does not replace the underlying source documents required to support the books.

Common mid-year document request gaps

Use these checks to keep the request focused on missing support and unresolved exceptions rather than rebuilding the full bookkeeping workflow.

Avoid duplicate, unclear, and incomplete requests

Avoid requesting “all financial documents” without naming the statements, reports, or explanations that are needed.
Keep source documents separate from reports produced after bookkeeping.
Keep Q2 support separate from Q3 requests instead of combining both periods in one unclear list.
Do not ask again for files already reviewed or otherwise resolved.
Check for new bank, card, payroll, sales, marketplace, and financing accounts before sending the request.
Do not treat an uploaded file as automatically received or resolved before staff review.
Keep the relationship between a replacement file and its rejected version visible.
Name the requested tax period instead of making a general tax-record request.
Do not close a request while unresolved items remain without an owner and next action.
Avoid separate July, Q2, and Q3 lists that duplicate the same document request.

How to use the mid-year checklist

Use one request per client and review period. Keep each supporting document visible as its own item so client follow-up and staff review remain separate.

1Set the review periodName the client and period, such as January through June, before choosing the records that are relevant to the engagement.
2Select only applicable checklist groupsRemove inventory, financing, payroll, tax, or other groups that do not apply to the client’s systems or agreed scope.
3Create one item for each supporting recordSeparate statements, reports, invoices, confirmations, and explanation requests so each item has a clear status.
4Add the request contextInclude the client, review period, due date, upload link, and a short note when the record needs a particular report or explanation.
5Send the request-specific upload linkLet the client respond to the listed items without needing to use a broader client workspace.
6Follow up on unresolved client-action itemsDo not repeat requests for files that are uploaded, awaiting review, accepted, received elsewhere, or documented as not applicable.
7Review files before resolving themCheck whether the file is readable, belongs to the requested item and period, and contains the support that was requested.
8Keep reports and supporting documents distinctUse reports to inform review, but keep the original statements, invoices, confirmations, and explanations tied to the request item.
9Carry forward only unresolved itemsClose completed work in the prior-period request and move only open exceptions, their owner, and next action into Q3 preparation.

Frequently asked questions

These answers keep document collection, review, bookkeeping work, and professional advice in their separate roles.

What documents should a bookkeeping firm request at mid-year?+

A mid-year request commonly includes bank and credit card statements, sales and merchant reports, AR and AP support, payroll records, tax confirmations when requested, financing documents, and explanations for unresolved transactions. The exact list should match the client’s systems, period, and engagement scope.

Does every client need every item on a mid-year checklist?+

No. Not every client needs every item. A service business without inventory may not need inventory support, and a client without financing may not need loan records. Use the checklist to select the records relevant to that client and review period.

Is a mid-year checklist a substitute for monthly bookkeeping?+

No. A mid-year checklist organizes supporting records and unresolved items for a defined review period. It does not replace recurring monthly bookkeeping, reconciliation work, journal entries, payroll work, tax filing, or accounting judgment.

What does Q2 close mean for a bookkeeping team?+

For bookkeeping teams, Q2 close normally means reviewing supporting records through June 30 and identifying unresolved items that need attention before the next period. The specific review steps depend on the client’s systems and engagement.

What should be carried from Q2 into Q3?+

Carry forward only unresolved records, their current owner, the reason they remain open, and the next action. Keep completed items in the prior-period record so Q3 reminders do not repeat resolved requests.

Should the client upload reports produced after bookkeeping instead of source documents?+

No. Reports such as a profit and loss statement or balance sheet can help with review, but they do not replace the underlying source documents, statements, invoices, payroll reports, and explanations used to support the work.

Do clients need a CollectCue account to respond to a mid-year request?+

No. A client can use a request-specific upload link without creating a CollectCue account. An uploaded file can still wait for staff review before its request item is resolved.

Is this checklist tax, legal, payroll, or accounting advice?+

No. This checklist is a document-collection aid. It does not provide tax, legal, payroll, or accounting advice, and it does not determine filing obligations, tax treatment, payroll conclusions, or ledger changes.

Related resources

Use these resources to turn the checklist into a structured request, follow up on open items, and review uploads.

Turn the mid-year document list into a tracked request

Create one request for the review period, keep each supporting document visible as a separate item, and carry only unresolved records into the next period.

See CollectCue features View pricing