Explanations on the error messages of the BOP (BZSt)

Here you will find an overview of all error codes listed in the interface documentation.

  • 01 = No IdNr. determined; request to the recipient required
  • 02 = IdNr. is not in the inventory
  • 03 = IdNr. is deprecated
  • 04 = The authorization for retrieval has not been confirmed
  • 05 = Regular request is not permitted at this time
  • 06 = The processing of the request is delayed
  • 07 = Request date is not permitted
  • 08 = Specified legal ground for request type 1 not permitted
  • 20 = No authorization for the request type
  • 99 = No IdNr permitted in the productive system

Enclosed you will find a more detailed overview of the error messages that could be received by us from the interface to the Federal Central Tax Office.

Explanations of the error codes

Returncode 01 = No IdNr. determined; request to the recipient required.

Inquiry with the service recipient required, as the person was not found in the IdNr-DB or was not clearly identified. It is recommended to ask the person for their IdNr.

Returncode 02 = IdNr. is not in the inventory.

The IdNr. is not contained in the IdNr. database. It is recommended to submit a new request (stating the personal data) or to ask the person for their IdNr.

Returncode 03 = IdNr. is deprecated.

In individual cases, more than one IdNr may have been assigned to a person. In such cases, the incorrectly assigned IdNr will be deactivated. In this case, it is recommended to submit a new request (stating the personal data).

Returncode 04 = The authorization for retrieval has not been confirmed.

The identity of the requested person has not been confirmed. It is recommended that you check the ID number and the personal data and, if necessary, submit a new request (stating the personal data).

Returncode 05 = Regular request is not permitted at this time.

The regular request may only be submitted between 01.09 and 31.10 of the current year. If it is submitted at a different time, it will be answered with this return code as a corresponding note and must be submitted again at the correct time.

Returncode 06 = The processing of the request is delayed.

The legal requirement stipulates that blocking notices received by the BZSt by a specified deadline must also be taken into account when the KiStAM is requested. In exceptional cases, there may be a backlog of blocking notices to be processed. In this case, the response to KiStAM queries will be paused while this backlog is being processed. As soon as all declarations have been processed, the responses are created and sent. The return code is considered a receipt that the BZSt has received the requests and will send the responses at a later date. Under no circumstances should the KISTAV or service provider resubmit the corresponding requests, as these will be rejected by the KiStA system as duplicates.

Returncode 07 = Request date is not permitted.

The request date is checked against the date of receipt of the request.

  • For the occasional request
    • the request date must be in the past
      • in addition, this date may not be more than four weeks before the date of receipt.
  • For a regular request
    • the date must be exactly 31.8. of the current year

In the event of an error, the request must be resubmitted with a corrected request date.

Returncode 08 = Specified legal ground for request type 1 not permitted.

No admissible information was provided for the legal reason in the request.

Returncode 20 = No authorization for the request type.

The authorization for the different request types is assigned individually. At the time of the request, the authorization for the request type was not assigned to the process participant.

Returncode 99 = No IdNr permitted in the productive system.

If an IdNr. occurs in a KiStAM request that must not occur in the productive system, this return code is returned. This is particularly the case if the IdNr begins with a 0. In this case, the KiStAV or service provider must ensure that the KiStA production system does not come into contact with test data.

 

Articles in this section

Was this article helpful?
0 out of 0 found this helpful