> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/magento-2-api-connector/magento2_en_us/order-processing/from-magento-order-to-business-central-document.md).

# From Magento Order to Business Central Document

The connector downloads Magento orders as dashboard data and creates BC sales documents from them.

### Process Chain

1. Download order via Cockpit, action, or verified job.
2. Save Magento header, lines, customer, addresses, payment, shipping, and tax.
3. Check dashboard status.
4. Create BC document automatically or manually.
5. Post.
6. Report shipment, tracking, and invoice.

### Keys

Magento Order ID/Increment ID and BC document number link the systems.

{% hint style="warning" %}
Do not manually change linked keys. If a link is missing, first check the dashboard and document fields.
{% endhint %}

### Verifications

Compare quantities, prices, discount, tax, shipping costs, customer, addresses, payment/shipping method, and options.


---

# 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.solutioo.de/magento-2-api-connector/magento2_en_us/order-processing/from-magento-order-to-business-central-document.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.