# Claims files that outlast the claim

> Insurance. A claim can be reopened, litigated or audited years after it is paid. Tabellix keeps the claim file, the wording that applied and every reserve decision on a verifiable record, then destroys it lawfully when its time comes.

## What gets asked: What auditors, reinsurers and courts ask.

- **The wording that applied.** The policy wording and endorsements in force when the policy was bound, not the version on file today.
- **Reserve movements.** Who changed a reserve, from what to what, and the reason given at the time.
- **A complete claim file.** Every notice, estimate, photo, report and letter, in order, unchanged since it was filed.
- **Outside parties.** What the loss adjuster, the claimant's lawyer or the reinsurer received, which version, and when.
- **Destruction when due.** Whether the retention period has passed, whether a hold applies, and who approved the destruction.
- **What the claims agent did.** Which steps an AI agent took on a claim, for which handler, and which decisions a person made.

## How Tabellix answers: The answer is in the file.

- **Wordings pinned to the policy.** Wordings are controlled documents with versions and scheduled effective dates. A link from a policy record pins the version it refers to, and that link never moves.
- **Every reserve change, recorded.** Each reserve change is its own event record, locked at capture. A correction is an amendment that states a reason, and the original value stays visible.
- **The claim as a case.** A claim file is a case record that binds its members in order. Holds, retention triggers and access flow from the claim to every document in it.
- **Outside parties without seats.** Adjusters, lawyers and reinsurers get expiring, watermarked shares or a data room, with an agreement before content. The [accounting of disclosures](https://tabellix.dev/privacy-retention/) lists every version each one received.
- **Lawful, verifiable destruction.** The system proposes what is due and records administrators approve each disposal. Destruction crypto-shreds the content, an active hold blocks it, and the ledger still verifies afterward.
- **Agents, as far as you decide.** Under the flexible preset you open individual agent permissions one by one, and an agent's signature always says it was the agent's. Every tool call carries the handler and the agent session.

## Typical records: A claim, end to end.

| Record | Kind | What it holds |
| --- | --- | --- |
| Policy wording HW-12 | document | Versions with scheduled effective dates; endorsements as their own documents; superseded wordings kept with their history. |
| Claim CL-55120 | case record | First notice, estimates, photos, reports and correspondence as ordered members; retention counted from the day the claim closes. |
| Reserve change | event record | Previous and new amount, the handler, the reason and the time, linked to the claim and locked at capture. |
| Underwriting referral | case record | The referral, the underwriter's decision signed with its meaning, and the guideline version that applied. |
| Independent adjuster report | document | Received through the claim, scanned for malware before anyone opens it, and versioned if a revised report follows. |

[Documents, records and the evidence about both](https://tabellix.dev/records/)

## Go deeper

- [Privacy and retention](https://tabellix.dev/privacy-retention/): Keep what the law requires and erase what privacy law allows, with the audit trail intact.
- [Records, not files](https://tabellix.dev/records/): Documents, records and the evidence about both, and what belongs in a system of record.
- [Security](https://tabellix.dev/security/): Deny by default, hidden existence, policy as code and a hardened platform.
- [Agents](https://tabellix.dev/agents/): AI agents act for a person, never above that person, and named people stay accountable.
- [Banking and financial services](https://tabellix.dev/industries/banking/): Systems of record where every decision, approval, and change remains verifiable for its full retention period.

## FAQ: Common questions.

### Can a claim file be destroyed early?

Where the deployment allows early destruction, records can be crypto-shredded under a legal order with two distinct approvers. An active hold refuses the order. The record's identity and history remain, and the ledger still verifies.

### Can reinsurers verify what they received?

Yes. A disclosure is a signed, deterministic bundle checked offline, and a data room reports what each recipient fetched.

### Are files from outside parties safe to open?

Every file is scanned for malware and served only after the scanner answers clean. A file that is not what it claims to be is refused, and downloads are served with active content blocked.

### How does a claims system vendor embed Tabellix?

Your claims system keeps its screens, rules and payments. It files each document and event into the claim case through one contract over gRPC or REST, and outside parties need no seat. Your brand appears on every customer-visible surface Tabellix provides.

## Contact

Tell us what you build and who audits it. We'll show you how Tabellix fits into your product and how it answers your auditors' most common questions.

Contact form: https://tabellix.dev/contact/

---

This page as HTML: https://tabellix.dev/industries/insurance/ · [Site guide for language models](https://tabellix.dev/llms.txt)