Missing Data – Costco Wholesale Corp

[Angelo Brizi]

1)
/api/v1/fact/search?concept.local-name=RevenueFromContractWithCustomerExcludingAssessedTax&period.fiscal-year=2019&period.fiscal-period=Y&entity.cik=0000909832&fact.ultimus=true&fact.has-dimensions=false&fields=fact.value

returns 152703000000

This is the 10-K filed on 2019-10-11 but the returned revenues are for the 12 months not the 3 months. The 10K reports 152703 (like the API) for the 12 months but only 34740 for the 3 months. How do I get the data for the 3 months (which should be 34740)?

2)
api/v1/fact/search?concept.local-name=RevenueFromContractWithCustomerExcludingAssessedTax&period.fiscal-year=2020&period.fiscal-period=1Q&entity.cik=0000909832&fact.ultimus=true&fact.has-dimensions=false&fields=fact.value

This correctly represents the Revenues for the filings 10Q on 2019-12-23. No issues here

3)
api/v1/fact/search?concept.local-name=RevenueFromContractWithCustomerExcludingAssessedTax&period.fiscal-year=2020&period.fiscal-period=2Q&entity.cik=0000909832&fact.ultimus=true&fact.has-dimensions=false&fields=fact.value

This is the 10Q filed on 2020-03-12 and it’s missing. Revenues should be 39072000000 but returned value is null

4)
api/v1/fact/search?concept.local-name=RevenueFromContractWithCustomerExcludingAssessedTax&period.fiscal-year=2020&period.fiscal-period=3Q&entity.cik=0000909832&fact.ultimus=true&fact.has-dimensions=false&fields=fact.value

This is the 10Q filed on 2020-06-04 and it’s missing. Revenues should be 37266000000 but returned value is null

Also data for 2019 2Q and 2019 3Q are missing.

[Arthur Olevskiy]

Hi Angelo,

I can help you with first issue. In your request, you specified “period.fiscal-period=Y” which is means 12 month. If you want get 3 quarters you can put following values: Y, 1Q, 2Q, 3Q, 4Q, 3QCUM, 1H, 2H. It depends on accounting data type if it is “duration” you need to put 3QCUM if data published “as for some date” you can put 3Q.

[Arthur Olevskiy]

As for me, it is better to get list of fact.id for specific filing and put it in request to get values.

[Arthur Olevskiy]

.

• This reply was modified 3 years, 8 months ago by Arthur Olevskiy.
• This reply was modified 3 years, 8 months ago by Arthur Olevskiy.

[Angelo Brizi]

Hi Arthur,
thanks a lot for your feedback. How do you get the list of fact.id for the specific filing?

For 2Q 2019, using either 2Q or 1H the query returns no data

api/v1/fact/search?concept.local-name=RevenueFromContractWithCustomerExcludingAssessedTax&period.fiscal-year=2019&period.fiscal-period=2Q,1H&entity.cik=0000909832&fact.ultimus=true&fact.has-dimensions=false&fields=fact.value

Same thing for 3Q 2019, using either 3Q or 3QCUM no data

api/v1/fact/search?concept.local-name=RevenueFromContractWithCustomerExcludingAssessedTax&period.fiscal-year=2019&period.fiscal-period=3Q,3QCUM&entity.cik=0000909832&fact.ultimus=true&fact.has-dimensions=false&fields=fact.value

or for 2Q 2020, using either 2Q or 1H still no data

api/v1/fact/search?concept.local-name=RevenueFromContractWithCustomerExcludingAssessedTax&period.fiscal-year=2020&period.fiscal-period=2Q,1H&entity.cik=0000909832&fact.ultimus=true&fact.has-dimensions=false&fields=fact.value

Thanks again.

[Arthur Olevskiy]

Hi Angelo,

I use this link
api/v1/relationship/tree/search?dts.id={dts_id}&network.link-name=calculationLink,presentationLink&format=flat&fields=relationship.target-datatype,relationship.target-concept-id,network.role-description.sort(ASC)

Also, you can play with requests in documentation (https://xbrlus.github.io/xbrl-api)

[Arthur Olevskiy]

Then, you can get relationship.target-concept-id value and make following request

https://api.xbrl.us/api/v1/fact/search?concept.id=&dimension.is-base=false&dts.id={dts_id}&fact.ultimus-index=1&period.fiscal-period=&period.fiscal-year=&fields=fact.value,fact.inline-display-value,concept.local-name

concept.id same as relationship.target-concept-id. I put list of ids, fiscal period and fiscal year period to request’s params

[Angelo Brizi]

Thanks a lot Arthur

[David Tauriello]

Hi Angelo – On your question about why you’re unable to return fact.value data for 2Q, 3Q or 3QCUM, it is because when we load the data, our process includes an algorithm to determine period.fiscal-period, based on a common reporting calendar framework with some flexibility for start/end dates and industry sector. Unfortunately, Costco’s timings don’t quite fit this expectation and as a result, we report the range as YYYY-MM-DD – YYYY-MM-DD.

api/v1/fact/search?concept.local-name=RevenueFromContractWithCustomerExcludingAssessedTax&entity.cik=0000909832&fact.ultimus=true&fact.has-dimensions=false&fields=fact.value,period.fiscal-period,entity.name,report.filing-date.sort(DESC)

I’ve raised this issue with the team and we’re looking at ways to address this as we process the data from the SEC. Check out this thread for a bit more discussion on fiscal v. calendar periods in the XBRL API: https://xbrl.us/forums/topic/reports-and-periods/#post-115421.

[Angelo Brizi]

Hi David, thanks a lot for your explanation. That was very helpful.

[izrar Ulhaq]

It is better to get list of fact.id for specific filing and put it in request to get values.

[David Tauriello]

Hi izrar – you can use a nested endpoint /report/fact to get the facts for a specific report without ’round-tripping’ to get the fact.id first. With the nested approach, you can get the value, id and all other attributes of the fact. See https://xbrlus.github.io/xbrl-api for details.

[Author]

Posts