> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-central/commander-central-user-guide/site-configuration/store-operations/tax-rates.md). # Tax Rates Tax rates configurations allows for up to eight different tax rates to be configured at one location. Tax rates can be added to departments or PLUs after they have been created to ensure the correct tax amount is collected on different types of sales.

Field/Button	Description
Name	Enter a descriptive name for the fee. The name prints on the receipt.
Indicator	Assigns an indicator to the item the tax was added to. The indicator will print out on the receipt to indicate one or more taxes were applied to specific departments or plus.
Rate	Enter in the percentage of the tax rate. For example, if the state tax rate was 7% then the rate would be 7.
Percent Start	The minimum dollar amount that can be taxed. For example, if taxes did not apply to transactions less than $0.10 then the percent start would be $0.10.
Price Includes Tax	Select this option if the price includes taxes.
Use Canadian GST	Used for Canadian Goods and Services tax.
Use Breakpoint Table	Select this option if the taxes configured require a breakpoint table. A breakpoint table specifies the taxable amount for the department or PLU it is assigned based on the cost of the individual line item.
Prompt for Exemption	See the Verifone Commander User Reference for more details on Breakpoint Tax configurations.

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-central/commander-central-user-guide/site-configuration/store-operations/tax-rates.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.