> For the complete documentation index, see [llms.txt](https://help.flowerbuddy.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.flowerbuddy.co/reference/event-page/taxes-discounts-fees/manage-event-taxes.md). # Manage event taxes Event taxes are built from two parts: the tax assigned to the event and the line items marked as taxable. Review both before relying on the calculated amount. A Tax Profile defines one reusable tax as a percentage or amount. A Tax Group keeps several Tax Profiles together so they can be added to an event as a set. ## Prepare the taxable line items Before adding the event tax, review the **Sales Tax** setting on each recipe, recipe group, or applicable line item: 1. Open **Recipes**. 2. Expand a line item. 3. Use **Sales Tax Applicable** when its price should contribute to the taxable amount. 4. Use **Sales Tax Not Applicable** when it should not. The tax calculation uses the taxable event lines and applicable discounts. Marking a recipe as taxable does not add a tax rate by itself. ## Add a Tax Profile Select **Add Tax** to open a dialog with a **Tax Profile** field. The dialog adds a reusable profile that already exists for the workspace; it does not edit the profile itself.

1. Select **Taxes, Discounts, & Fees**. 2. Select **Add Tax**. 3. Choose a **Tax Profile**. 4. Select **Add Tax**. FlowerBuddy does not list a Tax Profile that is already on the event. If the required profile does not exist, use **Create a new tax profile?** in the dialog, define the percentage or amount, then add it. The new tax row uses the selected profile's name, type, and rate or amount. Those profile fields are not edited on the event row. ## Add a Tax Group Use a Tax Group when the event needs a saved set of taxes: 1. Select **Add Tax Group**. 2. Choose the group. 3. Select **Add Tax**. FlowerBuddy adds each Tax Profile from the group that is not already present. The group name appears as a chip above the tax rows and on its associated taxes. You can create a new Tax Group from the same dialog when the reusable set does not exist yet. ## Review Cost, Price, and warnings For each tax row: * **Tax Type** and **Tax Rate** or **Amount** come from the Tax Profile. * **Cost** is FlowerBuddy's calculated tax for the current event. * **Price** is the tax amount included in the client price. Normally, Cost and Price should match. A tab warning appears when they differ. Review the taxable line items, discounts, Tax Profile, and current calculated Cost, then update Price when it should match the calculation. A zero-tax warning means no tax has been added or the total calculated tax is zero. This can be correct for a non-taxable event, but it should be reviewed rather than ignored accidentally. ## Remove a tax or Tax Group Removing a Tax Group chip removes only the group's association from this event. Its tax rows remain. Use this when the individual taxes should stay but the event should no longer identify them as that group. Deleting a tax row removes that tax from the event and removes any event Tax Group associations that contain its Tax Profile. Review the other taxes before confirming. ## Recognize amendments after signing After a contract is signed, adding, changing, or removing taxes can create amendments. Added or deleted labels identify the current change, and a reset control can return a row to its contracted value when available. Review the event's current Price and pending amendments before publishing an updated proposal or confirming the changes manually.