-
-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Financials Extraction from XBRL #74
Comments
Copied from Issue 73 For example, in the latest 10Q (Q2 2024) for $GD, the 10Q contains rows for Costs of Products and Services (us-gaap:CostOfGoodsAndServicesSold) but this fact is never loaded into the facts table in Edgar-tools or in the income-statement printed. Likewise for "us-gaap:InterestIncomeExpenseNet" and "us-gaap:OtherNonoperatingIncomeExpense" facts. This may possibly be related to these fields having a role of "http://fasb.org/us-gaap/role/ref/legacyRef" while most of the facts that do get loaded have a role of "http://www.xbrl.org/2003/role/disclosureRef" |
Note from https://github.com/emestee If this helps, here are the entry points from the FASB taxonomy that group the line items in the mandatory filing statements: |
@emestee what do you know about standardized statements vs as-reported statements? Do you know what defines the standard concepts that all companies include in their statements? |
circling back here as ive been playing with the new upgrades. Thanks for this - looks like a lot of work went into the rewrite. Were you able to pull in the productMembers as referenced here #66 (comment) I have been trying to pull in the concepts that feed into the Revenue Sales, but still can't figure that out correctly. The is the code snippet I have (eg for the AAPL XBRL instance)
Running this against AAPL Q2 10Q, I get the following facts:
The problem is that the us-gaap:ProductMember actually represents the total of all the individual product lines, so I end up double counting the product values. Like, how do you determine that the apple:* members are part of the productMember, while the serviceMember is on its own without any nesting? I want this product breakdown to work for any 10-Q so I can present where a companies incoming revenue comes from. |
I actually don't know, I imagine it is SEC regulation derived from federal law and incorporating FASB rules. I also don't think it should matter. SEC filings are validated upon submission and can be assumed to be compliant with technical requirements (otherwise the SEC parser will reject the filing). You should not assign any specific meaning to any items in the statement, other than their relationships to parent items, if any. |
I think I want to add a parameter that switches between as_reported - the rows and labels that the company wants to show and standard - a common set of values and labels that all companies are required to report. I think Bloomberg operates like that no? |
thats kind of what im doing where I use this library to pull in the data but then standardize things into my own fields. You prev had a version of that in your old income statement code, but the challenge is getting a mapping of all the fields into something. |
I'm struggling in this standardization now, would you please share the approach or some code to give me an idea? --I'm new to financial data and SEC but want to standardize financial statements for many companies. @amitgandhinz |
The new version is working much better on the financials statements! Thanks a lot for that! I think there is a small thing that could be highly improved in the cash flow statement. If I look at Apple, it seems like a lot of the lines are positive instead of being negative (like Share repurchases). |
@Colem19 @dgunning The statements are great; Dwight has done a great job. You are right though, good eye on identifying this issue. As an example I pulled (ULTA)'s most recent 10-Q via the TENQ-Class and I have identified a few more line items that either should have a negative output , positive output or its in reverse order (meaning 2024 should be positive and 2023 should be a negative). @dgunning do you anticipate that this will be fixed or is something that is fixable? |
Closing as fixed |
Version 3 of XBRL financials
The text was updated successfully, but these errors were encountered: