Skip to content

Main content

Historical Tariff Specific Ad Valorem Crosswalk Tool

Calculate historical tariff specific ad valorem crosswalk from explicit caller-supplied inputs.

Loading tool…

Description

equivalentRate = specificDutyPerUnit/customsValuePerUnit; duty = specificDutyPerUnit*quantity.

Historical accounting and tax terms depend on period, rate and valuation conventions. Applying a supplied factor to a ledger amount differs from establishing which historical contract, calendar or tariff actually applied.

equivalentRate = specificDutyPerUnit/customsValuePerUnit; duty = specificDutyPerUnit*quantity.

When to use this tool

Use Historical Tariff Specific Ad Valorem Crosswalk when checking a declared historical interest or duty term.

How to use the tool and how it works

  1. Enter specificDutyPerUnit, customsValuePerUnit, quantity. 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 equivalentRate, duty. Use the output convention below.

Require positive customsValuePerUnit and nonnegative quantity. equivalentRate = specificDutyPerUnit/customsValuePerUnit; duty = specificDutyPerUnit*quantity.1

Input fieldMeaning and unitsAccepted input
specificDutyPerUnitSpecific Duty Per UnitRequired. Finite number.
customsValuePerUnitCustoms Value Per UnitRequired. Finite number; strictly above 0.
quantityQuantityRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
equivalentRateEquivalent RateRequired. Finite number.
dutyDutyRequired. Finite number.
json
{
  "input": {
    "specificDutyPerUnit": 3,
    "customsValuePerUnit": 20,
    "quantity": 10
  },
  "output": {
    "equivalentRate": 0.15,
    "duty": 30
  }
}

Limitations and assumptions

  • Duty is currency per matching quantity unit and the equivalent rate is a fraction. Signed duties are accepted; historical tariff law, exemptions and actual assessed values are not inferred.
  • 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 relevant archival terms and legal context for actual ledger interpretation and obligations.

References

  1. Calculation and input contract: economic-history/historical-tariff-specific-ad-valorem-crosswalk — tool.io

Similar or alternative tools