Type of requests

Four types of requests are possible when setting the usecase in the request body and environment the solution is operating in.

They have effect on whether a filing is received and processed by the tax authorities.

There are two usecases available:

• validate to ensure the data is valid and generate a PDF draft preview

• send to submit data to the tax authorities and generate an official PDF transmission protocol

There are two environments available:

• development Intended for testing. The tax authorities do not process data, when transferred.

• production Going live to production with the solution. Data is generally processed by the tax authorities.

The four types are visualised with examples below.

The term in the bracket determines if the call is done [online] or [offline].

[offline] requests are processed purely locally and do not send any data to the ELSTER servers.

1 - Validate call in development environment [offline]

• The message is drafted locally. There is no data exchange with the tax authorities.

• Prints on protocol: Draft (black, German: „Entwurf“) and test case (red, German; „Testfall“)

2 - Send call in development environment [online]

• 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 call in production environment [offline]

• The message is drafted locally. There is no data exchange with the tax authorities.

• Prints on protocol: Draft (black, German: „Entwurf“)

4 - Send call in production environment [online]

• 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