CollectCue

Intercompany Transaction Support Request Checklist for Bookkeeping

An intercompany transaction support request checklist helps a bookkeeping team ask for client-provided records tied to two or more related entities. Use it when a transfer, shared expense, loan, reimbursement, management fee, or asset movement needs clearer source context. CollectCue organizes the request, upload, review, and follow-up workflow; it does not reconcile related-entity balances or determine transaction treatment.

View checklist
Browse the resources hub

Copy-ready request checklist

Intercompany Transaction Support Request Checklist

Copy this list for one client or group, entity pair, and defined period. Keep each source record as a separate requested item when it needs different client action or staff review.

1. Request context

Record the two entities and the transaction context before asking for support.

  • Client or group: [Client or group]
  • Entity A: [Entity A]
  • Entity B: [Entity B]
  • Bookkeeping period: [Period]
  • Transaction date: [Date]
  • Amount and currency, when known: [Amount / currency]
  • Direction of transfer: [Entity A to Entity B / Entity B to Entity A]
  • Client-provided purpose: [Purpose]
  • Request owner: [Team member]
  • Review owner: [Team member]
  • Due date: [Date]

2. Agreements and shared-service context

Request agreements only when they exist and the firm has asked for them.

  • Intercompany agreement when one exists and the firm requests it.
  • Shared-services or cost-sharing agreement when applicable.
  • Approval or board documentation only when maintained and requested.
  • Client explanation tying the transaction to the entities and period.

3. Transaction and third-party source support

Keep the original transaction source separate from any related internal record.

  • Invoice or credit memo issued between the entities.
  • Original vendor invoice when one entity paid a third-party cost for another.
  • Bank, wire, ACH, or transfer confirmation.
  • Related fees or currency records when relevant.

4. Entity-specific review context

Ask for an entity-specific system record only when it is needed for the defined review.

  • Entity-specific ledger or transaction export when requested for review.
  • A separate item for each entity pair, period, transaction type, or source that needs different review context.
  • A client explanation for a transfer, shared expense, loan, reimbursement, management fee, or asset movement when the available records are unclear.

Use this checklist for source context

Use it after the team identifies a related-entity transaction that needs client-provided support, not to decide what the transaction means in the books.

Appropriate request

A targeted request can identify the two entities, transaction date, period, known amount, direction, purpose, source records, owner, and current review status.

Outside the request workflow

The checklist does not reconcile balances, decide debt, equity, distributions, management-fee, transfer-pricing, interest, tax, legal, or audit treatment.

Status and next action

Use real request workflow states rather than a reconciliation or accounting-complete label.

Situation

The client has not supplied the defined record

Status

Waiting on client

Next action

Send a focused reminder naming the entity pair, period, and item.

Situation

A file or explanation arrived

Status

Uploaded / Pending review

Next action

Staff review whether it belongs to the requested transaction context.

Situation

Staff records evidence for the item

Status

Received

Next action

Leave any separate entity, period, or source item open until its own result is recorded.

Situation

The record needs a clear replacement

Status

Needs reupload

Next action

State the missing entity, period, source, or file issue without adding accounting instructions.

Separate-item guidance

One request can contain multiple items, but each item needs a clear scope.

Keep separate

Different entity pairs

Why it helps

Prevents records for one pair from being treated as support for another pair.

Keep separate

Different periods

Why it helps

Keeps the requested source period identifiable.

Keep separate

Different transaction types

Why it helps

Separates a transfer, shared cost, reimbursement, or asset movement when the requested records differ.

Keep separate

Different sources

Why it helps

Makes a vendor invoice, intercompany invoice, transfer confirmation, and explanation independently reviewable.

A clear client-facing request

Adapt this wording to the request scope. Replace every bracketed field and remove records that do not apply.

Client-facing request template

  • Subject: Support needed for [Entity A] and [Entity B] activity for [period].
  • Please provide the records listed below for the [transaction date] activity between [Entity A] and [Entity B].
  • For each item, include the applicable entity, period, and source. If a requested record does not exist, reply with a brief explanation rather than uploading an unrelated file.
  • Requested support: [intercompany agreement when requested], [invoice or credit memo], [vendor invoice], [transfer confirmation], [entity-specific export], and [client explanation].
  • Please upload by [due date].

Illustrative scenario

  • Synthetic example: [Harbor Thread Group] has a transfer from [Harbor Thread Services] to [Harbor Thread Retail] during [April 2026].
  • The request contains separate items for the transfer confirmation, the original vendor invoice, and a client explanation of the stated purpose.
  • The transfer confirmation is Uploaded / Pending review. The vendor invoice needs reupload because the first file names a different period.
  • The scenario does not say whether the activity is reconciled or how it should be recorded.

Common mistakes

  • Putting all related-entity activity into one vague requested item.
  • Mixing entity pairs, periods, currencies, or transaction types without identifying them.
  • Requesting internal approval material when it is not maintained or needed.
  • Treating an uploaded file as received before staff review.
  • Asking for passwords or access to every related accounting system.
  • Giving reconciliation, tax, legal, or accounting instructions inside the request.

Product boundary

  • CollectCue does not reconcile related-entity balances.
  • It does not determine debt, equity, distribution, management-fee, transfer-pricing, interest, tax, legal, or audit treatment.
  • It does not require or collect passwords to related accounting systems.
  • It helps the team organize requested items, uploads, review context, reuploads, and follow-up.

How to set up the support request

Set the transaction context first, then create a separate item for each record that requires a distinct source or review action.

  1. 1Name both entities and the periodRecord the entity pair, transaction date, direction, and client-provided purpose when known.
  2. 2Select only relevant sourcesRequest an agreement, invoice, confirmation, export, or explanation only when it applies to the defined activity.
  3. 3Separate the requested itemsDo not collapse the full intercompany history into one item when sources or periods differ.
  4. 4Review and follow upUse Pending review, Received, or Needs reupload based on the item-specific result without making a reconciliation conclusion.

Frequently asked questions

These answers focus on client document collection and staff review context.

What records may be requested for an intercompany transaction?+

Depending on the defined activity, the firm may request an existing agreement, invoice, credit memo, vendor invoice, transfer confirmation, entity-specific export, relevant fee or currency record, and a client explanation. The exact list depends on the entities, period, and review scope.

Can one request include multiple intercompany items?+

Yes. One request can include multiple items, but each should state its entity pair, period, transaction type, and requested source clearly.

Does uploading support mean the transaction is reconciled?+

No. An upload can be Pending review or need a replacement. CollectCue does not reconcile related-entity balances.

Should the client share accounting-system passwords?+

No. This checklist does not request or collect passwords. Follow the firm’s approved access process outside the document request workflow when access is needed.

What does CollectCue organize for intercompany support?+

CollectCue helps organize the client or group, entities, period, requested items, uploads, review status, reupload actions, and follow-up. It does not determine accounting, tax, legal, or audit treatment.

Related resources

Use these pages to turn focused support requests into clear client actions and review steps.

Bookkeeping client document request form

Set up an item-level request with a client, period, owner, due date, and review fields.

Open resource

Client document collection checklist

Use the general collection checklist for broader client-period support.

Open resource

Bookkeeping transaction clarification request templates

Use neutral wording when a transaction needs client-provided context.

Open resource

Bookkeeping source documents and reports guide

Decide whether the next item needs a source record, an open list, or an accounting-system export.

Open resource

Keep related-entity support organized by item

CollectCue helps teams keep each client-period requested item, upload, review context, reupload action, and follow-up in one request workflow. It does not reconcile balances or make accounting conclusions.

See how CollectCue works