Daily operations

Handling claims

How a claim follows its product and its binder: reporting, the coverage check, the worklist, your claims authority, referrals, the claim file and payments.

Updated 13 November 2026 · Written and reviewed by the Soldek team

A claim is linked to the policy it falls under and, through the policy, to its product. So the cover, the binder and the capacity provider are known the moment a claim is opened, the notification form asks what that product needs to know, and loss ratios update as you work.

Set up claims per product

Open a product and go to the Claims tab. What you set there is configuration, like the questions and the rules: it applies to new claims on that product from the moment you save.

Causes of loss
The list a claim is reported under. The worklist and the claims register group by it. Leave it empty and the cause is free text.
Questions at notification
Asked beside the standard fields (date of loss, amount, cause, description) on every notification form. The answers are stored on the claim per question.
Documents to collect
The checklist a new claim starts with. A document can be asked for every claim or only for certain causes, and be required or optional.
Standard excess
Copied onto every new claim; the handler can change it on the claim.
Notify within
The number of days after the loss within which a claim is to be notified. A later notification is flagged on the claim file.
Guidance
A few lines above the notification form: what to keep, who to call, what not to do.
When a claim arrives
Who on your team takes a new claim on this product, and after how many days it is first looked at again. The claim then arrives on the worklist with that name and that date on it, whoever reported it. Leave both empty and it arrives unassigned.
Who decides a claim
As the binder says, your team up to a limit per claim, or the insurer for every claim. A product can only be stricter than its binder; see Claims authority below.

Preview the form shows the notification form as it will read with what is on the tab, saved or not: once as your team and a broker see it, once as a policyholder sees it. The product check on the tab, and the Claims part of the product's status, say what would not work as you meant it, such as a handler who can no longer take claims or an excess that leaves nothing to pay.

Reporting a claim

  • Your team: New claim on the Claims screen.
  • A broker: from the broker portal, on any of their policies.
  • A policyholder: online in the policyholder portal, when you have given them access.

All three fill in the same form: choose the policy, and the form asks what the product of that policy asks. On a policy with a schedule of insured persons the form also asks who the claim is about. The product, the notification date, the excess and the document checklist are written by the platform, not by the person reporting.

A broker or policyholder who reports a claim receives a confirmation by e-mail with the claim number and the documents your product asks for that cause, so they know what to send. Your claims team receives the alert that a claim has arrived. If either e-mail could not be sent, the claim still stands and the history of the claim says so.

The claim file

Coverage check
What the policy record says about this loss: is the date of loss inside the term, was it notified in time, the sum insured and the excess against the amount claimed, conditions the policy is still subject to, and whether premium is overdue. These are facts for the handler; the decision stays yours.
Handler and follow-up
Assign the file to a colleague with the claims permission and set the date you look at it again, with a line on what it is for. A new claim starts with the handler and the first follow-up of its product, when the product sets them; the history says the product did.
Documents
Tick a document off when it arrives, or upload the file as that document. Ask for another document on this claim when you need one.
Financials and status
Reserve, settlement and excess, and the next step in the lifecycle. What was paid is the total of the payments on the claim.
Authority & payments
Where the claim stands against your claims authority, the referral to the insurer and their answer, and every payment on the claim.
History
Everything that happened on the file, with who did it.

The handler, the follow-up and the checklist are your team's working notes: the broker and policyholder portals do not show them. A broker does see the claims of their clients with the status and the amounts.

Statuses

Reported
Received, awaiting handling.
Investigating
Being assessed; reserve set.
Approved / Denied
Decision recorded with the reason.
Settled
Payment recorded.
Closed
No further action.

A claim moves forward along this path: the status picker only offers the next steps, denying needs a reason (it goes to the broker and into the file), settling needs the settlement amount, and a closed or denied claim can only be re-opened with a reason — never silently.

Claims authority: what you decide and pay yourself

A binding authority also says how far you handle claims. Record that on the binder (Binders, Claims authority) and the platform holds every claim under it to the agreement. Leave it unrecorded and nothing is checked.

Authority
Full (you decide and pay every claim), up to a limit per claim, or none (every claim goes to the insurer). A section can have its own authority and limit when the agreement differs per class of business.
The size of a claim
The largest of what is approved and paid on it, the settlement, and what is paid plus the outstanding reserve. A claim that grows past your limit shows as 'to refer' on the worklist.
Funding
A loss fund the insurer advances and tops up, which you pay from; or the insurer funds each payment, and you pay the claimant once their money is in.
Referrals go to
The insurer's claims address. Blank uses the lead underwriter's address on the binder.

A product can be stricter than its binder. Not every product is handled the same way. A small, high-volume product your team can decide and pay itself; on a larger or more complex one you may want the insurer involved sooner than the agreement requires. Set that on the Claims tab of the product, under Who decides a claim: as the binder says, your team up to a limit per claim, or the insurer for every claim.

  • The product's rule only ever makes the agreement stricter. A limit on the product that is higher than the binder's (or its section's) changes nothing: the binder's limit applies.
  • With 'the insurer decides every claim', your team completes the file and refers it; nothing is approved, paid or settled on the claim until the insurer's agreement is recorded.
  • A policy written outside a binder has only the product's rule. Without one, nothing is checked on its claims.
  • The rule applies to every claim on the product from the moment you save, also to claims that are open. The claim file says which rule applies and where it is set.

Within your authority you approve and pay the claim yourself. Above it, choose Refer to the insurer on the claim: the amount and your reasoning go to the insurer's claims address by e-mail and the referral stays open on the claim. Record their answer when it comes (agreed up to an amount, or declined, with who answered and their reference). From then on you settle and pay up to the agreed amount; a higher amount is a new referral.

Sharing the claim file with the insurer

The referral e-mail carries the amount and your reasoning, never documents. To decide, the insurer needs the file. On the Documents tab of the claim, Share the claim file compiles it from what the platform already holds and sends the insurer a secure link to it.

What goes in
A cover sheet (the parties, the policy, the figures, what you ask the insurer to agree and a list of what follows), the claim notification, the policy schedule, the endorsements, the conditions at bind with their questionnaire and your decision, and the documents uploaded on the claim. You tick what goes in; the cover sheet always does.
What stays out
The handler's internal notes. And on a policy with several insured persons, the health declaration and the conditions of the others: only those of the person the claim is about are offered.
One file
PDFs and images are merged into one PDF in that order. A document that is neither (a Word file, a protected PDF) travels beside it as its own download, and the cover sheet says so.
Who can open it
One address, the one you send it to. The link alone opens nothing: the recipient asks for a six-digit code, which goes to that address and is valid for ten minutes. Whoever has the link but not that mailbox gets nothing.
How long
You choose 7, 14 or 30 days. After that the link stops working and the copy of the file is removed. Revoke ends it at once, with a reason.
What you see
Every share on the claim with its recipient, its state and how often it was opened. Each opening, each code that was asked for and each revocation is a line in the history of the claim.

Why a link and not attachments: a claim file can hold data about someone's health. An attachment stays in every mailbox it passes through, can be forwarded without anyone knowing, cannot be taken back and leaves no record of who read it. A link is for one person, expires, can be withdrawn the moment it turns out to have gone to the wrong address, and shows you when it was opened. The e-mail itself carries nothing from the file, and your message to the insurer is printed on the cover sheet, not in the e-mail.

Payments on a claim

A payment is an indemnity to the claimant, an expense (a loss adjuster, a lawyer, a repairer) or a recovery you received. It is entered, approved and then marked paid with the date and the bank reference; who entered it and who approved it are both recorded. The platform records and checks payments; the transfer itself is made from your bank.

  • An indemnity is approved on an approved or settled claim; an expense can be paid while the claim is still being handled.
  • Approving is refused, with the reason, when it would take the claim past your authority without the insurer's agreement.
  • Marking a payment paid lowers the outstanding reserve by that amount and adds it to what is paid on the claim. A paid payment is final: correct it with a recovery or a new payment, never by editing.
  • A payment that is not going ahead is cancelled with a reason and stays on the file.
  • On a binder funded by the insurer, record the day their funds came in for a payment before you pay it out.

The Binders screen shows the loss fund per binder: what was paid from it and not yet reimbursed, and what is still available. Each payment is reported once on the claims bordereau of the period it was paid in; when the insurer reimburses that bordereau, record the funds received on it and the loss fund is whole again.

The worklist and the claims register

The Claims screen opens on every open claim. The four counts above the table (open, assigned to me, unassigned, follow-up due) are shortcuts — with a claims authority recorded there are three more: to refer to the insurer, awaiting the insurer, and payments to make. Filter further by status, product or product line, binder and handler. Export downloads exactly what is in view as an Excel workbook: one row per claim with the policy, product, binder, cause, dates, days open, handler, outstanding documents and every amount, plus a sheet that explains each column.

Reserves and payments are recorded per claim, documents and correspondence are attached, and every change is in the activity trail. Claims appear in the claims bordereau for their binder and in the loss ratio on the reports screen.

See it running.

Book a demo and we show you the complete platform live. Still stuck? Write to hello@soldek.io.