> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/owners-playbook/build-your-club/build-a-location/manage-tax-settings.md).

# Manage Tax Settings

Tax Settings let you define which products (bookings, events, memberships, etc.) should have tax applied, and at what percentage **for a specific venue**. Use this screen to keep each venue's tax configuration aligned with local rules across different types of revenue.

## Where to find Tax Settings

* Open **Venues** in the web admin
* Select the **Venue** you want to configure
* Go to the **Payments** tab
* Scroll to the **Taxes** section

\[SCREENSHOT NEEDED: Venues > \[Venue] > Settings page showing the Tax Settings section]

**PLEASE NOTE:** Tax settings are configured per venue. If you operate multiple venues in different locations, you'll need to set up taxes separately for each one.

You can define taxes at two levels:

Region – a broader geographic level (for example, a state or province).

Area – a more specific location within a region (for example, a city or zone).

If no tax is configured at the area level, the region tax will apply by default. When an area tax is configured, it takes precedence and overrides the region tax for that area.

## Add a new tax

Each tax you configure has a name, a percentage, and a list of product types it applies to.

* Click **Add Tax** button
* In the new tax card:
  * Enter a **Name**
    * Example: "NYC Sales Tax", "Court Booking Tax", "Membership Tax"
  * Enter the **Percentage**
    * Example: `8.75` for an 8. 75% tax
  * Under **Apply To**, select one or more product types the tax should apply to

\[SCREENSHOT NEEDED: Venue Tax Settings panel with a new tax card]

**PLEASE NOTE:** A tax must have a **name** and at least one **Apply To** option selected before you can successfully save the venue's settings.

## Apply To options

The **Apply To** field controls which types of purchases at this venue will include this tax. Some examples you may see:

* **Court bookings** – Standard court reservations
* **Clinic signup** – Clinic-style programs
* **Class (event type)** – Classes configured as events
* **Kids class signup** – Kids' class formats
* **Coaching** – Coaching sessions and private lessons
* **Day pass (Court +)** – Day passes for Court+ products
* **Events (event type)** – Community events and similar offerings
* **Additional guests (Court +)** – Extra guests added to Court+ reservations
* **Guest spot (Spot +)** – Guest spots on Spot+ reservations
* **Membership** – Membership subscriptions
* **Private events** – Private event signups and admin charges for private events
* **Regular (event type)** – Regular event-type products
* **Video replays** – Paid video replay products
* **Series signups** – Signups for an event series

As you select options, the helper text under the field shows **Exempt categories**, which are the product types that will **not** have this tax applied. This makes it easier to confirm that only the right products are taxed.

### Event signups (automatic behavior)

When you choose certain **event-type** options (for example, **Class (event type)**, **Events (event type)**, **Private events**, or **Regular (event type)**), the system automatically includes the underlying "event signup" category for you. This ensures taxes are consistently applied at signup time for those events, without requiring you to manage a separate hidden option.

You don't need to do anything extra for this behavior; it should happen automatically when you pick the relevant event-type options in **Apply To**.

## Edit an existing tax

To adjust a tax configuration for a venue:

* Find the tax card you want to change in that venue's **Tax Settings**
* Update the **Name**, **Percentage**, or **Apply To** options as needed
* Review the **Exempt categories** helper text to confirm the correct coverage
* Save the venue settings when you're done

Changes you make here will affect new charges going forward at this venue that meet the selected **Apply To** criteria.

## Remove a tax

If a tax no longer applies at a venue:

* On the relevant tax card, click **Remove**
* Confirm the removal (if prompted)
* Save the venue settings

After removal, that tax will no longer be applied to new qualifying purchases at this venue.

## Validation and error messages

If there are issues with your Tax Settings, you'll see an error notification when you try to save. Common validation messages include:

* **"Tax #X: Name is required"** – The tax is missing a name.
* **"\[Tax Name]: At least one Apply To option is required"** – The tax has no product types selected.

Fix these issues (add a name, select at least one **Apply To** option) and try saving again.


---

# 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://docs.podplay.app/owners-playbook/build-your-club/build-a-location/manage-tax-settings.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.
