Seller Profit Guard

What makes a multi-channel currency comparison wrong?

Last updated: 2026-08-09

Written and reviewed by Seller Profit Guard Editorial Team.

Common errors include reversing rate direction, mixing presentment with payout currency, applying a fee to the wrong base, double-counting embedded conversion, using a later market quote instead of the settlement rate, ignoring refund timing, converting costs twice, rounding early, mixing order denominators, and treating normalization as an FX forecast.

Multi-Channel Currency Conversion Mistakes flow from currency roles and timestamped evidence to normalized contribution, decision, and restoration
Use the currency error log to normalize matched closed currency cohorts.

Rate direction reversed

Common errors include reversing rate direction, mixing presentment with payout currency, applying a fee to the wrong base, double-counting embedded conversion, using a later market quote instead of the settlement rate, ignoring refund timing, converting costs twice, rounding early, mixing order denominators, and treating normalization as an FX forecast. Show the faulty field, distorted normalized result, corrected evidence, economic effect, and prevention control. Checkpoint 1 in the currency error log records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For rate direction reversed, 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 error log.

Currency roles mixed

Common errors include reversing rate direction, mixing presentment with payout currency, applying a fee to the wrong base, double-counting embedded conversion, using a later market quote instead of the settlement rate, ignoring refund timing, converting costs twice, rounding early, mixing order denominators, and treating normalization as an FX forecast. Show the faulty field, distorted normalized result, corrected evidence, economic effect, and prevention control. Checkpoint 2 in the currency error log records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For currency roles mixed, 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 error log.

Fee base wrong

Common errors include reversing rate direction, mixing presentment with payout currency, applying a fee to the wrong base, double-counting embedded conversion, using a later market quote instead of the settlement rate, ignoring refund timing, converting costs twice, rounding early, mixing order denominators, and treating normalization as an FX forecast. Show the faulty field, distorted normalized result, corrected evidence, economic effect, and prevention control. Checkpoint 3 in the currency error log records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For fee base wrong, 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 error log.

Embedded fee doubled

Common errors include reversing rate direction, mixing presentment with payout currency, applying a fee to the wrong base, double-counting embedded conversion, using a later market quote instead of the settlement rate, ignoring refund timing, converting costs twice, rounding early, mixing order denominators, and treating normalization as an FX forecast. Show the faulty field, distorted normalized result, corrected evidence, economic effect, and prevention control. Checkpoint 4 in the currency error log records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For embedded fee doubled, 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 error log.

Market quote substituted

Common errors include reversing rate direction, mixing presentment with payout currency, applying a fee to the wrong base, double-counting embedded conversion, using a later market quote instead of the settlement rate, ignoring refund timing, converting costs twice, rounding early, mixing order denominators, and treating normalization as an FX forecast. Show the faulty field, distorted normalized result, corrected evidence, economic effect, and prevention control. Checkpoint 5 in the currency error log records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For market quote substituted, 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 error log.

currency error log: market quote substituted
Original explanatory diagram for market quote substituted using invented aggregate values and no private seller data.

Refund timing ignored

Common errors include reversing rate direction, mixing presentment with payout currency, applying a fee to the wrong base, double-counting embedded conversion, using a later market quote instead of the settlement rate, ignoring refund timing, converting costs twice, rounding early, mixing order denominators, and treating normalization as an FX forecast. Show the faulty field, distorted normalized result, corrected evidence, economic effect, and prevention control. Checkpoint 6 in the currency error log records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For refund timing ignored, 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 error log.

Cost converted twice

Common errors include reversing rate direction, mixing presentment with payout currency, applying a fee to the wrong base, double-counting embedded conversion, using a later market quote instead of the settlement rate, ignoring refund timing, converting costs twice, rounding early, mixing order denominators, and treating normalization as an FX forecast. Show the faulty field, distorted normalized result, corrected evidence, economic effect, and prevention control. Checkpoint 7 in the currency error log records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For cost converted twice, 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 error log.

Rounding too early

Common errors include reversing rate direction, mixing presentment with payout currency, applying a fee to the wrong base, double-counting embedded conversion, using a later market quote instead of the settlement rate, ignoring refund timing, converting costs twice, rounding early, mixing order denominators, and treating normalization as an FX forecast. Show the faulty field, distorted normalized result, corrected evidence, economic effect, and prevention control. Checkpoint 8 in the currency error log records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For rounding too early, 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 error log.

Order denominator mixed

Common errors include reversing rate direction, mixing presentment with payout currency, applying a fee to the wrong base, double-counting embedded conversion, using a later market quote instead of the settlement rate, ignoring refund timing, converting costs twice, rounding early, mixing order denominators, and treating normalization as an FX forecast. Show the faulty field, distorted normalized result, corrected evidence, economic effect, and prevention control. Checkpoint 9 in the currency error log records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For order denominator mixed, 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 error log.

Forecast inferred

Common errors include reversing rate direction, mixing presentment with payout currency, applying a fee to the wrong base, double-counting embedded conversion, using a later market quote instead of the settlement rate, ignoring refund timing, converting costs twice, rounding early, mixing order denominators, and treating normalization as an FX forecast. Show the faulty field, distorted normalized result, corrected evidence, economic effect, and prevention control. Checkpoint 10 in the currency error log records channel, cohort, currency roles, amount layers, rate event, source version, owner, reviewer, and accepted formula before interpretation.

For forecast inferred, 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 error log.

Rate direction reversed: verification test 1

Create one synthetic counterexample for rate direction reversed. 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 roles mixed: verification test 2

Create one synthetic counterexample for currency roles mixed. 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.

Fee base wrong: verification test 3

Create one synthetic counterexample for fee base wrong. 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.

Embedded fee doubled: verification test 4

Create one synthetic counterexample for embedded fee doubled. 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.

Market quote substituted: verification test 5

Create one synthetic counterexample for market quote substituted. 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 error log: market quote substituted: verification test 5
Original explanatory diagram for market quote substituted: verification test 5 using invented aggregate values and no private seller data.

Refund timing ignored: verification test 6

Create one synthetic counterexample for refund timing ignored. 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.

Cost converted twice: verification test 7

Create one synthetic counterexample for cost converted twice. 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.

Rounding too early: verification test 8

Create one synthetic counterexample for rounding too early. 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 denominator mixed: verification test 9

Create one synthetic counterexample for order denominator mixed. 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.

Forecast inferred: verification test 10

Create one synthetic counterexample for forecast inferred. 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.

Multi-Channel Currency Conversion Mistakes: evidence exercise 1

Reperform rate direction reversed 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.

Multi-Channel Currency Conversion Mistakes: evidence exercise 2

Reperform currency roles mixed 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.

Multi-Channel Currency Conversion Mistakes: evidence exercise 3

Reperform fee base wrong 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.

Multi-Channel Currency Conversion Mistakes: evidence exercise 4

Reperform embedded fee doubled 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.

Multi-Channel Currency Conversion Mistakes: evidence exercise 5

Reperform market quote substituted 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 error log: multi-channel currency conversion mistakes: evidence exercise 5
Original explanatory diagram for multi-channel currency conversion mistakes: evidence exercise 5 using invented aggregate values and no private seller data.

Multi-Channel Currency Conversion Mistakes: evidence exercise 6

Reperform refund timing ignored 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.

Multi-Channel Currency Conversion Mistakes: evidence exercise 7

Reperform cost converted twice 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.

Multi-Channel Currency Conversion Mistakes: evidence exercise 8

Reperform rounding too early 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.

Multi-Channel Currency Conversion Mistakes: evidence exercise 9

Reperform order denominator mixed 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.

Multi-Channel Currency Conversion Mistakes: evidence exercise 10

Reperform forecast inferred 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.

Detect the double-fee trap

A common spreadsheet subtracts an aggregate payout deduction that already includes conversion, then subtracts fee base multiplied by fee rate a second time. Another applies the percentage to net source amount even though the platform rule specifies gross sale or gross order. Both errors can survive a simple total check because every field remains numeric.

Prevent the trap with a deduction inventory. For each component record name, currency, sign, source line, whether it includes conversion, and the exact formula field. Reconcile the explicit conversion fee to its source amount, rate, effective date, and statement. Block when the same source line maps to two fields or when the fee-base source is not named.

A sensitivity test changes only the fee base while holding deductions and rate constant. If a supposedly separate deduction moves with that fee, investigate overlap. Keep platform fee, bank conversion, price rounding, refund-rate difference, and base-currency operating cost outside the conversion fee unless the evidence contract explicitly includes them.

Reject coercion and false dates

Partially parsing values such as 10000eur, 1.03usd, or 2percent can silently accept unsupported input. Fractional retained-order counts and impossible dates such as 2026-06-31 are equally dangerous because they make audit trails look complete while violating the calculation contract.

The calculator requires plain decimals, positive whole retained-order and evidence-day counts, three-letter currency codes, and real YYYY-MM-DD dates. It also bounds rates and amounts, rejects deductions that consume gross retained revenue, and prevents a seller policy date from postdating the official source review.

When a structural input fails, 26 derived amount, rate, contribution, margin, and comparison outputs display Unavailable. This quarantine is deliberate: a Block packet can preserve the entered evidence for correction without presenting arithmetic that readers might mistake for a verified economic conclusion.

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.