ASF GitHub Bot commented on FINERACT-574:

GitHub user Nenge1 opened a pull request:



    This pull request fix the bug of duplicate posting in journal entries when 
share account is rejected

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Nenge1/fineract FINERACT-574

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #441
commit 613b802c0d410e9fc74b1268c222d3b9d48bf6d4
Author: Nenge <masoya>
Date:   2018-02-08T12:05:39Z



> Issues related to share Account Creation
> ----------------------------------------
>                 Key: FINERACT-574
>                 URL: https://issues.apache.org/jira/browse/FINERACT-574
>             Project: Apache Fineract
>          Issue Type: Bug
>          Components: Shares
>            Reporter: Santosh Math
>            Assignee: Shaik Nazeer Hussain
>            Priority: Critical
>              Labels: p1
>         Attachments: Screenshot from 2017-12-12 21-05-47.png
> 1. Create Share  Product with Accounting Enabled 
> 2. Create a share charge with type 'Share Purchase' ,'Flat' amount $2.
> 3. Create and activate savings account for client which is needed to link 
> with share account
> 4.  Create a share Account application for current date using above product 
> and charge and number of shares issued as 10 , each share price as $0.5.
> > Once you 'Submit' the share application journal entries are created 
> > (including charge) even though share account is not yet approved/activated.
> >Approve the share account and again duplicate jounal entries are created. 
> >If share account application is attached with 'Share Activation Fee' , upon 
> >submission of share account application, if we check 'Transaction Overview' 
> >tab, it shows 'Activation Fee' is received even though share account is not 
> >activated. Same is updated in the database 
> >table,"m_share_account_charge_paid_by". But under the 'Charges' tab, it 
> >shows Outstanding(which is correct).
> The all scenarios can be tested here by modifying application and using the 
> charges 
> 'Share Purchase Fee'  or  'Share Activation Fee'
> https://staging.openmf.org/#/viewshareaccount/5

This message was sent by Atlassian JIRA

Reply via email to