> 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 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 to drill into the individual transactions that make up their total. *** ### Change the date range Use the date picker to select any period. If you have multiple entities, use the entity dropdown to view a single business or all of them combined. *** ### 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 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.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 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.