Channel source lineage and reconciliation

Source contracts

CSV, TSV, and Excel are one-time source snapshots. A selected Google Sheets range creates a new immutable snapshot on refresh. InSales polling and Store API batches create versioned source receipts. Every path keeps workspace, source, revision, period, mapping, validation result, checksum or signature state, and commit status separate from the resulting financial rows.

Publication rule

Financial rows are published only after accepted mapping, validation, duplicate controls, and explicit commit or processor qualification. accepted_for_processing is not published. A cart event is an observation. Marketplace actual profit also requires a current independent evidence qualification for the exact account, period, currency, fingerprint, and tolerance.

Unavailable state and example

If a snapshot is stale, a signature fails, a revision is superseded, mapping is incomplete, or reconciliation evidence is absent, dependent metrics remain unavailable or explicitly partial rather than zero.

Example: an Excel import contains 100 accepted paid lines and two rejected returns. The observed paid revenue can be shown with an incomplete-return warning; fully loaded profit remains unavailable until the return and required cost evidence are corrected and reconciled.