> 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/accountants/readme.md). # Kick Docs for Accountants Guides for accounting firms running client books in Kick, from firm setup and onboarding through bookkeeping, close, and reporting. ### Frequently accessed


Setup Guide	Get your firm and first client set up in minutes	Setup Guide
Close Guide	Close the books faster using Kick best practices	Close Guide
Catch-Up Guide	Clean up multiple historical periods for new clients with ease	Catch-Up Guide
Multi-Entity	Streamline intercompany review and build automations that run across entities	Multi-Entity
Categorization	Learn how Kick's model works with Rules to automate categorization with accuracy	Categorization
Chart of Accounts	Use Kick's CoA templates to automate reporting based on entity type, or create one custom	Chart of Accounts
Transfers	Best practices for clearing account review and transfer automations	Transfers
Rules	Automate every part of your month-end close	Rules
Contact Us	Need help? Our team is here to support.	Contact Us

--- # 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/accountants/readme.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.