Home Forums The XBRL API Tackling issues with operating lease data

Viewing 2 reply threads
  • Author
    Posts
    • #184736
      Teji Abraham
      Participant

      Hi David:
      I have seen some issues with Operating Lease data and posting here to both raise awareness and also to inquire if there are any causes/solutions for these. Not sure if this is because of wrong xbrl filing from the company or some other reasons

      So the typical type of problems found are:
      a) Operating Lease total not adding up to the current and non-current components of Operating Lease
      b) Scale of Operating Lease data being wrong
      c) Mixing up of various operating lease data elements

      Thanks and look forward to your inputs.

      Example 1:
      Fonar Corporation
      Period: 2019-12-31, cik: 0000355019

      Per SEC Filing (all in thousands):
      Operating Lease Liability: 31,867
      Operating Lease Liability Current: 3185
      Operating Lease Liability Non-Current: 28682

      Per XBRL data feed (all in thousands):
      Operating Lease Liability: -987
      Operating Lease Liability Current: 3185
      Operating Lease Liability Non-Current: 28682

      Note: the negative Operating Lease Liability total despite the positive sub-components

      Example 2: (Scale of one of data components off by a factor of 1000)
      SecureWorks Corp
      Period: 2020-01-31, cik: 0000355019

      Per SEC Filing (all in thousands):
      Operating Lease Liability: 29,554
      Operating Lease Liability Current: 4,885 (implied, ie calculated)
      Operating Lease Liability Non-Current: 24,669

      Per XBRL data feed (all in thousands):
      Operating Lease Liability: 29,554,000
      Operating Lease Liability Current: NIL
      Operating Lease Liability Non-Current: 24,669

      Example 3: (Mixed up operating lease data elements)
      American River Bankshares
      Period: 2019-12-31, cik: 0001108236

      Per SEC Filing (all in thousands):
      Operating Lease Liability: 3098
      Operating Lease Liability Current: 769
      Operating Lease Liability Non-Current: 2329 (implied)

      Per XBRL data feed (all in thousands):
      Operating Lease Liability: 915
      Operating Lease Liability Current: 3098
      Operating Lease Liability Non-Current: NIL

      Note: Two issues in this example: total Operating Lease Liability is presented as Operating Lease Liability Current and values don’t add up accurately.

    • #184756
      David Tauriello
      Keymaster

      Hi Teji –

      In example 1, it looks like company is using the labels ‘Total lease liability’ for the tag FinanceLeaseLiability (31867) and ‘Present Value discount (5.5% weighted average)’ for OperatingLeaseLiability (-987) immediately above the total in the table.

      Search the label linkbase at https://www.sec.gov/Archives/edgar/data/355019/000035501920000007/fonr-20190930_lab.xml for text ‘Total lease liability’ and ‘Present Value discount (5.5% weighted average)’ to see these elements.

      In example 2, either the text “(in thousands)” is incorrect for the table – all of the values are in millions or the scale is incorrect on all of the values in the table (should be 3 not 6)

      Search for 29,554 in the company inline, then click the corresponding value and look at the ‘scale’ line: https://www.sec.gov/ix?doc=/Archives/edgar/data/1468666/000146866620000019/scwx10-kfy2020x01312020.htm

      I’ll circle back on example 3. FWIW, our Public Filings Database is a copy of what the SEC says it has accepted into EDGAR. The data is ‘as-filed’ – we don’t normalize what we get.

    • #184767
      Teji Abraham
      Participant

      Thanks much David. Some clarifications below.

      * Across all the data in my examples “(in thousands)” for xBRL data is from me to make the data more readable (I took the raw xbrl data and divided by 1000 to make it more presentable).

      *For Example 1, I am assuming your conclusion is that the company made an erroneous filing? Is there a possibility that the company accurately files the sec text filings but somehow ends up filing erroneous xbrl filing ?

      *For Example 2, as mentioned I made the divisions by 1000 for readability. And I did the division for all of the data items. For clarity the raw values from the xbrl api were: 29,554,000,000 (For Operating Lease Liability) and 24,669,000 (For Operating Lease Liability Non-current). And my apologies, the cik should be: 0001468666

      *Sounds good regarding Example 3.
      Thanks again, Teji

Viewing 2 reply threads
  • You must be logged in to reply to this topic.

Comment