...
The preparation of resubmission and correction reports is not yet supported.
| Anchor | ||||
|---|---|---|---|---|
|
These are some common errors and FAQ´s and their respective answer:
- Message gets rejected, protocol contains Message "The receiving Competent Authority detected one or more potential security threats within the decrypted version of the referenced file. Such threats include but are not limited to hyperlinks, Java script, and executable files."
- Check for Non-Schema supported Special characters in the File.
- The Interface of BZSt had a bug which reintroduced the unsupported Special Characters in a File upon opening on their side. From latest Information (03.2020) a fix was pushed by the BZSt. If this seems to be the issue, personal contact to the BZSt needs to be made to resolve.
- Xbrl Portal gives Error "Permission denied (public key)" on Upload / BOP-BZSt "Server could not be reached / Der Server konnte nicht erreicht werden. Bitte überprüfen Sie, ob Ihr aktuelles Nutzerzertifikat korrekt in den Browser eingebunden wurde. ..."
- in case of uploading to BZSt: Check if browser had imported the correct certificate
- check if the certificate has filetype '*.pem', it can be downloaded in BOP - "ELMA5 Zertifikat generieren" for the reporting user
- Contact BZSt / Check if the account is Allowed to Report. If not, the customer in question needs to fill out the formular here and send it to cbcr@bzst.bund.de . This will unlock the access and will make reporting possible.