Check a bank statement's account, period and pages before review

Check the evidence before checking the transactions

Finding that at review means reopening work you thought was finished. A short arrival check gives the reviewer a usable starting point.

A complete client folder still leaves someone turning supplier invoices into spreadsheet rows. That is the step ParseMill handles: upload invoice PDFs, review extracted details and line items beside the source, then download Excel. Keep document requests and engagement tracking in your existing process.

For context, Intuit's reconciliation instructions require selecting the account and using the statement's ending balance and ending date. A wrong document therefore creates a problem before matching begins. Our checks below are an original administrative workflow, usable with any approved document store.

Use six checks on each statement

1. Client and entity: compare the account holder shown in the file with the entity in the request. If the names differ, ask the owner to confirm the relationship before assigning it.
2. Account: use a masked reference already known to your team, such as checking ending 4821. Two accounts at the same bank remain separate requests. Do not put full account numbers in a general work tracker.
3. Coverage: record the opening and ending dates printed on the statement. A credit-card cycle may cross calendar months. Preserve those actual dates and record the bookkeeping month separately.
4. Pages: check the page sequence, any stated total page count, and legibility. A PDF with pages one and three is incomplete even when both open successfully.
5. Continuity: compare coverage with the last accepted statement for that account. Flag uncovered dates or overlapping coverage for review. Do not assume an overlap is a duplicate transaction.
6. Handoff: link the exact file version, write the check date, and name the reviewer. Use accepted for intake, clarification needed, or replacement requested as separate states.

If the file has no printed coverage or page count, record that uncertainty. Ask for the bank-generated statement when that is what the work requires. A transaction screenshot or downloadable activity list may be useful supporting evidence, but it should not silently replace the requested statement.

Worked example: three uploads, one outstanding statement

Synthetic example: North Avenue Studio is a fictional client. Its team expects two September statements. The account references, dates and filenames below are invented.

There are three uploaded files but only one accepted account-period requirement. The savings request remains open. The incomplete repeat needs an internal housekeeping decision, not another client reminder for checking. Counting files would conceal both distinctions. Track the internal duplicate-review task separately from the one outstanding client document request.

Keep statement files and imported transaction lines distinct

A feed showing transactions does not tell the intake coordinator which original file has been accepted. Xero's statement-line documentation distinguishes lines received through a bank feed, imported from a file, and created by manual reconciliation. That source information helps a reviewer investigate how records arrived; it does not replace this document checklist.

In your register, keep separate fields for statement-file location and transaction-import status. If two exports cover the same dates, ask the person responsible for imports to examine the overlap before another import. Never delete transactions or change an opening balance merely to clear an intake warning. Capture the discrepancy and route it to the person authorized to decide.

Send a precise replacement request and verify the result

A useful request names the missing requirement without repeating confidential details: Please upload the complete September 1–30 statement for the savings account ending 1932 through our usual secure portal. The file received covers August. Include all pages, including any page with the closing balance. Adapt the wording to the actual issue; do not ask for a password or banking sign-in.

When the replacement arrives, repeat the failed checks and point the register to the accepted version. Keep the previous upload according to your firm's existing document policy and label it clearly so it cannot become the working copy by mistake. Review a small completed cycle for wrong-period uploads, incomplete pages and duplicate requests. Count each issue separately, and record how many statements you checked before interpreting the rate.

The monthly document register shows how to track one row per requirement. Use the workflow toolkit guide to map your own intake checks, or bring a recurring unresolved step to a ParseMill workflow audit. The checklist works without a ParseMill account.

Questions about this workflow