Rating overrides
When you quote a job, PolicyCenter rates the job to determine the cost of each coverage. This information is stored in a series of Cost objects. The Cost objects are then used to calculate the quote.
PolicyCenter also provides the ability to manually override the rating for one or more specific Costs. When you override rating, you can change exactly one of the following Cost values:
- Base rate
- Adjusted rate
- Amount
- Term amount
You cannot override costs on a job until the job has been quoted. Overriding a cost does not change the status of the job. It remains with its status of "Quoted". Also, some cost types may be designated as not allowing overrides. For example, tax costs may not allow overrides as they must always reflect a fixed percent of some other cost.
In the base application, the only lines of business that support rating overrides are: Worker’s Compensation, Inland Marine, and Commercial Property. However, any line of product could be configured to support rating overrides.
For more information on the business functionality of rating overrides, see the Application Guide.
Rating overrides in Cloud API
To create a rating override, you must first determine the IDs of the relevant Cost objects. You can then override the rate or amount of each Cost as appropriate.
For example, suppose there is a quoted submission for a Commercial Property policy. The submission's ID is pc:S99. The policy includes a building with Business Personal Property Coverage. There are two costs for this coverage:
- Business Personal Property Coverage Basic Group I
- Base rate: 0.1500
- Adjusted rate: 0.1148
- Term amount: 11.00
- Amount: 11.00
- Business Personal Property Coverage Basic Group II
- Base rate: 0.1500
- Adjusted rate: 0.0822
- Term amount: 8.00
- Amount: 8.00
You want to modify these costs in the following way:
- Business Personal Property Coverage Basic Group I
- Override base rate value: 0.2000
- Business Personal Property Coverage Basic Group II
- Override term amount value: 10.00
- Override base rate value: 0.2000
Retrieving Cost IDs
To retrieve the costs for a quoted job, use the following endpoint:
- GET
job/v1/jobs/{jobId}/costs
The following is an example of a request for the costs for the submission discussed in the previous example, and a portion of the response. From this output, you can see that the IDs of the two costs are 49 and 50.
GET job/v1/jobs/pc:S99/costs
{
"count": 5,
"data": [
{
"attributes": {
"adjustedRate": "0.1148",
"amount": {
"amount": "11.00",
"currency": "usd"
},
"baseRate": "0.1500",
"coverable": {
"displayName": "1: Building # 1",
"id": "14"
},
"coverage": {
"displayName": "Business Personal Property Coverage",
"id": "CPBPPCov"
},
"id": "49",
"termAmount": {
"amount": "11.00",
"currency": "usd"
}
}
},
{
"attributes": {
"adjustedRate": "0.0822",
"amount": {
"amount": "8.00",
"currency": "usd"
},
"baseRate": "0.1500",
"coverable": {
"displayName": "1: Building # 1",
"id": "14"
},
"coverage": {
"displayName": "Business Personal Property Coverage",
"id": "CPBPPCov"
},
"id": "50",
"termAmount": {
"amount": "8.00",
"currency": "usd"
}
}
},
...
Creating rating overrides
To create a rating override, use the following endpoint:
- POST
job/v1/jobs/{jobId}/override-rating
The body of the request must contain an overrides
array. Each member
of the array must specify the costId
of the associated Cost and
exactly one of the following override properties:
overrideAdjustedRate
overrideAmountBilling
overrideBaseRate
overrideTermAmountBilling
A given Cost can only have one override at a time.
(The OverrideCostsAttributes
schema also includes two deprecated
fields: overrideAmount
and overrideTermAmount
.
These fields have been included for backwards compatibility. However, Guidewire
recommends using overrideAmountBilling
and
overrideTermAmountBilling
, respectively, as the latter fields
use the policy's settlement currency.)
You can optionally provide an overrideReason
, which must be defined
as a string.
The response to the /override-rating
call contains the Costs for the
entire job.
Rating overrides example
The following is an example of a POST that creates the two rating overrides discussed in the previous example.
POST job/v1/jobs/pc:S99/override-rating
{
"data": {
"attributes": {
"overrides": [
{
"costId": "49",
"overrideBaseRate": ".2",
"overrideReason": "Greater risk level at this location"
},
{
"costId": "50",
"overrideTermAmountBilling": "10",
"overrideReason": "Greater risk level at this location"
}
]
}
}
}
Amount overrides compared to rate overrides
For a given Cost, you can override either the amount (using either the
overrideAmountBilling
or
overrideTermAmountBilling
fields) or the rate (using either the
overrideBaseRate
or overrideAdjustedRate
fields).
The approach to use is determined by how rating is calculated for the given line of business. Some lines of business, such as the base configuration Worker's Compensation line, use amount overrides. Other lines of business, such as the base configuration Commercial Property line, use term overrides.