CSV date order: resolve DMY and MDY before mapping
How to declare date order in a custom USD CSV mapping so an ambiguous but calendar-valid date is interpreted consistently.
Why date order matters
A numeric date such as 03/04/2026 can represent different calendar dates depending on the source convention. A date parser can confirm that a result is a real calendar date, but cannot infer which valid interpretation the source intended. Record the source date order before mapping its columns.
An invented ambiguous date
The invented date 03/04/2026 means 2026-04-03 under DMY and 2026-03-04 under MDY. Both are calendar-valid; validity alone cannot establish the intended date. Declare the source date order before mapping. Never guess the correct date from a total.
What the mapping declares
The offline mapping example uses a declared profile: its headers and column names, date order (DMY, MDY, or YMD), pair layout, whether the amount is gross before costs or net after costs, fee sign convention, USD currency, and closed status. The mapping requires the CSV header to match the profile exactly; it does not guess columns or formats. Invalid dates are rejected, not inferred or repaired.
Scope and totals
This mapping is USD-only, for rows that are already closed and aggregated. It does no currency conversion and no fill matching. It reports accepted-only totals; rejected rows are excluded, and duplicate source IDs cause all occurrences to be rejected. Check rejected rows before interpreting a total. The separate fixed checker instead accepts its exact date,pair,gross,costs,notes header, ISO dates and other stated rules on its tool page.
Choosing a next step
To check whether the fixed checker format fits, review the USD CSV checker. For a different layout, download the format request checklist and describe the columns, intended date order, currency, amount and fee meanings, and closed-row structure through the CSV format contact link. Use invented examples only; do not send trading files, records, identifiers or credentials. The offline mapping is one fixed example of a declared configuration, not an arbitrary broker importer. An inquiry does not place an order or establish custom delivery availability, price, scope or timing.
Keep the interpretation explicit
Keep the declared date order with the mapping and retain the source file privately for your own review. If the source format does not make date order clear, ask its provider what convention it uses before mapping; do not decide from totals or trading outcomes.
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 ↗