> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/reporting-and-analytics/bevica_power_bi/target_cost_sales_-bevica_power_bi.md).

# Target Cost: Sales (Bevica Power BI)

Use target costs for margin reporting and compare target vs actual cost of sales.

### Target Cost: Sales (Bevica Power BI)

### Summary

You can use Target Costs for the calculations on your sales.

See this article to understand it: [Item Sales Line 'Target Cost'](/documentation/guides/pricing-costs-and-charges/item_sales_line_target_cost.md)

> NOTE: For Open Sales to use Target Cost the appropriate setting must be set in Bevica Setup

### Usage

Use the **Sales Cost Type** selector to determine which Cost should be used; Actual or Target. This can be used as an interactive page filter to reports.

You can apply this filter at a page or all pages level if required. The below example adds a filter to the page.

> NOTE: Actual is the default if no other selection is made

Only the **Cost of Sales (All)** measure is affected. If you select 'Target' as your Cost Type then Cost of Sales - Actual, Expected, Inventory and Non Invtbl will return 0.

* This also affects Margin - i.e., you must use 'All' if using Target Cost.
* Sales Measures Global also work with Target Cost

The **Var % / £ Cost of Sales (Target vs Actual)** can be used to view the difference between Actuals and Target Costs to debug or understand variances.

### Calculation

The calculation is:

* Target Cost from Item Ledger Entries x Quantity
* If ILE Target Cost = 0 then Item Target Cost x Quantity (this would always use the current item target cost at report refresh)
* Else 0


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kb.bevica.com/documentation/reporting-and-analytics/bevica_power_bi/target_cost_sales_-bevica_power_bi.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.