Description
Divide unitChargeableArea by positive totalChargeableArea for allocationShare and multiply totalServiceCharge by that share for unitCharge.
Property charges and rent allocations depend on a specified amount, period, and sharing rule. A prorated amount is arithmetic under that rule; it does not establish contractual liability or the amount legally payable.
Divide unitChargeableArea by positive totalChargeableArea for allocationShare and multiply totalServiceCharge by that share for unitCharge.
When to use this tool
Use Service Charge Area Share when you need one property-cost allocation using supplied amounts and dates.
How to use the tool and how it works
- Enter totalServiceCharge, unitChargeableArea, totalChargeableArea. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read allocationShare, unitCharge. Use the output convention below.
Divide unitChargeableArea by positive totalChargeableArea for allocationShare and multiply totalServiceCharge by that share for unitCharge.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| totalServiceCharge | Total Service Charge | Required. Finite number; minimum 0. |
| unitChargeableArea | Unit Chargeable Area | Required. Finite number; minimum 0. |
| totalChargeableArea | Total Chargeable Area | Required. Finite number; strictly above 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| allocationShare | Allocation Share | Required. Finite number. |
| unitCharge | Unit Charge | Required. Finite number. |
{
"input": {
"totalServiceCharge": 10000,
"unitChargeableArea": 80,
"totalChargeableArea": 1000
},
"output": {
"allocationShare": 0.08,
"unitCharge": 800
}
} Limitations and assumptions
- Unit area must lie within total area; lease terms, measured area standards, recoverable costs, and monetary rounding are not determined.
- 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
Check the agreement, billing period, local rules, and any charges omitted from the input.
References
Similar or alternative tools
- Expenditure Share Good
Require goodExpenditure within positive totalExpenditure and divide for share.
- Menu Price Service Charge Line
Multiply menuSubtotal by nonnegative serviceChargeRateFraction for serviceCharge and add it to subtotal for total.