Home › Forums › The XBRL API › Data in the wrong place.
- This topic has 2 replies, 2 voices, and was last updated 6 years, 10 months ago by Peter Guldberg.
-
AuthorPosts
-
-
Tuesday, February 12, 2019 at 5:19 PM #123436Peter GuldbergParticipant
When we come across data that seems to have been filed correctly with the SEC, but is under the wrong concept.local-name in the XBRL US database, do you want us to report it somewhere?
I’m not so worried that one particular piece of data of course, it’s more if it’s a sign of some general mapping thing that has gone wrong. It’s in more than one report, but so far only for one specific issuer.
fact.id=129160850 is an example of it. -
Thursday, February 14, 2019 at 12:41 PM #123713David TaurielloKeymaster
This query returns concept.local-name consistent with what’s in the xml the issuer submitted (we copy these files into our database every 10 – 15 minutes):
/report/fact/search?fact.id=129160850&fields=report.sec-url,report.entry-url,fact.xml-id,fact.value,concept.local-nameIf possible, please post back and let me know where you’re noting the inconsistency with what we’ve captured to the XBRL US Database of Public Filings (https://www.sec.gov/cgi-bin/viewer?action=view&cik=320187&accession_number=0000320187-16-000336&xbrl_type=v# or https://www.sec.gov/Archives/edgar/data/320187/000032018716000336/nke-5312016x10k.htm).
-
Friday, February 15, 2019 at 3:21 AM #123780Peter GuldbergParticipant
I guess it must be NKE that have filed it wrong then.
The fact above is from 2016 10-K but actually relates to the 2014 annual number. It is filed as “StockholdersEquityIncludingPortionAttributableToNoncontrollingInterest”
but the value of 85000000 is actually “AccumulatedOtherComprehensiveIncomeLossNetOfTax”It appears correctly in the interactive report at https://www.sec.gov/cgi-bin/viewer?action=view&cik=320187&accession_number=0000320187-14-000097&xbrl_type=v#
so I think they have filed it – mistakenly – under both XBRL names.If you run the query:
https://api.xbrl.us/api/v1/fact/search?report.id=163622&concept.local-name=StockholdersEquityIncludingPortionAttributableToNoncontrollingInterest,AccumulatedOtherComprehensiveIncomeLossNetOfTax&period.fiscal-year=2015,2016&fact.has-dimensions=false&fields=concept.local-name,period.fiscal-year,period.fiscal-period,fact.value,fact.has-dimensionsthe value appears under both concepts. But those are very different concepts, and would never be the same. In the case of NKE, they do not have a minority interest and should not be using the StockholdersEquityIncludingPortionAttributableToNoncontrollingInterest concept at all. They should use StockholdersEquity, which they do, and that is filed correctly.
They make this mistake consistently in later reports – so I guess the question becomes, is there a place – perhaps at the SEC? – where you can report obvious filing mistakes, to try and get them to get the filer to fix it?
-
-
AuthorPosts
- You must be logged in to reply to this topic.
Search Forums
Recent Topics
- Income Statement data for a company by David Tauriello
- Normalized data presentation by David Tauriello
- Extract Director RSUs/Options Form 14A by Priyanka Goonetilleke
- Using the offset parameter by David Tauriello
- Spreadsheet Commands: Query Worksheet and Query Workbook Query Workbook by Liam Noailles
Recent Replies
-
Income Statement data for a company 5 months, 2 weeks ago
-
Income Statement data for a company 5 months, 3 weeks ago
-
Using the offset parameter 9 months, 3 weeks ago
-
Using the offset parameter 9 months, 3 weeks ago
-
Using the offset parameter 9 months, 4 weeks ago
Documentation & Discussion
- Get started with Google Sheets OR
- Get started with Microsoft Excel OR
- Get access to as-filed data from us for other tools or your own app
- XBRL API Interactive Documentation
- Ten Tips & Techniques
- The XBRL API
- XBRL Data Community
- 2024 US GAAP Taxonomy Viewer
- Live support - Monday, 3:30 - 4:30 PM ET
Who's using this free data?
API Use 2024 || API Use 2023 || API Use 2022 || API Use 2021 || API Use 2020 || API Use 2019 || API Use 2018
Join XBRL US
- Individual Options - Basic, Power User & Sole Practitioner
- For Your Team - Startup, Non-Profit, Academic & Corporate options
- Member Benefits Comparison Table
Using the XBRL API with the Public Filings Database
Unless otherwise agreed to in writing, any and all use of the XBRL API to authenticate and retrieve data from the XBRL US Database of Public Filings implies user consent and agreement with the XBRL US API Agreement. If you are unable to agree to these terms, do not use the XBRL API.
To use the XBRL API outside of Google Sheets, your account needs to be provisioned for OAuth2 access.





