> For the complete documentation index, see [llms.txt](https://fitek-learning.fitek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fitek-learning.fitek.com/sales-invoices/getting-started.md).

# Getting started

You send invoices to your customers. Whether they're PDFs from your ERP, manually created, or part of a larger workflow - Fitek helps you turn them into compliant e-invoices and get them delivered.

This guide walks you through the first things you need to know before you start using Sales Invoices.

### What you'll learn in this section

* [**Understanding the Register**](/sales-invoices/getting-started/sales-invoices-register.md) – where all your sent invoices live (your main dashboard)
* [**Managing customers**](/sales-invoices/getting-started/managing-customers.md) – how to store and reuse customer details so you don't retype them
* [**Understanding statuses**](/sales-invoices/getting-started/understanding-statuses.md) – what each status means, and when you need to take action

After reading these pages, you'll be ready to either create your first invoice or set up an import flow.

***

### The three core ideas

#### 1. Everything lives in the Sales Invoices Register

Think of it as your invoice inbox - but for things you ***send***, not receive.

Every invoice you create or import appears here. You can see:

* Invoice number and customer
* Current status (Unsent, Sent, Import issues, Delivery issues)
* When it was created
* Financial summary (NET, VAT, Total)

From here, you can search, filter, sort, and send invoices. It's your main home when working with outbound invoices.

#### 2. Customer data is reusable

Instead of typing the same customer details every time, you store them in your customer register once they are created

When you create a new invoice, you pick a customer from your list – and their key details (Name, VAT number or registration number, and Country) fill in automatically. Language, Currency, and Payment terms can also come from the customer profile.)

As you import invoices, new customers are created automatically too. So your customer database grows naturally.

#### 3. Status tells you what to do next

Every invoice has a status that tells you where it is:

* **Unsent** – ready to send
* **Sent** – successfully sent out from Fitek (no delivery error was returned
* **Import issues** – something went wrong during creation/import (you need to fix it)
* **Delivery issues** – sent, but the customer's operator rejected it (you need to fix it and resend)

You use these statuses to stay organized: first fix issues, then send what's ready, then follow up on failures.

***

### What happens next

When you're ready, move to:

* **Understanding the Register** – see exactly what columns mean and how to filter your invoices
* **Managing your customers** – learn how to add, edit, and organize customer data
* **Understanding statuses** – deep dive into each status and what to do about them

Then jump to [**Creating & sending invoices**](/sales-invoices/creating-and-sending-invoices.md) to start working with real invoices.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://fitek-learning.fitek.com/sales-invoices/getting-started.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.