> For the complete documentation index, see [llms.txt](https://docs.goldenedi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goldenedi.com/business-central/configuration/invoicing/message-settings.md).

# Message Settings

In this chapter we will setup the message settings enabling the invoicing flow.

Start by searching and opening **GEDI message settings** to get to the list of all message settings.

![](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LVO7c8MSQ0ieazusCSE%2F-LXxmvlwVEda-h48Mv1X%2F-LXxnj_yQWdKkUrUmNni%2FScreenshot%202019-02-05%20at%2014.16.25.png?alt=media\&token=5d1603f6-45a0-4d79-9d9b-d4636c2ecc88)

Once inside you'll see a list contains profiles and message codes. This is to enable certain thing for each profiles, e.g. Sending invoices. We will need to add a few things in the list as listed in the table below. Substitute **CREDIFLOW** for the profile name you've chosen.

| Code | Description                 |
| ---- | --------------------------- |
| 020  | Create Invoice              |
| 021  | Invoice                     |
| 022  | Create Credit Memo          |
| 023  | Credit Memo                 |
| 092  | Create notification         |
| 093  | Notification                |
| 080  | Message sent successfully   |
| 081  | Message sent unsuccessfully |
| 082  | Set status to succeeded     |
| 083  | Set status to failed        |
| 206  | Control invoice             |
| 207  | Control credit memo         |

It should look something close to this when everything is done. 

![](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LVO7c8MSQ0ieazusCSE%2F-LrU8rzvyeRDGZrLfZSm%2F-LrU8sh_wucpYnjLW2Wd%2Fimage.png?alt=media\&token=44d27109-f369-4ceb-8c35-25ce30f07eb4)

{% hint style="success" %}
Now you've successfully created an invoicing flow.
{% endhint %}


---

# 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.goldenedi.com/business-central/configuration/invoicing/message-settings.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.