> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/service/insurance-companies.md).

# Insurance companies

The insurance companies an insurance claim can name, each linked to a customer record.

This is the list staff pick from when a service order is an insurance claim. Each entry is linked to a customer record that stands for the insurer.

|                   |                                                                                                                                                                                             |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Where             | **Settings → Insurance companies**, in the **Service orders** group                                                                                                                         |
| Used              | At intake and on the service order, when **Coverage** is **Insurance claim**                                                                                                                |
| Who can change it | Users with the **Service configuration** permission. Only they see the section in the menu. See [Permissions and roles](https://docs.flowretail.com/docs/service/permissions-and-roles.md). |

***

## The list

The list shows every entry by name, with the customer record it is linked to under **Invoiced as**. A deprecated entry stays in the list, greyed and marked **Deprecated**.

![Settings → Insurance companies with three entries, one of them marked Deprecated, and a row menu open](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FqSB3JoCFsxZmeOwZnR6C%2Fservice-insurance-companies-list.webp?alt=media)

The row menu has **Deprecate** or **Reactivate**, and **Delete**.

## New insurance company

Choose **New insurance company**, or select an entry to open **Edit insurance company**.

![the New insurance company dialog with a name filled in and the Invoiced as customer search open](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FcQRg0MK3HVxIddYbc8hm%2Fservice-insurance-company-dialog.webp?alt=media)

| Field           | Meaning                                                                                                                                                                                                                                                                              |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Name**        | Required, and unique in your company.                                                                                                                                                                                                                                                |
| **Invoiced as** | Required. The customer record that stands for the insurer. Search your customer register, or choose **New customer** to create one; the new record starts as a company. A customer record can be linked to only one entry. It is not the customer the sale is billed to (see below). |

***

## Where it is used

* At intake, choosing **Insurance claim** under **Coverage** shows **Insurance company**. The list offers every entry that isn't deprecated, plus **None**, so you can register a claim before you know the insurer.
* Picking an entry puts its linked customer record on the service order as the insurer. Staff can change it later on the service order.
* The insurer is recorded for information. The sales order is billed to the service order's own customer, whatever the coverage.
* On an insurance claim, the intake slip prints the insurer, the claim number and the deductible.

***

## Good to know

* **Linking another customer record** affects service orders registered from then on. Existing service orders keep the record they have.
* **Deprecate** removes the insurer from the intake list but keeps it in this list. **Reactivate** offers it again. Editing a deprecated entry doesn't reactivate it.
* **Delete** removes the entry for good and is always possible. Service orders that name the insurer keep it.
* **Merging customer records** moves the link to the record that remains.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flowretail.com/docs/service/insurance-companies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
