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

# Invoicing

View invoices synced from Stripe, Mercury, and BILL, and create and send invoices directly from Kick.

The **Invoicing** tab shows invoices from your connected **Stripe**, **Mercury**, or **BILL** accounts. Once an invoicing account is connected, invoices sync automatically with customer details, payment status, and line items (the individual products or services billed on an invoice).

You can also create and send Kick invoices directly from Kick.

***

### Views

Use the dropdown in the top right to switch between three views:

* **By customer**: one row per customer with invoice totals
* **By invoice**: one row per invoice
* **By line item**: one row per line item on each invoice, which shows you which products or services actually bring in the revenue

The chart at the top summarizes invoice totals by status. Click a segment to filter the list below.

***

### Invoice status

Each invoice shows a status set by Stripe, Mercury, or BILL, whichever one it came from:

| Status        | Meaning                             |
| ------------- | ----------------------------------- |
| Draft         | Invoice created but not yet sent    |
| Open          | Sent and awaiting payment           |
| Paid          | Payment received                    |
| Void          | Cancelled, so nothing is owed on it |
| Uncollectible | Marked as unlikely to be paid       |

Kick tracks one more thing on its own: whether you have matched an incoming payment to the invoice it paid. Matching in Kick records the payment against the invoice in your books, but it does not change the status in Stripe, Mercury, or BILL.

***

### Filters

Filter by date range, entity, status, amount, account, and more using the filters at the top of the page. The Invoicing tab defaults to invoices from the last 90 days.

***

### Creating invoices in Kick

Click **Create invoice** in the top right, then choose **Kick** to open the invoice drawer. You can also open Stripe, Mercury, or BILL to create an invoice in those tools.

The drawer opens with four sections. Expand them in whatever order you like:

* **Details**: customer information, invoice dates, and payment terms
* **Items**: the line items you are billing for
* **Design**: logo, colors, and font
* **Customize**: PDF size, memo, terms, and footer

When the invoice is ready, move to the send panel to preview the customer email, then send it immediately or schedule it for later.

### Payment processing fees

Kick does not add payment processing fees on top of Stripe. Stripe charges the processing fees for online payments:

* **Credit card payments**. 2.9% + $0.30 per successful payment.
* **ACH payments**. 0.8% of the payment amount, capped at $5.

For current Stripe pricing, see [Stripe pricing](https://stripe.com/pricing).


---

# 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/invoicing.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.