I have opened up my next year, (April 1 - March 31, 2014-15).
When I post a batch in April 2014, the posting journal that prints is the corresponding posting journal number from April 2013.
There are 5 April 2014 batches posted.
The April 2014 data seems to be correctly posted to the accounts,
We had exactly the same issue last year.

Hi Marc:

There are several ways to print the Posting Journal. Does it auto-print after posting? Or are you printing from the "Post" menu? Or, if you are using Ledger 9.1A, are you printing from the batch Inquiry screen?

If you are auto-printing after posting, tell us what the print dialogue shows. Near the top there is section entitled "Year". The correct year should be selected automatically. What are the options and which year is selected?

What version of Ledger are you using?

Hi Bruce
I've checked off the auto-print option, but do not clear the posting journal.
I've also tried re-printing from the post/print posting journals menu selection.
In both cases, 2015 is checked off.
Right now 9.1A (130726). I was going to run the upgrade the other day, but when I did a data integrity check, it detected an error on the "posting journals next year" and stopped at that point. (This was after the batches had been posted)

Hi Marc:

It sounds as if you're doing things correctly.

The next step is to make a backup of your Ledger data (File | Backup), run Data Integrity Check and click on the "Rebuild" button. Usually it can solve the problem but not always. Let us know the results of the "Rebuild". If the process looked successful, run the Data Integrity Check again.

Note: Whenever you run a process like this, there's always a small chance that things will get worse and you will need to restore from the backup. If you are uncomfortable with any of this process, I suggest talking with your Adagio consultant first.

Marc:

From the last upgrade:

The Next Year Posting Journal was not empty when Next Year was created if there had been an improper restore procedure (all GL data files were not deleted before restoring). The Create Next Fiscal Year function now checks for and corrects this condition.

I suspect that upgrading to the current version of Ledger and running the data integrity check rebuild function for Ledger will solve your problem.

Thanks Bruce & Douglas

I tried the re-build at the time I did the data integrity check - it didn't fix the problem, and the next D.I. check stopped at the same point.

I'd be willing to bet dollars to dimes that there is a background file that needs to be deleted so the program can recreate it. We had a similar problem last year with my financial statements, where the sets I had created seemed to have disappeared. When my re-seller came in (& called Softrak Tech support), the fix was quick & easy - delete the file and the program recreated it - all was well.

Hi Marc:

You could try Doug's suggestion of installing the Service Pack dated 2014-02-21 and then trying "Rebuild" again. The Update Note indicates the problem as described by Doug and then says that the "Create Next Fiscal Year" function has been revised to remedy the problem. It's worth seeing if the Data Integrity Check has been likewise revised.

There are a few situations where a file can be deleted and Adagio will happily recreate it with no loss of history but those are the exceptions rather than the rule.