Calculate Expense Cap Reimbursement
fund.expense_cap_reimbursement
Overview
Perform exact bounded expense cap reimbursement from caller-supplied fund terms. Contractual eligibility, fee policy, mappings, and materiality remain caller-controlled.
You receive deterministic fund fee and control evidence without hidden contractual choices for fund.expense_cap_reimbursement.
Reliability
DECIMAL_INVALID means a decimal is malformed or exceeds precision limits; correct it. FUND_INPUT_INVALID means an amount, rate, identifier, mapping, tolerance, or resulting balance violates the closed domain; correct it. ITEM_LIMIT_EXCEEDED means a series or mapping exceeds 10,000 rows; reduce it. This guidance applies specifically to fund.expense_cap_reimbursement.
Context footprint
The compact output replaces repeated fund fee and reconciliation arithmetic for fund.expense_cap_reimbursement. A successful call costs 1 execution credit.
When to use it
When actual expenses versus a contractual cap must produce a reimbursement amount.
When you are computing a performance fee on excess, not an expense-cap reimbursement.
Scope
Non-goals
- Does not choose eligibility, fee terms, crystallization policy, mappings, or materiality for fund.expense_cap_reimbursement.
- Does not infer prospectus terms, accounting recognition, market values, or investor treatment for fund.expense_cap_reimbursement.
Properties
Capabilities
Cost & billing
Flat rate per invocation
File handling
How we handle your data
What this means
This skill may receive sensitive content, but it does not target sensitive data and returns only a structured non-sensitive result.
Squillify guarantees
- Runs inside Squillify
- This skill runs inside Squillify.
- Payloads are not sent to an external service by this skill.
- Squillify does not permanently store submitted payloads.
- Telemetry records metadata only, not submitted content.
- Submitted payloads are not used for training.
- Submitted payloads are not reviewed by humans.
- This skill does not target sensitive data.
- The response does not contain submitted content.
Your responsibility
Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.
Input schema
| Field | Type | Required | Description |
|---|---|---|---|
| eligibleFundExpense | string | Yes | Required finite plain decimal `eligibleFundExpense` with at most 100 significant digits and scale 40. |
| fundExpenseCap | string | Yes | Required finite plain decimal `fundExpenseCap` with at most 100 significant digits and scale 40. |
Output schema
| Field | Type | Required | Description |
|---|---|---|---|
| reimbursement | string | Yes | Calculated normalized finite plain-decimal result. |
| netFundExpense | string | Yes | Calculated normalized finite plain-decimal result. |
API contract
POST /v1/executecurl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"fund.expense_cap_reimbursement","input":{"eligibleFundExpense":"120","fundExpenseCap":"100"}}'import { Squillify } from "@squillify/sdk";
const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });
const { output } = await sq.execute("fund.expense_cap_reimbursement", {"fundExpenseCap":"100","eligibleFundExpense":"120"});Errors
| Code | HTTP | Retryable | Description |
|---|---|---|---|
| VALIDATION_ERROR | 400 | No | The request payload failed schema validation. |
| UNAUTHORIZED | 401 | No | Missing or invalid API key. |
| SKILL_NOT_ACCESSIBLE | 403 | No | The API key is not granted access to this skill. |
| SKILL_NOT_AVAILABLE_FOR_PLAN | 403 | No | This skill is not included in your current plan. |
| PLAN_ELIGIBILITY_UNAVAILABLE | 503 | Yes | Plan eligibility could not be decided. Retry after backoff. |
| SKILL_NOT_FOUND | 404 | No | The requested skill or version does not exist. |
| TENANT_RATE_LIMITED | 429 | Yes | Request rate limit exceeded. Retry after backoff. |
| QUOTA_EXCEEDED | 429 | Yes | Plan quota exhausted. Retryable once the quota period resets. |
| EXECUTION_TIMEOUT | 504 | Yes | Execution exceeded the allowed time budget. |
| DECIMAL_INVALID | 400 | No | The request payload failed this skill's input validation. |
| FUND_INPUT_INVALID | 400 | No | The request payload failed this skill's input validation. |
Other limits
| Limit | Value |
|---|---|
| Recommended inline bytes | 32 KiB |
Limitations
- Does not choose eligibility, fee terms, crystallization policy, mappings, or materiality for fund.expense_cap_reimbursement.
- Does not infer prospectus terms, accounting recognition, market values, or investor treatment for fund.expense_cap_reimbursement.
- Contractual interpretation, eligibility selection, valuation sourcing, or materiality decisions for fund.expense_cap_reimbursement.
How to call
POST /v1/execute (requires authentication)
{
"skillKey": "fund.expense_cap_reimbursement",
"input": {
"fundExpenseCap": "100",
"eligibleFundExpense": "120"
}
}Examples
Verified primary
{
"fundExpenseCap": "100",
"eligibleFundExpense": "120"
}{
"netFundExpense": "100",
"reimbursement": "20"
}Verified alternative
{
"fundExpenseCap": "100",
"eligibleFundExpense": "80"
}{
"netFundExpense": "80",
"reimbursement": "0"
}Recommended use cases
- Exact fund fee or equalization reperformance for fund.expense_cap_reimbursement.
- Independent bounded rollforward or reconciliation evidence for fund.expense_cap_reimbursement.
Avoid for
- Contractual interpretation, eligibility selection, valuation sourcing, or materiality decisions for fund.expense_cap_reimbursement.
Related skills
Composable with
Safety & privacy
- Runs without calling any external service.
- Your payloads are never stored permanently.
- Telemetry captures metadata only — never your payload contents.
- We never train models on your payloads.
- No human reviews your payloads.