On Sun, Oct 6, 2019 at 2:59 PM Francis Guchie <[email protected]> wrote:
> Dear Jun, > > I am using fineract 1.x and i have just a few tweaks i have to do to do > current accounts or savings accounts. I capitalise on product definitions > and give them "global" settings. > Every client with that particular product will have services as per > product settings. > Hi Francis, will you be willing to send in a PR for the above? Am sure Jun will be willing to help review and see if this can add value to others in the community. > The only challenge i have been faced with with applying overdrafts on > particular particular accounts > Soon i will have a work around solution to it and may be i will send a PR > for it but under the fineract 1.x > This will be great. Thanks > > > > My Kind Regards > > Francis Guchie Kirago > > > > > > > > > On Sun, Oct 6, 2019 at 5:33 AM Jun King Miñon <[email protected]> wrote: > >> Hi Everyone, >> >> Our pilot bank is about to support Current accounts and looking into >> Mifos Savings product module, which has overdraft facility and allows 0 >> interest value, then I am thinking that it can already be used to support >> Current Account. However, I am worried on the tagging of the product as >> Savings and Current are two different deposits. >> >> I came across below jira ticket but no path-forward yet. >> >> https://issues.apache.org/jira/browse/FINERACT-200 >> >> Is there like a plan to separate Current from Savings account on the >> UI-level in Fineract or Fineract CN? >> >> Thanks in advance. Cheers! >> >> Regards, >> >> Jun King P. Miñon >> Consultant Software Engineer >> Core Banking Solutions >> >> >> PEARLPAY INC. >> >> 2nd Floor, 22 The Jupiter Center, Jupiter Street, Makati, 1209 Metro >> Manila, Philippines >> >> https://www.pearlpay.com >> https://www.linkedin.com/company/pearlpay >> https://www.facebook.com/PearlPayOFFICIAL >> >> This email and any files transmitted with it are confidential and >> intended solely for the use of the individual or entity to whom they are >> addressed. If you have received this email in error please notify the >> system manager. This message contains confidential information and is >> intended only for the individual named. If you are not the named addressee >> you should not disseminate, distribute or copy this e-mail. Please notify >> the sender immediately by e-mail if you have received this e-mail by >> mistake and delete this e-mail from your system. If you are not the >> intended recipient you are notified that disclosing, copying, distributing >> or taking any action in reliance on the contents of this information is >> strictly prohibited. WARNING: Computer viruses can be transmitted via >> email. The recipient should check this email and any attachments for the >> presence of viruses. The company accepts no liability for any damage caused >> by any virus transmitted by this email. E-mail transmission cannot be >> guaranteed to be secure or error-free as information could be intercepted, >> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. >> The sender therefore does not accept liability for any errors or omissions >> in the contents of this message, which arise as a result of e-mail >> transmission. Our company accepts no liability for the content of this >> email, or for the consequences of any actions taken on the basis of the >> information provided, unless that information is subsequently confirmed in >> writing. If you are not the intended recipient you are notified that >> disclosing, copying, distributing or taking any action in reliance on the >> contents of this information is strictly prohibited. Any views or opinions >> presented in this email are solely those of the author and do not >> necessarily represent those of the company. Employees of the company are >> expressly required not to make defamatory statements and not to infringe or >> authorize any infringement of copyright or any other legal right by email >> communications. Any such communication is contrary to company policy and >> outside the scope of the employment of the individual concerned. The >> company will not accept any liability in respect of such communication, and >> the employee responsible will be personally liable for any damages or other >> liability arising. >> _______________________________________________ >> Mifos-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/mifos-users >> >
