You could write a script for this (PreTotals or PreWrite event is what I'd recommend).

We've also set up emailed alerts (using 3rd party report automation software) to catch these at the SO stage.

Thank you! Looks like I'll be learning some script writing in Sage here soon then... Are you by any chance able to provide an example of that script?

I tend to encourage DIY, providing guidance instead of full scripts.  There are lots of code snippets on Sage City if you look.

For this, you'll be starting with a header object, so you open the Lines and loop through them, looking for your error condition (ignoring things like charge codes and comments which will not have unit price values), then use the Sage MessageBox method to present your message to the user.  (Avoid use of the VBScript msgbox method which doesn't work with certain versions of Sage 100). 

Add a filter to suppress the pop-up when there is no user interface (so you don't run into issues with integrated programs, or VI imports...).

I tend to encourage DIY, providing guidance instead of full scripts.  There are lots of code snippets on Sage City if you look.

For this, you'll be starting with a header object, so you open the Lines and loop through them, looking for your error condition (ignoring things like charge codes and comments which will not have unit price values), then use the Sage MessageBox method to present your message to the user.  (Avoid use of the VBScript msgbox method which doesn't work with certain versions of Sage 100). 

Add a filter to suppress the pop-up when there is no user interface (so you don't run into issues with integrated programs, or VI imports...).

Understood, thank you.