Skip to content

Main content

Commodity Tax Retailer Net Receipt

Subtract an explicit signed per-unit commodity tax from consumer payment without deciding incidence or legal tax treatment.

Loading tool…

Description

Subtract a supplied per-unit tax from a consumer payment.

Economic scalar terms depend on price/cost units, denominators, currency direction and the distinction between supplied scenarios and estimated behavior. A price-based margin differs from a cost-based markup, while a constant-revenue construction does not estimate demand. Local taxes, rebates and effect sums retain their stated accounting assumptions.

Subtract a supplied per-unit tax from a consumer payment.

When to use this tool

Use Commodity Tax Retailer Net Receipt when you already have consumerPaymentPerUnit, suppliedTaxPerUnit and need to subtract a supplied per-unit tax from a consumer payment.

How to use the tool and how it works

  1. Enter consumerPaymentPerUnit, suppliedTaxPerUnit. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read retailerNetReceiptPerUnit. Use the output convention below.

Return consumerPaymentPerUnit-suppliedTaxPerUnit, preserving signs.1

Input fieldMeaning and unitsAccepted input
consumerPaymentPerUnitConsumer Payment Per UnitRequired. Finite number.
suppliedTaxPerUnitSupplied Tax Per UnitRequired. Finite number.
Output fieldInterpretationReturned shape
retailerNetReceiptPerUnitRetailer Net Receipt Per UnitRequired. Finite number.
json
{
  "input": {
    "consumerPaymentPerUnit": 12,
    "suppliedTaxPerUnit": 2
  },
  "output": {
    "retailerNetReceiptPerUnit": 10
  }
}

Limitations and assumptions

  • Tax and payment must share a currency and unit basis. No remittance, tax applicability, economic incidence or actual retailer receipt is verified.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Use the complete budget, demand, cost and applicable rule definitions for an economic conclusion. Estimate and validate the actual model when effects or responses are needed; one signed wedge, supplied share or algebraic identity does not establish behavior or policy outcomes.

References

  1. Calculation and input contract: economics/commodity-tax-retailer-net-receipt — tool.io

Similar or alternative tools