> 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/import-mappings.md).

# Import Mappings

{% content-ref url="/pages/-LVcdqzuwS2300PqGc74" %}
[Import Libraries](/business-central/configuration/getting-started/import-libraries-and-mappings.md)
{% endcontent-ref %}

There are only five mappings that you need to import to your system. You can refer to the guide above to setup the prerequisits to import mappings and libraries into your system. 

| Mapping              |
| -------------------- |
| CRED-KREDITNOTA-365  |
| CRED-FAKTURA-365     |
| STD-SEND-FAILED-365  |
| STD-SEND-SUCCESS-365 |
| STD-ADMIN-SENT-365   |
| STD-CONTROL-INVOICE  |
| STD-CONTROL-CREDIT   |

Start by entering the library list and select any library of your choosing. We will use **LTD-STD** in this guide as the library for importing these mappings.

![Select the library you want these mappings to go into.](/files/-LXt0bTyj14nMgijbPWq)

Add mappings as described above to the library and mark so that we import them to the local system.

{% hint style="info" %}
Don't worry if the library is not empty, it will only import the mappings you choose and it won't touch the others.
{% endhint %}

![](/files/-LrU5q81xsBgKpQLOESV)

Fill in the GEDI-profile on the library card to the one you connected to **Golden EDI Cloud**.

![](/files/-LXt19CEeIvof0VNda8F)

Now we can create an internal request to request the mappings from the **Golden EDI Cloud.** Letting the service now that we want these written to our system. Do that by clicking 'Process' > 'Import marked mappings'.

![](/files/-LrU5hZ5HntqcHZiwp6L)

Now you can go to the message queue and process the messages to form a request for these mappings. This will be read shortly by the **Golden EDI Cloud** and it will write down the mappings to your system. The process for requesting and importing the mappings in the message queue is described on the following page.

{% content-ref url="/pages/-LXs3Zcdu233TQimpx3I" %}
[Import Mappings](/business-central/configuration/getting-started/import-mappings.md)
{% endcontent-ref %}

{% hint style="success" %}
Now we should have all requested mappings in the system and we can now proceed with the next steps.
{% 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 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.goldenedi.com/business-central/configuration/invoicing/import-mappings.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.