> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/day-to-day-operations/selling/payments/payment-methods/invoice-ehf.md).
# Invoice EHF
Send the invoice electronically as a structured EHF document to the customer's e-invoice address.
## What is this?
EHF is not a payment method of its own. It is an extension on top of **Invoice**: the customer still pays by invoice, but the document is built as a structured electronic invoice and delivered to their e-invoice address.
Flow Retail follows Peppol BIS Billing 3.0, the format Norwegian and Danish businesses exchange invoices in. Only business customers can receive it.
***
## How does it work?
Nothing changes at the till — the cashier selects Invoice as usual.
For company customers, the payment screen shows EHF Active or EHF Not Active, so you know before settling whether this one gets an electronic invoice.
Once the invoice settlement completes, Flow Retail builds and sends the document in the background. The receipt PDF travels with it, and each invoice carries a KID payment reference from the store's KID settings.
Delivery status lives on the order: the **EHF-invoice** section shows whether the send succeeded, the message back if it did not, a refresh and **Resend**.
{% hint style="info" %}
If the store has no usable bank account, Flow Retail blocks the invoice at the till rather than letting the send fail quietly afterwards.
{% endhint %}
***
## How do we get started?
Ask us to add the **EHF** and **KID** extensions to your account. Once they are there, four things have to be in place:
* Set your own **EHF Address** on the EHF extension under **Admin → Settings → Extensions** — the endpoint your invoices are sent from — and activate it on each store that sends electronic invoices.
* Activate **KID** on those stores, with the modulus type and mask you use for payment references.
* Fill in bank details on the store, or on its organisation. Danish stores paying by FIK also need the **Giro Account Number**.
* Turn on **EHF-invoice** for each customer, with their **EHF address**, in Flow Client under the customer's details. Only Company and B2B customers can have it.
{% hint style="warning" %}
The customer's organisation number has to be valid. Without one, the invoice cannot be addressed and will not be sent.
{% endhint %}
***
*Last updated 17.09.2026*
---
# 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.flowretail.com/docs/day-to-day-operations/selling/payments/payment-methods/invoice-ehf.md?ask=&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.