Re: [Mifos-developer] ERPNext ERP Accounting - Mifos

[Floyd N. <flo...@gm...>]

Thank you for the response Mr James Dailey. It took me a while to respond
because I wanted to get as much detail as possible. In this use case, We
will stick with Odoo ERP due to the fact that it is widely used and has
extensive documentation and community support. Odoo serves as the ERP in
this case handling financial management for the organization and is
integrated with Payment Providers such as bank and mobile money transfers
such as MTN Money. Fineract/Mifos in this set up manages the savings & loan
related transactions. For instance when We disburse a loan on Mifos   POST
https://DomainName/api/v1/loans/{loanId}?command=disburse   then on the
Odoo part the Accounting module will record the transaction and effect it
on running balance. Odoo also has a CRM which means that by effect all
clients on Mifos will also be on Odoo. Another update on Mifos
*https://fineract.apache.org/docs/legacy/index.html#journalentries_updatebalance
<https://fineract.apache.org/docs/legacy/index.html#journalentries_updatebalance>*
will also be effected.


On Fri, Apr 28, 2023 at 6:44 PM James Dailey <jam...@gm...> wrote:

> Hi Floyd
>
> Can you explain more??
>
> Good to see you are continuing your efforts. This idea, of combining
> Mifos/Fineract with an ERP resurfaces every few years.
> To my knowledge there have been several attempts with other ERPs, for
> example using ODOO.
>
> The problems that the ERP strategy solves are around extending key
> functionality and supporting new workflows not natively supported by
> Mifos/Fineract.
> The downside is the same as with any ERP:  If you can do "anything"
> then the design that you choose is important for long term
> sustainability.
> It's probably obvious but worth repeating that the best way to proceed
> is to not require new APIs from Fineract but rather to assume those
> are relatively static and build on top of the mental model at
> Fineract.
>
> This listserv may be the right place because the Mifos UI components
> are what you would be "Replacing" and thus would come into the
> conversation.  Mifos is where some outside-of-fineract components can
> live.
>
> *It would be useful for the community to have you explain your
> thinking around combining the ERP with Mifos/Fineract.  That kind of
> thinking and ideas are not proprietary but rather a useful
> conversation to get everyone on the same page.*
>
> For example, I would start with the event model, showing the logical
> flows between systems.
> [develop diagram of flows, arrows between customer module in both
> systems, account module and customer module, etc
> maybe include some data validation components in the ERP
> maybe include the authentication mechanism as well]
>
> Or, I would start with a minimal set of APIs on fineract that could be
> fit into a model at the ERP.
> [On create account event at ERP,  endpoint ==> POST
> https://DomainName/api/v1/clients ]
>
> Either way, explaining how you're thinking about this would be useful
> exploration.
>
> Thanks,
> James
>
> James Dailey
>
>
>
> On Tue, Apr 25, 2023 at 2:45 AM Floyd Nickson <flo...@gm...>
> wrote:
> >
> > Good Day Devs, I hope this message finds you well. We are in the process
> of extending the Mifos Accounting functionality by integrating it with
> ERPNext. Has anyone here ever made such an attempt? We would like to hear
> your experience and also ideas on how best such an endeavour can be handled
> successfully.
> > Thank you
> > Mifos-developer mailing list
> > mif...@li...
> > Unsubscribe or change settings at:
> > https://lists.sourceforge.net/lists/listinfo/mifos-developer
>
>
> Mifos-developer mailing list
> mif...@li...
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer