Bookkeeping Source Documents and Reports: What to Request and When

Different bookkeeping reports answer different request questions. Choose the file based on whether the team needs source-period evidence, transaction detail, business context, an itemized open list, an aging summary, or an accounting-system export. In many workflows, two related records are requested together, but CollectCue only organizes the request, upload, review, and handoff.

Browse the resources hub

Quick decision table

Need a source-period record

Request the statement, invoice, receipt, agreement, or other original-source record named for the item.

Need transaction-level detail

Request the export, open list, or itemized report when the responsible workflow asks for individually identifiable rows.

Need client-provided business context

Request the expense report, explanation, approval context, or other record that the client workflow uses.

Need a time-based summary

Request the aging report when the source system provides grouped balances by age or due date.

Need both a source and a report

Create separate requested items when each record answers a different review question.

Need an accounting conclusion

Keep the document request focused on collection; the responsible bookkeeper handles later accounting workflow decisions.

Ten source-document decisions

For each pair, choose the item that answers the current request question. Where both are useful, keep them as separate requested items so their upload and review status stay clear.

Bank statement PDF vs Transaction CSV

Direct answer: A PDF statement is the institution-provided source-period statement. A CSV is a structured transaction export when an external accounting workflow needs sortable or importable transaction rows.
Request Bank statement PDF when: Request the PDF when staff needs the client, account, and statement period visible in one source-period record.
Request Transaction CSV when: Request the CSV when the responsible workflow specifically needs structured transaction rows.
Often request both when: Both can be useful when the team needs a source-period statement and a separate structured export for downstream work.
What neither document decides: Neither proves the business purpose of an individual transaction.

Merchant payout report vs Bank deposit report

Direct answer: A payout or settlement report describes processor-side composition and timing. A bank statement or deposit record shows bank-side amount and posting activity.
Request Merchant payout report when: Request the payout report when the team needs the processor-side payout composition or timing requested by the firm.
Request Bank deposit report when: Request the bank record when the team needs the bank-side deposit activity for the defined period.
Often request both when: Both may be needed for the downstream reconciliation workflow.
What neither document decides: Neither record performs or completes that reconciliation in CollectCue.

Payroll register vs Payroll journal

Direct answer: A payroll register is employee or pay-period detail from the payroll workflow. A payroll journal or journal summary is accounting-oriented summarized posting information when the payroll system provides it.
Request Payroll register when: Request the register when the responsible bookkeeper needs the available employee or pay-period detail.
Request Payroll journal when: Request the journal or summary when the payroll system provides it and the responsible bookkeeper requests summarized posting information.
Often request both when: Both may be requested when detailed source context and a system-provided summary are needed for the defined review.
What neither document decides: Neither page gives payroll, tax, journal-entry, or reconciliation instructions.

Vendor invoice vs Receipt or payment confirmation

Direct answer: A vendor invoice can show a vendor-requested amount, item or service description, date, terms, and outstanding amount when shown. A receipt or payment confirmation records a completed payment or sale according to the issuing source.
Request Vendor invoice when: Request the invoice when staff needs the vendor’s stated charge, description, date, terms, or outstanding amount shown by the source.
Request Receipt or payment confirmation when: Request the receipt or payment confirmation when staff needs the available record of completed payment or sale.
Often request both when: A bank record, invoice, and receipt can answer different questions and may be requested together.
What neither document decides: No single document is presented here as universal legal proof or a final accounting conclusion.

Loan statement vs Amortization schedule

Direct answer: A loan statement is lender-provided period activity and balance information. An amortization schedule is scheduled payment allocation or projection when provided or maintained.
Request Loan statement when: Request the statement when the defined review needs lender-provided activity and balance information for the period.
Request Amortization schedule when: Request the schedule when it is provided or maintained and the responsible professional requests it.
Often request both when: Actual activity may require the statement as well as the schedule.
What neither document decides: Neither determines principal, interest, escrow, journal entries, or accounting treatment on this page.

Credit card statement vs Employee expense report

Direct answer: A credit card statement shows card-account activity and amount charged. An employee expense report provides employee-supplied business context, allocation, approval, and linked support when used.
Request Credit card statement when: Request the statement when the defined item needs card-account activity for the period.
Request Employee expense report when: Request the expense report when the item needs claimant context, allocation, approval, or linked support used by the client workflow.
Often request both when: Both are often requested because they answer different request questions.
What neither document decides: Neither document by itself determines deductibility, tax treatment, policy compliance, or final accounting classification.

Accounts receivable aging report vs Open invoice list

Direct answer: An AR aging groups outstanding customer balances by age or due-date buckets when the source system provides them. An open invoice list identifies outstanding customer invoices item by item.
Request Accounts receivable aging report when: Request an aging view when staff needs a time-based summary of outstanding customer balances.
Request Open invoice list when: Request an open list when staff needs invoice-level action or client follow-up context.
Often request both when: Both may help when the request needs a summary view and separately identifiable invoice items.
What neither document decides: Neither tells the user which balances to write off or makes an accounting decision.

Accounts payable aging report vs Unpaid bills report

Direct answer: An AP aging groups unpaid vendor balances by age or due-date buckets. An unpaid bills report identifies open vendor bills item by item.
Request Accounts payable aging report when: Request an aging view when staff needs a summary of unpaid vendor balances by age or due date.
Request Unpaid bills report when: Request an unpaid bills report when staff needs bill-level detail for the defined review.
Often request both when: Both can be requested when summary aging and item-level source context are needed.
What neither document decides: Neither provides a payment recommendation or cash-flow advice.

General ledger export vs Source documents

Direct answer: A general ledger export shows how activity was recorded in the accounting system. Source documents provide underlying transaction or business-event support available from the original source.
Request General ledger export when: Request the general ledger export when the responsible professional asks for system-recorded activity or account detail.
Request Source documents when: Request source documents when the defined item needs original statements, invoices, confirmations, agreements, or other available business-event support.
Often request both when: Both can be used in review when the firm needs recorded activity and the underlying source context.
What neither document decides: CollectCue does not perform vouching, tracing, audit testing, or accounting conclusions.

Bank feed data vs Source statement

Direct answer: Bank feed data is transmitted transaction data used by an external accounting system. A source statement is an institution-provided period statement requested for review.
Request Bank feed data when: Request bank feed information only when the responsible bookkeeper needs client-provided context for an external accounting-system issue.
Request Source statement when: Request the source statement when the team needs the institution-provided period statement for review.
Often request both when: Both may be relevant when a feed issue and the source-period record need to be discussed separately.
What neither document decides: A feed gap, duplicate, or mismatch is handled in the accounting system and by the bookkeeper; CollectCue requests and reviews the client-provided file only.

Use this guide before creating the request

It helps a bookkeeping team distinguish similar records and request each one for the question it can answer. It is not an accounting tutorial, audit guide, or general document glossary.

Good fit

Use it when a client request needs a clear choice between two similar reports or documents, or needs both records kept separate.

Not a final decision

The responsible bookkeeper decides which records are required for the engagement and handles accounting-system, reconciliation, tax, or journal-entry work after review.

Use the choice to make a better requested item

A clear item names the source, account or entity context, period, and the specific review question without claiming what the document proves.

Request-selection matrix

Use a statement, invoice, receipt, agreement, or confirmation when the request needs an available original-source record for a defined period or activity.
Use an export, open list, or report when the responsible workflow needs system-produced transaction rows, invoice detail, or a time-based summary.
Use an explanation, expense report, or approval context when the request needs client-provided business context used by that workflow.
Create separate items when two records answer different questions or need different client follow-up and staff review.
Keep accounting conclusions, reconciliation, policy decisions, and tax treatment outside the client document request.

Synthetic scenario

Synthetic example: [Northlight Goods] has a processor deposit in [May 2026] that needs the payout report and the bank statement kept as separate requested items.
The payout report is Uploaded / Pending review. The bank statement is still Waiting on client.
The request owner can follow up on the statement without asking the client to send the payout report again.
The scenario does not reconcile the deposit, calculate a result, or determine an accounting classification.

Common mistakes

Requesting a vague “report” without naming the needed source or question.
Treating a statement, an export, and client context as interchangeable.
Using an aging summary when the request needs invoice- or bill-level detail.
Treating an accounting-system export as a replacement for all available source documents.
Combining records that need different periods, owners, or review results into one requested item.
Treating an uploaded file as a completed accounting conclusion.

Product and accounting boundary

CollectCue organizes requested items, client uploads, staff review context, reupload actions, and handoff.
It does not connect to bank feeds, accounting systems, processors, or payroll systems.
It does not perform reconciliation, vouching, tracing, audit testing, journal entries, tax treatment, or accounting conclusions.

How to choose the next requested item

Start from the exact missing question, then choose the source record, report, or context item that addresses it without treating the request as accounting work.

1Name the client, source, and periodSet the context before deciding whether the next item is a statement, report, export, invoice, receipt, or explanation.
2Identify the questionDecide whether staff needs source-period evidence, transaction detail, business context, an open list, or an aging summary.
3Request one or both recordsUse separate requested items when two records answer different questions or require different review outcomes.
4Review without overclaimingRecord the item-level request status and leave reconciliation or accounting decisions to the responsible workflow.

Frequently asked questions

These answers keep the guide focused on what to request and when, not on accounting advice.

Should a bookkeeping request ask for a source document or an accounting-system report?+

Choose the record based on the request question. Source documents provide available support from the original source, while reports or exports can provide system-recorded detail or summaries. Some reviews need both as separate items.

When should two related records be requested together?+

Request both when they answer different questions, such as processor-side payout detail and bank-side deposit activity, or card-account activity and employee-provided expense context.

Does a report replace the underlying source support?+

Not necessarily. A report can be useful for its defined view, but it does not automatically replace the available statement, invoice, receipt, confirmation, agreement, or client explanation needed for another question.

Can CollectCue decide which record proves an accounting result?+

No. CollectCue organizes the request, upload, review, and handoff workflow. The responsible bookkeeper decides which records are needed and handles later accounting work.

How should similar records be tracked in one request?+

Create separate requested items when records have different sources, periods, owners, client actions, or review outcomes. This keeps follow-up specific and avoids closing one item because another file arrived.

Related resources

Use these resources to turn the document choice into a client-period request and manage what happens after the request is sent.

Bookkeeping client document request form

Turn a selected source or report into a clear client-period request item.

Open resource

Client document requests

See how requested items, upload links, review status, and follow-up fit in one workflow.

Open resource

Client document collection checklist

Use the general list when the team needs a broader starting point before selecting records.

Open resource

Employee reimbursement document request checklist

Use the specific reimbursement checklist when expense report and card-statement context are both relevant.

Open resource

Turn the selected record into a focused request

Use the Bookkeeping Client Document Request Form to name the client, period, source, item, owner, due date, and review context. CollectCue then helps organize the request, upload, review, and handoff workflow.

See how CollectCue works