> For the complete documentation index, see [llms.txt](https://developers.hyp.co.il/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.hyp.co.il/enterprise/documents-and-invoicing/enabling-invoicing.md).

# Enabling Invoicing in the Terminal

Using Hyp Enterprise's invoicing API requires connecting an invoice module to your merchant terminal. The invoice module is powered by [EZcount](https://www.ezcount.co.il/), an invoicing service provider that is a wholly owned subsidiary of Hyp.

Unless you enabled invoicing during [Hyp Enterprise onboarding](https://developers.hyp.co.il/enterprise/introduction/prerequisites-and-requirements.md), here's what you need to do to connect the invoice module to your terminal:

1. [Contact the Hyp sales team](mailto:sales@hyp.co.il).
2. Receive and sign the price quote provided by the Hyp sales team.
3. The sales team will connect your terminal to EZcount. If you are already an EZcount customer, you will receive a success email once the connection is made, and you can start issuing invoices. **If you are not an existing EZcount customer**:
   1. You will receive an email inviting you to complete your EZcount registration:

      ![EZcount invite email](https://3255314327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQDmIAW4sQ20lCItJGzcS%2Fuploads%2Fgit-blob-a95bf8124a1eb7c928ef20a4c1c1759b7d77e3ae%2Feasycount-registration-1.png?alt=media)
   2. Click the link in the email to complete your registration. You will be redirected to the following screen, where you need to enter your company's address and click **המשך** (**Continue**):

      ![EZcount registration screen](https://3255314327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQDmIAW4sQ20lCItJGzcS%2Fuploads%2Fgit-blob-cde788089f2f3560ac08273f528ce97b26697a92%2Feasycount-registration-2.png?alt=media)
   3. When the registration form opens, fill in the details, such as your merchant email, type of business, and invoice numbering rules, then click **הרשמה** (**Enroll**):

      ![EZcount registration form](https://3255314327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQDmIAW4sQ20lCItJGzcS%2Fuploads%2Fgit-blob-1605459d257debaf497de7ae85303eeaa236c8d7%2Feasycount-registration-3.png?alt=media)
   4. Once you submit the form, the Hyp sales team will connect your terminal to the EZcount system. You will then receive an email confirming the connection, and you can start [issuing invoices](https://developers.hyp.co.il/enterprise/documents-and-invoicing/issuing-invoices.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://developers.hyp.co.il/enterprise/documents-and-invoicing/enabling-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.
