I have had several situations where an account number no longer exists but a credit note is issued that was posted to the old account. The batch posts fine in invoicing (which it shouldn't do!) and it isn't until I try to post in the GL that I get the error.

As well, I have had invoices entered and the GL account number has been left blank and it posts fine in invoicing with no errors.

According to the help menu in Invoicing, posting should be halted and the invoice must be corrected before you are able to post. This isn't happening. I can't find a place in invoicing where you click field verification. It is clicked on in AR for all our users.

We are using Invoicing 8.1B. Your help would be appreciated.

Hi Vicki,

Indeed if an invoice was posted, then the GL account was deleted in Ledger, then a credit note was created from the history invoice, it is possible to post it without account verification. If the invoice detail was edited, the verification of the invalid GL account would occur, but only if the option to allow editing of the Revenue GL account on items is allowed.

I cannot save an item detail on an invoice or credit note with a blank GL account with Invoices 81B - verification fails immediately.

It is possible that in previous versions, Field Verification was disabled and not used. But you can no longer disable Verification in Invoices 81B. However, as indicated above, you have to visit the field in order to activate the verification.

For now, you'll have to re-direct the GL batch entry to a different and existing Ledger account. We'l see what we can do on our end.

As for the issue with creating a CN from history that was assigned to an account that no longer exists, do I select "edit new items on documents" under file/options? If this box is ticked, will this cause the error to occur before the CN is posted in Invoicing?

I should have clarified that in the other issue with being able to post the invoice with no account code assigned only happens when we use our MISC item code that lets us pick which account we want it to go to. I still don't understand how the subledger can let you post when part of the entry isn't assigned to a GL account.

Vicki:

The issue of allowing blank, or incorrect, GL codes in subledgers stems from the fact that those programs can be run without access to GL data (such as on a remote system). In this case, checking for GL codes would cause the program to stop working!

Isn't that why there should be a field verification option the same as there is in AP so that if there is no account number or it's invalid it won't let you post?? Can I get a resonse from softrak support for my above posting.

Thanks so much!

Hi Vicki,

As our Technical Support department mentioned, you have to visit the field for it to be "verified".