> For the complete documentation index, see [llms.txt](https://docs.powerall.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powerall.app/en/financial/cash/pay-directly.md).

# Pay directly

Sales invoices are usually paid via the bank and therefore also posted there, but in some cases you want to mark an invoice as paid immediately upon creating it, for example when selling at the counter. You can add a manual settlement to the sales invoice for this, but if this happens more often that is of course relatively a lot of work.

To make this easier, you can create a cash account that you use for **Direct payment**. To do this, follow the steps below:

{% stepper %}
{% step %}

### Create and set up cash account

Create a new cash account (or modify an existing one), for example **PIN** or **Cash register** and check **use for direct payment**. The description of the cash account is shown when invoicing.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu0jh0YrfkyoEuz2xa21S%2Fuploads%2FQqx2RZdKjH5k2MgTv2H6%2F1_aanmaken_kasrekening_light.mp4?alt=media&token=c34b2d3c-8165-4979-a14e-01cd98d9cffe>" %}
{% endstep %}

{% step %}

### Create invoice

If you now invoice a sales order, under the heading **General** the option **Direct checkout**. If you set this to **Yes** direct checkout will be started when invoicing.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu0jh0YrfkyoEuz2xa21S%2Fuploads%2F0hNwRqYGVAZgGJdXCEAb%2F3_verkooporder_factureren_light_v2.mp4?alt=media&token=ffbe0713-ed6e-4cea-a020-96c3ff4a1437>" %}
{% endstep %}

{% step %}

### Register payment

In the popup that now appears, choose the cash account you created in step 1. Then, when invoicing, a payment is added directly via the selected cash account. On the invoice, the payment text will state that the invoice has already been paid.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu0jh0YrfkyoEuz2xa21S%2Fuploads%2Fsh72qkzpav1BvTYC4nIY%2F5_betalingen_en_factuurtekst_light.mp4?alt=media&token=061f4ac0-4aed-4e76-8e24-673cdede865a>" %}
{% endstep %}
{% endstepper %}

### Link with the bank

For payments via PIN, the paid amount is usually deposited into your bank account at a later time (often in a batch). Before this happens, the amount is 'parked' on the general ledger account linked to the cash account. Because this account is linked to the cash account, you may not post directly to it from the bank (in this case, the cash account is a **sub-administration** of the general ledger account).

To still be able to post this, you can create an intermediate account, post the paid amount to it from the bank, and offset it via a cash entry. Because this is quite cumbersome, we have created an easier solution for this: by setting the intermediate account in the cash account as **Intermediate account cash & bank** you can select the cash account directly from the bank. So when your payout comes in, you directly choose the PIN cash account and the two postings are created automatically via the configured intermediate account.


---

# 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://docs.powerall.app/en/financial/cash/pay-directly.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.