Histórico da Página

To determine the client's credit limit rules, the following fields must be analyzed:

• Risk
• Credit Limit
• Secondary Credit Limit
• Credit Limit Due Date
• Credit Class
• Credit Limit Currency
• Parameters Used

Risk

Risk level in approving the client's credit in sales orders, in which it may have different contents:

• Risk A - it means there is no risk for sales, that is, the sales order is not blocked, except if the due date of the credit limit has passed.
• Risk B - this situation depends on the content of the MV_RISCOB, which indicates the number of acceptable overdue days in the payment of client bills. Additionally, the credit limit amount and the credit limit due date of the client.
• Risk C - this situation depends on the content of the MV_RISCOC, which indicates the number of acceptable overdue days in the payment of client bills. Additionally, the credit limit amount and the credit limit due date of the client.
• Risk D - this situation depends on the content of the MV_RISCOD, which indicates the number of acceptable overdue days in the payment of client bills. Additionally, the credit limit amount and the credit limit due date of the client.
• Risk E - it means there is a great risk in sales, that is, the sales order will always be blocked.
• Risk Z - SERASA integration, credit clearance by third-party software integration.

In this case, when the sales order is released for billing, it remains blocked until the system, via SERASA integration, receives the instruction for clearing it.

This feature is available due to a partnership between TOTVS and SERASA, which focuses on simplifying client access to the SERASA database, querying its information and updating it, as per the agreement with SERASA.

To update clients' financial information (payment habits, purchasing profile, overdue obligations and obligations to fall due) in the SERASA database, the SERASA - Relato routine must be run.

For automatic credit clearance, the RELATO product query service must be configured using the IP23 Data String, available in Protheus.

Practical Application

Considering that the Risk field in a client's register is defined as A, sales order of any value are not blocked during clearance because clients classified as Risk A have sales restrictions and all their orders are automatically cleared for credit.

In the case of a client classified as Risk E, the orders are always blocked for credit during clearance, regardless of the value.

...

Example:

Parameters with the following content defined:

• MV_RISCOB = 30 (tolerance of up to 30 days of overdue bill payment)
• MV_RISCOC = 20 (tolerance of up to 20 days of overdue bill payment)
• MV_RISCOD = 10 (tolerance of up to 10 days of overdue bill payment)

When the client is classified as Risk B, his sales orders are not blocked for credit even if there are bills receivable overdue for up to 30 days from the actual due date. If this period is exceeded, they are blocked.

The same concept is followed for clients considered as Risk C and Risk D. The parameter content and the number of days of overdue payment of bills are always checked.

Credit Limit

In the Credit Limit field, the total credit limit of the client is determined and this value is related to the Currency 1 field (national currency).

Secondary Credit Limit

This concept is applied when the user wants to control differentiated credit limits for some bills, such as for invoices and checks.

Example:

The primary credit limit of a client may be determined to be 1000.00 and the secondary limit to be 500.00. In this case, if the client owes 800.00 in invoices and 600.00 in checks (open bills), his/her credit is not approved, since the secondary credit limit was exceeded.

• To handle the Primary Credit Limit and Secondary Credit Limit, configure the Update Trade Notes Balances field of the bills types register, defining the transactions to be controlled by the primary or secondary limit, according to the bill type.
• Bill types not registered in this file are controlled by the Primary Credit Limit field.
• All bill types to which this control applies must be registered in the Types of Bills routine.

Limit Due Date

The Limit Due Date field determines the due date of the client's credit limit, which is directly related to the Credit Limit and Secondary Credit Limit fields.

Credit Class

Evaluation by credit class allows defining a value limit for invoicing per sales order of the client. This analysis compares the order value to the Class defined for the customer and the parameter content relating to the class (MV_PEDIDOn).

The system performs the order's credit analysis considering the rules defined for the risk level and credit limit due date as well.

The credit class depends on the parameters' contents:

• Class A - MV_PEDIDOA
• Class B - MV_PEDIDOB
• Class C - MV_PEDIDOC

Practical Application:

Parameters with the following content defined:

• MV_PEDIDOA = 10000
• MV_PEDIDOA = 5000
• MV_PEDIDOA = 3000

Considering that a client's register has the Class field defined as A, the Credit Limit field as R$ 10,000.00 and Credit Due Date as 31/12/2005, a sales order with the estimated value of R$ 5,000.00 is not blocked for credit during clearance because its value is lower than the maximum limit determined in the MV_PEDIDOA parameter.

In the case of another client defined as Class B, with the same credit limit/credit due date (R$ 10,000.00 - 31/12/05), a sales order with an estimated value of R$ 6,000.00 is blocked for credit during clearance, since its value is higher than the maximum limit defined in the MV_PEDIDOB.

• It is important to enter the Credit Limit and Credit Due Date fields.
• If the client risk is indicated, it always has priority over the credit class or credit due date.

Example:

If the client risk is defined as A and the order value is higher than the class defined for the client, or the credit limit is exceeded, the order is not blocked for credit, since there is no restriction for Class = A.

...

Credit Limit Currency

The CL Currency field is used for determining the hard currency for controlling credit limits and their respective balances. If it is not indicated, the currency indicated in the parameter MV_MCUSTO is used.

Practical Application

If the Credit Limit Currency field is defined as 1 (national currency), the values Currency 1 and Credit Limit are used for performing the client credit analysis.

On the other hand, if the Credit Limit Currency is defined as 2, the values Currency 2 and Secondary Credit Limit are used for performing the client credit analysis.

Parameters:

...