Creating claims with unverified policies

An unverified policy is a policy that is created during the FNOL process based on information supplied by an adjuster or by the caller application. This information may or may not correctly correspond to information in a Policy Administration System.

Unverified policies let an adjuster start the FNOL process without information from the PAS. Eventually, the policy must be refreshed with data from the PAS, thereby converting it to a verified policy. You cannot complete the claim process and make payments on a claim while the policy is still unverified.

Unverified policies can be used in either a test or production system. In a test system, unverified policies may be a useful way to create policies without having an integration point to a PAS and without needing to enable the Test Util API. In a production system, unverified policies are useful when there is a need to start the FNOL process and, for some reason, the policy is unavailable to ClaimCenter or cannot be found.

Unverified policies and composite requests

In ClaimCenter, you cannot create a policy that is not attached to a claim. Also, you cannot create a claim that has no policy. Therefore, when creating claims with unverified policies, you must create the unverified policy and the claim in the same call. The only way to do this is in the context of a composite request.

For more information on how to work with composite requests, see Composite requests.

The following sections discuss the endpoints used to create unverified policies and their child objects. In most cases, these endpoints are used as URIs inside a composite request, and not as the main URL for the request itself. The main URL for composite requests is always POST /composite/v1/composite.

To view an example of a payload that creates a complete claim with an unverified policy in a composite request, see Sample composite claim payload.