Skip to content

Main content

Business Travel Local Perdiem Cap Tool

Calculate business travel local perdiem cap from explicit caller-supplied inputs.

Loading tool…

Description

Multiply eligibleDays by dailyCap for expenseCap.

Trade-finance arithmetic combines supplied fees, exchange factors, timing windows, and reporting bases. A local consistency result does not establish document compliance, contract rights, or bank acceptance.

Multiply eligibleDays by dailyCap for expenseCap.

When to use this tool

Use Business Travel Local Perdiem Cap when you need one transparent cross-border cost or timing component.

How to use the tool and how it works

  1. Enter eligibleDays, dailyCap, actualExpense, employerAdvance. 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 expenseCap, reimbursable, settlement. Use the output convention below.

Multiply eligibleDays by dailyCap for expenseCap. Use the smaller of actualExpense and cap for reimbursable, then subtract employerAdvance for settlement.1

Input fieldMeaning and unitsAccepted input
eligibleDaysEligible DaysRequired. Finite number; minimum 0.
dailyCapDaily CapRequired. Finite number; minimum 0.
actualExpenseActual ExpenseRequired. Finite number; minimum 0.
employerAdvanceEmployer AdvanceRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
expenseCapExpense CapRequired. Finite number.
reimbursableReimbursableRequired. Finite number.
settlementSettlementRequired. Finite number.
json
{
  "input": {
    "eligibleDays": 3,
    "dailyCap": 100,
    "actualExpense": 350,
    "employerAdvance": 200
  },
  "output": {
    "expenseCap": 300,
    "reimbursable": 300,
    "settlement": 100
  }
}

Limitations and assumptions

  • Days may be fractional; a negative settlement is retained and employer policy, tax treatment, and expense eligibility are supplied externally.
  • 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 complete transaction, contract, bank terms, and applicable accounting policies before acting on a partial calculation.

References

  1. Calculation and input contract: international-business/business-travel-local-perdiem-cap — tool.io

Similar or alternative tools