> 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/common-workflows/memos.md). # Memos A memo is a free-text note attached to a transaction. It's the simplest way to add context to a charge - who you met with, what a purchase was for, or anything else that isn't obvious from the merchant name or amount alone. *** ### When to use a memo Memos are especially useful for: * **Meals and entertainment** - note who you met and the business purpose (the IRS requires this for the deduction to hold up) * **Unusual or one-off purchases** - explain what it was for so your accountant doesn't have to ask * **Ambiguous vendors** - a vendor name like "Amazon" could be office supplies, software, or personal. A memo clarifies it * **Transactions your accountant flagged** - if they opened a [Task](/working-with-your-team/tasks.md) asking about a charge, a memo on the transaction itself is the clearest way to answer *** ### Add a memo to a single transaction 1. Open any transaction by clicking on it 2. Click the **Memo** field 3. Type your note and save {% embed url="" %} *** ### Add memos in bulk If you need to add the same note to multiple transactions at once: 1. Select the transactions in the Transactions tab 2. Open the **Actions** toolbar 3. Choose **Add memo** and enter your note {% embed url="" %} *** ### Memos and your accountant Memos are visible to everyone with access to your workspace. Your accountant sees them when reviewing transactions, which means fewer back-and-forth questions and a faster close process. If you're preparing for [tax season](/best-practice-guides/tax-prep-guide.md), going through transactions with missing context and adding memos is one of the highest-value things you can do before handing off to your accountant. --- # 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: ``` GET https://docs.kick.co/common-workflows/memos.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.