Skip to content

Main content

Expense Cap Shared Receipt Term Tool

Calculate expense cap shared receipt term from explicit caller-supplied inputs.

Loading tool…

Description

Return allocated shared-receipt amount and capped payable term.

Administrative records encode delegated authority, invoice lines, reimbursement bases and supplied policy limits. Literal matches and amount allocations can reconcile asserted records while actual authority, eligibility, rights and accounting treatment depend on verified documents and applicable rules.

Return allocated shared-receipt amount and capped payable term.

When to use this tool

Use Expense Cap Shared Receipt Term when checking the stated administrative authority, invoice or expense convention.

How to use the tool and how it works

  1. Enter receiptTotal, allocatedFraction, priorReimbursement, cap. 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 allocated, payable. Use the output convention below.

Return allocated shared-receipt amount and capped payable term. Require nonnegative receipt/priorReimbursement/cap and allocation in [0,1]; allocated = receipt*fraction, payable = max(0,min(allocated-prior,cap)).1

Input fieldMeaning and unitsAccepted input
receiptTotalReceipt TotalRequired. Finite number; minimum 0.
allocatedFractionAllocated Fraction Unit: 1.Required. Finite number; minimum 0; maximum 1.
priorReimbursementPrior ReimbursementRequired. Finite number; minimum 0.
capCapRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
allocatedAllocatedRequired. Finite number.
payablePayableRequired. Finite number.
json
{
  "input": {
    "receiptTotal": 100,
    "allocatedFraction": 0.5,
    "priorReimbursement": 10,
    "cap": 30
  },
  "output": {
    "allocated": 50,
    "payable": 30
  }
}

Limitations and assumptions

  • Prior reimbursement above allocation yields zero; actual allocation, legal entitlement, tax and approval policy 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

Review the governing policy, authorization and financial records; involve the appropriate administrative, financial or legal professional for actual rights and payment decisions.

References

  1. Calculation and input contract: business-administration/expense-cap-shared-receipt-term — tool.io

Similar or alternative tools