Lifecycle & statuses
How an application becomes a policy, and what each status means. The same statuses appear in the Insurer Portal, the API and the webhooks.
Applications
submitted→under_review→approved| Status | Meaning | Moved on by |
|---|---|---|
submitted | The customer has paid and Sorplos has sent you the application. | You, by acknowledging it |
under_review | You've acknowledged it and are underwriting. | You |
rfi_required | You asked for more information. Sorplos is getting it from the customer — questions never go to the customer directly. | Sorplos, by answering — it then returns to under_review |
approved | You've accepted the risk. The policy follows when you confirm it. | You, by confirming the policy |
rejected | You've declined it. Sorplos refunds the customer. | — |
Policies
scheduled→active→expired| Status | Meaning |
|---|---|
scheduled | Confirmed, with a start date in the future. |
active | In force. |
manual_review | Held because the premium you confirmed differs from what the customer paid. Sorplos resolves it with you. |
expired | Past its expiry date. |
cancelled | Cancelled from an effective date. |
Policies are never overwritten. Every correction creates a new version (v2, v3…) and sends policy.corrected; earlier versions stay on record.
Claims
submitted→under_review→approved→settled→closedA claim can also be rejected. On the managed track Sorplos runs the claim on the customer's behalf; on the assisted track the customer deals with you and Sorplos guides them.
Products and prices
awaiting_company_admin→awaiting_sorplos→scheduled→liveNew listings and price changes are proposals. They need two approvals — your Company Admin, then Sorplos — and apply on their effective date. Nothing you upload changes a live price on its own, and every approved change keeps the previous version so it can be rolled back.