Content

Objective

The Natures work as classifiers of financial operations payable or receivable, being the case that, in accounts payable situations, they offer control of the process without direct collaboration of accounting. They are also responsible for defining the tax withholdings calculation.

You must previously group the Natures in accordance with the operation (payable or receivable) with the aim of making it easier to filter data in queries and reports. In this register, controlling management data involves the following routines:

Budgets.
Payable and Receivable Bills.
Incoming Document.
Sales Orders.
Outgoing Documents.
Financial Transactions in general.

Thus, the Natures Register is important for management control and for automatic generation of bills. They can be classified as detailed or summarized.

You can use natures to classify the origin of revenues and expenses, grouping the transactions with common characteristics. For example:

Payment of suppliers.
Receipt from customers.
General expenses.
Payments of utilities.

Note

To make it easier to identify the natures in system queries and reports, you must define a mask that, in fact, is the format for presenting the nature identification codes. In this case, you can use parameter MV_MASCNAT to set the number of levels and characters that define the format of the code; that is, at each level you can classify the origin and destination of each financial transaction.

Examples:

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

1st level with two digits: identifies the expense of the department.
2nd level with four digits: identifies the department.
3rd level with two digits: identifies the cost center.

99.9999.99

To better organize natures, you can set revenues and expenses to start with different codes, simplifying their grouping and totalization in queries and quotations.

XXXX.XX – Expenses.
XXXX.XX – Revenues.

By creating categories, you can add subcategories, as there may be different sources of revenues and expenses. 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.

100 - Revenues – Total.
1000.01 – Revenues – Maintenance Services.
1000.02 – Revenues – Equipment Sales.

Bills Payable Number	Name	Nature	Due date	Value
54661	ABC of Brazil	20.1000.01	04-Jun-16	5000.00
Total - 20.1000.01				5,000.00
54662	DEF of Brazil	20.1000.02	04-Jun-16	2000.00
Total - 20.1000.02				2,000.00
Total - 20.1000				7,000.00
54663	ABC of Brazil	20.1010.01	03-Jun-16	10000.00
Total - 20.1010.01				10,000.00
54664	DEF of Brazil	20.1010.02	03-Jun-16	3000.00
Total - 20.1010.02				3,000.00
Total 20.1010				13,000.00
Total - 20				20,000.00

See below an example of related use: Type of Nature, Parent Code and Apportionment in Multiple Natures.

Generating an accounts receivable bill:

Generating a accounts payable bill:

Note

Parameters MV_IRF, MV_ISS, MV_INSS and MV_FORINSS indicate the natures used when applying taxes in the deployment of bills payable and receivable. Default is IRF, ISS, INSS and INSS, respectively.

Related search: Parameter MV_NATSINT in configurator - Field Nature Type in Nature Data.

Mental Map

In this diagram, the data refer to the features of the routine:

In the main page of the routine, the following options are available:

Important

From version 12.1.27 onwards, the option Edit gains a new function: that of replicating the summarized nature of the Rural Producer Digital Cash Book (LCDPR) for detailed natures.

Main Fields

Automatic Routine

Procedure performed automatically in routine Nature (Fina010), without display of screens or the need for user interaction.

Used in customizations in which the process does not require user interaction (MSEXECAUTO)

Example of Automatic Routine

#INCLUDE "Protheus.ch"

USER FUNCTION FIN010INC()
LOCAL aArray := {}
 
PRIVATE lMsErroAuto := .F.
 
aArray := { { "ED_CODIGO"  , "TST"             , NIL },;
            { "ED_DESCRIC" , "DESCRIÇÃO TESTE" , NIL },;
            { "ED_CALCIRF" , "N"               , NIL },;
            { "ED_CALCISS" , "N"               , NIL },;
            { "ED_CALCINS" , "N"               , NIL },;
            { "ED_CALCCSL" , "N"               , NIL },;
            { "ED_CALCCOF" , "N"               , NIL },;
            { "ED_CALCPIS" , "N"               , NIL },;
            { "ED_DEDPIS"  , "2"               , NIL },;
            { "ED_DEDCOF"  , "2"               , NIL },;
            { "ED_COND"    , "R"               , NIL } }
 
MsExecAuto( { |x,y| FINA010(x,y)} , aArray, 3)  // 3 - Addition, 4 - Editing, 5 - Deletion
 
 
If lMsErroAuto
    MostraErro()
Else
    Alert("Nature successfully added!")
Endif
 
Return
 
USER FUNCTION FINA010ALT()
LOCAL aArray := {}
 
PRIVATE lMsErroAuto := .F.
 
aArray := { { "ED_CODIGO"  , "TST"                , NIL },;
                { "ED_DESCRIC" , "DESCRIPTION EDITED" , NIL } }  
           
DbSelectArea("SED")
DbSeek(xFilial("SED"))

MsExecAuto( { |x,y| FINA010(x,y)} , aArray, 4)  // 3 - Addition, 4 - Editing, 5 - Deletion

If lMsErroAuto
    MostraErro()
Else
    Alert("Nature successfully edited!")
Endif

Return
 
 
USER FUNCTION FIN010EXC()
LOCAL aArray := {}
 
PRIVATE lMsErroAuto := .F.
 
DbSelectArea("SED")
DbSeek(xFilial("SED")+"TST")
                                
aArray := { { "ED_CODIGO" , SED->ED_CODIGO , NIL } }
 
MsExecAuto( { |x,y| FINA010(x,y)} , aArray, 5)  // 3 - Addition, 4 - Editing, 5 - Deletion
 
If lMsErroAuto
    MostraErro()
Else
    Alert("Nature successfully deleted!")
Endif
 
Return

Reports

The reports below use the structure for Detailed/Summarized nature.

Related Information

Páginas filhas

Natures - FINA010 - Financials - P12