> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/reports/expenses-by-vendor.md). # Expenses by Vendor See exactly who you're paying the most and how your vendor spending breaks down. The Expenses by Vendor report shows a ranked list of every vendor you've paid, with totals for any period. It's the fastest way to see where your money is going and spot spending that's higher than expected. Go to **Accounting** → **Expenses by Vendor**. *** ### What you're looking at Each row represents a vendor (counterparty), with the total amount paid during the selected period. Click any vendor total to open the General Ledger, the complete transaction-by-transaction record behind your reports, filtered to that vendor and period. *** ### Change the date range Use the date picker to select any period. If you have multiple entities, use the entity dropdown to switch between them. The report shows one business at a time. *** ### Period columns Use the column selector to show a single **Total only** column, or to break vendor totals down **By month**, **By quarter**, or **By year**. *** ### Compare Use the **Compare** dropdown to add **Previous period (PP)** or **Previous year (PY)** alongside the current period. Show variance as a **Percentage (%)** or **Amount ($)**. *** ### Export Use the download button in the top right to export the report as **.xlsx** or **.pdf**. *** ### When to use it * To review your biggest expenses at a glance * To identify vendors you're paying regularly that you may want to renegotiate or cancel * To prepare for a budget conversation with your accountant * To answer the question: *who did I pay the most last year?* *** ### Counterparties For vendors to appear accurately in this report, [transactions](/common-workflows/transactions.md) need to have a counterparty assigned. Kick assigns counterparties automatically for most transactions, and you can set [Rules](/common-workflows/rules.md) to ensure specific vendors are always tagged correctly. → [Rules](/common-workflows/rules.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.kick.co/reports/expenses-by-vendor.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.