Skip to content
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

Parse "custom" xbrl files #28

Open
jakobdo opened this issue Jan 20, 2016 · 4 comments
Open

Parse "custom" xbrl files #28

jakobdo opened this issue Jan 20, 2016 · 4 comments
Assignees
Labels

Comments

@jakobdo
Copy link

jakobdo commented Jan 20, 2016

I'm unsure if this is a bug or just me who is to stupid to get this lib working.
I have tried to work with danish xbrl files from the danish site: virk.dk
Look at this f.ex:
https://datacvr.virk.dk/data/visenhed?enhedstype=virksomhed&id=27400744&soeg=danmark&type=Alle
Under "regnskaber" you should find a link to xbrl-files.
F.ex. this: https://datacvr.virk.dk/data/offentliggorelse?dl_ref=Y3ZyLmRrOi8veGJybHMvWC03RENCRUIxMi0yMDE1MDEzMF8xNjA5NTJfNzA0
When i look into the file, the xml is in this format:

I see tags like: e:ProfitLoss
But when i look into your parser, it looks for:
income_loss += xbrl.find_all(name=re.compile("(us-gaap:profitloss)", re.IGNORECASE | re.MULTILINE))

So is the only xbrl files supported, the files with: us-gaap: infront of the "tags" ?

@greedo greedo self-assigned this Jan 20, 2016
@heisen273
Copy link

Any updates on this issue? I'd love to parse virk.dk

@greedo
Copy link
Owner

greedo commented Dec 20, 2016

Yes @heisen273 @jakobdo currently US GAAP is the only accounting standard supported, through I could easily add support for other accounting standards

@heisen273
Copy link

@greedo Cmon, mate, dont hesitate to do it. I can help you with this as hard as I can, I've spent some time with your lib and modified it for my needs, - lemme know if there's anything i can help you with.

@jakobdo
Copy link
Author

jakobdo commented Dec 20, 2016

A dynamic "identifier" would be nice.
Or if you could create a schema or similar, then it would be "easy" to implement new standards. (i think)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants