|
|
|
MySF Administrator
Group: Administrators
Last Login: 17/05/2010 6:31:15 PM
Posts: 464,
Visits: 632
|
|
Hi,
We have tried to replicate the same problem on the current version of the software (6.0.1). All tests have worked fine on the files we have used in tests. However, when using your fund some transactions did not show on the bank rec, exactly as per your previous postings and emails. Specifically, they are missing from the bank reconciliation reports.
We have not been able to find why this happens with your fund. However, this will not affect the accounting within the software and will not impact on the accuracy of calculations.
Regards,
MySF
|
|
|
|
|
Master Member
Group: Forum Members
Last Login: Today @ 3:41:34 AM
Posts: 107,
Visits: 1,358
|
|
Hmmm,
Considering you said last February (when we were at version 3.2.2):
We have tested the data you have sent through and have also received mixed results when recalling past bank reconciliations. At this point it looks like the error is likely to be display level only and data is not affected.
Unfortunately changes to this area of the software will not be included in the next update, but will be included in the following one.
I find it disappointing and a little worrying that you can still see this problem with my fund file but you say:
We have not been able to find why this happens with your fund.
Whilst I accept that:
this will not affect the accounting within the software and will not impact on the accuracy of calculations.
The fact remains that bank reconciliations, together with other reports generated by MySF, are used to check that we have put all our info in correctly - we rely on them to be accurate and complete.
This error was one that I noticed - and now am aware of - however when sending my MySF file off for audit I had to advise the auditor that the problem was there but that the transactions were OK - just not to rely on viewing the reconciliations to check them.
More worrying is that if I have THIS problem (apparently unexplainable & unsolvable) - how do I know that I can rely on the reporting aspects of MySF - see my other post regarding distributions not showing up when filtering transactions by distribution - again the problem is not with the actual info in the fund but with the display/reporting of the info - but we need to be able to rely on this stuff.
Back to this specific problem - can you tell if it is just a problem with the previously entered info or is it ongoing with my fund file - ie if you enter some new transactions into my fund file and then do a new reconciliation does the problem persist into the new reconciliations.
More questions come to mind but I'll stop at that for now 
Regards,
Neil H.
|
|
|
|
|
MySF Administrator
Group: Administrators
Last Login: 17/05/2010 6:31:15 PM
Posts: 464,
Visits: 632
|
|
Hi,
When testing on 3.2.2 we did get mixed results. This meant that some reconciliations showed up as expected and others were missing transactions. Testing on the latest version also showed up similar results, in that some transactions were excluded.
The specific reasons for the exclusions appeared to be due to a failure in the date filtering, meaning that some transactions were excluded because the report filter saw them as being outside the specified date range.
The same tests ran without problems on other funds. For this reason we are unlikely to change that filter at the moment.
Regards,
MySF
|
|
|
|
|
Master Member
Group: Forum Members
Last Login: Today @ 3:41:34 AM
Posts: 107,
Visits: 1,358
|
|
Hi,
I am finding this very confusing.
I can accept that the problem is with the date filtering - in fact there seems to be other problems with the filters eg my other post regarding distributions not showing up when filtering transactions by distribution.
It seems to me that any filtering problem has to be either:
a) a problem with the filtering software, or
b) a problem with the data being filtered
If I understand you, you are saying because you cannot reproduce the problem with other data files (just my fund file) then you rule out a) and assume the problem is b).
However, I have some problems with this:
- the data is generated by MySF (not imported from some other source)
- whilst I can see that there could have been some event which corrupted some data, the behaviour of the reconciliation reporter does not seem to gel with this -
- what seems to be constant is that for any reconciliation where some transactions are not displaying it is always the last transactions which DO show and the earliest transactions which DON'T show.
- at any point the transactions reported and missing are consistent, ie running and rerunning the reports gives the same results UNTIL new transactions and reconciliations are processed then more transactions generally drop off some of the "view past reconciliations" reports.
- it is the actual process of running a reconciliation which creates problems with other past reconciliations (from different bank accounts) - see my post of 14/02/08.
So while the problem may indeed be in the data being filtered - it is running the bank reconciliations which are causing/changing these problems.
Whilst I appreciate the problems of fixing unreproducible faults, the fact is you can see and reproduce this fault in my fund file. I have a considerable amount of time and effort invested in my MySF fund file and I do not expect to be told, in effect, no one else is having this problem - live with it!
Regards
Neil H.
|
|
|
|
|
MySF Administrator
Group: Administrators
Last Login: 17/05/2010 6:31:15 PM
Posts: 464,
Visits: 632
|
|
Hi,
Additional testing has revealed the cause of this problem and I am happy to report that this is now fixed. You should find that your bank reconciliations show correctly after the next update.
The problem was in the filtering of the information, not the information itself.
The 'past bank reconciliation' report was set to display all transactions for the given account from the start date of the financial year through to the date of the bank rec. So the date range for what was to be included in the report was set initially as the start of the financial year through to the date of the bank reconciliation. In the next step the software tried to find any previous bank reconciliations for the same account. It then reset the start date of the date range to the date of the most recent bank reconciliation on this account.
The last step of the above is where the problem occurred. When looking for the previous reconciliation on a given bank account the software sometimes picked up the wrong bank reconciliation and therefore picked up the incorrect bank reconciliation date. This meant that the start date was set to an incorrect date, which in turn caused the date filtering to reject lines that should have been included in the report.
The above also explains why you saw some of the problems mentioned, such as more and more transactions being excluded from these reports as more bank reconciliations are processed.
Regards,
MySF
|
|
|
|
|
Master Member
Group: Forum Members
Last Login: Today @ 3:41:34 AM
Posts: 107,
Visits: 1,358
|
|
Hi,
That's really good news
Thank you for tracking the problem down.
When are you expecting to release the next update?
Regards,
Neil H.
|
|
|
|
|
MySF Administrator
Group: Administrators
Last Login: 17/05/2010 6:31:15 PM
Posts: 464,
Visits: 632
|
|
Hi,
We intend to issue the next update (6.0.2) on Monday.
This will include this fix, a change to the member positions report, an adjustment to the split of taxes during the year end as well as a change to how transactions are generated for carried forward losses.
Regards,
MySF
|
|
|
|