> 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/reporting_in_bevica_-_overview/checking_sales_line_margins.md).
# Checking Sales Line Margins
Check estimated margins on open sales lines before posting.
Bevica gives you the ability to check estimated sales lines margins as documents are created.
See also [Checking Inventory Margins](/documentation/reporting-and-analytics/reporting_in_bevica_-_overview/checking_inventory_margins.md).
{% hint style="warning" %}
**Prerequisites**
Customer and item setup.
Creating sales transactions.
{% endhint %}
### Margin checks on Sales Line Documents
When a sales line is created for **Inventory** Items, the following fields are available:
| Field | Note |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Unit Cost (LCY) | For item lines, this is the average cost of stock in inventory for the duty status of the order at the time the line is created.
Other line types may populate this field from their master record.
|
| Customer Unit Price | Bevica calculates the price per Unit of Measure the customer will pay for the goods. This value is excluding VAT, and includes Line Discount and any amount of Invoice Discount apportioned to it. It is meant for reporting only.
Customer Unit Price = ((Line Amount - Inv. Discount Amount) / Quantity)
|
| Customer Unit Price (LCY) | As above displayed in local currency. |
| Cash Margin | Bevica calculates the cash margin for the sales line, the value is in currency.
Customer Unit Price – Unit Cost.
|
| Cash Margin (LCY) | As above, in local currency. |
| Margin % | Margin % = ((Customers Unit Price - Unit Cost) / Customers Unit price) expressed as a percentage. |
The values are meant as an operational estimate at the time of creating and managing sales documents, prior to the transaction being posted. On posting, the values are copied to their appropriate posted documents.
{% hint style="info" %}
**Notes** The field **Profit %,** visible on sales transaction lines, is the same value copied directly from the Item card, it does not recalculate as prices or discounts are amended on any sales line.
{% endhint %}
### Actual Posted Profit Values
On posting a sales transaction involving stock, Bevica uses FIFO to refine cost of goods sold on item sales lines, creating **Value Entries** and **GL Entries**. These values will almost certainly be different from the Margin fields described above.
To view these posted values navigate to the **Item Ledger Entry**, more information here [Checking Inventory Margins](/documentation/reporting-and-analytics/reporting_in_bevica_-_overview/checking_inventory_margins.md).
{% hint style="info" %}
**Notes** Default Bevica is setup to calculate FIFO adjustments automatically on posting transactions. If this had been changed, the values above will not reflect the latest costs until the **Adjust Cost - Item Entries** routine is run.
{% endhint %}
### Sales Margin Filtered View
To help manage sales margins, you can create a filtered **Open Sales Lines** (see also [Open Sales Lines](/documentation/guides/sales/open_sales_lines_and_open_purchase_lines.md) and [Open Purchase Lines](/documentation/guides/purchasing/open_sales_lines_and_open_purchase_lines.md)) list setting your own upper and lower **Margin %** values, for example: i.e. ‘**< 25|>75’**.
This filter can be reviewed periodically for any percentages within your filter. You can then save the view and this will serve as a report to check your sales margins.
To read more about filters and views, please check the [Sorting, Searching and Filtering](https://docs.microsoft.com/en-us/dynamics365/business-central/ui-enter-criteria-filters) document.
---
# 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/reporting_in_bevica_-_overview/checking_sales_line_margins.md?ask=&goal=
```
`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.