> For the complete documentation index, see [llms.txt](https://docs.zwapgrid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zwapgrid.com/client-portal/systems/setup-guides/datev.md).

# DATEV Online

Prepare a DATEV Online connection for API.1.

DATEV Online supports accounting-period reads and company-scoped Accounting Data Exchange access through API.1. Production access requires separate provider approval and configuration. Contact [Zwapgrid](mailto:hello@zwapgrid.com) to confirm the connection setup for your environment.

## Supported scope

API.1 provides `GET /accountingperiods` for the selected DATEV accounting dataset. Proxy.1 can access DATEV Accounting Data Exchange routes within that same dataset. Other DATEV products and typed invoice, payment, customer, supplier, and accounting-write endpoints are not part of this integration.

An Accounting Data Exchange `POST` can start an export job; it does not post accounting entries.

## Before you start

You need a DATEV application with access to the Accounting Data Exchange product and a company dataset eligible for its export service. Confirm the required application approval, product subscription, and dataset permissions with DATEV. A successful Sandbox connection does not establish production approval.

## Configure and test

1. Confirm with Zwapgrid that DATEV is enabled for your environment.
2. In the Client Portal, create and publish a DATEV System Setting with the application credentials for that environment. Keep Sandbox and production credentials in separate settings.
3. Create a Development Consent using the published setting and complete the DATEV connection flow. The customer selects the accounting dataset to authorize.
4. Test `GET /accountingperiods` and any required Accounting Data Exchange export routes through Proxy.1 against that dataset.

See [System Settings](/client-portal/systems/system-settings.md) for the setting lifecycle. For proxy path and response limits, see the [Proxy.1 overview](/proxy.1/proxy.1.md#datev-online).


---

# 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.zwapgrid.com/client-portal/systems/setup-guides/datev.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.
