Description
Require aligned nonnegative costs and lineTerms, sum costs whose label exactly matches requestedTerm, and divide by positive totalCost.
Trade-finance arithmetic combines supplied fees, exchange factors, timing windows, and reporting bases. A local consistency result does not establish document compliance, contract rights, or bank acceptance.
Require aligned nonnegative costs and lineTerms, sum costs whose label exactly matches requestedTerm, and divide by positive totalCost.
When to use this tool
Use Incoterm Cost Line Share when you need one transparent cross-border cost or timing component.
How to use the tool and how it works
- Enter costs, lineTerms, requestedTerm, totalCost. Keep parallel arrays aligned. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read matchedCost, share. Use the output convention below.
Require aligned nonnegative costs and lineTerms, sum costs whose label exactly matches requestedTerm, and divide by positive totalCost.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| costs | Costs | Required. Array of finite number; maximum items 256. |
| lineTerms | Line Terms | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| requestedTerm | Requested Term | Required. Text; maximum UTF-16 length 8192. |
| totalCost | Total Cost | Required. Finite number; strictly above 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| matchedCost | Matched Cost | Required. Finite number. |
| share | Dimensionless fraction under the stated denominator policy. | Required. Finite number. |
{
"input": {
"costs": [
10,
20,
30
],
"lineTerms": [
"A",
"B",
"A"
],
"requestedTerm": "A",
"totalCost": 100
},
"output": {
"matchedCost": 40,
"share": 0.4
}
}Limitations and assumptions
- Share can exceed one because totalCost is supplied independently; no Incoterms responsibility or contract interpretation is inferred from labels.
- 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
Review the complete transaction, contract, bank terms, and applicable accounting policies before acting on a partial calculation.
References
Similar or alternative tools
- Trade Credit Window Share
Sum amount × duration and amount × supportedDuration; divide supported amount-time by positive total, otherwise return zero and defined false.
- Freight Term Place Qualifier Token
Check term against allowedTerms and place for nonwhitespace text.