CollectCue

Bookkeeping File Rejection and Reupload Checklist

A bookkeeping file should be sent back for reupload when staff cannot reliably review it for the requested client, period, or document item. Common reasons include an unreadable image, incomplete pages, an inaccessible or corrupted file, the wrong reporting period, the wrong client, mixed document types, a duplicate upload, or conflicting versions. A useful rejection note should name the exact issue and tell the client what replacement is needed. Avoid vague messages such as “wrong file” or “please resend.” Keep the requested item unresolved until the replacement has been reviewed.

Jump to checklist
Browse the resources hub

Copy-ready review checklist

Bookkeeping file review result

Copy the review result for one submitted file, then select the most specific category and replacement requirement. This is a review note, not accounting or legal advice.

Bookkeeping file review result

Copy the review context and replacement request, then use the most specific reason category below.

  • Client: [Client]
  • Request period: [Request Period]
  • Requested item: [Requested Item]
  • File name: [File Name]
  • Review status: Needs reupload
  • Reason category: [Wrong client / Wrong period / Cannot open / Incomplete / Unreadable / Unsupported type / Mixed documents / Duplicate / Conflicting version / Wrong document]
  • Specific issue: [Describe exactly what prevented review.]
  • Replacement needed: [Describe the exact document, period, pages, or format required.]
  • Suggested client message: We could not complete the review of this file because [Specific Issue]. Please upload [Replacement Needed] through the matching requested item.
  • Reviewer: [Reviewer]
  • Review date: [Review Date]
  • Internal notes: [Internal Notes]

1. Wrong client or request context

Reject the file when its client, account, request, or requested document context does not match what staff need to review.

  • File belongs to another client.
  • File was uploaded to the wrong client request.
  • File was attached to the wrong requested item.
  • Client, account, or document name does not match the request.
  • One file contains information for several clients.
  • Client-facing replacement reason: This file does not match the client or requested item. Please upload the correct document through the matching request item.
  • If another client’s information appears, stop normal review and follow the firm’s internal privacy or incident process outside CollectCue.

2. Wrong reporting period

State the requested period clearly rather than trying to correct the accounting records from a file-review workflow.

  • Previous month, following month, wrong quarter, or wrong fiscal year.
  • Partial period when a full period was requested.
  • Filename indicates one period but the visible document shows another.
  • Replacement file still covers the wrong dates.
  • Client-facing replacement reason: This file covers the wrong reporting period. Please upload the document for [Requested Period].
  • Do not use this checklist to change a ledger, adjust journal entries, or restate financial reports.

3. File cannot be accessed

A file that cannot be opened is not ready for review, even if it was successfully uploaded.

  • Corrupted file, empty file, incomplete upload, or file that does not open.
  • Unsupported archive, unavailable external link, or file requiring unavailable software.
  • Password prompt prevents review.
  • Client-facing replacement reason: We could not open or review this file. Please upload a new accessible copy in a supported file format.
  • CollectCue does not repair corrupted files or crack passwords. Staff should not alter the original file and present it as the client’s replacement.

4. Unreadable or incomplete

Use a visible, file-specific issue rather than asking staff to infer missing details from a poor source.

  • Blurry image, glare, shadow, cropped edges, cut-off text, low-resolution screenshot, or rotated pages.
  • Missing pages, incomplete multi-page file, or statement transaction details not visible.
  • Receipt date, vendor, or total is not visible.
  • Client-facing replacement reason: The document is incomplete or not readable enough for review. Please upload a clearer copy with all pages and key details visible.
  • Do not guess amounts, merchants, or accounting categories from an unclear image.

5. Unsupported file type or size

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

  • Use the current supported formats: PDF, DOCX, XLSX, CSV, JPEG, PNG.
  • Keep each file at 25 MB or smaller.
  • Client-facing replacement reason: This file type or size is not supported. Please upload the document using one of the listed supported formats and keep it within the current file limit.

6. Multiple document types in one file

A mixed upload makes it hard to keep a file decision connected to the correct requested item.

  • Bank statement combined with receipts, payroll report combined with invoices, or several unrelated requested items in one PDF.
  • Several clients in one file, an archive containing unrelated documents, or one screenshot showing unrelated documents.
  • Client-facing replacement reason: This file contains several unrelated document types. Please upload each document to its matching requested item.
  • CollectCue does not automatically split, classify, or extract mixed-document files.

7. Duplicate or replacement confusion

Keep the original and replacement context visible instead of guessing which upload should now be reviewed.

  • Same file uploaded twice or a replacement uploaded without saying which file it replaces.
  • Old and new versions both appear current, files have indistinguishable names, or a partial revision is supplied instead of a complete replacement.
  • Replacement still has the original issue.
  • Client-facing replacement reason: We received more than one version and cannot confirm which file should be reviewed. Please upload one clearly identified replacement or explain which version is current.

8. Conflicting versions

Ask the client to resolve visible conflicts without making an accounting conclusion from filenames alone.

  • Different totals, dates, page counts, or filenames for apparently the same report.
  • One version appears revised, or one is marked draft and another final.
  • Client explanation is needed to identify the version to review.
  • Client-facing replacement reason: The submitted versions conflict. Please confirm which version is current and upload the complete version that should be reviewed.
  • Staff should not decide accounting truth from filenames alone. Final accounting treatment happens outside CollectCue.
  • Do not silently delete or overwrite the earlier file unless the existing product lifecycle explicitly supports that action.

9. File does not satisfy the requested item

Name the missing requested document so the client can reupload the correct source for the stated period.

  • Wrong document category, summary supplied instead of a full statement, or screenshot supplied instead of the requested report.
  • File lacks the requested account or period, provides an explanation without support, a cover page without the document, or a financial report instead of source evidence.
  • Client-facing replacement reason: This upload does not contain the requested document. Please upload [Requested Document] for [Requested Period].

A rejection is a file-review decision

Use this resource to document why a submitted file cannot be reviewed and what the client should send next. It does not repair accounting data, make a legal conclusion, or replace staff review. CollectCue does not automatically repair, split, compare, or classify files.

Use an objective reason

Name the wrong client, requested item, period, visible page issue, access problem, format issue, duplicate, or conflict that stopped the file review.

Keep the request context together

Record the requested item, original file, replacement need, and review decision. An upload does not become received merely because a replacement arrived.

How to keep reupload decisions useful

Clear, neutral reasons keep the review moving while leaving accounting judgment and any firm-specific incident process in their proper workflow.

Use the most specific reason

  • Prefer “wrong reporting period,” “missing transaction pages,” or “password prompt prevents review” over a general “wrong file.”
  • Describe only the visible issue that prevented staff from reviewing the requested item.
  • Do not state that a client made a mistake, committed fraud, or created a compliance failure.

State the replacement requirement

  • Ask for the correct requested document, period, complete pages, accessible copy, supported format, or one clearly identified current version.
  • Use the matching requested item so the client, original file, replacement, and next staff review stay connected.
  • Do not ask the client to repair accounting records through a file-reupload message.

Review the replacement independently

  • Keep the original file context visible, but inspect the replacement as a new submitted file.
  • Do not mark the item received or close the request simply because another upload appeared.
  • Carry unresolved items into a later request only when the firm’s workflow requires it; avoid duplicate request items for the same replacement.

Clear rejection reasons clients can act on

Use neutral, practical language that tells the client what to send next without assigning blame or making a legal, fraud, or compliance conclusion.

Wrong period

This statement covers May. Please upload the statement for June.

Missing pages

The file appears to be missing pages. Please upload the complete statement, including all transaction pages.

Unreadable image

The receipt image is too blurry to read the date, vendor, and total. Please upload a clearer photo with the full receipt visible.

Password prompt

We could not open this file for review. Please provide an accessible copy or follow your firm’s approved password-sharing process.

Wrong requested item

This file does not match the requested payroll report. Please upload the payroll report through the Payroll Report item.

Mixed file

This upload includes several unrelated documents. Please upload each document to its matching requested item.

Conflicting versions

We received different versions of this document. Please confirm which version is current and upload one complete replacement.

Wrong client

This file does not match this client request. Please upload the correct document through the correct client request.

Keep the replacement connected to the original request

Only describe the lifecycle CollectCue supports today; this page does not claim a complete version history.

  • Keep the requested item unresolved after rejection.
  • Record the specific reason and ask for the replacement through the same requested item.
  • Preserve the relationship between the rejected file and replacement context.
  • Review the replacement independently before marking the item received.
  • Close the item only after the required document has been accepted.
  • Avoid creating duplicate request items for the same replacement.

What the staff review handoff looks like

The screenshot uses synthetic client and file data. It does not demonstrate OCR review, fraud detection, malware scanning, accounting approval, automatic file validation, or full version control.

CollectCue keeps the submitted file, request context, staff review status, and accept-or-reupload decision in one review workflow. It does not repair, compare, or classify the file for staff.

Client document requestsClient uploadDocument review

Product walkthrough — synthetic data

Monthly close request review showing files waiting for staff review and accept or reupload actions
The review workspace keeps the submitted file, requested item, status, and accept-or-reupload decision together. The screenshot uses synthetic client and file data.

CollectCue supports the request and review layer

CollectCue can help with

  • Keeping uploads connected to requested items.
  • Showing files waiting for staff review.
  • Recording a client-visible replacement reason and returning an item to a reupload state.
  • Receiving a replacement through the request-specific upload link while the item remains unresolved.

CollectCue does not

  • Repair corrupted accounting files, edit receipt photos, or remove PDF passwords.
  • Detect fraud, verify file authenticity, or split mixed PDFs automatically.
  • Compare financial documents line by line or determine the authoritative financial version.
  • Move transactions between periods, correct journal entries, perform reconciliation, or make accounting, tax, legal, privacy, or compliance decisions.

How to use the rejection and reupload checklist

Follow the file-review sequence before communicating a replacement request, then review the replacement before resolving the item.

  1. 1Open the submitted fileConfirm that staff can access the file before selecting a review outcome.
  2. 2Confirm client, period, and requested itemCheck the submission against the request context before assessing its contents.
  3. 3Select the most specific rejection categoryUse the category that best identifies what prevented reliable review.
  4. 4Write the visible file issueDescribe the exact page, access, format, context, or duplicate issue without assigning blame.
  5. 5State the replacement neededName the requested document, period, pages, or format the client should provide.
  6. 6Keep the requested item unresolvedDo not resolve the item merely because the first file was uploaded.
  7. 7Send the client-visible explanationUse a neutral, specific message through the matching requested item.
  8. 8Review the replacement before accepting itCheck the replacement independently while preserving its relationship to the original request.
  9. 9Mark received after reviewUpdate the item only after the replacement meets the request.

File rejection and reupload FAQ

These answers separate a client-file review result from accounting decisions, legal advice, and unsupported file handling claims.

When should a bookkeeping file be rejected?+

Request a reupload when staff cannot reliably review the file for the requested client, period, or document item. A rejection is a file-review decision, not an accounting judgment.

How specific should a reupload reason be?+

Name the visible issue and the exact replacement needed. For example, state the requested period, missing pages, accessible format, or requested item instead of writing only “wrong file.”

What should I do with a blurry receipt photo?+

Keep the item unresolved and ask for a clearer photo with the full receipt, date, vendor, and total visible. Do not guess the missing details.

What if a client uploads the wrong reporting period?+

Ask for the document for the requested period and keep the item unresolved. This workflow does not change ledger dates, journal entries, or financial reports.

What if the file cannot be opened?+

Ask for an accessible replacement in a supported format or follow the firm’s approved password-sharing process. CollectCue does not repair files or remove passwords.

What if one file contains several document types?+

Ask the client to upload each document to its matching requested item. CollectCue does not automatically split or classify mixed files.

How should conflicting file versions be handled?+

Keep the review context visible, ask the client to identify the current complete version, and review that replacement independently. Do not use a filename alone to decide the final version.

Does uploaded mean received in CollectCue?+

No. Uploaded means the file arrived. It can still need staff review or a replacement before the requested item is received or resolved.

Can CollectCue repair or split files automatically?+

No. CollectCue does not automatically repair corrupted files, split mixed PDFs, compare documents line by line, or determine an authoritative financial version.

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

No. Clients can use the request-specific upload link to send a replacement without creating a CollectCue account.

Related resources

Use the bank statement page for a statement-specific intake check, then use these resources for request setup, collection, follow-up, and document review.

Bank statement submission checklist

Prepare a bank or card statement for the next staff review step.

Open resource

Client document collection checklist

Decide which client documents to request for routine collection.

Open resource

Bookkeeping client document request form

Set the client, period, requested item, and review context before clients upload.

Open resource

AI-ready document review checklist

Keep source-file review separate from external automation and accounting handoff.

Open resource

Document chase SOP for bookkeepers

Connect unresolved document decisions to a consistent follow-up workflow.

Open resource

Client email templates for missing documents

Adapt follow-up language for items the client still needs to send.

Open resource

Keep rejected files connected to the next action

Record the exact file issue, request a replacement through the same requested item, and keep the request open until the document has been reviewed.

See CollectCue featuresView pricing