Category: (4) eTOM Process Type
Process Identifier: 1.6.12.3.2
Original Process Identifier:
Maturity Level: 3
Process that handles payments which substantially deviates from the cycle norm, insofar it would falsely trigger collections. “No treat” handling process removes a specific business party or Wholesale Partner from the automated process and logic due to the exceptions it would create operationally.
Process to accommodate recurring (non-monthly) payments. Explains how a CSP will differentiate wholesale business who pay quarterly from those who pay monthly. This prevents the customer from going into collections after the standard allotted time. “No treat” would for example be used where a business party or Wholesale Partner have made a special temporary agreements which are not handled by the automated process by configuration or adaption. Like Partial Payments in advance or “Short” Payments : Under normal conditions “Short Payments” will automatically fall into collections, but with No treat, an contracted obligation allows exceptions “for no treatment”.
This was created from the Frameworx 16.0 Model