What must be set up to ensure a worktag is entered on every customer invoice for a specific revenue category?

To ensure that a worktag is entered on every customer invoice for a specific revenue category, maintaining related worktag usage is the correct approach. This functionality allows organizations to specify which worktag can be associated with specific transactions, like customer invoices. By configuring related worktag usage, users can effectively enforce the requirement of inputting a particular worktag when processing invoices related to that specific revenue category.

Custom validation could indeed be a tool for checking the presence of a worktag, but it does not enforce the entry of a worktag directly during the transaction process. Instead, it would operate as a secondary check, which does not guarantee compliance in real-time as invoices are being created.

Adjusting worktag settings might involve modifying how worktags are utilized but does not specifically address this requirement for customer invoices in a targeted manner. Thus, related worktag usage is a more comprehensive solution to ensure that the worktag is systematically recorded for each relevant transaction.