-
Notifications
You must be signed in to change notification settings - Fork 26
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
Incorrect Sign On Some Numeric Facts #15
Comments
Here is one more example: I am trying to retrieve NetIncomeLossAttributableToNoncontrollingInterest NoncontrollingInterestMember value from Q1 2017 data ([SEC link to data](https://www.sec.gov/cgi-bin/viewer?action=view&cik=845877&accession_number=0000845877-17-000092&xbrl_type=v# The fact xml from agm_20170331.xml is below: <us-gaap:NetIncomeLossAttributableToNoncontrollingInterest contextRef="FD2017Q1YTD_us-gaap_StatementEquityComponentsAxis_us-gaap_NoncontrollingInterestMember" decimals="-3" id="Fact-080C7834C860474640CE01C86E8BFB62" unitRef="usd">15000</us-gaap:NetIncomeLossAttributableToNoncontrollingInterest> The absolute value is 15000, but in the "CONSOLIDATED STATEMENTS OF EQUITY Statement" at SEC site showing the value as -15000 (negative 15). The presentation link (agm-20170331_pre.xml) is available and it has the reference to the above fact. However, there are no facts in Calculation link base (agm-20170331_cal.xml). <link:calculationLink xlink:role="http://www.farmermac.com/role/ConsolidatedStatementsOfEquityStatement" xlink:type="extended" /> My guess is perhaps there are few more xml files - probably from the default gaap - that need to be analyzed to determine the correct sign. I hope this helps. |
Thank you for the additional information! Do you, by chance, have URLs to the XBRL document instances? |
My guess is that it has to do with Gepsio possibly not respecting the |
Here is the link to xbrl instance: So far, I did not see any issues with decimals. All decimal values have expected zeros. |
From a user email:
The text was updated successfully, but these errors were encountered: