> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/settings/set-the-next-invoice-number.md).

# Set the next invoice number

Choose where your business's invoice numbering continues, such as **50000** when moving to Essential from another system.

> **Where to find it:** Settings → Quotes & Invoices → Invoicing → Invoice → Invoice numbering.

You need permission to manage invoicing integrations to change this setting.

1. Enter a whole number in **Next invoice number**, such as **50000**.
2. Click **Save** in the Invoice numbering section.
3. Create an invoice and send it (or finalize it without sending). It receives **50000** at that moment, and subsequent invoices receive **50001**, **50002**, and so on in the order they go out.

The setting applies to new invoices across your business, including recurring invoices. Existing invoices keep their numbers. Your first invoice defaults to **1001** unless you change this setting.

A draft has no number until it leaves Draft, so drafts you delete or void never use one up. Numbers can only move forward. Invoices that were sent, finalized, paid, voided, or deleted after being numbered keep their numbers reserved, including a numbered invoice you revert to Draft. The number shown in settings is the next available number; if another staff member creates an invoice while you're editing, you may need to refresh and enter a higher number before saving.

If you're continuing from another invoicing system, choose a number above the highest number used there, including invoices you haven't imported into Essential.

Related: [Create an invoice](/revenue/invoices/create-an-invoice.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://learn.withessential.com/administration/settings/set-the-next-invoice-number.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.