Skip to content

Main content

Internal Charge Fixed Share

Allocate an explicit shared-charge fraction and add a distinct fixed internal charge without double-counting it in the shared base.

Loading tool…

Description

Allocate a supplied charge base proportionally and add a fixed charge.

Administrative records depend on policy dates, authorization scope, attendance denominators and accounting definitions. A calendar-date shift does not skip holidays, a quorum fraction is not a quorum decision, and a weighted voting fraction differs from economic ownership. Recorded signatory presence does not authenticate a signature or establish authority.

Allocate a supplied charge base proportionally and add a fixed charge.

When to use this tool

Use Internal Charge Fixed Share when you already have totalCharge, allocationFraction, fixedCharge and need to allocate a supplied charge base proportionally and add a fixed charge.

How to use the tool and how it works

  1. Enter totalCharge, allocationFraction, fixedCharge. 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 allocatedVariableCharge, totalAllocatedCharge. Use the output convention below.

Require totalCharge/fixedCharge>=0 and fraction in [0,1]; variable=totalCharge*fraction, totalAllocated=variable+fixedCharge.1

Input fieldMeaning and unitsAccepted input
totalChargeTotal ChargeRequired. Finite number; minimum 0.
allocationFractionAllocation FractionRequired. Finite number; minimum 0; maximum 1.
fixedChargeFixed ChargeRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
allocatedVariableChargeAllocated Variable ChargeRequired. Finite number.
totalAllocatedChargetotalCharge*allocationFraction+fixedCharge; fixedCharge is added after allocating the full totalCharge.Required. Finite number.
json
{
  "input": {
    "totalCharge": 1000,
    "allocationFraction": 0.25,
    "fixedCharge": 20
  },
  "output": {
    "allocatedVariableCharge": 250,
    "totalAllocatedCharge": 270
  }
}

Limitations and assumptions

  • The fixed charge is added separately, not subtracted from the base before allocation. Total allocated may exceed totalCharge; no fee rule, invoice or actual obligation is verified.
  • 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 controlled policies, meeting records, contracts and account definitions. Apply the complete applicable rules when actual approval, payment or governance matters; local version selection and arithmetic do not make those determinations.

References

  1. Calculation and input contract: business-administration/internal-charge-fixed-share — tool.io

Similar or alternative tools