> 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.md). # Invoicing Create, send, and track invoices, and keep your receivables in sync with your books. ### Accessing invoicing Go to the [Invoicing](https://use.kick.co/invoicing) tab. Use the date picker to filter by date range, the entity dropdown to filter by entity, and the view menu to switch between By invoice, By customer, and By line item. #### Invoice integrations Create invoices in Kick, or connect the invoicing tool you already use. Kick brings in invoices from every connected source, so they all appear in one place. **Kick invoicing (recommended)** Kick invoices are created, sent, and tracked entirely inside Kick. They're connected to the rest of your books: * Customers, items, and classes come from your Kick workspace * Send invoices by email with a PDF attached, or schedule them to send later * Collect payments online through Stripe * Payments are matched to invoices automatically * Journal entries are posted to your Accrual ledger as the invoice moves between statuses To create one, click **Create invoice** in the top right. → [Create a Kick invoice](/accountants/bookkeeping-workflows/invoicing/create-a-kick-invoice.md) **Stripe, Mercury, and BILL** Already invoicing in another tool? Connect it and Kick will bring in those invoices. Open the dropdown next to Create invoice and choose Stripe, Mercury, or BILL. If the account isn't connected yet, Kick starts the connection first. Otherwise, the provider opens in a new tab so you can create the invoice there. Synced invoices keep the status from the source tool, shown as their External status. If you edit their content in the source tool, changes sync back to Kick. {% hint style="info" %} Using more than one tool? Every connected source appears in the same table. Use the Account filter to see invoices from one source. {% endhint %} *** ### Invoice summary The bar at the top shows your invoice totals by status: Draft, Open, Paid, Void, and Uncollectible. Click any segment to filter the table to those invoices. *** ### Views **By invoice** One row per invoice. Click a row to open the invoice details panel. **By customer** One row per customer, with their open balance split by aging period. Click an amount to see the invoices behind it. The built-in Aging invoices review view gives you a quick look at outstanding balances by customer. {% hint style="info" %} For a point-in-time aging report you can export, use the [A/R Aging Summary](/accountants/reports/a-r-aging-summary.md). {% endhint %} **By line item** One row per invoice line. Use this view to review and recode how invoice line items are categorized. *** ### Filters Click Filter to narrow the table. Available filters: * Invoice date — Filter by invoice date range * External status — Filter by the status in the source tool (if syncing invoices from an integration) * Kick status — Filter by the invoice's status in Kick * Due date — Filter by due date range * Amount — Filter by amount * Account — Filter by source: Kick, Stripe, Mercury, or BILL * Catalog item — Filter by item * Subscription — Filter by subscription (Stripe-only) * Match — Filter by whether payments have been matched * Customer — Filter by customer * Terms — Filter by payment terms Clicking a segment in the summary bar also adds a filter, such as Not yet due or 1–30 days past due. Active filters appear as removable chips next to the Filter button. *** ### Bulk changes Select invoices or line items using the checkboxes, then open the bulk actions menu. **By invoice** * Mark void — Void the selected invoices as of a date you choose * Mark uncollectible — Write off the selected invoices as of a date you choose * Set counterparty — Change the customer. Only available when every selected invoice is a draft. If some of the selected invoices can't be changed, Kick updates the rest and tells you which ones were skipped and why. **By line item** Work through invoice line items the same way you'd handle a batch of transactions: * Class — Assign a class to the selected lines * Income account — Change the income account the lines post to * Receivables account — Change the receivables account the lines post to *** ### Invoice details panel Click any invoice to open its details panel. What you can change: | | Kick invoices | | --------- | ------------------ | | Status | ✓ (not after Void) | | Due date | ✓ (not after Void) | | Memo | ✓ | | Documents | ✓ | To change an invoice's line items, customer, or amounts: * Draft Kick invoices — Click View to open the full editor * Sent Kick invoices — Use Revise invoice from the three-dot menu * Synced invoices — Edit in the source tool **More actions (three-dot menu)** All invoices: * Show line items: see each line on the invoice. * View journal entries: see the entries this invoice posted to your Accrual ledger. Kick invoices only: * Duplicate invoice: create a new draft copy of the invoice. * Save as template: reuse this invoice's details for future invoices. * Copy payment link: copy the link your customer pays from. This appears only when online payments are on. * Revise invoice: void an Open invoice and create a corrected draft. * Delete: permanently remove a draft invoice. → [Invoice status](/accountants/bookkeeping-workflows/invoicing/invoice-status.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/accountants/bookkeeping-workflows/invoicing.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.