The classes register is very important for system management control, since it makes possible to control company finances without the direct participation of the Accounting department in the automatic generation of bills. It is by classes that the system classifies bills payable and receivable, depending on the operation.

Classes can be defined as detailed or summarized, allowing the aggregation of financial reports based on summarized classes.


The classes register has two view modes:

  • Default: displays class data.
  • Structured: displays the screen split into two sections: one with the class tree and the other with the class data.


Important:

Classes classified as summarized cannot be added to financial routines (using [F3]).

This type of class can only be added to the Classes register.

Classes allow classifying the origin of revenues and expenses, grouping the transactions with common characteristics, such as:

  • payment of suppliers;
  • collections from clients;
  • overhead;
  • payments of utilities.

To allow management control, classes must be entered in the Budgets, Inbound Documents, Sales Orders, Outbound Documents routines and all the financial transactions, making it possible to follow up budgeted and actual amounts.

To simplify the identification of classes in systems queries and reports, a mask must be defined. The mask is the format for presenting the identification codes of classes in queries and reports provided by the system.

The MV_MASCNAT parameter defines this mask, i.e., the amount of levels and characters defining the code format.

The feature for structuring class code in levels allows the classification of each financial transaction origin and destination at each level.

Example:

If the parameter content is 242, the code is treated in three levels:

  • 1st level with two digits - it identifies the department expense
  • 2nd level with four digits - it identifies the department
  • 3rd level with two digits - it identifies the cost center

Example: 99.9999.99

For better arranging classes, we suggest that revenues and expenses begin with different codes, simplifying their grouping and totalization in queries and budgets.

Example:

10.XXXX.XX - Revenues

20.XXXX.XX - Expenses

By creating categories, it is possible to include subcategories, since there may be different sources of revenue or expense. This possibility allows that, when querying bills payable or budgets, the balances be totalized by category and, at the end, be grouped from the main (parent) category.

Example:

  • 20,100 - Revenues - Total
  • 20.1000.01 - Revenues - Maintenance Services
  • 20.1000.02 - Revenues - Equipment Sales

Bills Payable Number

Name

Class

Due date

Amount

54661

Panasonic do Brasil

20.1000.01

04-Jun-04

5,000.00

Total - 20.1000.01




5,000.00

54662

Samsung do Brasil

20.1000.02

04-Jun-04

2,000.00

Total - 20.1000.02




2,000.00

Total - 20.1000




7,000.00

54663

Panasonic do Brasil

20.1010.01

03-Jun-04

10,000.00

Total - 20.1010.01




10,000.00

54664

Samsung do Brasil

20.1010.02

03-Jun-04

3,000.00

Total - 20.1010.02




3,000.00

Total 20.1010




13,000.00

Total - 20




20,000.00

Important:

The MV_IRF, MV_ISS, MV_INSS and MV_FORINSS parameters indicate which classes are to be used for applying taxes when implementing bills receivable and bills payable. Default is IRF, ISS, INSS and INSS, respectively.


If the Schedule routine and the Adapter EAI are configured, it is possible to integrate TIN (TOTVS Real Estate Enterprising) and Protheus to send and receive XML files, according to the XSD ractified by TOTVS®.



RM Integration:

This routine features integration with RM Classis Net.

For technical details on Procedures of Deployment and Use, Table Synchronization between Databases, and Parameterization for Generation, refer to the Manual of Integration Protheus x Classis, available at the TDN portal.

Also check the information about Education Management.

The MV_RMCLATX parameter allows the generation of tax bills from RM Classis Net native bills, according to the pattern present in the Financials module. In the Customer register, you must configure a client which allows the collection of taxes, as per the default usage of Microsiga Protheus®.



Procedures

Adding classes:

1. In Classes, click Add.

The system displays the routine's inclusion screen.

2. Fill out data according to field help instructions.

3. Fields in this routine are self-explanatory, but check Main Fields and Controls topic.

4. Check data and confirm inclusion.



Procedures

Adding classes:

1. In Classes, press [F12] to select the register's display method.

2. A window appears with options for selection: Classic and Structured.

When selecting Structured, exit and enter the routine again.

3. Fill out data according to field help instructions.

4. Fields in this routine are self-explanatory, but check Main Fields and Controls topic.

5. Check data and confirm inclusion.



See Also