Payment processor report request
- Client:
- Bookkeeping period:
- Payment processor:
- Request owner:
- Review owner:
- Client due date:
Payment Processor Settlement and Reserve Report Request Checklist
Define the merchant accounts, reporting period, settlement files, payout details, processing fees, refunds, disputes, adjustments, and reserve records needed from a payment processor source. This is a processor report request checklist, not a payment processing guide, reserve appeal guide, reconciliation workflow, or tax checklist. CollectCue can organize requested items, uploads, staff review, and reupload actions. It does not connect to payment processors, retrieve reports, calculate reserves, or reconcile payouts.
Client-period processor source request
Quick answer
A payment processor report request checklist defines the merchant account scope, Merchant IDs, reporting period, timezone, currencies, requested report types, output format, and review owner.
Keep settlement summary, payout detail, transaction-level settlement export, processing fees, refunds, disputes or chargebacks, adjustments, reserve balance, reserve activity, and reserve releases distinct when the firm needs them as separate source records.
Uploaded does not mean Received. One accepted report does not complete every requested item. The firm decides which reports are required, and CollectCue does not retrieve or reconcile processor data.
Copy-ready payment processor report request checklist
The visible checklist and copied text use one structured source. The copy contains placeholders only—no client data, processor name, Merchant ID, account number, URL, token, query, file name, or internal note.
Account scope
- [ ] Legal business name or approved account label
- [ ] Processor account name
- [ ] Merchant ID or MID list
- [ ] Parent, chain, location, or account-group identifier, if applicable
- [ ] Currency or currencies
- [ ] Responsible client contact or report provider
Reporting period
- Start date:
- End date:
- Reporting timezone:
- One-time or recurring request:
- Reporting frequency, if recurring:
Settlement and payout reports
- [ ] Settlement summary
- [ ] Payout detail
- [ ] Transaction-level settlement export, if requested
- [ ] Processing fee report
- [ ] Refund report
- [ ] Dispute or chargeback report
- [ ] Adjustment report
- [ ] Processor balance or activity report, if requested
Reserve reports
- [ ] Reserve balance report
- [ ] Reserve activity report
- [ ] Held-funds detail
- [ ] Reserve release activity
- [ ] Reserve type or description shown by the processor
- [ ] Other reserve-related source report selected by the firm
Output
- [ ] Combined report across selected MIDs
- [ ] Separate report for each MID
- [ ] Separate report by location or entity
- [ ] Separate report by currency
- [ ] CSV
- [ ] XLSX
- [ ] Other source-generated format selected by the firm
Review tracking
- Still needed:
- Pending staff review:
- Received:
- Needs reupload:
- Current blocker:
- Next action owner:
- Review date:
- Notes:
Define the request before the client starts exporting reports
The firm decides which reports are required. Use separate requested items whenever the source, account scope, report type, period, or next action differs.
Merchant account scope
Name the processor account, selected Merchant IDs, location or entity context, and currencies needed for the request. A Merchant ID (MID) is an identifier used by a processor for a merchant account, location, or processing setup.
Review boundary
Uploaded does not mean received. Staff records received only after accepting a report for that requested item, and one accepted report does not complete every open item.
Turn scope into a client-period document request
A clear request names what the client or report holder should provide and how staff will review it. It does not make a decision about the processor data itself.
Set the account and period scope
- Name the client, bookkeeping period, payment processor, request owner, review owner, and client due date.
- Record the account scope, selected Merchant IDs, location or entity context, reporting timezone, currencies, and exact start and end dates.
- Choose combined or separate output only after the firm decides how each requested source should remain identifiable.
- Use client-facing report names instead of unexplained processor-specific abbreviations.
Keep uploads and review visible
- Use Waiting on client while a requested processor report still needs a client response or upload.
- After an upload, use Pending review and keep the next action with staff. Do not remind the client for an item already pending staff review.
- Record Received only after staff accepts the report for that requested item.
- Use Needs reupload when staff needs the correct MID, period, currency, scope, or a usable replacement file.
Where this checklist fits
Use it for a client that has one or more payment processor accounts and needs a period-specific source report request. It is not a universal requirement for every client.
Best for
- Clients using one or more payment processors.
- Multi-location businesses with several Merchant IDs.
- Subscription and ecommerce businesses.
- Businesses with multiple currencies.
- Firms requesting settlement and payout support.
- Firms reviewing reserve or held-funds activity.
- Recurring monthly or quarterly processor requests.
Not designed to replace
- A payment processor portal or payment gateway.
- A merchant acquiring platform.
- Accounting or reconciliation software.
- Chargeback management, fraud, or risk systems.
- Tax software.
Define the processor account scope
Set the scope before the client exports reports. The request names the source context; it does not create processor access, an integration, or a mapping rule.
Processor account
Record which processor account or merchant portal is expected to provide the report.
Merchant ID (MID)
A Merchant ID (MID) is an identifier used by a processor for a merchant account, location, or processing setup. Use an approved label or placeholder in public examples, not a real MID.
Parent, chain, location, or group
Record this identifier only when the processor or client actually uses that structure to identify the requested scope.
Currency scope
State whether the request needs one currency, several currencies, a combined currency summary, or separate reports per currency. CollectCue does not identify, split, or convert currencies.
Responsible contact
Name the client contact or report provider who has the report or knows how to export it. This is a request owner field, not a portal-access or credential model.
Required reports
The firm decides whether settlement, payout, fee, refund, dispute, adjustment, or reserve reports are required for the client and period.
Multiple MIDs: combined report or separate reports
Neither output is universally better. Choose the format that leaves the requested account scope clear enough for the client and staff.
Combined report
It can fit when selected MIDs belong to the same client, share a period and timezone, are clearly labeled by MID, and staff needs a group-level view. Check whether a missing MID, mixed currency, or unattributable fee or adjustment would make the report unclear.
Separate reports
They can fit when MIDs belong to different locations or entities, staff reviews each source independently, currencies or periods differ, or a combined report does not label each MID clearly. They create more requested items, so keep each item name specific.
CollectCue does not merge MIDs, separate reports, map settlement data, or deduplicate uploaded files. The firm chooses the request structure and staff reviews the submitted source records.
Keep settlement, payout, transaction export, and bank statement distinct
These records can describe related activity, but they are not the same requested file.
Settlement summary
Period-level activity such as gross settlement activity, processing fees, refunds, disputes, adjustments, and a processor-calculated net settlement or total.
Payout detail
The composition and timing of one or more payouts.
Transaction-level settlement export
A source record for the firm when it specifically needs transaction-level settlement detail.
Bank statement
The record of activity entering or leaving the bank account; it is not a processor settlement or payout report.
CollectCue does not compare these reports, verify a net amount, detect missing transactions, or complete processor-to-bank reconciliation.
Request fees, refunds, disputes, and adjustments by source
Processor report names vary. Use a clear client-facing description and separate requested items when the firm needs different periods, account scopes, or review actions.
Processing fee report
Processor-displayed fee activity or a fee summary.
Refund report
Refund activity shown by the merchant or processor source.
Dispute or chargeback report
Dispute or chargeback activity for the defined scope and period.
Adjustment report
Processor-recorded manual, operational, or account adjustments.
The firm decides whether to request these reports separately. CollectCue does not manage disputes, decide chargeback outcomes, assess fraud, decide fee treatment, or classify processor activity.
Keep reserve report scope factual
Reserve records belong here only as requested source reports. This checklist does not assess a reserve or advise on the processor's decision.
Reserve balance report
Reserve activity report
Held-funds detail
Reserve release activity
Processor-provided reserve type or description
Reserve-related adjustment detail
Report period and currency
Related merchant account or MID
The page does not decide whether a reserve is reasonable, whether a rate is correct, whether it should be released, any legal timing, risk decision, appeal approach, chargeback threshold, or financial sufficiency. CollectCue does not calculate or manage reserves.
State the period, timezone, currency, and expected file format
These fields keep the requested report identifiable before staff review. They are request details the firm defines, not automatic processor checks.
Start date, end date, and timezone
Use an exact date range instead of “latest report,” “recent activity,” or “last few months.” Record whether the processor report uses UTC, a processor timezone, an account timezone, or another configured timezone. CollectCue does not convert or normalize processor timezones.
Currency and frequency
For multiple currencies, request one combined report, one report per currency, or one per MID and currency as the firm decides. State whether the request is a one-time historical request, monthly, quarterly, or another recurring cadence. CollectCue does not convert currencies.
Expected file format
A processor may generate CSV, XLSX, PDF, or another source format. Current CollectCue public uploads accept PDF, DOCX, XLSX, CSV, JPEG, or PNG files up to 25 MB each. If a processor generates another format, the firm should confirm its upload workflow before requesting it. CollectCue does not convert, normalize, extract, or import processor exports.
Use client-facing report names
Use the wording a client or report holder can recognize, while retaining enough context for staff review.
Merchant account or location
Settlement summary
Payout detail
Processing fee report
Refund report
Dispute or chargeback report
Reserve activity report
Explain MID when it first appears. Avoid unexplained abbreviations such as TID, ARN, BIN, ICA, or BAI2 unless the request immediately explains why that processor-specific field is necessary.
Use status to separate client action from staff review
These are the request workflow states used on the page. Do not add a reconciliation, verification, approval, or accounting-complete status.
Requested report has not been uploaded
Status: Waiting on client
Next action: Client
Report uploaded, not yet reviewed
Status: Pending review
Next action: Staff
Staff accepts the report for this item
Status: Received
Next action: Staff records decision
Wrong MID, period, currency, scope, or unusable file
Status: Needs reupload
Next action: Client after staff review
Settlement summary received, payout detail missing
Status: Settlement item Received
Next action: Payout item remains open
One selected MID complete, others unresolved
Status: Completed MID item Received
Next action: Remaining items continue separately
Uploaded does not mean Received. One accepted processor report does not complete every requested item. Do not remind the client for an item already Pending review.
Requested-item examples
These placeholders show how to name a requested item without publishing a real client, account, MID, or processor detail. Completion evidence means ready for staff review, not reconciled or complete accounting work.
Settlement summary
Requested item: Settlement summary for [processor account or approved account label] for [bookkeeping period]
Completion evidence: The processor source, requested period, and applicable account scope are identifiable and ready for staff review.
Payout detail
Requested item: Payout detail for [date range]
Completion evidence: The payout dates, applicable account scope, and requested period are identifiable.
Multiple MID report
Requested item: Settlement report for the selected Merchant IDs for [bookkeeping period]
Completion evidence: Each requested MID or approved account label is included or separately identified.
Processing fee report
Requested item: Processing fee report for [bookkeeping period]
Completion evidence: The processor source, period, currency, and fee activity are identifiable.
Refund and dispute report
Requested item: Refund and dispute activity report for [bookkeeping period]
Completion evidence: The requested period and relevant activity categories are identifiable.
Reserve activity report
Requested item: Reserve balance and activity report for [bookkeeping period]
Completion evidence: The processor source, account scope, currency, report period, and reserve activity are identifiable.
Processor request workflow evidence
This product walkthrough supports the request, upload, and review workflow only.
A single processor request can contain separate settlement, payout, fee, refund, and reserve requested items while keeping the upload workflow and review context together.
Product walkthrough — synthetic data
Common processor request mistakes
Clear scope keeps the request usable for the client and for staff review.
Asking for “the processor report” without naming the report type.
Failing to list the applicable Merchant IDs.
Using a combined report that does not label each MID.
Requesting separate reports when one clearly labeled combined report is sufficient.
Omitting the exact start and end dates.
Failing to record the reporting timezone.
Mixing currencies without defining the expected output.
Treating a settlement summary as payout detail.
Treating a payout report as a bank statement.
Forgetting processing fees.
Forgetting refunds, disputes, or adjustments.
Requesting reserve data without naming the report period.
Treating an uploaded file as Received before staff review.
Sending reminders while the report is Pending review.
Closing every requested item when only one report was accepted.
Asking the client for processor passwords or MFA codes.
Claiming CollectCue connects to or retrieves processor reports.
Claiming CollectCue automatically reconciles payouts.
Giving reserve appeal or chargeback advice inside a document request checklist.
Publishing full Merchant IDs in public examples.
Connect the checklist to the document request workflow
The checklist defines what to request. These resources cover the related client action and review boundaries without changing the processor-report scope.
Turn the checklist into a client document request form and use the client document request workflow to keep client, period, and requested items connected. For a broader starting point, use the client document collection checklist.
Use a client upload for the requested items and document review before staff records a result. The automated reminders workflow applies only while an item still needs client action, not while it is pending staff review.
Use the checklist in a processor report request workflow
The steps organize a document request around client-provided reports. They do not connect to a processor, retrieve a report, or reconcile transactions.
- 1Define the account scopeRecord the processor account, selected MIDs, client or location context, currencies, responsible contact, and whether the output should be combined or separate.
- 2State the exact reporting periodUse a start date, end date, reporting timezone, and recurrence when relevant instead of asking for a vague recent or latest report.
- 3Create distinct requested itemsAdd settlement summary, payout detail, fee, refund, dispute, adjustment, and reserve reports as separate items when their source or review requirement differs.
- 4Review each upload in contextAn upload is pending review until staff accepts it for that item or requests a replacement. Received does not close other requested items automatically.
- 5Follow up on the next client actionFollow up on items waiting on the client or needing reupload. Keep reports pending staff review out of client reminders until staff records the next decision.
Payment processor report request checklist FAQ
These answers focus on asking for and reviewing client-provided processor reports. They do not provide accounting, tax, legal, reserve, chargeback, or processor risk advice.
What is a payment processor report request checklist?+
A payment processor report request checklist defines the merchant account scope, Merchant IDs, reporting period, timezone, currencies, requested report types, output format, and review owner for one client-period request.
What is a Merchant ID in a processor report request?+
A Merchant ID, or MID, is an identifier a processor uses for a merchant account, location, or processing setup. Record only the MID labels the firm needs for the requested scope; do not publish a real MID in a public example.
Should multiple Merchant IDs be included in one report?+
The firm decides. A combined report can fit when the selected MIDs share the same period and timezone and are clearly labeled. Separate reports can fit when locations, entities, currencies, or report periods differ.
What is the difference between a settlement summary and payout detail?+
A settlement summary can show period-level activity. Payout detail shows the composition and timing of one or more payouts. They are different requested items, and neither is the same as a bank statement or transaction-level settlement export.
Should processing fees be requested separately?+
The firm decides whether a separate processing fee report is needed. Processor report names vary, and one source report may include several categories. Use a plain-language request name that identifies the needed source and period.
What reserve reports may a bookkeeping firm request?+
A firm may request reserve balance, reserve activity, held-funds detail, reserve release activity, or another processor-provided reserve source report for a stated account scope, period, and currency. This checklist does not assess reserve terms or outcomes.
Should refunds and chargebacks be included?+
The firm decides which refund, dispute, chargeback, or adjustment reports are required. Keep them as separate requested items when their period, scope, or review action differs.
Is an uploaded processor report automatically received?+
No. An uploaded report is pending review until staff records a decision for that requested item. One accepted report does not complete every other requested item in the request.
Does CollectCue connect to payment processors?+
No. CollectCue does not connect to payment processors, retrieve processor reports, or map Merchant IDs. The firm defines the request scope and collects client-provided source records through its document request workflow.
Does CollectCue reconcile processor reports with bank statements?+
No. CollectCue does not reconcile processor reports with bank statements, calculate reserves, or manage chargebacks. These answers describe document collection and review workflow, not accounting, tax, legal, or financial advice.
Related source-report request resources
Use these focused resources when the request also needs an industry checklist, timing plan, bank-statement intake check, completion standard, or replacement-file workflow.
Subscription business bookkeeping document checklist
Use this broader industry checklist for billing, processor, bank, payroll, and expense inputs behind a subscription business.
Open resourceEcommerce bookkeeping document checklist
Use this broader checklist for marketplace, orders, inventory, fulfillment, processor, and returns sources.
Open resourceBookkeeping source report availability calendar
Plan when each source report normally becomes available before sending the client-period request.
Open resourceBank statement submission checklist
Use this when a bank or card statement needs its own period, file, coverage, and submission review.
Open resourceRequest completion criteria template
Define the evidence staff needs before marking one requested item as received.
Open resourceFile rejection and reupload checklist
Use this when staff needs a replacement because the uploaded file has the wrong source, period, scope, or readability.
Open resourceHow CollectCue fits
CollectCue helps small bookkeeping teams organize processor report requests by client, bookkeeping period, requested item, upload, staff review result, and reupload action. The firm decides which reports are required and how processor data should be interpreted. CollectCue does not connect to payment processors, retrieve settlement files, map Merchant IDs, calculate reserves, manage chargebacks, or reconcile payouts to bank activity.