Insight brief
Export checks before tax review
A practical brief on comparing platform exports with payer forms and deposit trails.
The mismatch is normal
Platform exports often include fees, refunds, reserve releases, and timing differences that do not appear the same way on payer forms or bank downloads. The point of an export check is not to decide which number belongs on a return. It is to make the conflict visible before professional review.
The first pass should preserve the raw export and a readable working copy. The packet should identify the platform, download date, date range, and any filters used during export. Those details are often the difference between a useful comparison and a row count that cannot be repeated.
What to compare
A useful check compares date range, payer name, gross amounts, fees, refunds, deposits, and year labels. If an export covers a different period than the form, the packet should say so. If a deposit appears twice, the duplicate should be marked rather than deleted silently.
Bank deposits are useful, but they are not the whole story. Fees, reserves, refunds, chargebacks, and payout timing can make a deposit trail look different from a gross platform report. The packet should describe that difference plainly and avoid forcing a silent reconciliation.
How to write the note
The note should name the files compared, the rows that conflict, and the question that remains. A short plain note is better than a spreadsheet that hides every uncertainty behind a finished total.
The note should be short enough to read before opening the spreadsheet. It can say which files were compared, which rows or periods need attention, and what question remains for the owner or later reviewer. The spreadsheet then supports the note instead of replacing it.
When to stop
Stop when the source trail is organized enough for a qualified reviewer to evaluate. Do not turn an unresolved export conflict into a filing conclusion.
The stopping point is a visible conflict list. If the conflict cannot be resolved from the records at hand, the packet should say that and preserve the files that produced the question.
Export comparison checklist
Start with the unedited platform export, the payer form, the deposit download, and any client statement that covers the same period. Add a short source note for each file. The note should include file name, date range, account or platform, and whether the file appears complete.
Then compare the records in layers. First check whether the years match. Next check whether gross rows, fees, and refunds are separated or blended. Finally check whether payouts are grouped by transaction date, settlement date, or bank deposit date. The point is not to make the records agree. The point is to understand why they do not.
Question-ledger language
Good export questions are specific. Write “April payout rows appear in the platform export but not in the bank download” instead of “income mismatch.” Write “Form total includes gross amount before platform fees” instead of “1099 wrong.” Specific wording helps the owner gather the missing source or explain the timing difference.
The ledger should also identify when the question belongs to a later professional review. A record-prep packet can show the conflict and the source files. It should not turn that conflict into a tax position.
What not to overwrite
Do not overwrite the original export after cleaning rows. Keep the raw file, then make a working copy for comments or filters. The raw file is the source reference; the working copy is the review aid. If only the working copy remains, later readers may not be able to repeat the comparison.
Also avoid replacing a conflict with a single “corrected” total. A corrected total may be useful later, but the record-prep packet should show how the number was built and where the source conflict appeared.
Readable handoff note
A good handoff note might say that the platform export covers January through December, the payer form reports a gross annual amount, and the bank download shows net deposits after fees. It then names the rows or months that need review. That level of detail gives the next reviewer enough context without forcing them to inspect every file first.
The note should be placed near the comparison sheet, not buried in a general remarks file. Source conflicts are easiest to review when the note and evidence live together.