> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/edi/currently-supported-e-invoice-standards/roadmap.md).

# Additional formats and transmission requirements

For the inspected format and version scope, use the [country overview](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents.md). The following families already have catalogue entries and country guides; they should not be read as promises of future support:

* [Sweden — Svefaktura 1.0](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/sweden.md)
* [Denmark — OIOUBL 2.1](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/denmark.md)
* [Norway — EHF Invoice 3.0](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/norway.md)
* [France — Factur-X](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/france.md)

Chorus Pro is a transmission platform. Processing Factur-X or Peppol XML does not establish connectivity to Chorus Pro or tax clearance. Confirm the required connector, environment and transmission process separately.

For an additional requirement, retain an original sample and identify its format, syntax, version, profile and business document type. Compare it with the country guide, then test the required extraction and export in your organization.


---

# 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.docbits.com/administration-and-setup/settings/global-settings/document-types/edi/currently-supported-e-invoice-standards/roadmap.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.