> 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/beginner-courses/lessons/gedi-status-codes.md).
# GEDI Status Codes
The 'GEDI Status' gives information about a 'GEDI Message's' current status.
## Introduction
In the 'GEDI Status Codes' page view in Business Central you will find 'GEDI Status Codes'. The 'GEDI Status Code' is connected to a 'GEDI Message Code'. When a 'GEDI Message' is created or executed, depending on the configuration, a 'GEDI Status' will be created.
The 'GEDI Status Codes' page view shows the configured status codes with Code, Description, Code Next Step Suceeded / Failed and Status Color Scheme.
## Extras
{% hint style="info" %}
More information on this subject can be found in our ['Core Concepts'/'GEDI Status Codes'](/standard-app-core-concepts/concepts/gedi-status-codes.md).
A complete list of standard 'GEDI Status Codes' can be found in ['Standards](broken://spaces/Qs8RQAUXhZJLqyRtzHNZ/pages/u5c19pBh1QYNU3HT9DSO)'/'GEDI Codes'.
{% endhint %}
## GEDI Status in Business Central
The GEDI Status can be found in different places in Business Central.
In sales documents such as 'Sales Order' and 'Sales Invoice' under section 'Invoice Details'
In 'Posted Sales Invoice' under section 'Shipping and Billing'
In list views such as Posted Sales Invoices, Posted Sales Shipments etc.
There are also GEDI Specific list views in Business Central where you can see the status. 'GEDI Posted Sales Invoices', 'GEDI Posted, Sales Shipments' etc. The benefit of using the GEDI specific lists are that they are already filtered by documents that have been processed via Golden EDI instead of showing all records. Also, they are showing the 'GEDI status' according to the defined color scheme.
In 'GEDI Status Ledger' you are able to find how the status have changed for each document.
{% hint style="info" %}
It is possible to translate the 'GEDI Status Code Description' for example to be presented in company internal language.
{% endhint %}
## Next step
Next and final step in the Beginner Courses part of the Implementation Academy is to learn about the 'CIP Customer View'.
---
# 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/beginner-courses/lessons/gedi-status-codes.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.