> 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.md).

# common workflows

- [Transactions](https://docs.kick.co/common-workflows/transactions.md): View and manage all the financial activity flowing through your connected accounts.
- [Reviewing Transactions](https://docs.kick.co/common-workflows/reviewing-transactions.md): Sign off on transactions field by field, see who reviewed what and when, and filter to what still needs eyes.
- [Categorization](https://docs.kick.co/common-workflows/categorization.md): Kick automatically categorizes your transactions and learns from your changes
- [Personal to Business](https://docs.kick.co/common-workflows/personal-to-business.md): Capture business expenses that were paid from a personal account.
- [Reconciliation](https://docs.kick.co/common-workflows/reconciliation.md): Confirm that your Kick transactions match your official bank statements, period by period.
- [Journal Entries](https://docs.kick.co/common-workflows/journal-entries.md): Understand what journal entries are, when they're created, and how to view them in your books.
- [Revenue recognition](https://docs.kick.co/common-workflows/revenue-recognition.md): Spread a sale across the months you earn it, instead of booking it all when you invoice or get paid.
- [Transfers](https://docs.kick.co/common-workflows/transfers.md): Make sure money moving between your accounts is recorded correctly and doesn't skew your reports.
- [Splits](https://docs.kick.co/common-workflows/splits.md): Break a single transaction into multiple line items when a charge covers more than one category or business.
- [Rules](https://docs.kick.co/common-workflows/rules.md): Automate how Kick handles recurring transactions so you spend less time on manual categorization.
- [Classes](https://docs.kick.co/common-workflows/classes.md): Track performance by location, department, project, or any other dimension that matters to your business.
- [Counterparties](https://docs.kick.co/common-workflows/counterparties.md): Vendors and customers in Kick - how they work and how to manage them.
- [Loans](https://docs.kick.co/common-workflows/loans.md): How to record loan payments correctly so your books stay accurate and your Balance Sheet reflects what you actually owe.
- [Payroll](https://docs.kick.co/common-workflows/payroll.md): How payroll transactions flow into Kick and what to do if you run payroll outside of Gusto.
- [Memos](https://docs.kick.co/common-workflows/memos.md): Add notes to transactions to explain what they were for - useful for your accountant, your records, and audit readiness.
- [Documents](https://docs.kick.co/common-workflows/documents.md): How to store, attach, and find business documents in Kick - contracts, statements, tax forms, and more.
- [Invoicing](https://docs.kick.co/common-workflows/invoicing.md): View invoices synced from Stripe, Mercury, and BILL, and create and send invoices directly from Kick.
- [Bill Pay](https://docs.kick.co/common-workflows/bill-pay.md): View and manage your bills in Kick, with real-time sync from Ramp or BILL.


---

# 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/common-workflows.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.