For insurers and banks
Connect pricing and underwriting models to your applications.
Pricing and risk teams maintain calculations and rules in Excel. XSheet turns a supported workbook into an API for quoting, underwriting and banking applications. Review its effect and approve its release before the new model answers production calls.
Insurance
Carry the approved rate into quotes and renewals.
Your actuarial team maintains the rating logic. Applications call the service with the risk details, and approved routing rules select the appropriate version by inputs such as state and effective date.
-
Rating engines
Serve the rating workbook of a personal or commercial line as the API that quoting, policy administration and renewal systems call.
-
Table-shaped inputs
Send the locations of a property policy, the drivers of a motor policy or any other list as a table that maps straight to a range in the workbook.
-
Versions by state and date
A decision table picks the version for each request by state, segment or effective date. A new rate version for one state can start on the first of July while every other state stays on the current one.
-
Rate change impact
Planned: before a new version goes live, compare its results with the current version’s across a portfolio of cases and see how the change is distributed across segments.
Underwriting
Apply the rules your underwriting team maintains.
When eligibility criteria and limits live in Excel formulas or lookup tables, applications can call those rules through the same versioned API. Verification and release approval apply to rule changes as well as rate changes.
- Eligibility, limits and referral flags
- An underwriting application sends the facts the workbook needs. The model returns the outputs its author defined, such as eligibility, a coverage limit or a referral flag. A reason code is available when the workbook calculates one; XSheet does not invent an explanation.
- The application controls the next step
- Your underwriting system handles documents, case assignment and human review. It uses the returned result to continue its process. Include boundary cases and expected referrals in verification before approving a changed workbook.
Banking
Connect pricing workbooks to banking applications.
Product and risk teams maintain the pricing or grading logic in Excel. Applications submit inputs to the service and receive outputs that identify the model version used.
-
Loan and deposit pricing
Serve pricing grids, rate adjustments and fees from the workbook the pricing team maintains, without re-implementing them in each system.
-
Installments and schedules
Calculate installments and repayment schedules with the formulas already in the workbook, and return them as tables.
-
Credit grading
Turn scorecards and grading tables into an API whose every answer can be traced to the version that produced it.
-
Evidence for model risk
Give model-risk and audit teams the verification report of each version, the approvals behind each promotion and a receipt for each recorded call.
For regulated teams
Trace a customer result through the model and its approvals.
For a disputed premium or a model review, the calculation result is only part of the record. Review the version that answered, the approval behind its release and the policy governing its retained inputs.
-
Control
Production is read-only and changes only by promotion, with maker-checker approval bound to the exact diff and two people by default.
-
Evidence
A request ID and a receipt for every recorded call, replay while the inputs are retained, and a hash-chained audit log of every change.
-
Data protection
Call history is configured per environment. In production, inputs and outputs are kept for 30 days by default, encrypted and masked in display, while request IDs, metadata and receipts are kept for ten years by default.
-
Excel stays the model
Modelers keep the tool they know. Each version is checked against the results Excel saved in the workbook.
-
Customer-hosted deployment
Operate the complete platform on your infrastructure. Keep model administration, model publishing and pricing APIs within your installation, with access and data policies set by your team.
-
Defined operating responsibilities
Review connectivity, software delivery, recovery and support with your infrastructure and vendor-risk teams before introducing production data.
Questions
What insurers and banks ask.
- Is XSheet limited to insurance and banking?
- No. The API runs the supported calculations and rules in the workbook. Other applications include product quotes, commissions, cost estimates and operational eligibility checks. The Use cases page explains these patterns and how to assess a workbook.
- Can we run XSheet on our own infrastructure?
- Yes. The customer-hosted model includes the application, model publishing, calculations and persistent records. Pricing calls run locally without an XSheet-operated calculation service. Identity, updates and operational tools need a separate connectivity review, including validation of any offline requirement.
- How does a rate change reach production?
- The pricing team uploads the changed workbook as a new version. It is checked against Excel, and the service’s test cases can be run on it. By default a second person approves it before it takes over. An impact analysis against the current version is planned. Nobody rewrites the formulas in another system.
- Will an XSheet upgrade change our prices?
- No. A published version never changes, and an upgrade of the platform never changes the results of an existing version. If you upload the same workbook again after an engine upgrade, it becomes a new version, and its promotion shows the engine change before anyone approves it.
- What happens to customer data sent in calls?
- Each environment decides whether its call history keeps full inputs, masked inputs or metadata only, and development environments never see production data. Request IDs, metadata and receipts stay for their retention period. Erasure of a person’s call inputs and outputs on request, so the running service can no longer read them, is planned.
- Can auditors review the records without changing anything?
- Yes. Auditors can review models, call records, the audit log and evidence without changing them. Payload visibility follows the environment’s data policy and the auditor’s permissions. An operator command checks the whole audit log and names the first point where the log was changed, if there is one.
XSheet
See how your model would work as an API.
Discuss the workbook your team maintains and the applications that need its results. Explore integration and deployment in your environment.