> For the complete documentation index, see [llms.txt](https://paykilla.gitbook.io/paykilla-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://paykilla.gitbook.io/paykilla-docs/introduction/create-invoice.md).

# Create invoice

### 1. Where to find

<div data-with-frame="true"><figure><img src="/files/74pErPTKsNwbFQSOZhdk" alt=""><figcaption></figcaption></figure></div>

1. Go to **Payments** in the left-hand menu.
2. Click **Create invoice**.
3. You will see the **Create new manual invoice** form.

### 2. Step-by-step: create a manual invoice

1. Go to **Payments → Create invoice**.

{% columns %}
{% column %}

<div align="center" data-with-frame="true"><figure><img src="/files/A7s8LBVbEskWaimTLTy0" alt=""><figcaption></figcaption></figure></div>
{% endcolumn %}

{% column %}

1. In **Purpose\***, enter a clear name (e.g. `Test invoice` or `Consulting services May`).
2. In **Total price\***:
   * Enter the **Amount** (e.g. `250`).
   * Choose the **Currency** (e.g. `USD`).
3. (Optional) Turn on **Invoice with open price** if the payer should choose the amount themselves.
4. (Optional) Expand **Description** and add additional details for the client.
5. (Optional) Expand **Products or services** and fill in what exactly the client is paying for.
6. (Optional) Expand **Select payment methods and lifetime of invoice** and:
   * Limit payment methods if needed.
   * Set an expiration time for this invoice if it must be paid within a certain period.
7. Click **Create**.
   {% endcolumn %}
   {% endcolumns %}

Your manual invoice is now created and can be sent to the client via link, email or any other communication channel supported by your system.

### 3. Form fields

#### 3.1 Purpose \*

Short internal name of the invoice.

* Shown in the payments list and inside the invoice details.
* Used to quickly identify what this invoice is for (e.g. *“Website redesign – April”*).
* Required field.

#### 3.2 Total price \*

Block with two inputs:

* **Amount** – numeric value of the invoice total.
* **Currency selector** – fiat currency of the invoice (for example, **USD**).

> The system will later convert the specified fiat amount into the crypto amount at the moment of payment.

Required field unless the **Invoice with open price** toggle is enabled.

#### 3.3 Invoice with open price

Toggle that switches the invoice into **open amount** mode.

* **Off** – the client must pay **exactly** the total price specified in the *Amount* field.
* **On** – the total price is not fixed; the payer chooses the amount themselves (for example, donations or tips).

When the toggle is on, the *Amount* field becomes optional and is used as a **suggested** amount (if filled).

#### 3.4 Description

Optional free-text field.

* Use it to add details that will be visible to the client: scope of work, order ID, notes, etc.
* Supports multiple lines of text.

Collapsed by default; click the **Description** row to expand it.

#### 3.5 Products or services

Optional structured description of what you are selling.

Typical usage:

* Add the list of products or services included in this invoice.
* Indicate quantities and unit prices (if supported in your current build).
* Helps both you and the client to see what exactly is being paid for.

Collapsed by default; click **Products or services** to open the section and add data.

#### 3.6 Select payment methods and lifetime of invoice

Block that controls:

* **Methods** – which payment methods / currencies will be available for this invoice.
  * Default value: **All** supported methods for your account.
* **Lifetime** – how long the invoice will be available for payment.
  * Default value: **Unlimited** (invoice does not expire automatically).

Collapsed by default; click the row to adjust methods and lifetime if you want to restrict them for this particular invoice.

### 4. Actions

At the bottom of the form you have two buttons:

* **Cancel**
  * Closes the form without saving changes.
  * The invoice is **not** created.
* **Create**
  * Validates all required fields.
  * If everything is correct, creates a new invoice and redirects you to:
    * either the **invoice details** page,
    * or back to the **Payments** list with the new invoice at the top (depending on your current build).
  * If some data is missing or incorrect, validation errors are shown on the problematic fields.