> 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/documents.md). # Documents How to store, attach, and find business documents in Kick - contracts, statements, tax forms, and more. Kick lets you store and attach business documents directly in your workspace: receipts, contracts, bank statements, tax forms, vendor agreements, and anything else your accountant or business might need on hand. *** ### What to store in Kick Documents works best for records that are tied to specific transactions or need to be accessible to your accountant: * **Bank and credit card statements** - useful for reconciliation and as backup if a connection ever gaps * **Loan agreements** - important context when [splitting](/common-workflows/splits.md) payments between principal and interest * **Vendor contracts** - useful when a recurring charge needs context or changes amounts * **Tax forms** - 1099s, W-2s, and year-end processor summaries from Stripe or PayPal * **Payroll records** - supporting documentation for payroll journal entries * **Large purchase invoices** - anything over $75 that might require documentation for a deduction *** ### How to upload and attach documents **Attach to a transaction:** 1. Open any transaction by clicking on it 2. Click **Upload receipt** 3. Choose **Upload Receipt** to add a file from your device, or **Browse from documents** to link an existing file from your Documents library The document is stored in Kick and linked to that transaction - so when your accountant opens it, everything is in one place. **Upload to the Documents library:** For documents that aren't tied to a single transaction - like a loan agreement or a vendor contract - go to **Documents** in the left nav and upload directly. Search by filename or keyword to find files later. Scanned receipts are automatically renamed to `Merchant - Date - Amount` when Kick can read the receipt details. You can restore the original filename from the document row menu or as a bulk action. *** ### Sharing with your accountant Any document you upload is immediately visible to team members with access to your workspace. There's no need to email files or share folders outside Kick - your accountant sees everything when they log in. If your accountant needs a specific document, they can request it through [Tasks](/working-with-your-team/tasks.md) and you can attach it directly in the task thread. *** ### Documents at tax time At year-end, having documents already in Kick means your accountant doesn't have to chase anything down. Before generating your [Tax Package](/reports/tax-package.md), do a quick check: * Loan agreements are uploaded and linked to relevant transactions * Year-end statements from Stripe, PayPal, or other processors are attached * Any 1099s you've received are stored and accessible * Large or unusual purchases have documentation attached → [Tax Prep Guide](/best-practice-guides/tax-prep-guide.md)\ → [Receipts](/setting-up/receipts.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/common-workflows/documents.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.