> 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/bookkeeping-workflows/invoicing/items.md). # Items Items are the products and services you sell. Save them once, then add them to any Kick invoice without retyping the name, price, or accounts. ### Where to find items Go to Invoicing, and open the [Items](https://use.kick.co/invoicing/items) tab. ### Add an item 1. Click Add item in the top right. 2. Fill in the item details (see below). 3. Click Save. You can also add an item while you're creating an invoice or template. In the Items section, type a new name in the Item column and choose to add it as an item. #### Item details | Field | Description | Plan | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------ | | Item name | Required. Appears on the invoice. | All plans | | Item description | Appears on the invoice line. You can change it on each invoice. | All plans | | Price | One or more prices for the item. See Prices below. | All plans | | Income account | Where the revenue from this item posts. | All plans | | Class | One or more classes, to track the item by location, project, or any custom system. | Plus and Advanced | | Receivables account | Where the amount owed posts until the invoice is paid. Defaults to Accounts Receivable. You can pick a custom receivables account instead. | Plus and Advanced, with the Accrual ledger on for the entity | | Entity | The entity the item belongs to. Only shown if the workspace has more than one entity. | All plans | {% hint style="info" %} An item belongs to one entity, and its accounts come from that entity's chart of accounts. To sell the same item from two entities, create it once for each. {% endhint %} #### Prices An item can have more than one price. For example, you might have a standard rate and a discounted rate. * Click **Add price** to add another price. Each price can have its own description. * The first price is the Default. To change it, open the three dots on another price and click Set as default. * You can Archive or Delete a price you no longer use. An item always keeps at least one active price. To archive or delete the default price, set a different price as the default first. When you pick an item on an invoice, each active price appears as its own option, with the default price first. The price you pick fills in the Rate on the line. ### The Items tab Columns on the Items tab include: * **Item**. The item name. * **Item description**. * **Rate**. The item's default price. * **Class**. Plus and Advanced only. * **Income account**. * **Receivables account**. On Plus and Advanced, with the Accrual ledger on. * **Entity**. * **Last updated**. * **Invoices**. How many invoices use the item. Use column settings to show, hide, or reorder columns. To narrow the list: * Search by item name or description. * Filter by entity. * Switch between Active, All, and Archived items. ### Edit, duplicate, archive, or delete an item Open the three dots on an item row. * **Edit**. Change the item's details. Changes apply only to invoices you create afterward. Existing invoices keep the item details they were created with. * **Duplicate**. Creates a copy of the item that you can edit. * **Archive**. Hides the item from the item list on new invoices. Existing invoices aren't affected. Switch the filter to Archived to find it, and click Unarchive to restore it. * **Delete**. Permanently removes the item. This is available only if the item has never been used on an invoice. {% hint style="info" %} You can't delete an item that has been used on any invoice, including drafts and void invoices. Archive it instead. {% endhint %} --- # 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/bookkeeping-workflows/invoicing/items.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.