Page Comparison

...

• When submitting before the 1st of December 2019, the BZSt Number has to be added instead of the Steuernummer.
• When submitting on or after the 1st of December 2019, the Steuernummer has to be provided, but in a special format:
  • No special characters like "/" are allowed.
  • The Steuernummer has to be provided as a 12-diget, so called "Bundesschema" (see more information and sample Steuernummern on Wikipedia).
  • If the Steuernummer is only 9 or 10 digest, the Bundesland Finanzamtsnummer has to be added as a prefix.
  • If the Finanzamtsnummer is not know, it can be found out by searching the city of the Finanzamt in the Gemfa 2.0 tool on the BZSt Webpage:
    https://www.bzst.de/DE/Service/Behoerdenwegweiser/Finanzamtsuche/GemFa/finanzamtsuche_node.html

To enable the German CbC report and its specific fields in the converter, it must be selected in the and or all appropriate German specific fields have to be filled in the Excel Template.
Image Added Image Added

Submitting Reports to BZSt using the ELMA SFTP Upload

Since August 2019 it is required to send the CbC files to the German Tax Authority with the ELMA interface. The file can either be uploaded online through the BZSt Online Portal (BOP) or submitted via the the built-in SFTP client of the AMANA CbCR Converter .To enable the German CbC report and its specific fields, it must be selected in the and or all appropriate German specific fields have to be filled in the Excel Template. Please see documentation about field in Excel and the "Kommunikationshandbuch" issued by BZSt https://www.bzst.de/DE/Unternehmen/Intern_Informationsaustausch/CountryByCountryReporting/ElektronischeDatenuebermittlung/elektronische_Datenuebermittlung .html#js-toc-entry6 .
Image Removed

To send the file via the AMANA CbCR Converter to the BZSt, a PEM certificate file is required. The PFX certificate provided for the BOP login can not be used. The PEM certificate file can be requested and downloaded from the BZSt Online Portal (BOP) at https://www.elster.de/bportal/formulare-leistungen/versandmassendaten
The CbC Converter Application does allow sending an existing XML document – it is recommended to send only validated final reports to the BZSt.

...

It is recommend to download all files before deleting them from the server.

Anchor
_Toc501102560 _Toc501102560

Preparation of

...

Deletions and Correction Reports

If a submitted and accepted report needs to be corrected, a resubmission needs to be created. These consist of a deletion of the old report and a newly created report.
The preparation of resubmission and correction reports is not yet supported.To create a Deletion, the old (submitted) report first needs to be loaded into the Converter. Please make sure, the correct CbC-Receiver / Report Rype is selected by using the radio buttons or dropdown menu. 
The old report can then be loaded by using the File-Menu: clicking on 'Open Report' and selecting the XML-File.

After loading the submitted report with the contend that needs to be resubmitted, the File-Menu can be used to start the creation of a delete-submission by clicking on 'Create Deletion for existing Report'. This will open a menu to save the created XML-file.
The process will end with the following Message, showing the path and filename, confirming that the file was created. 
Image Added  

Afterwards, a normal report should be created to resubmit the deleted data in correct form. 
Please make sure to use the validation-function to find any Issues in the data or report. 

In case of an error, please check the FAQ section in this Guide. 

Anchor
Encryption SwitzerlandReport for ESTV Encryption SwitzerlandReport for ESTV

Encryption of CbCR - Switzerland report for Upload at ESTV Portal

This Information is taken from ESTV´s Technical Information Document (10. March), which is subject to change. For any questions regarding the encryption of reports please contact ESTV directly. 

Note from ESTV: The reporting is, until further notice and as on the ESTV Website described, done as an encryped attachment via Mail. This is expected to change in 2020 to be handled exclusively over the ESTV Portal. ESTV will publish the date of change on their Website. 

The public CBC-Certificate for encryption (Step 3.) can be downloaded from the ESTV Portal. The Encryption-tool needed is Uploaded there and must be downloaded first. With this tool, the CBC-Report can be encrypted as expected by the ESTV.

Please export your Report from the CBC-Converter to a location where Read & Write is possible. The Report (XML-File) needs to be compressed and encrypted to enable Upload. To encrypt the file, please follow the following Steps:

1.  Compress the exported CBC-XML File
   1. The XML-filename must be "CBC_Payload.xml" 
   2. Compress the renamed File into a Archive with name "CBC_Payload.zip"
2. Encrypt the archive with the tool from ESTV with the following settings
   1. AES-256 must be used as Encryption-Type
   2. CBC (Cipher Block Chaining) must be used as Cipher mode
   3. Initialization Vector (IV): 16 byte  
   4. Key size: 256 bits/ 32 bytes
   5. Encoding: None
   6. Padding: PKCS#7 or PKCS#5, Note: For this encoding please use a different & generate a new Initialisation Vector every time 
3. Encrypt the AES-Key and IV-Parameter with the Public-Key from the CBC-Certificate
   1. AES-Key and IV-Parameter will be combined before the encryption (48 bytes in total)
   2. The encryption used is RSA with PKCS#1 v1.5 Padding
4. Create the Resultfile-Package
   1. Create a Zip-File with content CBC_Key (Result from Step 3) and CBC_Payload (Result from step 2)
      This will result in a Zip-Archive with any Filename but ending on .zip

The Resultfile from Step 4 can then be uploaded to ESTV.

Anchor
FAQ FAQ

Frequently Asked Questions & Common Errors

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 AMANA XBRL Converter escapes those special characters since November 2019 (Version 1.1.8).
  • The system of BZSt had a issue which reintroduced the unsupported special characters in a file upon opening on their side. This issues has been fixed at the BZSt at the 27th of February 2020.

• XBRL Portal displays error "Permission denied (public key)" on file 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 form here and send it to cbcr@bzst.bund.de . This will unlock the access and will make reporting possible. 

• Deletion: "No report loaded" error

Image Added

Please make sure the old report is loaded and the correct CbC-Receiver was selected. To load the report with data to be corrected, click on File → Open Report. It is not possible to create a deletion without the (old) submitted report loaded in. 

• Deletion: "Not yet validated or has errors" warning

Image Added

The loaded file was not yet validated or has validation-errors.  Please make sure your data is valid and readable. 
Creating a deletion with an invalid file will lead to an invalid deletion-file.
Clicking "Nein" / No, the process will be stopped so the file and data can be validated in the normal fashion.