If a message was rejected, A filing can be rejected due to a configuration error is likely. Please check the following things settings when creating a filing by file upload: - The file must be a zip file.
- The content of the zip file must be a single XBRL file with the extension .xbrl.
If the message filing is still rejected, please contact our support at xbrl-support@amana.de . | Error message rejected filing | Reason | See chapter |
|---|
| No reporting request for the reported |
key | due date <...>, taxonomy <...> and entity <...> found. | There is no |
notification reporting request in the system for this |
key due date, this taxonomy, and this entity. | Rejected Filings | | The specified SenderId <...> and reported XBRL Id <...> in the XBRL document do not match. | XBRL |
Id message | filing differs from the XBRL |
Id | ID of the reporting entity selected during |
message | the filing upload | Rejected Filings | | Filing version duplicate was detected: the same file was processed at <date/time> (FilingId=<...>). |
Message | Filing version duplicate was detected: the same file was processed at <date/time> (FilingId=<...>). | Rejected Filings |
|