The existing Customer approval workflow is a valuable tool to ensure that changes to critical customer fields (such as payment terms) are properly reviewed and approved. However, this workflow only applies after the customer record has already been created.

In our case, the most sensitive point is actually during the initial creation of the customer, especially when a prospect is converted into a customer. At this stage, key fields like payment terms, credit limits, and methods of payment are defined – but these values can currently be entered and saved without any approval process.

Suggested improvement:

Enable the Customer approval workflow (or a similar validation process) to be triggered during the initial creation of a customer.

For example:

• Allow users to convert a prospect to a customer.
• Require approval for specific fields (same as in the existing Customer approval workflow) before the record is fully active or used in transactions.
• Optionally allow configuration to define which fields or scenarios should require approval at creation.

Business impact:

This ensures that all relevant customer master data is validated before being used in downstream processes, reducing the risk of incorrect financial conditions, duplicate records, or manual rework later on.