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):
If 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:
the 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?
- You must be logged in to reply to this topic.
XBRL API Resources
- The XBRL API
- XBRL Data Community
- XBRL API Interactive Documentation
- XBRL API Documentation (PDF)
- Get Started with Google Sheets
- OR request account provisioning to use Client ID and secret pairs in your app and:
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.
Ready to work with the API in Excel's Power Query, or with your own system or app?
Contact us at firstname.lastname@example.org to have your existing XBRL US Web account provisioned to generate client ID/Secret pairs to work with the XBRL API in a REST client or other application, including Excel's Power Query.
NOTE: You do not need to generate client ID/Secret pairs if you use the Google Add-on and Google Sheet exclusively to access data - the XBRL API Authentication Add-on handles this automatically.
Your account needs to be provisioned before you can login and generate client ID/secret pairs.
Login or register for a free account.
Join XBRL US
- Individual Options - Basic, Power User & Sole Practitioner
- For Your Team - Startup, Non-Profit, Academic & Corporate options
- Member Benefits Comparison Table