... if we really need some sort of XBRL support then we should really consider integrating https://github.com/Arelle/Arelle... seems to be the gold standard in the open source world (note: it's implemented in Python)... if it's good for the SEC then it should be good for us?
Cheers On Tue, Jul 14, 2026 at 3:52 PM VICTOR MANUEL ROMERO RODRIGUEZ < [email protected]> wrote: > I think it should be deprecated and supported by a third party reporting > tool. In some cases the reporting are required to be generated using XBRL, > but they follow specific layout which I think it is not supported neither > implemented in Apache Fineract > > El mar, 14 jul 2026 a las 7:09, Ádám Sághy (<[email protected]>) > escribió: > >> Hi Dhroov, >> >> >> Thanks for bringing this topic up for discussion. >> >> >> I’m curious to know if anyone in the community is actively using this MIX >> XBRL module…otherwise we can consider deprecating it. >> >> >> Regards, >> >> Adam Saghy >> >> On Jul 14, 2026, at 2:08 PM, Dhroov Sankla <[email protected]> >> wrote: >> >> Hello Fineract Developers, >> >> While working on the serialization modernization for the MixReport module >> (FINERACT-2670), we ran into architectural roadblocks stemming from legacy >> dependencies. Specifically, the module still relies on >> javax.script.ScriptEngine, which has been deprecated since Java 11 and >> removed in subsequent releases. >> >> Given that the MIX XBRL standard itself has long been abandoned globally ( >> https://themix.org), maintainers Aleksandar Vidakovic and Adam Saghy >> suggested on PR #6090 that we open a broader discussion here. >> >> Should we proceed with refactoring the existing serialization logic >> natively, or is it more valuable to the project to deprecate and completely >> remove the fineract-mix sub-module from the codebase to clean up >> technical debt? >> >> I would love to hear the community's thoughts on this. >> >> Regards, >> Dhroov Sankla >> >> >>
