Thanx for the feedback.
1) System backdating would not work because the solution is already
hosted on a remote server.
2) The Redo Loan Functionality is great, however this might not be
feasible because Clients Pay are made to the Bank and the MFI can only
know a client made a payment through a bank statement or when a client
presents a bank voucher to the MFI.
And with this sort of arrangement almost all Loan payments are seen
after the actual date of payment, so this would mean redoing loans all
the time.
In my view if it were possible to release the payment date and meeting
schedule connection so that the error of "Date of transaction is
invalid. It can not be
prior to last meeting date of the customer" does not surface, then we
can have the flexibility to make backdated payments.
On Nov 29, 1:19 pm, Keith Woodlock <keithwoodl...@...> wrote:
> Thomas,
>
> Rather than backdating the system which will work but would not be the
> adivised way of doing this.
>
> In the 'admin' there is a link for some functionality named 'Redo Loan'.
>
> This supports 'taking on a loan and inputting its payments in the
> past'. So if you make a note of all the payments made on the existing
> loan and the one missing one from July, you can close off/cancel
> existing loan and create another loan using the 'redo loan'
> functionality and use all the same payment information + the one
> missing payment to bring the loan upto date.
>
> regards,
> Keith.
>
> On Tue, Nov 29, 2011 at 6:44 AM, Pradeep Ku. Panda
>
>
>
> <pradeep....@...> wrote:
> > Hi,
> > By using the Apply Payment tab. You can able to enter the data on an
> > earlier date.
>
> > On Tue, Nov 29, 2011 at 11:53 AM, Thomas (Uganda) <ndal...@...> wrote:
>
> >> Hi Guys, thanx for the gr8 work.
>
> >> I need to input a loan payment made on an earlier date. eg If a loan
> >> payment was made on 27th July 2011 to the Bank, and i realises that
> >> today on 26 November 2011 (No other payment were med in between), so i
> >> need to input this loan made on 27 July 2011. How can i do that.
>
> >> Currently an error of 'Date of transaction is invalid. It can not be
> >> prior to last meeting date of the customer.' appears.
>
> >> Anyway i work around this?
>
> >> Thanx
>
> >> ------------------------------------------------------------------------------
> >> All the data continuously generated in your IT infrastructure
> >> contains a definitive record of customers, application performance,
> >> security threats, fraudulent activity, and more. Splunk takes this
> >> data and makes sense of it. IT sense. And common sense.
> >>http://p.sf.net/sfu/splunk-novd2d
> >> _______________________________________________
> >> Mifos-users mailing list
> >> Mifos-us...@...
> >>https://lists.sourceforge.net/lists/listinfo/mifos-users
>
> > --
> > Regards
> > Pradeep Panda.
>
> > ------------------------------------------------------------------------------
> > All the data continuously generated in your IT infrastructure
> > contains a definitive record of customers, application performance,
> > security threats, fraudulent activity, and more. Splunk takes this
> > data and makes sense of it. IT sense. And common sense.
> >http://p.sf.net/sfu/splunk-novd2d
> > _______________________________________________
> > Mifos-users mailing list
> > Mifos-us...@...
> >https://lists.sourceforge.net/lists/listinfo/mifos-users
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Mifos-users mailing list
> Mifos-us...@... href="nethttps://lists.sourceforge.net/lists/listinfo/mifos-users" target="_new">nethttps://lists.sourceforge.net/lists/listinfo/mifos-users
|