Thanks for the tip Wayne!  (Looks we have a customer showing the same pattern).

We are also experiencing this in Sage 100 Standard (2023) v 7.2.3.0

FYI - We have an open ticket for this: Request Number 8010091262 (Status as of 5/20/2024: Fix Pending)

Can you reply on here if/when you have a response to your ticket? We are experiencing the same issue since we updated and would love to know if this is still being worked on.

Contact Sage support.  There is a Pre-Release fix available if you sign a Pre-Release agreement.

Anyone had any luck fixing this issue?  We just upgraded from Sage 100 2021 to 2024 and ran in to this issue.  We are invoicing about 1000 Sales Orders a day and 98% have a /C comment line at the top.  Any help would be appreciated.

This appears to be resolved in PU1.  If for some reason you can't install PU1 of v2024; then open a ticket with Sage requesting the fix. 
Sales Order  New in Product Update 1

Tax class is missing from tax code no longer appears when changing the Sales Tax Schedule on a
Sales Order Invoice, when the first line on the sales order is /C.

DevID 117076

Thanks for the response.  I can see where it is fixed in PU1 for Sage 300, but we are running Sage 100 and we should have all updates installed.  I started a case with Sage Support and they are working on it for us, but please let me know if you are aware of an update for Sage 100 that addresses the issue.  It's possible that I am missing it.

Thanks

Sage Support got back to me and said the problem has been fixed in update 1 for 2024.  They referenced document # 230609212953310 in the Knowledge Base.  Once I logged in via Customer Portal, I was able to find the document and it gave me a path to download the update.   We will give it a shot tonight and see how it works

Thanks

I have a concern with how Sage handled this patch. I ran into this on 2022.6 and it was only because I was working on updating a customer site who also had payroll and unfortunately decided that "while I was in the system" that I should install the latest supported product update --- 2022 PU6.

The customer did not notice this issue occurring until I installed PU6

Sage opted not to release a product update 7 and instead the Sage 100 2022 last PU appears to be 6 -- which is where the customer noticed the bug.

The only option given to this customer was to sign a waiver for a fix for a supported version of Sage 100 where the bug appears like it could have been introduced by  Sage in 2022 PU6.

I'm confused as to why Sage wouldn't have issued a public patch on this if in fact it was a bug they introduced in 2022.6. Given this experience I've changed my recommendation to customers: 

1. Don't install a PU unless it clearly resolves a known issue that you are experiencing

2. PU won't automatically be released for supported versions

3. Sage no longer appears to be posting fixes to their download portal. It remains to be seen if this will be a permanent policy and, if so, whether all future patches will be "waiver required".