Cover page ixbrl tagging errorsAnswered
1) For "Large accelerated filer" I am getting an error that the the fact has an incorrect or missing fact value, date/date range, or unit. It is set to text format. Details mention boolean value error. Is the boolean box supposed to be tagged vs. the words "Large accelerated filer"? The sample project had the words tagged.
2) I am getting the following DQC error on the document fiscal period focus of Q2 "The number of days, 91 in the date range reported for Document Fiscal Period Focus, 2019-04-01 to 2019-06-30 is not consistent with the Document Fiscal Period Focus with a value of Q2." I had initially had the date range set to YTD like the rest of the cover page, but changed to QTD thinking it would fix, but it did not. I was thinking possibly I needed to change the format of the cell to "period" and select a format for number of days, but I don't see that as an option. Does anyone know what I am doing wrong?
Thanks for the question. I did a little checking and below are my suggestions.
For item 1, I would try the following steps to address this error:
- Delete the contents in the cell that contains "Large accelerated filer"
- Re-type "Large accelerated filer"
- Check the cell to see if it shows green, i.e. no tagging errors
- Generate iXBR and review the SEC Viewer for a value of "Large Accelerated Filer"
If this does not resolve the error, then I might recommend reaching out to your CSM or a member of our Professional Services team to help address.
For item 2, the error message is not actually related to the value "Q2" tagged on the DEI but instead is letting you know that a text block tag (Level 1, Level 2 or Level 3) is not utilizing a YTD date. As a reminder, all text blocks must utilized YTD dates. I'd see if you can track down which one it might be. Lastly, the XBRL date on the "Q2" should also be the YTD date.
Hope that helps. Let me know what other questions you have, or if you need any clarification on the above. Thanks again and happy tagging!1
Very helpful, as always. Both solutions worked! Thanks Mike!0
Please sign in to leave a comment.