• Solutions
    • FERC XBRL Reporting
    • FDTA Financial Reporting
    • SEC Compliance
    • Windows Clipboard Management
    • Legato Scripting
  • Products
    • GoFiler Suite
    • XBRLworks
    • SEC Exhibit Explorer
    • SEC Extractor
    • Clipboard Scout
    • Legato
  • Education
    • Training
    • SEC and EDGAR Compliance
    • Legato Developers
  • Blog
  • Support
  • Skip to blog entries
  • Skip to archive page
  • Skip to right sidebar

Thursday, February 01. 2024

Issue Filing Large XBRL Reports to the EDGAR System

Some time over the weekend of January 27th, EDGAR XBRL filers began experiencing an issue when submitting large XBRL filings to the EDGAR system. This issue concerns a change that was made in Arelle. Specifically, when an XBRL report is run through Arelle with too many possible dimensional combinations on a single report, Arelle now produces an error and the EDGAR System rejects the filing. The SEC is working on a solution to this issue.


The error appears as follows:


WRN: XBRL ERROR MESSAGEMSG: Error: [error] Presentation grouphttp://xbrl.sec.gov/rr/role/RiskReturnDetailData with 5 axes could havemore than 2 billion cells. Split up this presentation group and see EFM6.25.2 to see how to reduce the number of combinations


This is a significant issue for Risk/Return filings in particular, since the default presentation can be a single detail data presentation that combines all facts. Thus, if there are more than three or perhaps four series in the report, this error is likely to occur. GAAP filers can also be impacted if they have extremely large detail narrative notes in their submissions.


Currently, the only known work-around is to split the large presentation up into smaller presentations. GAAP filers can use the Edit Engram Presentation function in GoFiler to force facts to render elsewhere in the filing. For Risk/Return filers, there is no way to fix this problem other than manually editing the presentation to split the detail data into smaller sections. This approach involves XML code editing.


The SEC’s Structured Data expects this to be changed to a non-fatal warning by Tuesday, February 6th. In the mean time, we highly recommend you avoid filing large XBRL reports until after the SEC implements their fix if you can do so. If you must file before then and need assistance, our support staff is able to adjust your filings manually; we would require a 1–2 hour warning that you require our help.


For more details, please contact support.

Posted by
Administrator
in EDGAR News, GoFiler Updates, SEC Filing Help at 11:16
Trackbacks
Trackback specific URI for this entry

No Trackbacks

Comments
Display comments as (Linear | Threaded)
No comments
The author does not allow comments to this entry

Quicksearch

Categories

  • XML Accounting
  • XML AICPA News
  • XML FASB News
  • XML GASB News
  • XML IASB News
  • XML Development
  • XML Events
  • XML FERC
  • XML eForms News
  • XML FERC Filing Help
  • XML Filing Technology
  • XML Information Technology
  • XML Investor Education
  • XML MSRB
  • XML EMMA News
  • XML FDTA
  • XML MSRB Filing Help
  • XML Novaworks News
  • XML GoFiler Online Updates
  • XML GoFiler Updates
  • XML XBRLworks Updates
  • XML SEC
  • XML Corporation Finance
  • XML DERA
  • XML EDGAR News
  • XML Investment Management
  • XML SEC Filing Help
  • XML XBRL
  • XML Data Quality Committee
  • XML GRIP Taxonomy
  • XML IFRS Taxonomy
  • XML US GAAP Taxonomy

Calendar

Back May '25 Forward
Mo Tu We Th Fr Sa Su
Sunday, May 18. 2025
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  

Feeds

  • XML
Sign Up Now
Get SEC news articles and blog posts delivered monthly to your inbox!
Based on the s9y Bulletproof template framework

Compliance

  • FERC
  • EDGAR
  • EMMA

Software

  • GoFiler Suite
  • SEC Exhibit Explorer
  • SEC Extractor
  • XBRLworks
  • Legato Scripting

Company

  • About Novaworks
  • News
  • Site Map
  • Support

Follow Us:

  • LinkedIn
  • YouTube
  • RSS
  • Newsletter
  • © 2024 Novaworks, LLC
  • Privacy
  • Terms of Use
  • Trademarks and Patents
  • Contact Us