I am running Ledger 9.0D(111017) and Multicurrency 8.1B(110311)
If I create the new fiscal year and then post a journal entry in the old year, it results in a Data Integrity warning as follows:
"Account[4500- ] fiscal year[2012] opening balance of $703,652.94 does not match total of all currencies 707,537.72" Then at the bottom of the Integrity Check screen, an additional message says "Application Integrity Phase..2 warnings found" (It ways 2 warnings because the error I quoted is printed twice) Account 4500 is my retained earnings account. If I do not create the new fiscal year, I can post the journal entries with no integrity errors. My question is twofold:
1. Do you know what is causing this to occur and
2. What is the significance of the warning? (it is only a warning, not an error) If I ignore it and continue on, is something nasty going to happen to me down the road?
As always, much obliged for your help.

Barry:

This is a known issue that several of my clients have been experiencing. Not sure what progress Softrak has made with getting this resolved.

Hello Barry,

I think Doug is confusing this with a problem fixed long ago when people changed the acceptable currencies for the retained earnings account after creating a new year. This was fixed long ago.

Could you send me a backup of your GL that exhibits the problem? Thanks.

Andrew:

I should have mentioned: different bug same error or possibly the same bug just not fully fixed. I need to dig up the details and get them to you.

Hi Doug,

Well, sadly we have had no data from Ken and we have no knoowledge of what might be causing this problem. Since Ken has a dataset that exhibits an issue, and we have had not other reports, perhaps we can wait for him to provide the data?

Hi Ken,

Thanks for sending us the data so that we could track down a problem that has existed in Adagio Ledger since its first ship 4 or 5 years ago.

You can resolve the problem by unposting the batches you have posted since creating the new year, changing the Retained Earnings account to "Accept all currencies", and then posting the batches again.

We will force the Retained Earnings account to accept all currencies in a Multi-Currency site in the next Service Pack to Adagio Ledger.

Andrew:

My apologies for the delay in this response:

Further to the bug fix done a year ago (April 2011) and the databases that were repaired at that time:

If you don’t still have copies of the databases from that time I may still have them. You can create an error in these databases using the following steps/conditions:

1. Retained Earnings is multi-currency.
2. Next fiscal year is open.
3. Post an expense or income transaction to the current year.

Personally I don’t believe the MC should be turned on for RE but at some point in the past we are forced to, otherwise the year end would not run. Currently MC is not required for RE and if not turned on this integrity error does not occur. As per your post if you propose to go back to this model (force MC to be on for RE) then you need to resolve this problem.

Given that the specific currencies assigned to RE are the currencies in use I'm unclear how a change to All currencies resolves the problem.

Unless I am mistaken, you will discover that your client has restricted the RE account to accept specific currencies, and they have added a new one to their chart without adding it as an accepptable currency to be posted to the RE account.

Hence the requirement to permit all (source) currencies be posted to the Retained Earnings account.

I'm prepared to be proven wrong.

I'll have to check but know I see your arguement for wanting to force 'All currencies', though I will stick to my arguement that MC should never be turned on in RE (as RE should only be in home currency given that the transaction source currency is irrelevent to RE).

I agree it should be an all or nothing proposition.

The restriction on RE account to, say, only CAD and USD, still doesn't explain the appearance of that error in the database, having only these two currencies.

It's the restricition to specific currencies that is causing the problem.

The solution is simple. Unpost the batches. Turn on "Accept all currencies on the RE account. Post the batches again.

I would suggest to limit the user's choice of MC settings for RE accounts in the future releases.

That change has already been made and will be in the next Service Pack / Hot Fix.