In this article
A downloaded CSV is a useful starting point. A reconciliation adds a defined scope, a comparison, an explanation of differences and a record of what remains open.
What the official export guide establishes
Real documents CSV transaction reports for closed, pending and terminated activity, with a selectable reporting period. Its guide gives examples of information such as commission amounts, dates, fees and payout measures. It does not make every exported number equivalent to cash received, and this article does not promise a fixed column schema for every account or future export.
Our method begins after an authorized reader obtains the relevant report. It is an editorial approach to understanding a file, not a substitute for current product instructions or professional accounting advice. Keep the original download unchanged, then make a working copy in the protected location appropriate to your business. This publication does not accept uploads or inspect your records.
Write the scope before opening a formula
Record which report category you chose, the requested date range, when the export was generated and what question you intend to answer. A calendar-month reconciliation and a cap-cycle review are different projects. A pending report and a closed report are different populations. State those distinctions before combining anything.
Also note what the report does not establish. A closed-transaction population may be useful for reviewing activity, but a separate source can be needed for payment timing. An exported amount with a tax-related label does not independently settle your individual filing treatment. A scope note prevents a spreadsheet from acquiring authority beyond the question it was meant to support.
Inspect structure before totals
Check that the file opened with separate columns, readable dates and intact identifiers. Spreadsheet software can reinterpret some values when importing text. Preserve the source file so that a display change can be distinguished from a source change. If a field looks unexpected, inspect the import method before assuming the system exported bad data.
Count the apparent records and look for blank rows, repeated headings or summary rows that should not be treated as ordinary transactions. Do not assume one row equals one unique transaction until the report's structure supports that interpretation. A count is useful only when you know what is being counted.
Create a small field dictionary
A field dictionary explains how your working file uses a column. For each relevant field, note the original heading, the meaning supported by the source, the format and the intended comparison. Keep an “unconfirmed meaning” label when necessary. Do not turn a guess into a definition by giving it a polished heading.
For example, your working notes might identify an original date field as “date shown by export; basis needs confirmation,” rather than immediately renaming it “cash received.” A transaction reference can be used for matching only after you know whether it is stable and sufficiently specific. These are proposed review practices, not claims that reZEN provides columns with these exact names.
Match records before matching totals
A total can agree even when the wrong records are included. Two omitted values can offset an unrelated extra value. Begin by checking the population: which source records belong in the comparison, which are present and which appear more than once. Only then compare the relevant amounts.
Keep a separate exceptions list for a missing record, an apparent duplicate, a date-basis question or an unexplained difference. Do not delete a row from the working file just because it seems inconvenient. Mark why it is excluded from a particular calculation, and retain a way to trace that decision back to the unmodified source.
A fictional month-end example
A fictional agent exports closed activity for one month and compares it with a private register. The export contains six rows; the register lists five transaction references. That does not automatically mean there is an extra transaction. The first task is to understand whether the report can contain more than one row associated with a transaction or another kind of detail.
After examining the structure, the agent finds that one register entry used a shortened reference and two records were mistakenly treated as one. The population question is resolved before the arithmetic review begins. In another month, the same initial symptom might have a different cause. The method asks for evidence instead of making a universal diagnosis from the row count.
Classify differences by type
Use a few clear categories: population, timing, interpretation, version or unexplained amount. A population difference concerns which records belong. A timing difference concerns which period or date basis is being used. An interpretation difference concerns what a field means. A version difference concerns a changed source. An unexplained amount remains open until supported evidence clarifies it.
The categories are not excuses to ignore a discrepancy. They make the next action more precise. A date-basis question needs a different investigation from an arithmetic difference on a single statement. Assign each exception a person or authorized route, a next step and a review date appropriate to the business need.
Avoid formulas that hide uncertainty
A formula that replaces blanks with zero may make a total look complete while concealing missing information. A lookup that returns the first match may hide duplicates. A manually typed adjustment can conceal the original difference. Use clear labels and review outputs that show these conditions rather than silently absorbing them.
This article does not prescribe a particular spreadsheet product or formula syntax. The control principle is simpler: a reviewer should be able to tell which values came from a source, which were calculated and which remain unknown. If the spreadsheet cannot make that distinction visible, simplify it before relying on its results.
Close with an exception summary
A reconciliation result should state the scope, the checks performed, the explained differences and the unresolved items. “Total matched” is not enough if the population was never checked. “Complete except for one version question assigned for review” may be an honest and useful conclusion.
Save the working file and summary according to the applicable business process. Do not set a universal retention period from this article. The IRS general recordkeeping page explains the importance of supporting records; an accountant can advise which materials and treatment apply to your circumstances. Use the year-end packet guide to make that professional handoff clearer, without turning a monthly operational check into tax advice.
Source notes
Public sources checked October 22, 2026. Product facts are attributed to the official references below. Review methods and fictional examples are original editorial analysis, not a private-account test or an official Real procedure. Current terms and product details can change. General information only, not tax, investment, legal or individual financial advice.