Bank Statement Submission Checklist for Bookkeeping

Before a bank or credit card statement is accepted for bookkeeping review, confirm that it belongs to the correct client and account, covers the requested period, includes the expected pages, opens normally, and is readable without cropped transaction details. If the file is locked, incomplete, blurry, from the wrong period, or attached to the wrong requested item, keep the item unresolved and ask for a corrected replacement. Receiving a file does not mean it has been accepted.

Jump to checklist

Browse the resources hub

Copy-ready submission checklist

Bank statement submission check for [Client / Period]

Use this checklist for one client, account, requested item, and reporting period. It prepares a file for staff review; it does not verify authenticity or make an accounting decision.

1. Correct client and requested item

Confirm the statement belongs to the client and the specific item staff were asked to review.

Correct intended client.
Correct bank or credit card account.
Correct requested item.
Client name or masked account reference is visible when the statement provides it.
The file does not contain records for another client.
The upload does not combine unrelated client records.
If it appears to belong to another client, do not accept it. Follow the firm’s internal privacy or incident process outside CollectCue and request the correct file through the correct client request.

2. Correct reporting period

Use the visible statement dates and request context to check that the file covers the intended review period.

Statement start and end dates match the requested period.
The file is not from the previous or following month.
A quarterly or multi-month statement was requested when that is what was uploaded.
The filename does not conflict with the visible statement period.
A replacement covers the period that was originally requested.
Do not use this intake check to correct an accounting period. Accounting adjustments remain outside CollectCue.

3. Page completeness indicators

Look for practical page-level signals before staff decide whether the file is ready for review.

Sequential page numbers are present when the bank provides them.
A visible “Page X of Y” count is consistent when the statement provides one.
No visible transaction table is cut off.
The first and last statement pages are present.
Opening and ending balances are visible when the statement provides them.
Summary and transaction pages are not obviously separated from one another.
There are no obvious duplicate pages or blank pages caused by a failed scan or export.
Disclosures and intentionally blank pages are handled according to the firm’s requirements.
Banks do not all use the same page layout. Date gaps, visible balances, and page counts are signals, not proof of completeness or authenticity.
CollectCue does not automatically count or verify statement pages.

4. File access

Open the file before changing its review status so staff can see whether the statement is actually accessible.

File opens normally and is not corrupted, empty, or zero bytes.
File is not an unsupported archive.
Reviewer can access every page with the firm’s available software.
The upload is not an inaccessible external link.
Any password prompt follows the firm’s approved password-sharing process.
If the statement cannot be opened, keep the item unresolved and ask for an accessible replacement.
CollectCue does not remove or crack PDF passwords. Do not send passwords through normal email just to complete this check.

5. Readability and visible content

Review the visible source at normal zoom before deciding whether it can support the next staff review step.

Dates, descriptions, and amounts are readable at normal zoom.
Transaction details and page edges are not cropped.
There is no excessive blur, glare, shadow, or low-resolution capture.
Pages have the correct orientation.
Long statements are not represented only by unclear screenshots.
Annotations do not block critical details.

6. File type and size

Current CollectCue public uploads accept PDF, DOCX, XLSX, CSV, JPEG, PNG files up to 25 MB each.

File uses one of the currently supported formats: PDF, DOCX, XLSX, CSV, JPEG, PNG.
Single file is 25 MB or smaller.
If the type or size is not supported, keep the item unresolved and ask for a supported replacement.

7. One upload, one clear purpose

Keep the file tied to a single requested item so staff can make a clear review decision.

The upload is one statement or related statement set for the requested item.
The file does not mix unrelated categories such as receipts, payroll reports, contracts, or statements for several clients.
Separate bank or card accounts are attached to the item the firm requested for each account.
A multi-page statement may remain one file when all pages serve the same requested item.
A mixed document file should be replaced with separate files for the matching request items.
CollectCue does not automatically split or classify mixed-document PDFs.

This is an intake check, not an accounting decision

Use the checklist to prepare a bank or card statement for the next staff review step. It does not replace that review.

What this checklist covers

It checks file intake and review preparation: client and account context, requested period, visible page indicators, file access, readability, upload limits, and the next reupload action.

What it does not decide

It does not verify statement authenticity, reconcile a bank, determine accounting treatment, or replace staff review. Visible balances and page counts are not proof of authenticity or completeness.

Common bank statement submission problems

Use a specific, neutral action so the client knows what to replace without turning a file-review issue into an accounting or authenticity conclusion.

Context and period problems

Wrong client, wrong account, wrong requested item, or wrong reporting period: keep the item unresolved and ask for the correct statement through the matching request item.
Filename and visible period do not match: ask for the period shown in the request, not an accounting correction.
Several accounts combined: ask for the account statement needed for the matching item unless the firm requested the group together.

Page and readability problems

Missing, duplicated, cropped, blank, or cut-off pages: ask for a complete replacement with all transaction pages.
Blurry image, glare, shadow, or unreadable details: ask for a clearer source file or photo with critical details visible.
Do not infer transactions, amounts, or accounting categories from an unclear file.

Access and format problems

Password prompt, corrupted or empty file, inaccessible link, or unsupported file: keep the item unresolved and ask for an accessible replacement in a supported format.
A statement mixed with unrelated documents: ask the client to upload each document to its matching requested item.
CollectCue does not repair files, remove passwords, automatically count pages, or split mixed documents.

What the client upload request looks like

The screenshot uses synthetic client and file data. It does not demonstrate automatic statement validation, OCR, password removal, fraud detection, or reconciliation.

In CollectCue, the client can respond through a request-specific upload link without creating an account. Staff still decide whether the uploaded statement meets the requested item before it is received.

Client document requests Client upload

Client request page showing uploaded, received, not-applicable, and not-submitted document statuses — The client sees each requested document as a separate item. Uploaded files remain connected to the requested item and can still require staff review or replacement.

CollectCue supports the request and review layer

CollectCue can help with

Requesting a document by client and period.
Keeping the file connected to its requested item.
Showing staff review and reupload status.
Keeping a replacement request open until it is reviewed.

CollectCue does not

Verify statement authenticity, detect fraud, or store banking credentials.
Remove passwords, perform OCR, or automatically count pages.
Reconcile accounts, match transactions, import bank feeds, or correct accounting periods.
Determine accounting, tax, or legal treatment.

How to use the bank statement submission checklist

Review one requested statement at a time, document the file-specific issue, and leave any unresolved item open for the correct next action.

1Confirm client and accountMatch the statement to the intended client, bank or card account, and requested item.
2Confirm the periodCheck visible start and end dates against the requested review period.
3Open before changing statusMake sure the file opens and the reviewer can reach all available pages.
4Review visible page indicatorsLook for page sequence, first and last pages, cut-off tables, duplicate pages, and obvious gaps.
5Check readabilityConfirm transactions and critical details can be read at normal zoom.
6Match the requested itemKeep a clear purpose for the upload instead of mixing unrelated accounts or document types.
7Keep unresolved when neededDo not accept a file merely because it arrived if staff cannot reliably review it.
8State the specific replacement needAsk for the correct period, complete pages, accessible file, or separate document as applicable.
9Mark received after staff reviewOnly update the request item after the required statement has been reviewed.

Bank statement submission FAQ

These answers distinguish file readiness from staff review, statement authenticity, and accounting work.

What should be checked before accepting a client bank statement?+

Check the client, account, requested item, reporting period, visible pages, readability, file access, type, size, and whether the statement needs a replacement. An uploaded file can still wait for staff review.

What should I do if the statement is password protected?+

Keep the item unresolved and ask for an accessible copy or follow the firm’s approved password-sharing process. CollectCue does not remove or crack PDF passwords.

How can I tell whether statement pages may be missing?+

Look for visible page numbers, page counts, cut-off tables, duplicate pages, and first and last pages. These are review signals only; banks use different layouts, and page counts or balances do not prove completeness or authenticity.

What if the client uploads the wrong accounting period?+

Keep the request item unresolved and ask for the requested statement period. This intake step does not make accounting-period adjustments.

Should several bank accounts be combined into one file?+

Only if the firm requested that related set as one item. Otherwise, ask the client to use the matching requested item for each account so staff can review them separately.

What file types can clients upload to CollectCue?+

Current public uploads accept PDF, DOCX, XLSX, CSV, JPEG, PNG files up to 25 MB each.

Does an uploaded statement automatically become received?+

No. Uploaded means a file arrived. Staff should review it before marking the requested item received, accepted, or resolved.

Can CollectCue verify whether a bank statement is authentic?+

No. This checklist prepares a file for staff intake review. It does not verify statement authenticity, reconcile a bank account, or determine accounting treatment.

Do clients need a CollectCue account to upload a statement?+

No. A client can upload through a request-specific upload link without creating a CollectCue account.

Related resources

Use the general collection and request resources for what to request, then use this page for one statement’s intake readiness and the reupload checklist for a specific file issue.

Turn the statement checklist into a tracked request

Request the correct statement for the client and period, keep the file connected to its requested item, and review it before marking it received.

See CollectCue features View pricing