Skip to content

Main content

Service Charge Area Share Tool

Allocate an explicit service-charge total by chargeable area without inferring lease exclusions or legal recoverability.

Loading tool…

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

  1. Enter totalServiceCharge, unitChargeableArea, totalChargeableArea. 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 allocationShare, unitCharge. Use the output convention below.

Divide unitChargeableArea by positive totalChargeableArea for allocationShare and multiply totalServiceCharge by that share for unitCharge.1

Input fieldMeaning and unitsAccepted input
totalServiceChargeTotal Service ChargeRequired. Finite number; minimum 0.
unitChargeableAreaUnit Chargeable AreaRequired. Finite number; minimum 0.
totalChargeableAreaTotal Chargeable AreaRequired. Finite number; strictly above 0.
Output fieldInterpretationReturned shape
allocationShareAllocation ShareRequired. Finite number.
unitChargeUnit ChargeRequired. Finite number.
json
{
  "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

  1. Calculation and input contract: real-estate/service-charge-area-share — tool.io

Similar or alternative tools