Which records should I keep to investigate a marketplace payout discrepancy?

Start by identifying the two things being compared

A payout discrepancy often begins with an imprecise question: sales were higher, so why was the deposit lower? Specify the two values, their date ranges, currencies, and definitions. Gross order value for a calendar week is not directly comparable to a payout containing transactions settled during a different period.

Record the expected amount, the observed amount, and the source of each. If the expected value came from a spreadsheet, preserve the calculation and input files. If the observed amount came from a bank entry, keep the bank reference and date alongside the platform payout identifier. This first step can reveal that the issue is a timing or scope difference before anyone starts investigating individual orders.

Preserve the original transaction identity

An order can generate several financial events: an initial payment, a partial refund, an adjustment, a fee, or a later dispute-related entry. Keep the platform's transaction references as well as the order reference. The same order number alone may not identify which event explains a particular settlement line.

Link these references to any corresponding store order without replacing the original marketplace identity. A marketplace-managed payment may appear differently from a payment captured directly through your store. When you investigate a difference, the original financial record is the starting point. A convenient operational summary is helpful for navigation, but it should not be treated as a substitute for the transaction detail supplied by the platform that handled the money.

Keep amounts separated by their meaning

Store product amounts, discounts, shipping, taxes, fees, refunds, and adjustments in distinct fields when the source provides them. Record currency explicitly. A total that blends several components makes it difficult to explain why an order's selling price differs from the contribution it makes to a payout.

For a simple fictional example, a settlement may contain 1,000 in charges, 50 in refunds, 100 in fees, and a 20 adjustment, producing 830 before any other entries. Those figures are illustrative, not a marketplace fee schedule. The useful point is that each component has an identity and a sign. Keep the source description of an unfamiliar adjustment so the person investigating can ask a precise question rather than guessing its purpose.

Distinguish transaction time from payout time

Keep the time an order was placed, the time the payment event occurred, the time it entered settlement, and the payout date when those are available. These timestamps answer different questions. An order near midnight may fall into one operational day and another reporting period depending on the platform's time zone.

Shopify Payments documentation separates payout details from pending transactions and provides exports for investigation. Other marketplaces use their own settlement structures and schedules. Review the definitions in the source report before matching by date. If you normalize timestamps into a common time zone for analysis, preserve the original value and zone too. That makes it possible to explain differences without permanently losing the platform's reporting context.

Save source exports in an orderly, access-controlled place

Keep the original export used for the investigation, with a clear filename that identifies the platform, account, report type, date range, and export date. Avoid editing the only copy. Work from a separate analysis file so another person can reproduce the comparison from the same input.

Limit access according to the information the file contains and your business's retention practices. A payout investigation does not justify collecting unrelated customer details. Record where the authoritative file is stored rather than attaching copies to every chat thread. When an export is regenerated, preserve enough version context to know whether it contains later adjustments. Two files with the same reporting period may not be identical if one was produced after additional activity was posted.

Create an exception list with a reason for each difference

Match records using stable references where possible, then classify the unmatched items. Useful categories include timing difference, missing transaction, unmatched refund, unexpected fee, currency mismatch, duplicate import, and unexplained adjustment. Keep unresolved items separate from differences that have been explained but not yet reflected in a later payout.

For each exception, record the amount, source references, evidence reviewed, owner, and next action. If you contact a platform, include the exact payout and transaction identifiers rather than sending only a screenshot of a total. A well-formed question makes the support conversation more efficient. It also keeps the team from opening several cases for the same difference while the first investigation is still underway.

For example, an unmatched negative entry should remain a specific question until its source is understood. Record the platform's description exactly in your working evidence, connect any supplied order or transaction reference, and check whether a later report adds more detail. Do not immediately classify it as a fee because that category makes the totals reconcile. A temporary unexplained category is more honest and easier to investigate than a confident but unsupported label. Once the cause is confirmed, update the classification and retain the evidence used. This makes the resolution reproducible for a colleague who did not participate in the original support conversation.

Reconcile changes across periods without erasing history

Some differences resolve in a later settlement rather than changing the original payout. Keep a link between the original exception and the later correcting transaction. Mark the outcome and the evidence that supports it. Do not simply overwrite the earlier number until the spreadsheet looks balanced.

Shopify's Payments activity report is an example of a period-based view that groups balance activity separately from individual payout detail. Use the appropriate source view for the question you are answering. Your operational reconciliation should make the movement understandable; formal accounting treatment belongs with your finance process. Clear event history helps both tasks by preserving what happened, when it happened, and which later entry resolved the original question.

Make the next investigation easier than the last

After resolving a case, identify which missing record or unclear definition made the work slow. Perhaps the original channel transaction ID was absent, the time zone was not recorded, or a fee category was imported as a generic adjustment. Improve that part of the record before the next reporting cycle.

Keep a short reconciliation guide for each platform with the relevant report names, identifiers, and normal timing considerations. Review a sample periodically to confirm that the guide still matches the current exports. The goal is not to create an enormous financial archive without purpose. It is to retain the right evidence so a future discrepancy can be explained through a clear sequence of records instead of a fresh search through every dashboard.