mifos
  1. mifos
  2. MIFOS-2715

Configuration setting: Pre-populate the amount due field with the next payment (even if the date is before meeting date)

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Trivial Trivial
    • Resolution: Unresolved
    • Affects Version/s: Release 1.4
    • Fix Version/s: Unscheduled
    • Component/s: Loan Account
    • Labels:
    • Team:
      Core

      Description

      Currently, with enda operations, the clients are often paying before the meeting date set for the client (ie, they don't have center meetings at enda, rather, the meeting date is used as a "pay by this date", kind of like regular commercial loans).

      The issue is that when the cashier is going through mifos and clicking on apply payment, the amount shown on the screen is 0 since its before the clients meeting date.

      enda would like this to pre-populate with whatever is the next payment amount due, so the cashier can just click through the screen quickly.

        Activity

        Hide
        Ryan Whitney added a comment -

        Scenarios that need to be answered

        1. If the client has paid early on their next payment, will it auto-populate with zero indicating they are a head or just populate with whatever is the next payment amount.

        2. How does it handle early partial payments

        3. How does it handle late payments and late partial payments?

        Show
        Ryan Whitney added a comment - Scenarios that need to be answered 1. If the client has paid early on their next payment, will it auto-populate with zero indicating they are a head or just populate with whatever is the next payment amount. 2. How does it handle early partial payments 3. How does it handle late payments and late partial payments?
        Hide
        Kay Chau added a comment -

        Answers

        1. No, it should populate to next amount

        2. it should pre-populate to rest of payment due at next repayment

        3. It should pre-populate to everything that's overdue plus next payment.

        Basically in all scenarios, just take next payment that hasn't been paid in full and pre-populate with that amount.

        Show
        Kay Chau added a comment - Answers 1. No, it should populate to next amount 2. it should pre-populate to rest of payment due at next repayment 3. It should pre-populate to everything that's overdue plus next payment. Basically in all scenarios, just take next payment that hasn't been paid in full and pre-populate with that amount.
        Hide
        Kay Chau added a comment -

        Scenarios

        1) User has $50 due for next payment - none of it has been paid. Pre-populate field with $50.
        2) User has a payment of $50 due next week, but has paid $20 of it. When Mifos user goes into Mifos, they should see pre-populated amount of $30 due for next payment.
        3) User has paid off next 2 weeks of $50 each ($100 total). The following payment due is $50 in 3 weeks. $50 should be pre-populated amount.
        4) User is overdue, and did not pay last week's installment of $50. They have now $100 due next payment - $50 from last week, and $50 this week. Pre-populate with $100. <- this is current behavior.

        Show
        Kay Chau added a comment - Scenarios 1) User has $50 due for next payment - none of it has been paid. Pre-populate field with $50. 2) User has a payment of $50 due next week, but has paid $20 of it. When Mifos user goes into Mifos, they should see pre-populated amount of $30 due for next payment. 3) User has paid off next 2 weeks of $50 each ($100 total). The following payment due is $50 in 3 weeks. $50 should be pre-populated amount. 4) User is overdue, and did not pay last week's installment of $50. They have now $100 due next payment - $50 from last week, and $50 this week. Pre-populate with $100. <- this is current behavior.

          People

          • Assignee:
            mifosdeveloperqueue
            Reporter:
            Ryan Whitney
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: