Because the GL is still on 2015.  Close the year, post the error batch.

Jay Thx for prompt response!

I can not close Fiscal 2015 becos we are still in Per 10. We still have two months May/June to enter in 2015. Yet July vouchers also need to be paid.

We should be able to work in both periods together.

Then don't post any 2016 subledger batches when they get to the GL until 2015 is closed.

But 2015 & 2016 vouchers are generally all mixed together. As the bills come in, they get entered with the right date, whether current year or next year.

Isn't there a way where the two fiscals work together and are "Date" sensitive for transactions?

Really appreciate your help/guidance.

Ignore all GL error batches until the new year is created.

You have two options:

1) Create the new fiscal year in the GL and make sure that the allow posting to prior year is select in the GL Options.  This will allow you to do entries for either year and they will post to the correct year based upon their dates.

2) Don't create the new year and leave the error batches open in the GL until you create the 2016 fiscal year and then go back on post them

If you do option one make sure all other prior years are locked down so you can't post them by mistake.  I have many clients that do option 1, you just have to be careful when entering the dates.

Thanks Bernie & Jay,

I can't go with option 1 because its too early. We just closed Per 10 with May/June entries & Audit still pending.

I can't go with option 2 because it will create too many unmanageable "error" batches.

I guess I will have to go with a third option. Keep all next fiscal year transactions pending as far as possible with a distinct possibility of the AP clerk losing vouchers/invoices and book only extremely necessary vouchers of next fiscal Yr and keep error batches to a minimum. This messes up the normal process of booking voucher invoices as they come in, irrespective of the date or period and the expenses being tracked in the right bucket in GL in real time.

However, this sucks! Sage 300 should work like real life accounting. I hope the re-designers are looking.

Thanks for all your help.

Anup Gupta

1. This will never be changed or re-designed, it's a core part of the G/L module design.  

2. Error batches are quite manageable, you ignore them.  

3. In 16 years of supporting this software, none of my clients have ever complained about this.  You need to change your expectations.

This will never be changed, it is NOT a simple programming fix.

Ha Ha,, Jay!

We should not be escapists lowering expectations rather than finding solutions. That's a consultant's job!

I have been in the same field for 27 years supporting Sage and MS products. There are other SW that do not have this anomaly.

And its a simple programming fix!

In Periodic Processing, instead of Creating GL Batches by "Posting Sequence", create it by DATE or PERIOD.

I know it can be done. Please don't lower YOUR expectation. Ask Sage and thou shall receive.

With kind regards,

Anup

Ha Ha,, Jay!

We should not be escapists lowering expectations rather than finding solutions. That's a consultant's job!

I have been in the same field for 27 years supporting Sage and MS products. There are other SW that do not have this anomaly.

And its a simple programming fix!

In Periodic Processing, instead of Creating GL Batches by "Posting Sequence", create it by DATE or PERIOD.

I know it can be done. Please don't lower YOUR expectation. Ask Sage and thou shall receive.

With kind regards,

Anup

This will never be changed, it is NOT a simple programming fix.

It makes no sense.

Anyway you can add your opinion here:

www5.v1ideas.com/.../Sage300ERP

Creating the new year in the GL does not stop you from working in your current year and prior year at the same time. Why are you reluctant to creating the new year in the GL? It will allow you to post your batches and get the best of both worlds.

Anup I think you are completely missing the point.  What is the problem with posting in 2015 and 2016 at the same time?  In fact Sage 300 is probably the most flexible you are ever going to get in this regard and it is absolutely NOT an anomaly or software problem.