Save CSV reconciliation counts without exporting trade details
Learn what the CSV Journal Checker reports, how accepted-only totals and row rejection reasons work, and how to describe a different CSV layout using invented examples.
What the report contains
The checker processes a selected UTF-8 CSV in your browser. Its JSON reconciliation report contains the number of input rows, accepted rows and rejected rows, accepted-rows-only USD totals in integer cents, and each rejected CSV row number with its reason. It does not include raw notes, pairs, source IDs or the input filename. Downloading the report saves it on your device; avoid sharing it if row-level rejection details are sensitive.
Three input rows produce two accepted and one rejected; accepted gross 8,015 cents minus 290 cents costs is 7,725 cents net, and rejected CSV record 4 is separately identified.
Open full-size diagram ↗Fixed checker requirements
The fixed format uses exactly these columns in order: date,pair,gross,costs,notes. It accepts real YYYY-MM-DD dates, uppercase AAA/BBB pairs, USD-only amounts written with dot decimals and at most two decimal places, and nonnegative costs. Gross is before costs; net is gross minus costs. Rows must already be closed and aggregated: one row per trade. There is no currency conversion or fill matching. The file limit is 1 MiB and 1,000 data rows. A rejected row is excluded from accepted-only totals, so those totals are not full-file totals.
An invented reconciliation report
Three invented rows contain two valid closed USD trades and one invalid date. The valid rows have gross USD 120.35 with costs USD 2.10, and gross USD -40.20 with costs USD 0.80. The report records 3 input rows, 2 accepted and 1 rejected; accepted-only gross is 8015 cents, costs 290 cents and net 7725 cents. The invalid third data row is CSV row 4. No raw notes, pairs or input filename appear in this report.
When your CSV has a different layout
The checker uses a fixed header and fixed amount and date rules; it does not guess columns or formats. The separate mapping code describes a declared custom mapping with explicit headers, date and pair formats, amount meaning, fee sign and closed status. It requires USD and rejects duplicate source IDs rather than selecting a winner. This describes supported mapping behavior, not a promise that a custom mapping is available, ordered or priced. Do not send actual trading files, records, account identifiers or credentials.
Choose a next step
Use the CSV Journal Checker page to review the fixed format and its local report. If it does not fit, use the CSV format request instructions and describe the structure with exactly three invented rows, or contact us through the CSV format fit form. No purchase is required; no quote, availability, automatic reply or response time is promised.
Sources and conventions
Examples are hypothetical. Arithmetic follows the formulas documented in our methodology. Broker contract specifications determine actual lot, margin and execution conditions. These sources document definitions and data; a source link does not imply endorsement of SanForex or a trading service.
These materials are prepared with AI assistance and checked against worked examples and deterministic calculation tests where applicable. They are not an expert suitability assessment or investment advice.
Open trade csv checker tool ↗