> 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.md).

# Invoice

Let a registered customer take the goods now and pay against an invoice with a due date.

## What is this?

Invoice lets a registered customer take the goods now and pay later. The sale is settled against that customer's ledger, the customer gets an invoice instead of a receipt, and the amount stays outstanding until the money arrives.

It is built into Flow Retail — no provider, no terminal, no extension. The credit is yours, not a third party's.

***

## How does it work?

Invoice needs a customer on the order; a guest sale cannot be invoiced.

Pick Invoice on **Choose payment method** and the till asks for a **Due date**, pre-filled from the customer's payment terms or 14 days ahead when they have none. It can be set from tomorrow up to a year out.

The amount is locked: an invoice covers whatever is left on the order. Take part of the sale on another method first if you like — the invoice settles the rest in full.

The till confirms <kbd>Invoice created</kbd> and asks **Does the customer want the invoice?** It goes out as a PDF, subject `Invoice #<order number> from <store>`.

A refund is a credit note, not a reversal — there is no card transaction to send money back through. A negative settlement produces a credit memo.

{% hint style="warning" %}
One payment cannot both sell and take back items:

> You cannot pay by invoice when the same payment both sells and returns items. Register the sale and the return separately.
> {% endhint %}

Two more limits: a receipt can carry only one invoice settlement, and an invoice cannot be paid off with another invoice.

With B2B in use, an invoice to a business customer also needs a contact person and must fit the customer's remaining credit limit.

***

## How do we get started?

Add Invoice under **Admin → Settings → Payment Methods**, then enable it in the stores that should offer it.

Two pieces of accounting setup go with it:

* A **Customer Ledger** number series on each store. This is what gives each invoiced customer their own ledger account number.
* A ledger number for the payment method per store, so invoice sales post to the right account.

Unpaid invoices are followed up in the Open Items report, with due date, amount and customer ledger.

[Invoice EHF](/docs/day-to-day-operations/selling/payments/payment-methods/invoice-ehf.md) adds electronic delivery on top of this method.

***

*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.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.