You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by Dhroov Sankla <dh...@gmail.com> on 2026/07/14 12:08:51 UTC
[DISCUSSION] Deprecation and potential removal of the MIX XBRL module (FINERACT-2670)
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
Re: [DISCUSSION] Deprecation and potential removal of the MIX XBRL module (FINERACT-2670)
Posted by Ádám Sághy <ad...@gmail.com>.
Hi,
I believe the decision has been made: we will deprecate and remove this feature from the next release.
Anyone disagree with this?
Regards,
Adam Saghy
> On Jul 14, 2026, at 7:05 PM, James Dailey <ja...@gmail.com> wrote:
>
> +1 to deprecate
>
> +1 to external toolset and reporting
>
> Potentially +1 for the Arelle solution- seems perfect
>
> —-
>
> Origin of the Mix XBRL was my initial work on outreach to World Bank CGAP (when Mix market was part of that) with the concept being that Microfinance Institutions needed a way to prove their Financial bono fides.
>
> Thus I think that the important point here is that the reporting infrastructure needs to have sufficient fidelity and transparency.
>
> Ratio calculations are important to be defined within the project as long as they tie to outside standards.
>
> Thanks
> James
>
>
>
> Sent from Gmail Mobile
>
> On Tue, Jul 14, 2026 at 7:09 AM Aleksandar Vidakovic <cheetah@monkeysintown.com <ma...@monkeysintown.com>> wrote:
>> ... 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 <victor.romero@fintecheando.mx <ma...@fintecheando.mx>> 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 (<adamsaghy@gmail.com <ma...@gmail.com>>) 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 <dhroovsankla2004@gmail.com <ma...@gmail.com>> 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 <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
>>>>>
>>>>
Re: [DISCUSSION] Deprecation and potential removal of the MIX XBRL module (FINERACT-2670)
Posted by James Dailey <ja...@gmail.com>.
+1 to deprecate
+1 to external toolset and reporting
Potentially +1 for the Arelle solution- seems perfect
—-
Origin of the Mix XBRL was my initial work on outreach to World Bank CGAP
(when Mix market was part of that) with the concept being that Microfinance
Institutions needed a way to prove their Financial bono fides.
Thus I think that the important point here is that the reporting
infrastructure needs to have sufficient fidelity and transparency.
Ratio calculations are important to be defined within the project as long
as they tie to outside standards.
Thanks
James
Sent from Gmail Mobile
On Tue, Jul 14, 2026 at 7:09 AM Aleksandar Vidakovic <
cheetah@monkeysintown.com> wrote:
> ... 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 <
> victor.romero@fintecheando.mx> 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 (<ad...@gmail.com>)
>> 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 <dh...@gmail.com>
>>> 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
>>>
>>>
>>>
Re: [DISCUSSION] Deprecation and potential removal of the MIX XBRL module (FINERACT-2670)
Posted by Aleksandar Vidakovic <ch...@monkeysintown.com>.
... 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 <
victor.romero@fintecheando.mx> 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 (<ad...@gmail.com>)
> 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 <dh...@gmail.com>
>> 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
>>
>>
>>
Re: [DISCUSSION] Deprecation and potential removal of the MIX XBRL module (FINERACT-2670)
Posted by VICTOR MANUEL ROMERO RODRIGUEZ <vi...@fintecheando.mx>.
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 (<ad...@gmail.com>) 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 <dh...@gmail.com>
> 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
>
>
>
Re: [DISCUSSION] Deprecation and potential removal of the MIX XBRL module (FINERACT-2670)
Posted by Ádám Sághy <ad...@gmail.com>.
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 <dh...@gmail.com> 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 <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
>