Partial Exports and Truncated Venue Statements

An export's contents are read in the context of its perimeter. A clean CSV with neat totals can still cover only part of the period the file claims. The signal that something is missing is rarely inside the file; it is the gap between the date range printed on the export and the date range the engagement is supposed to cover.

DC-Services records the perimeter on the source page before classifying any row. The first row, the last row, the gaps within the range and the difference between the export's coverage and the engagement's coverage are part of the metadata. The reader sees the edges before the contents.

Some venues cap exports at a fixed row count and silently omit the older rows. Some default to the last twelve months unless the user explicitly extends the range. Some segment exports by sub-account and produce one file per account, with no warning when the user downloads only the default.

Each behaviour is reasonable as platform design and unreasonable as a basis for a documentation file that has not adjusted for it. The classification names the behaviour for what it is and records the cap, the default range or the sub-account coverage in plain language on the source page.

Truncation patterns include date-range truncation, row-count truncation, sub-account omission, transaction-type omission and currency-pair omission. Each pattern leaves a different footprint and requires a different remediation step. The file names the pattern and records the specific evidence supporting the classification.

Where the pattern is identifiable from the export itself — the last row hitting a round number that suggests a cap, the first row arriving mid-period without an opening balance — the evidence is recorded on the source page. Where the pattern is only confirmable by re-pulling the export with a different setting, the re-pull is requested and the response preserved.

Where the missing range can be requested from the venue, the request is preserved in the file with its date, the channel used and the response. A venue that produces the missing range allows the truncation to be closed; a venue that does not, or cannot, leaves the truncation as an unresolved matter rather than an undocumented one.

Verification of the augmented file requires re-running the integrity checks. The combined coverage of the original export and the supplementary range is recorded as the new perimeter, with both sources cited. The file does not treat the supplementary range as if it had been part of the original export.

Some venues purge older data on a published schedule, retain it only in aggregate, or have been wound up entirely. Where the missing range cannot be reconstructed, the file records the absence as an unresolved matter and identifies the period the file does not cover.

Calculations against the available range are labelled as such. A balance summary derived from a partial export is not stated as a position for the engagement period; it is stated as a position for the export's actual period, with the gap to the engagement period named on the same page.

Ownership indicators derived from a partial export apply only to the period the export covers. A venue's KYC attribution recorded inside the range does not extend, on the strength of that record alone, to the period outside it. The file states the temporal scope of each ownership indicator.

Transfer continuity breaks at the truncation boundary. A transfer present in the partial export with no visible counterpart on the missing side is documented as a single-sided observation rather than a continuity finding. The file does not infer the other side from the existence of this one.

Each source page begins with the export's actual range, the user-stated intended range, the gap between the two, and the steps taken to close the gap. The metadata is in the same view as the contents, so a reviewer does not have to look elsewhere to know what they are reading.

The summary at the front of the file lists every partial source by name, its coverage and the residual gap. A reviewer reading the summary knows the file's coverage limits before reading the body, which is the only honest way to present a position drawn from imperfect inputs.

Where the missing range can be requested, the framework specifies the request: the venue's channel, the data required, the date by which the response is needed for the file to be useful. The request is preserved in the file as part of the audit trail.

Where the missing range cannot be requested, the framework identifies alternative sources that may carry equivalent evidential weight: counterparty records on the receiving side, chain records for self-custody movements, contemporaneous correspondence. Each alternative is named with its evidential limits.