---
title: Use For Cost Configuration
description: "In order to test basic rating with a `Use For Cost` configuration, you **must have the following**before proceeding to the `usageRateGroup` , `usageRate` and `usageRatePlan` setup/screens: - Have 1x MRC service that has the checkbox `Usage Based Service = true`…"
url: "https://learn.logisense.com/docs/1894645781/"
updated: "2025-06-11"
category: "Usage & Rating"
---

# Use For Cost Configuration

In order to test basic rating with a `Use For Cost` configuration, you **must have the following**before proceeding to the `usageRateGroup` , `usageRate` and `usageRatePlan` setup/screens:

- Have 1x MRC service that has the checkbox `Usage Based Service = true`

![](https://learn.logisense.com/wp-content/uploads/2025/05/use-for-cost-configuration-1.png)

- Have 1x package + frequency setup that uses the MRC service that was created from the above bullet

**Package**

![](https://learn.logisense.com/wp-content/uploads/2025/05/use-for-cost-configuration-2.png)

**Frequency**

![](https://learn.logisense.com/wp-content/uploads/2025/05/use-for-cost-configuration-3.png)

Now that we have the service, package and frequency setup we can proceed with the `Use For Cost` configuration.

- Create the first set of `usageRateGroup` - `usageRate` - `usageRatePlan`
  - usageRateGroup screen: useForCost = true
  - usageRate screen: rate type = rated / type= use for cost
  - usageRatePlan screen: add the usageRateGroup created in the first sub bullet into the new `usageRatePlan` (i.e. useForCost_plan)

**First set - usageRateGroup**

![](https://learn.logisense.com/wp-content/uploads/2025/05/use-for-cost-configuration-4.png)

**First set - usageRate**

![](https://learn.logisense.com/wp-content/uploads/2025/05/use-for-cost-configuration-5.png)

**First set - usageRatePlan**

![](https://learn.logisense.com/wp-content/uploads/2025/05/use-for-cost-configuration-6.png)

- Create the second set of `usageRateGroup` - `usageRate` - `usageRatePlan`
  - usageRateGroup screen: useForCost = false
  - usageRate screen: rate type = rated markup / type= standard
  - usageRatePlan screen: none and you must add the usageRateGroup created from the the first sub bullet of the second set into the usageRatePlan of the first set (i.e. useForCost_group_2 is added into useForCost_plan)

**Second set - usageRateGroup**

![](https://learn.logisense.com/wp-content/uploads/2025/05/use-for-cost-configuration-7.png)

**Second set - usageRate**

![](https://learn.logisense.com/wp-content/uploads/2025/05/use-for-cost-configuration-8.png)

**Second set - usageRatePlan**

![](https://learn.logisense.com/wp-content/uploads/2025/05/use-for-cost-configuration-9.png)

Now that you have completed the `Use For Cost` configuration it is time to test rating.

- Have an account and ensure that it has a proper jurisdiction code for taxing purposes
- Create an account package using the MRC service that was created from the prerequisite steps and ensure that you select the `Use For Cost` rate plan (i.e. useForCost_plan)
- Also ensure that the service has an proper UdrUsageIdentifier
- Send usage against the service within the current period

**Verify rating in the following tables**

To check quickly if you have a proper UDRMediated and UDRRated record you can run the SQL below where `UdrUsageIdentifier` is equal to whatever was added as the UdrUsageIdentifier into the service:

```
SELECT M.ID, M.Date, M.UDRUsageIdentifier, M.Value, R.UDRMediatedID, R.ValueRounded, R.ChargePreBucketing, R.Charge
FROM UDRMediated M INNER JOIN UDRRated R
    ON M.ID = R.UDRMediatedID
    WHERE UDRUsageIdentifier like '%<UdrUsageIdentifier>%' ORDER BY ID DESC
```

- Note that this query is expected to return 1 line/record which is from the UdrMediated and UdrRated tables
  - If the query returns blank then please check the `UDRUsageException` table for further investigation
- Let’s take this account for example: I sent a “901” value for the usage towards the service with rated cost = 1 and the rated markup cost = 1 (based on useForCost_1 rate plan)

![](https://learn.logisense.com/wp-content/uploads/2025/05/use-for-cost-configuration-10.png)

![](https://learn.logisense.com/wp-content/uploads/2025/05/use-for-cost-configuration-11.png)

- How `Use For Cost` works is that it “adds” the rated markup cost on top of the rated cost so in this particular test we have:
  - Rated cost = 1 x value = 901 = Rated cost charge = $901
  - Rated markup = 1 x value = 901 = Rated markup cost charge = $901
  - (Rated cost charge = $901) + (Rated markup cost charge = $901) = $1,802.00 which is what you can see from the table and after the account was billed

![](https://learn.logisense.com/wp-content/uploads/2025/05/use-for-cost-configuration-12.png)

There’s definitely room for experimentation, like having different rated cost/rated markup cost amounts also with different rate types but for now that concludes the basic `Use For Cost` setup and configuration.