A prepaid-expense request stays clear when the client, entity, bookkeeping period, vendor or counterparty, prepaid item, coverage period, requested record, and next action stay connected. The checklist requests factual source support; it is not a prepaid accounting tutorial, amortization calculator, journal-entry guide, tax guide, or audit-compliance guide.
Browse the resources hubUse this checklist when the bookkeeping team already knows which prepaid item needs support and needs to request the source records behind it. CollectCue organizes the request, upload, review, reupload, and handoff. It does not calculate amortization or determine accounting treatment.
Copy-ready request checklist
Copy this list when the team has identified one prepaid item and needs the source records for a defined bookkeeping period or review. Keep each record separate when it needs its own client action or staff review.
Set the client, entity, prepaid-item context, period, owners, and due date before requesting source records.
Request the underlying purchase or agreement records only when they apply to the named prepaid item.
Keep payment evidence tied to the named prepaid item and source period when the firm requests it.
Name the service or coverage period without turning the request into an amortization calculation.
Request maintained schedules only when the firm needs them for the current review.
Keep a change, credit, or cancellation record with the specific prepaid item it affects.
Use the existing request workflow states without creating a prepaid-specific status.
Source documents describe the underlying purchase, agreement, payment, or coverage period. An existing prepaid schedule is a client- or accounting-workflow record that may summarize how the prepaid item is being tracked. They are not interchangeable. CollectCue does not create, calculate, validate, or reconcile a prepaid schedule.
Decision point
What it identifies
Source documents
The available purchase, agreement, payment, or coverage context for the named prepaid item.
Existing prepaid schedule
How the client or accounting workflow has recorded or summarized the named item, when a maintained schedule exists.
Decision point
When to request it
Source documents
When the firm needs the underlying source record for the stated item, period, payment, agreement, or coverage question.
Existing prepaid schedule
When the firm specifically requests an existing maintained schedule for the current review.
Decision point
Who usually provides it
Source documents
The client, vendor, insurer, counterparty, financial institution, or other source identified in the request.
Existing prepaid schedule
The client or the accounting workflow that maintains the schedule.
Decision point
What it does not decide
Source documents
Amortization, capitalization, materiality, tax deductibility, journal entries, debit or credit treatment, or professional sufficiency.
Existing prepaid schedule
Whether the schedule is complete, correct, validated, reconciled, or the final accounting treatment.
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.
A focused client request asks for the identifiable record behind the prepaid item and keeps the coverage period, staff review, and possible replacement connected to that item.
Use separate requested items whenever the prepaid item, vendor or counterparty, source record, coverage period, client action, or review result differs.
These answers explain client document collection and do not make an accounting, tax, legal, payroll, or compliance decision.
A firm can request the vendor invoice, relevant agreement or order form, payment support when requested, service or coverage dates, a maintained prepaid schedule when it exists and is needed, and relevant renewal, amendment, cancellation, credit, or refund support for the named item.
No. CollectCue organizes client-period requested items, uploads, staff review, reupload, and handoff. It does not calculate amortization, create schedules, post journal entries, or determine accounting, tax, or audit treatment.
No. Uploaded means the file is Pending review. Staff review the file against the requested item before recording it as Received or requesting a replacement for that item.
Use these pages for the next request, review, reupload, or follow-up action.
Use the conversion-focused checklist when a defined cutoff-date review needs prepaid support alongside other source records.
Open resourceUse the recurring-billing checklist when annual plans and subscription records need a broader billing-period request.
Open resourceStart with the general collection list before selecting the prepaid items that need focused source support.
Open resourceCreate a client-period request with named items, owners, due dates, and review context.
Open resourceChoose whether the next item needs an original source record, a report, or maintained context.
Open resourceCollectCue helps teams organize the client, period, named prepaid records, uploads, review status, reupload actions, and handoff. It does not calculate amortization or determine accounting treatment.
