The Importance of Reporting Design when Converting to ESEF Wrong fonts, misaligned amounts, low quality images and an overall poor visual appearance are among the most common graphical mistakes when converting your annual report to ESEF. You need to pay attention to the design of your ESEF report, but what should you pay attention to […]
Webinar: ESEF – Are You Ready for the New Reporting Format? On Wednesday the 29th of July we hosted a webinar for the Austrian market. The webinar was aimed at explaining what the new reporting format will mean for them. It also included a showcase of how our product can make their lives easier when […]
Lors d’un récent webinaire, la société française, Pomelo-Paradigm, a approuvé le produit ParsePort parce qu’il fonctionne extrèmement bien avec leur nouvelle solution collaborative Pomdoc Pro.
Comment KoneCranes est devenu prêt aux reporting ESEF Aujourd’hui, de nombreuses sociétés cotées en bourse sont à la récherche d’un fournisseur de solutions ESEF afin de se conformer à l’obligation ESEF. La société finlandaise, KoneCranes, a également cherché une solution ESEF optimale. En lancant le processus de sélection d’un fournisseur ESEF, l’équipe de KoneCranes a […]
In what may be the fastest certification process in the history of certification processes, XBRL International gave our software their approval.
As with all business intelligence, data quality in XBRL is key. We all know the saying “garbage in is garbage out”. So how do we ensure data quality from the very beginning?
In this article, first published in ThinkTWENTY20 Magazine in March, Kim Eriksen, CEO of ParsePort, tells us the story behind ESEF.
Even though private businesses are in a desperate need of help, you should not worry about ParsePort.
The final release of the CRD IV 2.9.1 taxonomy has been published and this means that reports in 2020 need to be created with the 2.9.1 version. Get the full rundown of changes here.
The Solvency II taxonomy has been updated and this means that reports from reference date 31-12-2019 should be reported with taxonomy version 2.4.0.