> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/settings/access/vendor-client-best-practices.md).

# Vendor & Client: Best Practices

Best practices for vendors and clients working together on Anedot, including Billing Agreements, vendor access, Permission Sets, Teams, and Vendor Earnings.

When a **vendor** (a consultant, agency, or other service provider) works with a **client** (the organization that owns the fundraising account), the two usually set up a [Billing Agreement](/settings/finance/billing-agreements.md), vendor user access, and sometimes [Teams](/settings/access/teams.md). This article covers what a vendor account is, how Billing Agreements work between vendors and clients, and how to set up vendor access.

## What Is a Vendor Account?

A vendor account is an Anedot account for consultants, agencies, and service providers. Vendors use it to:

* Receive markup fees from clients through Billing Agreements.
* Review those earnings in **Finance > Vendor Earnings**, which replaces **Transactions** in the Finance menu for vendor accounts. It lists each client donation the vendor earned a markup on, with the amount, Anedot fees, vendor fees, and net.

## Billing Agreements

A Billing Agreement lets a vendor collect a markup on donations made to a client's Action Pages. The client creates the agreement in their own account and names the vendor as the recipient. See [Billing Agreements](/settings/finance/billing-agreements.md) for the steps.

### For Vendors

* Share your vendor account ID with the client. It's the ID after `/accounts/` in the web address when you're signed in to your vendor account.
* Agree on the markup rate and terms with the client before work begins. A **Markup** agreement can be more than 0% and up to 95%. To track a relationship billed outside Anedot, the client can use an **Offline** agreement instead.

### For Clients

* Only users with **Billing Agreements: Edit** permissions can create or terminate agreements. The built-in **Owner** and **Super Admin** permission sets include it. **Admin** does not.
* The agreement takes effect as soon as it's created, so confirm the terms in writing first.
* The markup rate and terms can't be changed after the agreement is created. To change them, create a new agreement and terminate the old one.

## Recommended Vendor Access

Invite vendor staff as users on the client's account with only the access their work needs. See [Users](/settings/access/users.md).

| Access                    | When to use                                                                                                                                                               |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Custom permission set** | Building pages, running campaigns, or setting up Billing Agreements, without bank account or user management. See [Permission Sets](/settings/access/permission-sets.md). |
| **Super Admin**           | Long-term partners who manage the full account, including users and bank accounts.                                                                                        |

Pair a custom permission set with [Teams](/settings/access/teams.md) when the vendor should only see certain Action Pages. Leave **Account Management: Edit Bank Accounts** off for vendor permission sets so your organization controls where deposits go.

## Teams For Vendor Visibility

* **Vendors** see only the Action Pages tagged for their Team.
* **Clients** can limit vendor access by campaign or department.

## Checklist: What Vendors Need From Clients

1. A written agreement on the markup terms.
2. User access with a [custom permission set](/settings/access/permission-sets.md) or Super Admin.
3. A Team assignment, when using [Teams](/settings/access/teams.md), made after the vendor accepts their invite.
4. A Billing Agreement created by the client with the vendor's account ID.

## Related Articles

* [Billing Agreements](/settings/finance/billing-agreements.md)
* [Users](/settings/access/users.md)
* [Permission Sets](/settings/access/permission-sets.md)
* [Teams](/settings/access/teams.md)
* [Connected Accounts](/settings/access/connected-accounts.md)


---

# 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.anedot.com/settings/access/vendor-client-best-practices.md?ask=<question>&goal=<user_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.