> For the complete documentation index, see [llms.txt](https://za.docs.rechtlogisch.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://za.docs.rechtlogisch.de/beta/general/environments.md).

# Environments

Both the use case of a request (`validate` or `send`) and environment the solution is operating (`development` or `production`) have an effect on whether a filing is received and processed by the tax authorities. There are two environments available:

* **`development`** Intended for testing. The tax authorities do not process the transferred data.
* **`production`** Going live to production with the solution. Data is generally processed by the tax authorities.

The environment is controlled by setting [APP\_ENV](/beta/setup/settings.md#app_env) in `.env`.

The constellation of use cases and setting the environment results in the following four types of calls:

## 1 - Validate request in `development` environment

* The message is drafted locally. There is no data exchange with the tax authorities.
* Prints on protocol: Preview (black, German: „Vorschau“) and test case (red, German; „Testfall“)

## 2 - Send request in `development` environment

* A test transmission to the tax office is performed. The message is sent, but it is not processed by the tax authorities.
* Prints on protocol: Test case (red, German; „Testfall“), date and time of transmission (German: "Sendedatum") and transfer ticket on the side

## 3 - Validate request in `production` environment

* The message is drafted locally. There is no data exchange with the tax authorities.
* Prints on protocol: Preview (black, German: „Vorschau“)

## 4 - Send request in `production` environment

* A transmission to the tax office is performed. The message is sent and is processed by the tax authorities.
* Prints on protocol: Date and time of transmission (German: "Sendedatum") and transfer ticket on the side
