CollectCue

Partial-Month Bookkeeping Document Request Checklist

A partial-month request identifies the client, entity, exact start and end dates, source coverage, opening context, and handoff boundary. It keeps a full-month statement and a date-range export as different ways to request factual coverage.

View checklist
Browse the resources hub

Quick answer

Use this checklist when a bookkeeping engagement starts, ends, pauses, or changes responsibility partway through a month. It requests records for an exact date range and handoff context without deciding cutoffs, accruals, pricing, reconciliation, or accounting completeness.

Copy-ready request checklist

Partial-Month Bookkeeping Document Request Checklist

Copy this list for one client, entity, exact start date, exact end date, and handoff context.

1. Request header

Set the date range, reason, and handoff context before selecting records.

  • Client: [Client name]
  • Entity: [Entity name]
  • Exact start date: [Date]
  • Exact end date: [Date]
  • Reason for the partial period: [Reason]
  • Prior owner or next owner when relevant: [Context]
  • Request owner: [Team member]
  • Review owner: [Team member]
  • Client due date: [Date]
  • Internal handoff date: [Date]

2. Banking and card records

Request date coverage without treating a partial range as a universal rule.

  • Statement covering the partial-period dates.
  • Interim transaction export only when requested by the responsible workflow.
  • Opening or ending balance context when requested.
  • New or closed account support when relevant.

3. Sales and processor records

Request the source reports that match the defined dates and items.

  • Sales report for the exact date range.
  • Processor payout or settlement report.
  • Invoice or transaction export.
  • Refund, credit, or dispute support only when relevant.

4. Payroll, vendor, expense, and handoff records

Use these items only when they apply to the defined service boundary.

  • Payroll report covering the defined dates or pay cycles.
  • Vendor bills and invoices within scope.
  • Receipts and expense support for identified items.
  • Reimbursement or contractor support when applicable.
  • Trial balance, closing report, or reconciliation report only when requested.
  • Prior-period unresolved-item list or outstanding AR/AP reports when relevant.
  • Source documents that cross the handoff date.
  • Client explanation for records outside the normal statement cycle.

Full-month statement vs date-range export

Choose the record that supplies the needed coverage for the defined request.

Request need

Statement covers the defined dates

Possible support

Request the statement and item-specific context that applies.

Do not assume

That every partial period needs a separate export.

Request need

Statement does not cover the needed range

Possible support

Request a date-range export only when the responsible workflow needs it.

Do not assume

That a CSV is mandatory or decides completeness.

Request need

Handoff crosses a date

Possible support

Request the named source record, opening or ending context, and client explanation where relevant.

Do not assume

Cutoffs, accruals, reconciliation, pricing, or accounting outcomes.

Item status and next action

Keep a missing client action distinct from staff review and a specific replacement request.

Situation

The requested support has not arrived

Status

Waiting on client

Next action

Ask for the named record or factual context for that item.

Situation

A file or response has arrived

Status

Uploaded / Pending review

Next action

Staff review the item, period, source, and readable context before resolving it.

Situation

Staff records evidence for the requested item

Status

Received

Next action

Keep other requested items open until they have their own review result.

Situation

The file is wrong, incomplete, unreadable, or for a different item

Status

Needs reupload

Next action

Request a replacement only for the affected requested item.

Make the date boundary observable

A partial-period request works when every requested item has a clear date range, source coverage, and next action.

Client-facing request template

  • Subject: Records needed for [client] from [exact start date] through [exact end date].
  • Please upload the listed statements, reports, invoices, receipts, payroll, sales, and opening or handoff records by [due date].
  • Use the exact date range and the requested source in each item description.
  • For records that cross the handoff date or normal statement cycle, include the requested client explanation or source context.
  • If a file covers the wrong dates, replace only the affected requested item.

Synthetic illustrative scenario

  • Synthetic example: [Westline Workshop] changes bookkeeping responsibility on [May 18, 2026].
  • The request covers [May 1] through [May 18] with separate items for a bank statement, a sales report, a payroll report, and an unresolved-item list.
  • The bank statement is Uploaded / Pending review. The sales report needs reupload because it covers the full quarter instead of the requested dates.
  • The scenario does not decide cutoffs, accruals, journal entries, reconciliation, engagement pricing, or accounting completeness.

Common mistakes

  • Using a vague month label instead of exact start and end dates.
  • Treating a full-month statement as complete date coverage without reviewing it.
  • Assuming a CSV or export applies to every request.
  • Mixing pre-handoff and post-handoff records in one unclear item.
  • Using the request to decide pricing, accounting cutoffs, or reconciliation results.

Product boundary

  • CollectCue organizes client-period requested items, uploads, review context, reuploads, and follow-up.
  • It does not recommend or provide bank access, decide engagement pricing or fee proration, or claim that a CSV applies to every request.
  • It does not decide cutoffs, accruals, journal entries, reconciliation, accounting completeness, or a universal partial-month rule.

How to use this checklist

Use the exact date range and handoff context to select each record rather than treating a partial month as a standard monthly request.

  1. 1Set the exact periodRecord the client, entity, exact start and end dates, partial-period reason, handoff context, owners, and due date.
  2. 2Select date-appropriate sourcesRequest statements, exports, sales, payroll, invoices, receipts, and opening context only when they fit the defined dates.
  3. 3Separate coverage gapsKeep a wrong-range file, a crossed handoff record, and a missing opening context as distinct items.
  4. 4Review coverage before resolutionStaff review the requested range and source context before marking an item Received or Needs reupload.

Frequently asked questions

These answers explain client document collection and do not make an accounting, tax, legal, payroll, or compliance decision.

Must every partial-month request use a date-range export?+

No. Request an interim or date-range export only when the responsible workflow needs coverage that the available statement or source record does not provide.

What records can be requested for a partial-month engagement?+

A firm may request statements, date-range exports when needed, sales or processor reports, payroll reports, bills, receipts, opening or ending context, unresolved-item lists, and records that cross the handoff date when they apply.

Does a partial-month request decide accounting cutoffs or completeness?+

No. It organizes the exact dates and requested factual support. Accounting cutoffs, accruals, journal entries, reconciliation, and completeness decisions remain outside the request.

What happens when an upload covers the wrong dates?+

Staff can keep that item in Needs reupload and ask for a replacement only for the affected requested item.

Related resources

Use these pages for the next request, review, reupload, or follow-up action.

Source report availability calendar template

Plan when source reports are expected before turning a partial period into item-specific requests.

Open resource

Bookkeeping month-end close checklist

Keep recurring full-period collection separate from a partial-period handoff request.

Open resource

Bookkeeping client document request form

Create a client-period request with exact dates, owners, due date, and review fields.

Open resource

Keep partial-period records in one clear request

CollectCue helps firms organize the exact date range, requested records, uploads, staff review context, reupload actions, and follow-up. It does not decide accounting, pricing, or handoff outcomes.

See how CollectCue works