> 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).

# Roadmap

**Chorus Pro (France)**

  •  **Scope:** French platform for B2G invoicing, which also aligns with PEPPOL BIS and Factur-X.

  •  **Note:** While Chorus Pro is more of a platform than a format, supporting its data structures and validations might be beneficial for working with French public entities.

**Svefaktura (Sweden)**

  •  **Scope:** A legacy Swedish e-invoice format.

  •  **Basis:** Based on UBL, historically used for B2G invoicing in Sweden.

  •  **Common Version:** Svefaktura 1.0 (largely being superseded by PEPPOL BIS)

  •  **Note:** Although being phased out in favor of PEPPOL BIS, still appears in some legacy scenarios.

**OIOUBL (Denmark)**

  •  **Scope:** Widely used for B2G invoicing in Denmark.

  •  **Basis:** UBL-based format aligned with Danish national requirements.

  •  **Common Version:** OIOUBL Invoice/2.02 (and subsequent updates)

  •  **Note:** Predecessor to current EN 16931-based formats; may still be in use by Danish entities.

**EHF (Norway)**

  •  **Scope:** Norway’s national standard for electronic invoicing.

  •  **Basis:** PEPPOL BIS Billing 3.0 compliant; EHF (Elektronisk Handelsformat) is essentially a localized profile.

  •  **Common Version:** EHF Invoice and Credit Note 3.0

  •  **Note:** Standard format for public sector invoices in Norway, strongly linked to PEPPOL.


---

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