Seller Profit Guard

Where should multi-channel currency data come from?

Last updated: 2026-08-09

Written and reviewed by Seller Profit Guard Editorial Team.

Use platform transaction or payout records for source and payout amounts, order timelines for applied rates, official help for definitions and fee bases, aggregate refund records for reversals, bank statements for any second conversion, seller ledgers for base-currency costs, and dated owner-review records for accepted assumptions and restoration.

Reliable Multi-Channel Currency Data Sources flow from currency roles and timestamped evidence to normalized contribution, decision, and restoration
Use the currency evidence map to normalize matched closed currency cohorts.

Transaction record

Use platform transaction or payout records for source and payout amounts, order timelines for applied rates, official help for definitions and fee bases, aggregate refund records for reversals, bank statements for any second conversion, seller ledgers for base-currency costs, and dated owner-review records for accepted assumptions and restoration. Record source owner, report, access date, data-through date, currency roles, grain, exclusions, and accepted version. Checkpoint 1 in the currency evidence map records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For transaction record, keep gross source amount, deductions, fee percentage and base, exchange-rate direction, timestamp, normalized revenue, base costs, retained orders, target, conflict, backup, stop rule, and restoration separate.

Use invented or approved aggregate values only. Exclude private emails, buyer identities, addresses, order rows, account IDs, payment details, bank records, credentials, private invoices, campaign identifiers, and raw exports from the public currency evidence map.

Order timeline

Use platform transaction or payout records for source and payout amounts, order timelines for applied rates, official help for definitions and fee bases, aggregate refund records for reversals, bank statements for any second conversion, seller ledgers for base-currency costs, and dated owner-review records for accepted assumptions and restoration. Record source owner, report, access date, data-through date, currency roles, grain, exclusions, and accepted version. Checkpoint 2 in the currency evidence map records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For order timeline, keep gross source amount, deductions, fee percentage and base, exchange-rate direction, timestamp, normalized revenue, base costs, retained orders, target, conflict, backup, stop rule, and restoration separate.

Use invented or approved aggregate values only. Exclude private emails, buyer identities, addresses, order rows, account IDs, payment details, bank records, credentials, private invoices, campaign identifiers, and raw exports from the public currency evidence map.

Payout statement

Use platform transaction or payout records for source and payout amounts, order timelines for applied rates, official help for definitions and fee bases, aggregate refund records for reversals, bank statements for any second conversion, seller ledgers for base-currency costs, and dated owner-review records for accepted assumptions and restoration. Record source owner, report, access date, data-through date, currency roles, grain, exclusions, and accepted version. Checkpoint 3 in the currency evidence map records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For payout statement, keep gross source amount, deductions, fee percentage and base, exchange-rate direction, timestamp, normalized revenue, base costs, retained orders, target, conflict, backup, stop rule, and restoration separate.

Use invented or approved aggregate values only. Exclude private emails, buyer identities, addresses, order rows, account IDs, payment details, bank records, credentials, private invoices, campaign identifiers, and raw exports from the public currency evidence map.

Official fee definition

Use platform transaction or payout records for source and payout amounts, order timelines for applied rates, official help for definitions and fee bases, aggregate refund records for reversals, bank statements for any second conversion, seller ledgers for base-currency costs, and dated owner-review records for accepted assumptions and restoration. Record source owner, report, access date, data-through date, currency roles, grain, exclusions, and accepted version. Checkpoint 4 in the currency evidence map records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For official fee definition, keep gross source amount, deductions, fee percentage and base, exchange-rate direction, timestamp, normalized revenue, base costs, retained orders, target, conflict, backup, stop rule, and restoration separate.

Use invented or approved aggregate values only. Exclude private emails, buyer identities, addresses, order rows, account IDs, payment details, bank records, credentials, private invoices, campaign identifiers, and raw exports from the public currency evidence map.

Refund record

Use platform transaction or payout records for source and payout amounts, order timelines for applied rates, official help for definitions and fee bases, aggregate refund records for reversals, bank statements for any second conversion, seller ledgers for base-currency costs, and dated owner-review records for accepted assumptions and restoration. Record source owner, report, access date, data-through date, currency roles, grain, exclusions, and accepted version. Checkpoint 5 in the currency evidence map records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For refund record, keep gross source amount, deductions, fee percentage and base, exchange-rate direction, timestamp, normalized revenue, base costs, retained orders, target, conflict, backup, stop rule, and restoration separate.

Use invented or approved aggregate values only. Exclude private emails, buyer identities, addresses, order rows, account IDs, payment details, bank records, credentials, private invoices, campaign identifiers, and raw exports from the public currency evidence map.

currency evidence map: refund record
Original explanatory diagram for refund record using invented aggregate values and no private seller data.

Chargeback record

Use platform transaction or payout records for source and payout amounts, order timelines for applied rates, official help for definitions and fee bases, aggregate refund records for reversals, bank statements for any second conversion, seller ledgers for base-currency costs, and dated owner-review records for accepted assumptions and restoration. Record source owner, report, access date, data-through date, currency roles, grain, exclusions, and accepted version. Checkpoint 6 in the currency evidence map records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For chargeback record, keep gross source amount, deductions, fee percentage and base, exchange-rate direction, timestamp, normalized revenue, base costs, retained orders, target, conflict, backup, stop rule, and restoration separate.

Use invented or approved aggregate values only. Exclude private emails, buyer identities, addresses, order rows, account IDs, payment details, bank records, credentials, private invoices, campaign identifiers, and raw exports from the public currency evidence map.

Bank conversion

Use platform transaction or payout records for source and payout amounts, order timelines for applied rates, official help for definitions and fee bases, aggregate refund records for reversals, bank statements for any second conversion, seller ledgers for base-currency costs, and dated owner-review records for accepted assumptions and restoration. Record source owner, report, access date, data-through date, currency roles, grain, exclusions, and accepted version. Checkpoint 7 in the currency evidence map records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For bank conversion, keep gross source amount, deductions, fee percentage and base, exchange-rate direction, timestamp, normalized revenue, base costs, retained orders, target, conflict, backup, stop rule, and restoration separate.

Use invented or approved aggregate values only. Exclude private emails, buyer identities, addresses, order rows, account IDs, payment details, bank records, credentials, private invoices, campaign identifiers, and raw exports from the public currency evidence map.

Base-cost ledger

Use platform transaction or payout records for source and payout amounts, order timelines for applied rates, official help for definitions and fee bases, aggregate refund records for reversals, bank statements for any second conversion, seller ledgers for base-currency costs, and dated owner-review records for accepted assumptions and restoration. Record source owner, report, access date, data-through date, currency roles, grain, exclusions, and accepted version. Checkpoint 8 in the currency evidence map records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For base-cost ledger, keep gross source amount, deductions, fee percentage and base, exchange-rate direction, timestamp, normalized revenue, base costs, retained orders, target, conflict, backup, stop rule, and restoration separate.

Use invented or approved aggregate values only. Exclude private emails, buyer identities, addresses, order rows, account IDs, payment details, bank records, credentials, private invoices, campaign identifiers, and raw exports from the public currency evidence map.

Source version

Use platform transaction or payout records for source and payout amounts, order timelines for applied rates, official help for definitions and fee bases, aggregate refund records for reversals, bank statements for any second conversion, seller ledgers for base-currency costs, and dated owner-review records for accepted assumptions and restoration. Record source owner, report, access date, data-through date, currency roles, grain, exclusions, and accepted version. Checkpoint 9 in the currency evidence map records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For source version, keep gross source amount, deductions, fee percentage and base, exchange-rate direction, timestamp, normalized revenue, base costs, retained orders, target, conflict, backup, stop rule, and restoration separate.

Use invented or approved aggregate values only. Exclude private emails, buyer identities, addresses, order rows, account IDs, payment details, bank records, credentials, private invoices, campaign identifiers, and raw exports from the public currency evidence map.

Owner and restore record

Use platform transaction or payout records for source and payout amounts, order timelines for applied rates, official help for definitions and fee bases, aggregate refund records for reversals, bank statements for any second conversion, seller ledgers for base-currency costs, and dated owner-review records for accepted assumptions and restoration. Record source owner, report, access date, data-through date, currency roles, grain, exclusions, and accepted version. Checkpoint 10 in the currency evidence map records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For owner and restore record, keep gross source amount, deductions, fee percentage and base, exchange-rate direction, timestamp, normalized revenue, base costs, retained orders, target, conflict, backup, stop rule, and restoration separate.

Use invented or approved aggregate values only. Exclude private emails, buyer identities, addresses, order rows, account IDs, payment details, bank records, credentials, private invoices, campaign identifiers, and raw exports from the public currency evidence map.

Transaction record: verification test 1

Create one synthetic counterexample for transaction record. Change a single currency, amount, deduction, fee-base, rate, timestamp, refund, base-cost, retained-order, or threshold field; retain the prior packet; and show the normalized-revenue, contribution, margin, per-order, rate-gap, and Block, Review, or Ready effect.

Reconcile the counterexample against first-party transaction, order-timeline, payout, refund, chargeback, bank-conversion, base-cost, official-definition, source-version, owner, reviewer, protected-baseline, stop-trigger, and restored-result evidence.

Explain why the test does not prove a future rate, hedging value, timing advantage, channel superiority, demand, conversion, lifetime value, cash availability, accounting income, functional currency, tax treatment, or legal compliance.

Order timeline: verification test 2

Create one synthetic counterexample for order timeline. Change a single currency, amount, deduction, fee-base, rate, timestamp, refund, base-cost, retained-order, or threshold field; retain the prior packet; and show the normalized-revenue, contribution, margin, per-order, rate-gap, and Block, Review, or Ready effect.

Reconcile the counterexample against first-party transaction, order-timeline, payout, refund, chargeback, bank-conversion, base-cost, official-definition, source-version, owner, reviewer, protected-baseline, stop-trigger, and restored-result evidence.

Explain why the test does not prove a future rate, hedging value, timing advantage, channel superiority, demand, conversion, lifetime value, cash availability, accounting income, functional currency, tax treatment, or legal compliance.

Payout statement: verification test 3

Create one synthetic counterexample for payout statement. Change a single currency, amount, deduction, fee-base, rate, timestamp, refund, base-cost, retained-order, or threshold field; retain the prior packet; and show the normalized-revenue, contribution, margin, per-order, rate-gap, and Block, Review, or Ready effect.

Reconcile the counterexample against first-party transaction, order-timeline, payout, refund, chargeback, bank-conversion, base-cost, official-definition, source-version, owner, reviewer, protected-baseline, stop-trigger, and restored-result evidence.

Explain why the test does not prove a future rate, hedging value, timing advantage, channel superiority, demand, conversion, lifetime value, cash availability, accounting income, functional currency, tax treatment, or legal compliance.

Official fee definition: verification test 4

Create one synthetic counterexample for official fee definition. Change a single currency, amount, deduction, fee-base, rate, timestamp, refund, base-cost, retained-order, or threshold field; retain the prior packet; and show the normalized-revenue, contribution, margin, per-order, rate-gap, and Block, Review, or Ready effect.

Reconcile the counterexample against first-party transaction, order-timeline, payout, refund, chargeback, bank-conversion, base-cost, official-definition, source-version, owner, reviewer, protected-baseline, stop-trigger, and restored-result evidence.

Explain why the test does not prove a future rate, hedging value, timing advantage, channel superiority, demand, conversion, lifetime value, cash availability, accounting income, functional currency, tax treatment, or legal compliance.

Refund record: verification test 5

Create one synthetic counterexample for refund record. Change a single currency, amount, deduction, fee-base, rate, timestamp, refund, base-cost, retained-order, or threshold field; retain the prior packet; and show the normalized-revenue, contribution, margin, per-order, rate-gap, and Block, Review, or Ready effect.

Reconcile the counterexample against first-party transaction, order-timeline, payout, refund, chargeback, bank-conversion, base-cost, official-definition, source-version, owner, reviewer, protected-baseline, stop-trigger, and restored-result evidence.

Explain why the test does not prove a future rate, hedging value, timing advantage, channel superiority, demand, conversion, lifetime value, cash availability, accounting income, functional currency, tax treatment, or legal compliance.

currency evidence map: refund record: verification test 5
Original explanatory diagram for refund record: verification test 5 using invented aggregate values and no private seller data.

Chargeback record: verification test 6

Create one synthetic counterexample for chargeback record. Change a single currency, amount, deduction, fee-base, rate, timestamp, refund, base-cost, retained-order, or threshold field; retain the prior packet; and show the normalized-revenue, contribution, margin, per-order, rate-gap, and Block, Review, or Ready effect.

Reconcile the counterexample against first-party transaction, order-timeline, payout, refund, chargeback, bank-conversion, base-cost, official-definition, source-version, owner, reviewer, protected-baseline, stop-trigger, and restored-result evidence.

Explain why the test does not prove a future rate, hedging value, timing advantage, channel superiority, demand, conversion, lifetime value, cash availability, accounting income, functional currency, tax treatment, or legal compliance.

Bank conversion: verification test 7

Create one synthetic counterexample for bank conversion. Change a single currency, amount, deduction, fee-base, rate, timestamp, refund, base-cost, retained-order, or threshold field; retain the prior packet; and show the normalized-revenue, contribution, margin, per-order, rate-gap, and Block, Review, or Ready effect.

Reconcile the counterexample against first-party transaction, order-timeline, payout, refund, chargeback, bank-conversion, base-cost, official-definition, source-version, owner, reviewer, protected-baseline, stop-trigger, and restored-result evidence.

Explain why the test does not prove a future rate, hedging value, timing advantage, channel superiority, demand, conversion, lifetime value, cash availability, accounting income, functional currency, tax treatment, or legal compliance.

Base-cost ledger: verification test 8

Create one synthetic counterexample for base-cost ledger. Change a single currency, amount, deduction, fee-base, rate, timestamp, refund, base-cost, retained-order, or threshold field; retain the prior packet; and show the normalized-revenue, contribution, margin, per-order, rate-gap, and Block, Review, or Ready effect.

Reconcile the counterexample against first-party transaction, order-timeline, payout, refund, chargeback, bank-conversion, base-cost, official-definition, source-version, owner, reviewer, protected-baseline, stop-trigger, and restored-result evidence.

Explain why the test does not prove a future rate, hedging value, timing advantage, channel superiority, demand, conversion, lifetime value, cash availability, accounting income, functional currency, tax treatment, or legal compliance.

Source version: verification test 9

Create one synthetic counterexample for source version. Change a single currency, amount, deduction, fee-base, rate, timestamp, refund, base-cost, retained-order, or threshold field; retain the prior packet; and show the normalized-revenue, contribution, margin, per-order, rate-gap, and Block, Review, or Ready effect.

Reconcile the counterexample against first-party transaction, order-timeline, payout, refund, chargeback, bank-conversion, base-cost, official-definition, source-version, owner, reviewer, protected-baseline, stop-trigger, and restored-result evidence.

Explain why the test does not prove a future rate, hedging value, timing advantage, channel superiority, demand, conversion, lifetime value, cash availability, accounting income, functional currency, tax treatment, or legal compliance.

Owner and restore record: verification test 10

Create one synthetic counterexample for owner and restore record. Change a single currency, amount, deduction, fee-base, rate, timestamp, refund, base-cost, retained-order, or threshold field; retain the prior packet; and show the normalized-revenue, contribution, margin, per-order, rate-gap, and Block, Review, or Ready effect.

Reconcile the counterexample against first-party transaction, order-timeline, payout, refund, chargeback, bank-conversion, base-cost, official-definition, source-version, owner, reviewer, protected-baseline, stop-trigger, and restored-result evidence.

Explain why the test does not prove a future rate, hedging value, timing advantage, channel superiority, demand, conversion, lifetime value, cash availability, accounting income, functional currency, tax treatment, or legal compliance.

Reliable Multi-Channel Currency Data Sources: evidence exercise 1

Reperform transaction record with invented same-day and delayed-payout cohorts. Hold source and base currency roles, gross amount, deduction definition, fee base, base costs, retained-order definition, rounding, and evidence controls constant where comparison requires them.

Archive the accepted packet before varying the field. Explain the resulting net source amount, conversion fee, normalized revenue, base costs, contribution, margin, per-order contribution, A-minus-B difference, rate gap, decision, monitoring trigger, and restoration path.

The exercise remains educational and source-linked. It does not fetch a live rate, recommend a transfer or hedge, predict a currency, approve a channel, determine accounting or tax treatment, or replace market-, region-, plan-, payment-, platform-, bank-, contract-, or professional review.

Reliable Multi-Channel Currency Data Sources: evidence exercise 2

Reperform order timeline with invented same-day and delayed-payout cohorts. Hold source and base currency roles, gross amount, deduction definition, fee base, base costs, retained-order definition, rounding, and evidence controls constant where comparison requires them.

Archive the accepted packet before varying the field. Explain the resulting net source amount, conversion fee, normalized revenue, base costs, contribution, margin, per-order contribution, A-minus-B difference, rate gap, decision, monitoring trigger, and restoration path.

The exercise remains educational and source-linked. It does not fetch a live rate, recommend a transfer or hedge, predict a currency, approve a channel, determine accounting or tax treatment, or replace market-, region-, plan-, payment-, platform-, bank-, contract-, or professional review.

Reliable Multi-Channel Currency Data Sources: evidence exercise 3

Reperform payout statement with invented same-day and delayed-payout cohorts. Hold source and base currency roles, gross amount, deduction definition, fee base, base costs, retained-order definition, rounding, and evidence controls constant where comparison requires them.

Archive the accepted packet before varying the field. Explain the resulting net source amount, conversion fee, normalized revenue, base costs, contribution, margin, per-order contribution, A-minus-B difference, rate gap, decision, monitoring trigger, and restoration path.

The exercise remains educational and source-linked. It does not fetch a live rate, recommend a transfer or hedge, predict a currency, approve a channel, determine accounting or tax treatment, or replace market-, region-, plan-, payment-, platform-, bank-, contract-, or professional review.

Reliable Multi-Channel Currency Data Sources: evidence exercise 4

Reperform official fee definition with invented same-day and delayed-payout cohorts. Hold source and base currency roles, gross amount, deduction definition, fee base, base costs, retained-order definition, rounding, and evidence controls constant where comparison requires them.

Archive the accepted packet before varying the field. Explain the resulting net source amount, conversion fee, normalized revenue, base costs, contribution, margin, per-order contribution, A-minus-B difference, rate gap, decision, monitoring trigger, and restoration path.

The exercise remains educational and source-linked. It does not fetch a live rate, recommend a transfer or hedge, predict a currency, approve a channel, determine accounting or tax treatment, or replace market-, region-, plan-, payment-, platform-, bank-, contract-, or professional review.

Reliable Multi-Channel Currency Data Sources: evidence exercise 5

Reperform refund record with invented same-day and delayed-payout cohorts. Hold source and base currency roles, gross amount, deduction definition, fee base, base costs, retained-order definition, rounding, and evidence controls constant where comparison requires them.

Archive the accepted packet before varying the field. Explain the resulting net source amount, conversion fee, normalized revenue, base costs, contribution, margin, per-order contribution, A-minus-B difference, rate gap, decision, monitoring trigger, and restoration path.

The exercise remains educational and source-linked. It does not fetch a live rate, recommend a transfer or hedge, predict a currency, approve a channel, determine accounting or tax treatment, or replace market-, region-, plan-, payment-, platform-, bank-, contract-, or professional review.

currency evidence map: reliable multi-channel currency data sources: evidence exercise 5
Original explanatory diagram for reliable multi-channel currency data sources: evidence exercise 5 using invented aggregate values and no private seller data.

Reliable Multi-Channel Currency Data Sources: evidence exercise 6

Reperform chargeback record with invented same-day and delayed-payout cohorts. Hold source and base currency roles, gross amount, deduction definition, fee base, base costs, retained-order definition, rounding, and evidence controls constant where comparison requires them.

Archive the accepted packet before varying the field. Explain the resulting net source amount, conversion fee, normalized revenue, base costs, contribution, margin, per-order contribution, A-minus-B difference, rate gap, decision, monitoring trigger, and restoration path.

The exercise remains educational and source-linked. It does not fetch a live rate, recommend a transfer or hedge, predict a currency, approve a channel, determine accounting or tax treatment, or replace market-, region-, plan-, payment-, platform-, bank-, contract-, or professional review.

Reliable Multi-Channel Currency Data Sources: evidence exercise 7

Reperform bank conversion with invented same-day and delayed-payout cohorts. Hold source and base currency roles, gross amount, deduction definition, fee base, base costs, retained-order definition, rounding, and evidence controls constant where comparison requires them.

Archive the accepted packet before varying the field. Explain the resulting net source amount, conversion fee, normalized revenue, base costs, contribution, margin, per-order contribution, A-minus-B difference, rate gap, decision, monitoring trigger, and restoration path.

The exercise remains educational and source-linked. It does not fetch a live rate, recommend a transfer or hedge, predict a currency, approve a channel, determine accounting or tax treatment, or replace market-, region-, plan-, payment-, platform-, bank-, contract-, or professional review.

Reliable Multi-Channel Currency Data Sources: evidence exercise 8

Reperform base-cost ledger with invented same-day and delayed-payout cohorts. Hold source and base currency roles, gross amount, deduction definition, fee base, base costs, retained-order definition, rounding, and evidence controls constant where comparison requires them.

Archive the accepted packet before varying the field. Explain the resulting net source amount, conversion fee, normalized revenue, base costs, contribution, margin, per-order contribution, A-minus-B difference, rate gap, decision, monitoring trigger, and restoration path.

The exercise remains educational and source-linked. It does not fetch a live rate, recommend a transfer or hedge, predict a currency, approve a channel, determine accounting or tax treatment, or replace market-, region-, plan-, payment-, platform-, bank-, contract-, or professional review.

Reliable Multi-Channel Currency Data Sources: evidence exercise 9

Reperform source version with invented same-day and delayed-payout cohorts. Hold source and base currency roles, gross amount, deduction definition, fee base, base costs, retained-order definition, rounding, and evidence controls constant where comparison requires them.

Archive the accepted packet before varying the field. Explain the resulting net source amount, conversion fee, normalized revenue, base costs, contribution, margin, per-order contribution, A-minus-B difference, rate gap, decision, monitoring trigger, and restoration path.

The exercise remains educational and source-linked. It does not fetch a live rate, recommend a transfer or hedge, predict a currency, approve a channel, determine accounting or tax treatment, or replace market-, region-, plan-, payment-, platform-, bank-, contract-, or professional review.

Reliable Multi-Channel Currency Data Sources: evidence exercise 10

Reperform owner and restore record with invented same-day and delayed-payout cohorts. Hold source and base currency roles, gross amount, deduction definition, fee base, base costs, retained-order definition, rounding, and evidence controls constant where comparison requires them.

Archive the accepted packet before varying the field. Explain the resulting net source amount, conversion fee, normalized revenue, base costs, contribution, margin, per-order contribution, A-minus-B difference, rate gap, decision, monitoring trigger, and restoration path.

The exercise remains educational and source-linked. It does not fetch a live rate, recommend a transfer or hedge, predict a currency, approve a channel, determine accounting or tax treatment, or replace market-, region-, plan-, payment-, platform-, bank-, contract-, or professional review.

Build a platform rule ledger

For Etsy, preserve listing currency, Payment account currency, sale amount, conversion fee, applied market rate, and supported deposit-currency context. For Shopify, preserve store, presentment and payout currencies, capture or reversal event, historical rate, plan and region, conversion-fee base, and the April 6, 2026 rule transition. For TikTok reporting, label ad-account and shop currencies plus attributed and real-time reporting dates.

Every source row needs URL, page title, platform, market, plan or payment path, access date, rule effective date, data-through date, accepted excerpt or definition, and evidence owner. A seller-owned statement row additionally records report name, cohort grain, currency role, amount field, timestamp field, exclusions, and whether the value is estimated or settled.

Official guidance defines the rule, but the seller's dated transaction, payout, refund, chargeback, or bank evidence supplies the actual entered amount and event. Neither replaces the other. A current help page cannot prove what a historical settlement used, and a statement line cannot explain a platform formula without its rule version.

Map every conversion event

Create one row for customer presentment, store or shop reporting, platform conversion, payout currency, and bank receipt. If no conversion occurs at a layer, say so explicitly. If a later bank converts again, record its separate rate, direction, fee, timestamp, and received amount rather than blending it into the platform rate.

Refunds and chargebacks receive their own rows because their event dates and rates can differ from the original capture. TikTok Ads reporting can use ad-account currency while the shop uses another currency, so advertising analytics must not be substituted for settled seller revenue without a bridge.

The evidence map uses aggregate totals and redacted identifiers only. Buyer names, emails, addresses, order rows, payment instruments, bank details, credentials, private invoices, and raw exports remain outside public content and durable operational reports.

Sources and further reading

Related Seller Profit Guard tools

Next step: Open Seller Profit Guard.

This is operational planning help, not tax, accounting, legal, financial, or platform-policy advice. Review the Terms and disclaimer, and verify current platform rules and fee assumptions before changing prices.