> 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/freemium/user-guide/invoice-process.md).
# Invoice Process
Now when the customer cards are configured correctly, we look at how the invoice process to send PDF email works with the Golden EDI app.
When a sales order, invoice or credit note is created, it will inherit the 'GEDI profile' from the customer cards that we have configured. The GEDI profile will activate the freemium functions.
{% hint style="warning" %}
Before posting a sales invoice or credit note, it is possible to remove or change the 'GEDI profile' on it to override the customer cards for that specific sales invoice or credit note.
{% endhint %}
When you are trying to "post" a sales invoice or credit memo, the Golden EDI app will listen to this event and add it to the 'GEDI Message Queue' as an unprocessed message.
{% hint style="info" %}
At this point the '**GEDI Status'** for the posted sales invoice or credit note have been updated to '**Requested'**, letting you know that the message is queued.
{% endhint %}
Every 5 minutes during normal business hours, a 'Job Queue Entry' is scheduled to process all unprocessed message in the 'GEDI Message Queue', at this point they will be sent out as emails via your SMTP.
{% hint style="success" %}
If the email was sent out successfully, the '**GEDI Status'** of the posted sales invoice or credit note will be updated to '**Sent**'.
{% 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/freemium/user-guide/invoice-process.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.
