CollectCue

Owner Draw and Shareholder Distribution Support Request Checklist

A bookkeeping team can use this checklist to request factual support for a defined owner-related transfer. One request can hold several requested items, while each transfer keeps its own date, recipient context, source account reference, status, and staff review result.

View checklist
Browse the resources hub

Quick answer

Use this checklist when a payment to an owner, member, partner, or shareholder needs factual source support. It organizes the transfer, recipient context, period, explanation, and any maintained supporting records without deciding what the transaction is or how it should be treated.

Copy-ready request checklist

Owner Draw and Shareholder Distribution Support Request Checklist

Copy this list for one client, entity, transfer, and bookkeeping period. Keep factual source support separate from the eventual accounting or tax decision.

1. Request setup

Set the client, entity, transfer, owners, and due date before asking for support.

  • Client: [Client name]
  • Entity: [Entity name]
  • Bookkeeping period: [Period]
  • Transaction date: [Date]
  • Amount: [Amount]
  • Recipient or owner context: [Owner, member, partner, or shareholder]
  • Source account or masked account reference: [Masked reference]
  • Request owner: [Team member]
  • Review owner: [Team member]
  • Due date: [Date]

2. Possible requested support

Request only the records that apply to the defined transfer and are maintained or requested by the firm.

  • Bank, ACH, wire, check, or transfer confirmation.
  • Relevant bank statement or account activity.
  • Client explanation of the purpose.
  • Existing approval, resolution, meeting record, or written authorization only when maintained and requested.
  • Operating, partnership, shareholder, or ownership agreement only when relevant and requested.
  • Existing owner distribution or draw schedule when maintained.
  • Supporting correspondence tied to the specific transfer.
  • Related repayment record only if the client says repayment is expected.

3. Keep transfers separate

Write one requested item for each factual support gap that needs its own review.

  • Separate different owners, entities, periods, or transfer dates.
  • Keep a contribution separate from a distribution or withdrawal.
  • Name the requested support instead of asking for a general explanation of all owner activity.

Keep owner-related transfers item-specific

The request identifies factual support; it does not classify the transfer.

Transfer context

Different owner or entity

Request as

A separate requested item with the recipient and entity context.

Do not decide

Whether the payment is equity, debt, compensation, or another outcome.

Transfer context

Different transfer date or period

Request as

A separate requested item with its own period and source record.

Do not decide

Whether dates create a tax, legal, or accounting result.

Transfer context

Contribution and distribution activity

Request as

Separate requests with the factual source support for each transfer.

Do not decide

Whether either transaction has a final accounting or tax classification.

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.

Ask for support without deciding the transaction

A clear request describes the transfer and the source support needed, while the responsible professional handles any conclusion outside the request workflow.

Client-facing request template

  • Subject: Support needed for owner-related transfers for [entity] in [bookkeeping period].
  • Please upload the listed support for each transfer by [due date].
  • For each item, include the transfer confirmation or account activity, recipient context, and the requested explanation or maintained supporting record.
  • Please keep different owners, entities, transfer dates, and contribution or distribution activity as separate items.
  • If a file belongs to a different transfer or period, upload the replacement only for the affected item.

Synthetic illustrative scenario

  • Synthetic example: [Harbor Pine LLC] requests support for two owner-related transfers in [April 2026].
  • One item asks for a bank transfer confirmation and purpose explanation for [Owner A]. A second item asks for the maintained schedule for a separate transfer to [Owner B].
  • The first file is Uploaded / Pending review. The second item is Waiting on client.
  • The scenario does not decide whether either transfer is a draw, distribution, salary, dividend, loan, reimbursement, debt, or equity.

Common mistakes

  • Combining several owners or transfer dates into one request item.
  • Requesting an agreement or approval as though every transfer needs one.
  • Treating a bank record as a final accounting or tax conclusion.
  • Treating an uploaded file as Received before staff review.
  • Requesting a general explanation when a specific transfer record is needed.

Product boundary

  • CollectCue organizes client, period, requested items, uploads, review status, reupload actions, and follow-up.
  • The request does not decide whether a transaction is a draw, distribution, salary, dividend, loan, reimbursement, debt, or equity.
  • It does not determine basis, retained earnings, reasonable compensation, solvency, tax forms, deductibility, or tax treatment.

How to use this checklist

Use a separate item whenever the transfer, recipient, entity, period, source record, or review result differs.

  1. 1Set the transfer contextRecord the client, entity, date, amount, recipient or owner context, masked source reference, owners, and due date.
  2. 2Choose factual supportRequest the transfer record, account activity, client explanation, or maintained agreement or schedule that applies.
  3. 3Keep items distinctSeparate each owner, entity, period, date, and contribution or distribution transfer.
  4. 4Review before resolutionUse Pending review, Received, or Needs reupload only after staff review of that item.

Frequently asked questions

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

What support can a firm request for an owner draw or distribution?+

A firm may request transfer confirmation, relevant account activity, the client explanation, and maintained approval, ownership, agreement, schedule, correspondence, or repayment support when those records apply and are requested.

Should different owner transfers be combined in one upload item?+

No. Keep transfers separate when the owner, entity, period, date, source record, or review result differs.

Does a transfer record decide the accounting or tax treatment?+

No. The record supplies factual support. It does not decide whether the transaction is a draw, distribution, salary, dividend, loan, reimbursement, debt, equity, or another outcome.

What does CollectCue organize for this request?+

CollectCue helps organize clients, periods, requested items, uploads, staff review status, reupload actions, and follow-up. Professional conclusions remain outside the request workflow.

Related resources

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

Transaction clarification request templates

Use focused client wording when the next item needs a factual explanation or supporting document.

Open resource

Bookkeeping client document request form

Set up a client-period request with items, owners, due date, and review context.

Open resource

Completion criteria template

Define the observable review boundary before an item is recorded as received.

Open resource

Keep owner-related transfer support organized

CollectCue helps firms organize the client, period, requested transfer support, uploads, review context, item status, reuploads, and follow-up. It does not make accounting, tax, legal, or compensation decisions.

See how CollectCue works