We recently updated our GL (9.3B 210527) and AP (9.3C (211207).
I have tried to post an AP batch with a typical monthly transactions and it rejected all of my transactions with a tax distribution entry. The error message:
"Unable to post batch 128 entry 1: invoice 211103ADOBE1 for vendor VISAGA. Detail tax GL Account/Department invalid or inactive."
The rejected transactions are straightforward, I think!

Any thoughts on what might be causing this error?

Thanks
Karin

Hi Karin,

Look at the batch listing, and check each account for invoice 211103ADOBE1 for vendor VISAGA. Make sure each account exists in your Ledger and is active.

The large batch was a combo of VISA transactions, some invoices had tax included, some not. Those that did not have the tax account code were posted properly. All invoices that included the tax account code were rejected. This account code is our main code used in all of our typical transactions and is set to active in the GL.
I attempted a very simple two line invoice with the tax code included and it was rejected with the same message as above.
Any other options?

Karin:

This type of problem is best solved by having hands on the database. Your Adagio consultant should be able to figure this out fairly quickly.

Thanks Doug, was hoping to resolve here but I agree, it's probably best for her to have a virtual peek!

Update:
Wanted to let everyone know that the issue related to distribution codes we had set up as upper and lowercase (HST and hst). The latest AP update somehow caused these distribution codes to no longer work. Work around was to create a new distribution code H13.

This was not a program problem. The problem is in the Distribution codes. The 2 HST Distribution codes were set to Purchase but... they both have a Department in the Tax Department field. At some point, they were modified. The AP message was correct. The Account & Department assigned to the Distribution code are invalid.

Thanks for the clarification Tech Support.
These distribution codes have been this way for at least 7 years and not updated at any time. It's possible they weren't set up properly from the beginning and the latest update caused a problem.

Really appreciate the great advice provided on this forum!

Often an upgrade will start checking things that were not checked before, though if these Distributions were previously used then error should have been showing up when the transactions arrived in GL.