Description
Return netCost=directTransfer+overhead-sharedCredit and overheadShare=(overhead-sharedCredit)/netCost.
Public agreements, monitoring, dialogue, and assistance records use explicit identifiers, time windows, accounting bases, and participation categories. A match or coverage share describes a supplied representation. It does not independently establish the accuracy of a record, the fairness of a process, or conditions on the ground.
Return netCost=directTransfer+overhead-sharedCredit and overheadShare=(overhead-sharedCredit)/netCost.
When to use this tool
Use Relief Transfer Overhead Share when you need this local public-record match, participation measure, duration, or accounting check.
How to use the tool and how it works
- Enter directTransfer, overhead, sharedCredit. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read netCost, overheadShare. Use the output convention below.
Require nonnegative directTransfer, overhead, and sharedCredit with sharedCredit<=overhead and directTransfer+overhead>sharedCredit. Return netCost=directTransfer+overhead-sharedCredit and overheadShare=(overhead-sharedCredit)/netCost.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| directTransfer | Direct Transfer | Required. Finite number; minimum 0. |
| overhead | Overhead | Required. Finite number; minimum 0. |
| sharedCredit | Shared Credit | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| netCost | Net Cost | Required. Finite number. |
| overheadShare | Overhead Share | Required. Finite number. |
{
"input": {
"directTransfer": 80,
"overhead": 30,
"sharedCredit": 10
},
"output": {
"netCost": 100,
"overheadShare": 0.2
}
}Limitations and assumptions
- Amounts need one currency, period, and accounting basis. Credit is supplied; the ratio does not establish aid effectiveness, verified delivery, or correct financial reporting.
- 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. Signed zero is exported as zero.
Alternative or Complementary methods
Verify the underlying public sources, time basis, inclusion policy, and interpretation of the reporting denominator. Substantive agreement analysis or current field conditions require information beyond these supplied tokens or coordinates.
References
Similar or alternative tools
- Agreement Clause Date Offset
Compare supplied public agreement date coordinates without interpreting legal effect.
- Ceasefire Clause Date Span
Measure explicitly supplied public clause day bounds without interpreting obligations or forecasting compliance.