Index

Objective

Accounts payable are commitments represented by the purchase of goods, services, salaries, taxes, leasing, loans, contributions, machinery, inputs for production, and more.
The Accounts Payable routine of the Microsiga Protheus system controls all documents, also called bills, that the company pays and which can be: trade notes, checks, promissory notes, prepayments, advance payments, invoices, etc. The data registered contribute to decision making on all company commitments that involve the disbursement of resources, being also attributed to the following criteria:

Cash Flow preparation.
To make sure the term of payment is met, considering the possibility of getting discounts and, mainly, to avoid penalties leading to the payment of fines and interest.
To prioritize payments in the hypothesis of financial difficulties.
To identify situations contracted but not paid.
To ensure reconciliation with accounting balances.

The types of bills identify the amount pertaining to a determined income or expense. You must define them in table 05 (Bill Types) of the Configurator module or in the Bill Types routine.

You can add a bill to the portfolio payable manually (by personally typing bills) or automatically (from incoming invoices, provided that the Purchases and/or Stock and Costs modules are integrated with the Financial module).

To automatically generate the bill, the Purchases and/or Stock and Costs modules must be deployed and integrated, because the process depends on the receipt of incoming documents and purchase orders.
The Accounts Payable register is prepared as follows:

Incoming invoice created in the Stock and Costs module	Bills generated in Accounts Payable
101010 (R$ 6,000) in 6 installments of 1,000	101010 A - 1,000 101010 B - 1,000 101010 C - 1,000 101010 D - 1,000 101010 E - 1,000 101010 F - 1,000

To configure installments alphabetically, set the content of parameter MV_1DUP to the letter A. Yet, to divide installments numerically, select option 1.

Grouping the bills by nature generates results in a structured and organized manner (reports), which is a powerful management tool.

Use the breakdown option to generate multiple bills from a single bill, all with the same value (installment) or the value divided by the number of installments (total).

Invoicing, when integrated, generates bills payable through the Commission Update routine. These bills are displayed by default with option COM. Set parameter MV_3DUPREF to define their prefix.

The system tracks the suppliers history details like maximum balance, average and maximum arrears and control of balances payable as value due, overdue and others.

When paying bills, the system offers company X bank features, such as automatic payments and printing checks. You can post bills payable either manually or automatically, by unit or by batches received from banks.

You can control bills regarded for cash flow purposes, because when you add accounts payable, the system updates this flow and makes accounting entries through parameter settings and standardized entries.

Mental Map

Study the chart below to become acquainted with the features of this routine:

Linha Microsiga Protheus - Inglês > Accounts Payable - FINA050 - Financials - P12 > FINA050_390555.jpg

Before you start the addition process, press key [F12\] to set routine parameters, following these criteria:

Field:	Description
Display Acctg. Entry?	Select Yes or No to indicate whether to display accounting entry when booking online. Example: Yes.
Book Prov. Bills?	Select Yes or No to indicate whether to book provisional bills. Example: No.
Ent. accts in apportionment?	Select Yes or No whether to display fields for entry of debit and credit accounts in bill apportionment. Example: Yes.
Online Booking?	Select Yes or No to indicate whether to book transactions online; that is, one at a time (adding a bill, posting, generating a check, deleting, etc.) or offline, with all entries not made online are booked in one batch process. Example: No.
Gen. check f/ Adv.?	Select Yes or No to indicate whether to generate check for advance payment bills. Thus, the system enables field Check when you add the advance payment and when you enter its number, the bank transaction occurs. Example: Yes.
Apportion value?	Enter value for accounts payable apportionment. It offers options Gross (bill value plus taxes) and Net (value without taxes). Example: Gross.
Group Accounting Entry?	Select Yes or No to indicate whether to group accounting entries of apportionment in a single line, if accounts, cost center, item and value class are the same in the entries. Example: No.
Display apportionment deletion?	Select Yes or No to display apportionment screen when deleting the bill. Example: Yes.
Bank Trans. w/out check?	Enter whether to generate bank transaction when field Gen. Check f/ Adv. is filled out with option No. It offers these options: Yes: cash advance (with transaction). No: advance without bank transaction for submission of CNAB (DOC/TED). Example: No.
Gen. apportionment?	For situations involving multiple natures, enter whether to generate apportionment as nature/cost center. For tax values, it is applied only if value apportionment option is filled out as net. It offers options Bill and Bill/Taxes. Example: Bill.
Add Apportionment of a bill from a module other than Financials.	Select the bill and go to option Edit, access tab Accounting and find the field Apportionment (E2_RATEIO). When you select Yes or No, the apportionment screen is displayed. Example: No. Note: The bill cannot be booked for this situation.

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

You can add information from documents/bills to be paid by the company.
Upon selecting this option, choose the Branch desired and click Ok.
Follow the instructions in Main Fields to fill out the data.
See also the features available in Related Features.

You can edit information from documents/bills to be paid by the company.
Upon selecting this option, choose the Branch desired and click Ok.
Follow the instructions in Main Fields to adjust the data.
See also the features available in Related Features.

You cannot edit fields Nature (E2_NATUREZ), Due Date (E2_VENCTO), Actual Due Date (E2_VENCREA) and Value (E2_VALOR) if the financial bill has tax bill(s) posted, because these fields directly affect the data of tax bills.

You can delete a document/bill. To do so, select the item and click Related Features / Delete.
Check available data and click Confirm.
See also the features available in Related Features.

You can view information from documents/bills to be paid by the company.
See also the features available in Other Actions.

Use filters to search for information, ordering it in accordance with a given characteristic.
Example:

branch+prefix+bill no.+installment+type+supplier+store.
branch+paymt. order

Characteristically, you can add a provisional bill in the accounts payable routine without the company having the invoice or the official document. Thus, when the provisional bill is replaced by the original one, you can edit such data as values, nature, history, taxes, etc. You can also select bills of different currencies and generate them in the target currency following these criteria:

Do not convert: only bills of the currency selected are displayed for replacement.
Convert: all provisional bills from the supplier are displayed and the balances of the bills checked are converted to the currency selected.

When you activate option Replace, enter supplier number and bill store. If you prefer, use the standard query feature (press key F3).
A list of bills is displayed in accordance with selected supplier of type PR.
Select and confirm the bill. The system then offers the option to register the bill payable.

You can delete bills with breakdowns. When you activate this option, place the cursor on the bill that generates the breakdown you want to cancel and confirm the procedure.

This option allows viewing of apportionments generated while adding bills payable.

You can schedule the due date of the bill. Just enter the date desired and confirm it.

Run the default knowledge base routine of the system with generic information stored in files. This information can be pictures, texts, spreadsheets or any relevant file type.

Use this option to indicate the status of bills through colors and/or symbols.

Linha Microsiga Protheus - Inglês > Accounts Payable - FINA050 - Financials - P12 > fina050_legenda.jpg

To display processing log data on the bill selected, as well as to search its information ordered by filters in accordance with the characteristic desired, such as date+time or user+date+time.
Use option Details to view highlighted data on date, time, user, message, process and subprocess.

To locate and display accounting entries from the document that originated them.

To control documents when the bill is linked to them.

Use this option to query a contract (and its status) associated with a bill payable, as well as when the bill was generated from an incoming document composed of items from more than one purchase order with contract.

To edit bills payable in batches, through feature Facilitator (MATA984)

Main Fields

General Data

Field:	Description
Prefix:	To identify a set of bills that belong to the same group or branch. Once you enter the prefix, it becomes an integral part of the access key to the bill. Note To configure installments alphabetically, set the content of parameter MV_1DUP to the letter A. Yet, to divide installments numerically, select option 1.
Bill No.:	Enter bill number. Example: FIN000024
Installment:	Enter bill installment. The system allows you to control the breakdowns of a bill. Example: 1
Type:	Classify the bill by its purpose. The types are registered in table 05 (Bill Types) of module Configurator or in routine Bill Types. If needed, you can use the Standard Query feature to select the bill and fill out the field. Example: TX (this acronym refers to fees bill). Note Special Types Provisional Bills Provide revenues that occur for budget/cash flow purposes. When you deploy the bill, specify type PR or enter its status in field Bill Types. To confirm it, use the Replace option, entering the code/store of customer/supplier. Advances Identify a bill paid in advance (PA); that is, paid fully or in part before the invoice is issued. Bank balance is updated online as there is inflow/outflow of money in the Bank. When you deploy the bill, enter type RA or PA or advance receipt/payment in field Bill Types. Then, enter the data related to the advance: Bank, branch, account and check (only for payments). Set parameter MV_PABRUTO to generate the advance payment, as follows: Gross Value: when taxes are not deducted from advance payment. Net Value: when taxes are deducted from advance payment. System default is to add a PA calculating tax value on gross amount, generating a bill related to the net value and the bills for each withheld tax. You can also withhold INSS in the advance payment by generating a bill of type INA to pay the tax. To do this, set field Calculate INSS to Yes. The full package involves some routines: Addition of bills in accounts payable routine. Payments bordereau. Manual and automatic posting. Clearing of accounts payable. Payments bordereau with taxes. Credit Notes Used to indicate the existence of credit/debit notes in Customers or Suppliers. In these cases, the bank balance is not updated. When you deploy a credit note, specify type NCC or NDF, or enter Credit Note/Debit Note in field Bill Types. Deductions Use this to enter values to be deducted from the bill. It is always linked to a main bill. To deploy a deduction bill, enter type AB or the type indicated as Deduction in field Bill Types. Enter the prefix, number and installment of the main bill, or place the cursor on the main bill and enter the type related to the deduction. Note If the system finds bills with keys similar to the key of the deduction you are adding, a screen is displayed with the bills for you to select the correct bill to be deducted. Example:
Nature:	Identify the origin of the nature of the bill and use this item for consolidation, as well as to control the budget. If needed, you can use the Standard Query feature to select the nature of the bill and fill out the field. Example: ISS Warning This field will not be available for editing when the bill payable is booked or posted.
Supplier:	Enter supplier code. If needed, you can use the Standard Query feature to select the registered supplier and fill out the field. Example: FIN061
Store:	Enter the code of the supplier's store. Example: 01
Supplier Name	Display the name of the supplier. This is automatically filled out in accordance with the content of field Supplier. Example: LE Supplier
Issue Dt.:	Date of bill issue. Example: 12/17/2015
Due date:	Enter the nominal due date of bill also taking any possible postponements into account. Example: Bill number FIN000024 is due on 12/17/2015, but due to business matters with the supplier, its payment is postponed 10 days. Thus, fill out this field with the date 12/27/2015. Note The system does not allow a due date set before the issue date of the bill.
Actual Due Date:	Actual due date of bill automatically calculated from the date entered in field Due Date. Example: 12/17/2015 Note The system takes only business days into account; that is, it checks whether the due date is on a Saturday, Sunday or holiday, disregarding these days. There is also the checking of the days of withholding suggested by the Bank, which includes the transfer of bills from the Bank to the portfolio and, consequently, adjusts the content of the field.
Bill Value:	Original value of the bill in currency. Example: 1,835.62
History:	Use this field to add a short note about the bill.
Balance:	In this field, the system keeps the updated balance of the bill value after each transaction you make. Example: 1,835.62
Currency:	Code of the currency used in the bill. Currency 1 = default domestic currency and currencies 2 to 5 in accordance with criteria set in parameters MV_MOEDA2, MV_MOEDA3, MV_MOEDA4 and MV_MOEDA5 through the Configurator module. Example: 1
Vl. BRL:	Value of bill stated in currency. Example: 1,835.62
Currency Rate:	If you enter a rate, it is used as conversion base at the time of posting; otherwise, the rate contracted or the currency date on day of posting is used.
Appr. Code:	Approver code of bill following simple approval rules or fixed fund competence. If needed, you can use the Standard Query feature to select the approver of the bill and fill out the field.

Taxes
The fields of this folder are automatically filled out in accordance with the instructions registered in routines Nature and Supplier (here tax withholding follows the business rule attributed to the supplier).
The field contents can also come from routines that involve integrated processes, such as the TIO and Product registers.
Note
You can adjust the values that are automatically filled out; however, they interfere in the calculation of the bill for payment.

Field:	Description
ISS:	The content of this field refers to service tax and is automatically calculated by the system following this priority: The system checks whether the class registered allows ISS calculation defined in the Calculate ISS? field. In the Suppliers register, it checks the collection of ISS through the content defined in field Collect ISS? Thus, when the field is filled out with Yes, the system does not perform the calculation (because the supplier collects the ISS). If it is set to option No, the system calculates it in accordance with MV_ALIQISS parameter settings. Note The following parameters are also considered: MV_MUNIC: Indicates the ISS provider. The system generates a new bill payable for the city government defined in this parameter, when the bill receivable is added. MV_DIAISS: due date for paying the bill. Example: Rate of 5% in parameter MV_ALIQISS; that is, content equal to 5. Registration of a nature that calculates ISS and of a supplier that does not collect this tax. With this scenario, the addition of a bill payable of BRL 1,000.00 will have field ISS automatically filled out with the value BRL 50.00. Note The system deducts the original ISS value from the bill; that is, in the aforementioned example, when you enter the value of 1,000.00 for the bill, it is converted to 950.00 (deducting 50.00 that refer to ISS). While adding, the system automatically creates a bill (Type ISS) for payment of ISS collected for the city government.
IRRF:	Field IRRF (Income Tax Withheld by Tax Authorities) is automatically calculated in accordance with the priorities set for Natural Person and Legal Entity. Note For both situations, the use of common parameters is worth considering; however, their settings meet each profile in their own way and occasion: MV_VENCIRF: Indicate whether to generate the IR bill from the date of issue, due date or bill booking date. MV_VLRETIR: Specify the minimum value for exemption from IRRF withholding. In this case, the bill with amount lower than this parameter is not generated and IR is zero. Natural Person Supplier The system considers the IRRF Table or it may use the Nature Rate. Nature Rate Some operations require the use of a rate different from the progressive table. In these situations, just fill out the following fields in the Nature Register: IRRF calculation (ED_CALCIRF) = Yes IRRF percentage (ED_PERCIRF) = 10 Capital interest (ED_JURCAP) = Yes Examples of operations that use a rate different from progressive table: Own Capital Interest, Contract Termination, Prizes in Goods or Services, etc. Example: If, when adding a bill payable, you consider a Natural Person supplier and set a percentage rate of 15% set in field IRRF Perc of the Nature Register, and also set field Calculate IRRF = Yes and field Cap Interest 1 = Yes. When you enter a value of BRL 10,000.00, the system displays the following information: field value is recalculated and displays the value of BRL 8,500.00, whereas in the taxes tab, the system displays in IRRF field the value of BRL 1,500.00 and in field IRRF Base the system displays the value of BRL 10,000.00. When you add the bill, the system generates a bill payable of type TX with the IRRF value calculated for the Federal Government. Progressive Table For natural person IRRF calculation using progressive table, fill out the following fields in the Nature Register: IRRF calculation (ED_CALCIRF) = Yes IRRF percentage (ED_PERCIRF) = 0 Capital interest (ED_JURCAP) = No Example: You add a bill payable with a supplier that is a Legal Entity, setting a percentage of 3% in the IRRF Table and using a nature that calculates the IRRF with a percentage of 8%. If you enter a bill in the amount of BRL 1,000.00, the system automatically fills out the field IRRF with the value of 30.00 (considering the IRRF table, not the Natures register). The system deducts the IRRF value from the original value of the bill. Thus, when you enter the amount of 1,000.00 for the bill, the system converts it to 970.00 (after deducting 30.00 pertaining to IRRF). When you add the bill, the system generates a bill payable of type TX with the IRRF value calculated for the Federal Government. Besides the IRRF Table, you must also set some influential parameters: MV_VCTIRPF: uniquely generates the IRRF by date when the bill payable is from a Natural Person supplier. You may set its content in accordance with the following options: E: to generate the bill related to the IRRF from the bill issue date. V: to generate it from the bill due date. C: to generate it from the bill booking date. Example: Issue of bill - E
Data of the main bill BRL 7,300.00 (BRL 10,000.00)
IRRF - BRL 2,700.00.
Bill issue date - 9/1/2015.
Bill due date - 10/12/2015.

Data of TX bill from generated IRRF

Main value of bill BRL 2,700.00.

Bill due date 10/10/2015.

Due Date - V

Data of the main bill BRL 7,300.00 (BRL 10,000.00)

IRRF - BRL 2,700.00.

Bill issue date - 9/1/2015.

Bill due date - 10/12/2015.

Data of TX bill from generated IRRF

Main value of bill BRL 2,700.00.

Bill due date 11/10/2015.

Booking - C

Data of the main bill BRL 7,300.00 (BRL 10,000.00)

IRRF - BRL 2,700.00.

Bill issue date - 9/1/2015.

Bill due date - 10/12/2015.

Booking date - 9/1/2015.

Data of TX bill from generated IRRF

Main value of bill BRL 2,700.00.

Bill due date 10/10/2015.

Note
If you do not create parameter MV_VCTIRPF, the system maintains the same process to generate the IRRF, in accordance with parameter MV_VENCIRF, for Natural Persons as well as for Legal Entities.

MV_TMSVDEP: calculates the IRRF of Natural Persons when issuing accounts payable bills, considering the number of dependents; thus, the bill generation deducts from the IRRF the value per dependent defined by the Federal Revenue Service.

Legal Entity Supplier
The system checks the fields Calculate IRRF and IRRF Perc. found in the Natures register, as well as the content of parameter MV_ALIQIRF.
Example:
Rate set to 3% in parameter MV_ALIQIRF and a nature that calculates IRRF with a percentage of 8%. When you add bill of BRL 1,000.00, the system fills out field IRRF with the value of BRL 80.00 (with reference to the Natures register).
Note
IR calculation and withholding for Legal Entities, pursuant to article 724, item II from RIR, approved by Decree No. 3,000/99
The withholding of taxes by tax authorities occurs only for incomes that integrate the calculation base of taxes owed by Legal Entities the taxing of which is based on taxable income, presumed profit or estimated profit.
It is understood that the IR-Fonte generator factor related to services rendered by Legal Entities to other Legal Entities is on daily basis; therefore, you must add invoices from the same supplier on the same day for limitation purposes, and not add invoices the generator factors of which occur in different days.
Thus, if in the month more than one payment is made or incomes are credited to the same Legal Entity, the tax is calculated on the value of each factor and, if the minimum value of BRL 10.00 is not reached, exemption of tax withholding is granted, even if the tax amount calculated in the month on the sum of these incomes surpasses this limit.
Example:

Description	Values
Invoice No. 100.	BRL 550.00
Invoice No. 120.	BRL 650.00
Total payable on 09/10/15.	BRL 1,200.00
IRRF to be withheld (BRL 1,200.00 x 1.5%).	BRL 18.00
Net value payable to supplier (with IR withholding)	BRL 1,182.00

The system calculates the IRRF in accordance with the Progressive Table for Legal Entity Supplier in the case of freelance business agents that only mediate business trades done by third parties.
To perform the calculation, you must associate a Supplier (Legal Entity) and fill out field IRRF Sch. with option Yes when adding a bill of accounts payable.
Besides the Progressive Table, you must also set some influential parameters:

MV_VENCIRF and MV_MP447: IRRF withholding when generating bills payable with the parameter, in accordance with Provisional Measure 447/2008.

The due dates of generated tax bills (IRRF and INSS) are calculated up to the twentieth day of the following month.
Example:

Tax	Parameter Config.	Issue of original bill	Original Bill Maturity	Original Bill Actual Due Date	Due Date
IRRF	Issue (MV_VENCIRF)	11/21/15	12/20/2015	12/22/2015	12/19/2015
IRRF	Due date (MV_VENCIRF)	11/21/15	12/20/2015	12/22/2015	01/20/2015

Note
The parameter MV_MP447 is only taken into account in calculation of due date for IRRF and INSS if the occurrence date on the bill (Issue Date or Due Date) starts on 11/1/15. In the example, both the issue date and due date are considered in this parameter.

MV_VENCCRC: exclusive process to generate IRRF taxes pursuant to article 34 of Law No. 10,833.

The Federal Public Administration entities, pursuant to article 34 of law No. 10,833, are required to withhold Income Tax, CSLL, COFINS and PIS/PASEP on bills payable.
To meet the demands of this legislation, you must configure the parameter MV_VENCCRC with default content equal to 6147#6175#6188#8739#8767#6190.
Example:

Data of the main bill BRL 9,850.00 (BRL 10,000.00)

IRRF - BRL 150.00.

Bill issue date - 9/1/2015.

Bill due date - 09/19/2015.

Data of TX bill from generated IRRF

Main value of bill BRL 150.00.

Bill due date 10/13/2015.

Note
If you do not create the parameter MV_VENCCRC, the system maintains its default process defined in parameter MV_VENCIRF, pursuant to article 70 of law 11,196 from 11/21/2005. As exemplified and in accordance with parameter MV_VENCIRF, the IRRF bill due date is 10/10/15.

|

INSS:

This field pertains the Contribution to the National Institute of Social Security. The system automatically fills it out when a bill payable is added, following these criteria:
The system checks whether the nature registered allows INSS calculation through the field Calculate INSS? and its respective percentage through the field INSS Perc.
In the Suppliers register, check whether field Calculate INSS? is filled out with Yes.
Example:
Registration of a Nature that calculates INSS (percentage of 8%), customer with INSS calculation and addition of bill payable of BRL 1,000.00 for supplier. In this scenario, field INSS is automatically filled out with the value of BRL 80.00.
The system deducts the INSS value from the original value of the bill. Using the example above, when you enter the amount of 1,000.00 for the bill, the system converts it to 920.00 (after deducting 80.00 of INSS).
When you add the bill, the system generates a bill payable of type INS with the INSS value calculated for INPS.
The content of this field also affects the settings of some parameters:

MV_INSS: enter the nature for INSS bill classification.
MV_VLRETIN: Enter the minimum value for exemption from payment, without generating the bill.

MV_VENCIRF and MV_MP447: INSS withholding when generating bills payable, in accordance with Provisional Measure 447/2008.

The due dates of generated tax bills (IRRF and INSS) are calculated up to the twentieth day of the following month:
Example:

Tax	Parameter Configuration	Original bill issue	Original bill due date	Original bill actual due date	Due date
INSS	Issue (MV_VENCINS)	11/21/15	12/20/2015	12/22/2015	12/19/2015
INSS	Due date (MV_VENCINS)	11/21/15	12/20/2015	12/22/2015	01/20/2015

Note
The parameter MV_MP447 is only taken into account in calculation of due date for IRRF and INSS if the occurrence date on the bill (Issue Date or Due Date) starts on 11/1/15. In the example, both the issue date and due date are considered in this parameter.|

Generate DIRF:

Enter whether the bill is used for DIRF generation in integration with Payroll. Fill out this field by selecting between options: 1-Yes and 2-No.
Example:
2-No

Withholding Code:

Use this field to make the exclusive codes for tax withholdings more flexible, when you add an invoice through modules Purchases or Financials with the withholding of PIS, COFINS or CSLL taxes and fields PIS Withh., COF. Withh. Code, or CSL Withh. Code are filled out; thus, the data are saved in the Parent trade note, ignoring the codes that are currently preset in the system, which are:

5952 - when the bill withholds the three taxes: PIS, COFINS and CSLL.
5979 - when the bill withholds only PIS.
5960 - when the bill withholds only COFINS.

5987 - when the bill withholds only CSLL.

In Child taxes, the withholding codes are recorded in field Withholding Code, in accordance with the data from the new fields, if they were created and filled out. When they are not filled out, the system also records in this field; however, it uses the same process of the Parent trade note.
Examples:
Addition of bill payable with withholding of PIS, COFINS or CSLL without filling out fields PIS Withh. Code, COF Withh. Code and CSL Withh. Code:

Bill withholds the three taxes: PIS, COFINS and CSLL.
Main value
BRL 6,000.00
PIS
BRL 39.00
COFINS
BRL 180.00
CSLL
BRL 60.00
Withholding Code
5952
Bill collects only PIS tax:
Main value
BRL 6,000.00
PIS
BRL 39.00
COFINS
BRL 0.00
CSLL
BRL 0.00
Withholding Code
5979
Bill collects only COFINS tax:
Main value
BRL 6,000.00
PIS
BRL 0.00
COFINS
BRL 180.00
CSLL
BRL 0.00
Withholding Code
5960
Bill collects only CSLL tax:
Main value
BRL 6,000.00
PIS
BRL 0.00
COFINS
BRL 0.00
CSLL
BRL 60.00
Withholding Code
5987

Addition of a bill payable with fields PIS Withh. Code = 3770 / COF Withh. Code = 5960 / CSL Withh. Code = 5987 filled out:

Main value	BRL 6,000.00
PIS	BRL 39.00
COFINS	BRL 180.00
CSLL	BRL 60.00
Withholding Code	3770
COFINS.Withh.Code	5960
CSL.Withh.Code	5987
SEST/SENAT:	The calculation of SEST/SENAT (Transportation Social Service / Transport Learning National Service) payment amounts, which the Financials module can generate when the Transportation Management module is not in use. Note The parameter MV_FORSESTindicates the default supplier for SEST bills.
COFINS:	Contribution value for Social Security Financing calculated on the gross revenue of companies. Example: 300.00
PIS/PASEP:	Value that corresponds to the 1% rate levied on payroll. Example: 65.00
CSLL:	Value that corresponds to the Social Contribution rate on profits in accordance with the activities performed. Example: 100
PCC Base:	Base value used to calculate the tax. Example: 10,000.00
ISS Due Date:	Due Date of ISS generated when adding the Incoming Invoice.
Serv. Ac. Val.:	Value of service received within the month, in accordance with Municipal Law No. 1,802, dated 26 of December of 1969, of Sao Bernardo do Campo - SP.
DCTF Variat.:	Enter the variation for the revenue code in accordance with the Codes Table in DCTF.
DCTF Per.:	Enter the periodicity of the revenue code used in DCTF.

D: for daily periodicity.
S: for weekly periodicity.
X: for ten-day periodicity.
Q: for fortnightly periodicity.
M: form monthly periodicity.
B: for bimonthly periodicity.
T: for quarterly periodicity.
U: for four-month periodicity.
E: for biannual periodicity.

A: for annual periodicity.|

ISS Withh. Form.:	Enter the condition to be applied in calculation of ISSQN withholding (Service Tax of Any Nature) for this bill, which can consider the minimum value for withholding or always withhold it. Fill out this field with one of these options: 1 – Cons. Min. Val. (default value). 2 – Always withhold it.
Apply Min. Val.:	Define whether the values of PIS/COFINS withholding entered in bill payable must respect the minimum withholding value of BRL 5,000.00, introduced in Law 10,925 or withhold it regardless of the value. Fill out this field with one of these options: 1 - Yes 2 - No
FETHAB Inst.:	Installment number of FETHAB (State Fund for Transport and Housing).
FETHAB Val.:	Bill value of FETHAB (State Fund for Transport and Housing).
ISS Rate Code:	This field remains enabled when the ISS rate is registered through routine ISS Multiple Rates, thus allowing the selection of an ISS rate for the bill payable. If you do not fill out this field, the rate used in bill payable is the rate set in parameter MV_ALIQISS.
IRPF Base:	Tax calculation base (when only this field is enabled) or IRRF Calculation base when other tax base fields are enabled. Thus, it defines whether the IRPF calculation is reduced, meeting the cases mentioned in the Normative Instruction SRF No. 15 from February 6, 2001. When you enter the reduced IRPF value, its calculation is performed at the posting of accounts payable; hence, the requirements:

Supplier Register: this must be a Natural Person with income tax withholding at bill posting.

Nature Register: nature that calculates income tax and that has reduced base.

Note
Legal Grounds
Normative Instruction SRF No. 15 dated February 6, 2001
Art. 12. Real estate rentals paid by Legal Entity are not part of the calculation base for income tax levy purposes:
I - Value of taxes (IPTU), rates, and emoluments levied on the asset that produces income;
II - Rent paid by the rental of sublet real estate;
III - Expenses paid for collection (bank bill) or receipt;
IV - Condominium expenses.
§ 1st The charges above can only be deleted from the rental value when burden has been exclusively to the landlord.
§ 2nd When rent is paid by real estate offices, legal representative, or by any person chosen by the landlord, the payment date considered is that one in which the tenant made the payment, regardless of when it goes to the beneficiary.
§ 3rd Compensation by advance termination or contract termination is considered taxed income for the beneficiary.|

INSS Withh. Code:	Code of INSS withholding.
DARF ID:	DARF identification (Federal Revenues Collection Document).
INSS Prov.:	This field stores the INSS provisioning for bills of type PA (Advance Payment) in accordance with the settings of parameters MV_PABRUTO=2 and MV_PAPRIME=2.
FABOV Inst.:	Installment of tax FABOV (Cattle Raising Development Fund).
FABOV Val.:	Value of tax FABOV (Cattle Raising Development Fund).
FACS Inst.:	Installment of tax FACS (Soy Culture Development Fund).
FACS Val.:	Value of tax FACS (Soy Culture Development Fund).

Administration

Field:

Description

Delinq. Fee:

In this field, enter the value to be added to the bill for each day of payment arrears. For calculation purposes, the system takes consecutive days into account and this field has priority on field Interest Perc. at bill posting.
Note
If needed, you can change the priority depending on the settings of parameter MV_FINJRTP which follows some criteria when bills have both fields filled out:
1 - Apply only the Delinquency Fee (default content).
2 - Apply only Interest.
3 - Apply the Delinquency Fee and Interest.
Example:
Considering a bill with the following characteristics:

Prefix: 001.
Number: 000014.
Type: DP.
Issue date: 4/10/15.
Due date: 4/11/15.
Actual due date: 4/11/15.
Original value: 1,000.00.
Delinquency Fee: 1.00.

At bill posting, the system displays the following data:
Date of bill posting: 4/16/15.
Delinquency fee value: 5.00 (for 5 days in arrears).

Bill value received: 1,005.00.|

Interest Perc.:

In this field, enter the interest percentage to be levied per day on the original bill value for payment arrears. For calculation purposes, the system uses consecutive days.
For the system to use the interest percentage, do not fill out the field Delinquency Fee, otherwise it is given priority.
Note
If needed, you can change the priority depending on the settings of parameter MV_FINJRTP which follows some criteria when bills have both fields filled out:
1 - Apply only the Delinquency Fee (default content).
2 - Apply only Interest.
3 = Applies Delinquency Fee and Interest.
Example:
Consider a bill due on 4/11/2015 (Saturday). In this case, its actual due date is on 4/13/2015; however, if the payment is made on 4/16/2015, the system considers 5 days of arrears and the scenario becomes as follows:

Prefix: 001.
Number: 000015.
Type: DP.
Issue date: 4/09/15.
Due date: 4/11/15.
Actual due date: 4/13/15.
Original value: 1,000.00.
Delinquency fee: not entered.
Interest perc.: 1.00 (1% on the original bill value).
Posting date: 4/16/15.

Value received: 1,050.00.|

Addition:	Added value applied to bill. It is added at the time of posting, even if the bill is paid until the due date, with a fixed addition value known at the time of deployment.
Cash flow:	In this field, define whether the bill must be considered in cash flow; that is, in the control of the financial transaction pertaining the inflows and outflows of financial resources. The options available for its completion are:

S – Yes.

N - No.|

Breakdown:

This field allows you to generate several bills with different due dates, from a single addition. Use this resource for expenses with fixed due dates (such as rental payments).
The breakdown of a bill can be by accounting apportionment (standard entry 511) or by multiple natures (standard Entry 510). The percentages entered in the apportionment are copied to all breakdown installments.
The system does not treat taxes in this situation.
If you use a breakdown without apportionment, the standard accounting entry is 577.
You cannot perform a breakdown by apportionment and by multiple natures in a single operation.
To calculate taxes, the following conditions are required in case of bill breakdown:

Use the process of Financial Tracing: this offers a way to view negotiations made with the financial bills that compose the initial document.
In routines Supplier and Nature, the field Breakdown must be filled out with the option Yes.

The tax bills, configured for withholding when issuing bills payable, are generated in accordance with the calculation rule of each tax.
For taxes that involve the calculation on a given period or value (such as PIS, COFINS and CSLL withheld at issue), there is no recalculation or adjustment in the following situations:
The withholding bill of the taxes is outside the breakdown.

After cancellation, when the default procedure of cumulativeness for withholding taxes is not followed.

Note
You can delete bills with breakdowns in the Accounts Receivable routine.|

Approver:	Approver required for bill payment. You can use it in the workflow process.
Reduction:	This field defines a reduction value applied to the bill. When entered in the posting payable (regardless of posting date), the system reduces the value entered in this field from the value of the bill.
Mult. Natures:	Use this field to define whether to classify bills in multiple natures. To enable this field while adding a bill payable, set parameter MV_MULNATP to T. When you distribute the value of the bill among multiple natures, you may apportion the value of each nature among various cost centers, considering some criteria for the standard entries:

508 - Apportionment by cost center of distribution in multiple natures.

509 - Cancellation of apportionment by cost center of distribution in multiple natures.

These standard entries are available for online (508, 509) or offline (508) accounting and must be used together with standard entry 510 (addition of accounts payable bills).
Distributions of values by multiple natures that do not use apportionment by cost center are booked as additions (standard entry 510).
Distributions that use apportionment by cost center are booked by the aforementioned entries (however, standard entry 508 is not executed if standard entry 510 does not exist).
You must book bills payable using the same standard entry for bill addition/deletion. Simply enter the value to be booked in the Standard Entry register. If you do not follow this procedure, the value booked may become duplicated.
Note
When you add bills payable with apportionment via automatic routine, set parameter MV_RATAUTO to .T. to display the multi-nature apportionment screen.|

Rate Currency indexation rate Currency:	Field that contains the last rate used in indexation calculation for bills with currency other than 1.
Has Docs:	Define whether the bill has linked documents that aim to block bills payable that do not present required documents.

Bank

Field:	Description
Bearer:	Code of bearer used for identifying the collection agent in charge of collecting the bill.
Payment Mod.:	Expected payment modality. Example: 1 – TED.
Sched. date:	Date scheduled for bill clearing.
Typ. Field:	Data related to the typable field of bill.
Sup. branch:	Bank branch of supplier payment of bill payable.
DV branch:	Verification digit of bank branch of supplier payment of bill payable.
Sup. account:	Bank account of supplier payment of bill payable.
DV account:	Verification digit of bank account of supplier payment of bill payable.
Sup. bank:	Bank of supplier payment of bill payable.
Paymt Method:	Enter the preferred payment method for supplier.

Accounting

Field:	Description
Apportionment:	Enter whether the bill value must be apportioned in various cost centers by selecting one of the options S - Yes and N - No. Entries of bills payable can be apportioned among accounting entities (ledger account, cost center, accounting item and value class). This way, the standard entries must be registered:

511 - Enter the accounts payable bill with apportionment (standard entry).

512 - Deletion of accounts payable bill with apportionment. \\
 \\
You must check the configuration of fields activated by pressing *\[F12\]{*}, as they determine the value used in the apportionment (gross or net), grouping of entries, ledger account data, etc. \\
Note \\
Apportionments entered for the accounts payable process have an internal control as a single entry key through field *Seq. It.* (not displayed onscreen), in which the apportionment rows are automatically and sequentially numbered as items. \\
Set parameter *MV_INTPMS* to apportion accounts payable by project.|

Ledger acct:	Define the ledger account in which to manually create the ledger entry in budget plans related to accounts payable.
Daily seq.:	Sequential code of journal for accounting.
Journal code:	Code of journal to be used for transaction.
Cost c.:	Cost Center used in the accounts payable process.

Others

Field:	Description
Proj. Apport.:	Indicator of apportionment of Projects (linked to PMS - Project Management). Select option 1 - Yes or 2 - No to fill out the content of this field.
Budg. Code:	Represents the code of budget plan and the request is validated in this plan in relation to budgeted and executed. The system always uses the content of this plan with the default plan set in parameter MV_PLAPAD; however, you can also enter the desired plan to make the purchase and, consequently, the reserve of the values preset in this plan.
Contract No.:	Code of contract.
Cont. ver.:	Code of contract revision.
Spreadsh. No.:	Code of contract spreadsheet.
Sched. No.:	Code of financial schedule of contract.
Installment No.:	Installment of financial schedule.
RDA Code:	Code of service network related to routine Service Networks of module Health Care Plan.
Contr. Bonus:	Value of contract bonuses deducted in financial bill.
Contr. Withh.:	Value of contract withholding deducted in financial bill.
Contr. Fine:	Value of contract fines deducted in financial bill.
Contr. Discount:	Value of contract discounts deducted in financial bill.
Ref. proc.:	Number of referenced process related to bill. This information is used when generating SPED, PIS and COFINS.
Process tp.:	Define the type of process related to bill. This information is used when generating SPED, PIS and COFINS.
Carrier code:	Code of freight carrier responsible for generating the bill.
Carrier name:	Name of freight carrier responsible for generating the bill.
Serv. tp.:	Type of service rendered.
FAMAD Vl.:	Value of tax FAMAD (Timber Development Fund).
FUMIPEQ Vl.:	Value of FUMIPEQ (Municipal Stimulus Fund for Micro and Small Businesses).
FAMAD Inst.:	Installment of FAMAD (Timber Development Fund).
FUMIPEQ Inst.:	Installment of FUMIPEQ (Municipal Stimulus Fund for Micro and Small Businesses).
INSS Withh.:	Refers to the INSS value withheld when bills are generated by the Transportation Management module through field INSS Withheld in routine Trip Complement when the vehicle fleet refers to a third party or associated; however, when owned the field is not enabled. Values entered in field INSS Withheld refer to transport services rendered by the driver in other carriers. This value is added to the INSS value calculated in relation with the freight to be received in the teamster contract, considering the settings of parameter MV_LIMINSS.
CNO Code:	Enter the code related to national works register.
CNPJ (EIN):	CNPJ (EIN) of INSS (Brazilian Social Security) withholder.

Automatic Execution

Execution of automatic operations

OVERVIEW

Example of automatic execution of the inclusion, deletion and edition operations of bills payable.
Warning
The Fa050Inclu() function cannot be used in customizations because it is a menu function; there are some dependencies on privates variables declared in FINA050.

EXAMPLE OF USE

\\
*Addition*  Expandir origem 
#INCLUDE "Protheus.ch"
USER FUNCTION FIN050INC()
 LOCAL aArray := \{\}
  \\
 PRIVATE lMsErroAuto := .F.
 \\
 //Structure for PA ( Advance Payment )
 aArray := \{ \{ "E2_PREFIXO"  , "PAG"             , NIL \},;
    \{ "E2_NUM"      , "0001"            , NIL \},;
    \{ "E2_TIPO"     , "PA"              , NIL \},;
    \{ "E2_NATUREZ"  , "001"             , NIL \},;
    \{ "E2_FORNECE"  , "0001"            , NIL \},;
    \{ "E2_EMISSAO"  , CtoD("17/02/2012"), NIL \},;
    \{ "E2_VENCTO"   , CtoD("17/02/2012"), NIL \},;
    \{ "E2_VENCREA"  , CtoD("17/02/2012"), NIL \},;
    \{ "E2_VALOR"    , 5000              , NIL \},;
    \{ "AUTBANCO"    , "001", NIL \},;
    \{ "AUTAGENCIA"  , "1234", NIL \},;
    \{ "AUTCONTA"    , "123456", NIL \} \}
\\
 //Structure for other bills
 aArray := \{ \{ "E2_PREFIXO"  , "PAG"             , NIL \},;
    \{ "E2_NUM"      , "0001"            , NIL \},;
    \{ "E2_TIPO"     , "NF"              , NIL \},;
    \{ "E2_NATUREZ"  , "001"             , NIL \},;
    \{ "E2_FORNECE"  , "0001"            , NIL \},;
    \{ "E2_EMISSAO"  , CtoD("17/02/2012"), NIL \},;
    \{ "E2_VENCTO"   , CtoD("17/02/2012"), NIL \},;
    \{ "E2_VENCREA"  , CtoD("17/02/2012"), NIL \},;
    \{ "E2_VALOR"    , 5000              , NIL \} \}
  \\
 MsExecAuto( \{ |x,y,z| FINA050(x,y,z)\}, aArray,, 3)  // 3 - Inclusion, 4 - Edition, 5 - Deletion
  \\
  \\
 If lMsErroAuto
  MostraErro()
 Else
  Alert("Bill included successfully")
 Endif
  \\
Return
*Editing*  Expandir origem 
#INCLUDE "Protheus.ch"
USER FUNCTION FIN050ALT()
 LOCAL aArray := \{\}
  \\
 PRIVATE lMsErroAuto := .F.
\\
 aArray := \{ \{ "E2_PREFIXO"  , "PAG"             , NIL \},;
    \{ "E2_NUM"      , "0001"            , NIL \},;
    \{ "E2_VALOR"    , 2000              , NIL \} \}  
\\
 DbSelectArea("SE2") 
 DbSetOrder(1)
 DbSeek(xFilial("SE2")+"PAG"+"0001     "+" "+"NF") //Edition must have SE2 record positioned
    \\
 MsExecAuto( \{ |x,y,z| FINA050(x,y,z)\}, aArray,, 4)  // 3 - Inclusion, 4 - Edition, 5 - Deletion
\\
 If lMsErroAuto
  MostraErro()
 Else
  Alert("Bill edited successfully")
 Endif
\\
Return
*Deletion*  Expandir origem 
#INCLUDE "Protheus.ch"
USER FUNCTION FIN050EXC()
 LOCAL aArray := \{\}
  \\
 PRIVATE lMsErroAuto := .F.
  \\
 DbSelectArea("SE2") 
 DbSetOrder(1)
 DbSeek(xFilial("SE2")+"PAG"+"0001     "+" "+"NF") //Deletion must have SE2 record positioned
         \\
 aArray := \{ \{ "E2_PREFIXO" , SE2->E2_PREFIXO , NIL \},;
     \{ "E2_NUM"     , SE2->E2_NUM     , NIL \} \}
  \\
 MsExecAuto( \{ |x,y,z| FINA050(x,y,z)\}, aArray,, 5)  // 3 - Inclusion, 4 - Edition, 5 - Deletion
  \\
 If lMsErroAuto
  MostraErro()
 Else
  Alert("Bill deleted successfully")
 Endif
 \\
Return
\\
*Addition with VA (Accessory Values)*  Expandir origem 
#INCLUDE "Protheus.ch"
USER FUNCTION FIN050VA()
    LOCAL aArray := \{\}
    LOCAL nOpc   := 3 // 3-Addition, 4 Editing
 \\
    // Accessory value data.
    LOCAL aVAAut     := \{\}
    LOCAL cValAce1   := "000001"  // Va Code
    LOCAL nValAce1   := 200       // Va Code
    LOCAL cValAce2   := "000012"
    LOCAL nValAce2   := 4
 \\
    PRIVATE lMsErroAuto := .F.
  \\
    aArray := \{ \{ "E2_PREFIXO"  , "PAG"             , NIL \},;
              \{ "E2_NUM"      , "0001"            , NIL \},;
              \{ "E2_TIPO"     , "NF"              , NIL \},;
              \{ "E2_NATUREZ"  , "001"             , NIL \},;
              \{ "E2_FORNECE"  , "0001"            , NIL \},;
              \{ "E2_EMISSAO"  , CtoD("17/02/2012"), NIL \},;
              \{ "E2_VENCTO"   , CtoD("17/02/2012"), NIL \},;
              \{ "E2_VENCREA"  , CtoD("17/02/2012"), NIL \},;
              \{ "E2_VALOR"    , 5000              , NIL \} \}
  \\
    // Array with accessory value
    aAdd(aVAAut, \{cValAce1, nValAce1\})
    aAdd(aVAAut, \{cValAce2, nValAce2\})
 \\
    MsExecAuto( \{ |a,b,c,d,e,f,g,h,i,j,k,l| FINA050(a, b, c, d, e, f, g, h, i, j, k, l)\}, aArray,, nOpc,,,,,,,,, aVAAut)  
  \\
    If lMsErroAuto
        MostraErro()
    Else
        If nOpc == 3       
            Alert("Bill successfully added!")
        Else
            Alert("Bill edited successfully")
        EndIf
    Endif
  \\
Return
*Addition with PA with check*  Expandir origem 
#INCLUDE "Protheus.ch"
USER FUNCTION FIN050INCPA()
    LOCAL aArray := \{\}
  \\
    PRIVATE lMsErroAuto := .F.
  \\
    aArray := \{ \{ "E2_PREFIXO", "PAG"             , NIL \},;
              \{ "E2_NUM"      , "0001"            , NIL \},;
              \{ "E2_TIPO"     , "PA"              , NIL \},;
              \{ "E2_NATUREZ"  , "001"             , NIL \},;
              \{ "E2_FORNECE"  , "0001"            , NIL \},;
              \{ "E2_EMISSAO"  , CtoD("17/02/2012"), NIL \},;
              \{ "E2_VENCTO"   , CtoD("17/02/2012"), NIL \},;
              \{ "E2_VENCREA"  , CtoD("17/02/2012"), NIL \},;
              \{ "E2_VALOR"    , 5000              , NIL \},;
              \{ "AUTBANCO"    , "FIN"             , NIL \},;
              \{ "AUTAGENCIA"  , "00015"           , NIL \},;
              \{ "AUTCONTA"    , "0000000001"      , NIL \},;
              \{ "AUTMOED"     , "1"               , NIL \},;
              \{ "AUTCHEQUE"   , "124569"          , NIL \}\}
  \\
    MsExecAuto( \{ |x,y,z| FINA050(x,y,z)\}, aArray,, 3)  // 3 - Addition
   \\
    If lMsErroAuto
        MostraErro()
    Else
        Alert("Bill successfully added")
    Endif
  \\
Return
*Addition with project apportionment (PMS)*  Expandir origem 
USER FUNCTION F050IPMS()
 Local cPref := "FIN"
 Local cNum := "210408001"
 Local cPar := "1"
 Local cTipo := "NF"
 Local cNaturez := "FGRV01"
 Local cFornec := "FGRV04"
 Local cLoja := "01"
 Local nValor := 1000
 Local aGrvSe2 := \{\}
 Local aInfProj := \{\}
 Local aInfAFR := \{\}
 \\
 PRIVATE lMsErroAuto := .F.
 \\
 PREPARE COMPANY ENVIRONMENT "T1" BRANCH "D MG 01 " MODULE "FIN" TABLES "SE2","SE5","SA2","AFR","AF9","AF8"
  \\
 aAdd(aInfAFR, \{"AFR_PROJET", PadR("PMSU000023", TamSX3("AF9_PROJET")\[1\]), Nil\})
 aAdd(aInfAFR, \{"AFR_TAREFA", "01.02", Nil\})
 aAdd(aInfAFR, \{"AFR_TIPOD", PadR("0004", TamSx3("AFR_TIPOD")\[1\]), Nil\})
 aAdd(aInfAFR, \{"AFR_VALOR1", nValor, Nil\})
 aAdd(aInfAFR, \{"AFR_REVISA", StrZero(4, TamSX3("AFR_REVISA")\[1\]), Nil\})
 aAdd(aInfAFR, \{"AFR_PREFIX", cPref, Nil\})
 aAdd(aInfAFR, \{"AFR_NUM", cNum, Nil\})
 aAdd(aInfAFR, \{"AFR_PARCEL", cPar, Nil\})
 aAdd(aInfAFR, \{"AFR_TIPO", cTipo, Nil\})
 aAdd(aInfAFR, \{"AFR_FORNEC", cFornec, Nil\})
 aAdd(aInfAFR, \{"AFR_LOJA", cLoja, Nil\})
 aAdd(aInfAFR, \{"AFR_DATA", Date(), Nil\})
 aAdd(aInfAFR, \{"AFR_VENREA", Date(), Nil\})
 aAdd(aInfProj, aInfAFR)
 \\
 aGrvSe2 := \{ \{ "E2_PREFIXO" , cPref , NIL \},;
 \{ "E2_NUM" , cNum , NIL \},;
 \{ "E2_TIPO" , cTipo , NIL \},;
 \{ "E2_NATUREZ" , cNaturez , NIL \},;
 \{ "E2_FORNECE" , cFornec , NIL \},;
 \{ "E2_LOJA" , cLoja , NIL \},;
 \{ "E2_EMISSAO" , Date() , NIL \},;
 \{ "E2_VENCTO" , Date() , NIL \},;
 \{ "E2_VENCREA" , Date() , NIL \},;
 \{ "E2_VALOR" , nValor , NIL \},;
 \{ "E2_PROJPMS" , "2" , NIL \},;
 \{ "E2_HIST" , "Project Addition" , NIL \},;
 \{"AUTRATAFR" , aInfProj ,Nil \} \}
 \\
 MsExecAuto( \{ |x,y,z| FINA050(x,y,z)\}, aGrvSe2,, 3) // 3 - Addition, 4 - Editing, 5 - Deletion
 \\
 If lMsErroAuto
  MostraErro()
 Else
  Conout("Bill successfully added!")
 Endif
 \\
Return
*Bills payable withholding code*  Expandir origem 
#INCLUDE "Protheus.ch"
\\
/*When there is any type of operation involving the entry of value in field
 E2_CODRET, you need to use function SetFuName("FINA050") before running MSExecAuto(),
 because a validation exists in X3_VALID -(EXISTCPO("SX5","37"+M->E2_CODRET) .AND. Iif(FUNNAME() $ "FINA050|FINA750",FA050Natur(),.T.))
 of this field that will only calculate the tax by withholding code if FunName() is found in "FINA050".*/
\\
USER FUNCTION F050CODRET()
 LOCAL aArray := \{\}
  \\
 PRIVATE lMsErroAuto := .F.
 \\
 //Structure for other bills
 aArray := \{ \{ "E2_PREFIXO"  , "PAG"             , NIL \},;
    \{ "E2_NUM"      , "0001"            , NIL \},;
    \{ "E2_TIPO"     , "NF"              , NIL \},;
    \{ "E2_NATUREZ"  , "001"             , NIL \},;
    \{ "E2_FORNECE"  , "0001"            , NIL \},;
    \{ "E2_EMISSAO"  , CtoD("17/02/2012"), NIL \},;
    \{ "E2_VENCTO"   , CtoD("17/02/2012"), NIL \},;
    \{ "E2_VENCREA"  , CtoD("17/02/2012"), NIL \},;
    \{ "E2_VALOR"    , 5000              , NIL \},;
     \{ "E2_DIRF"     , "1", NIL \},;
    \{ "E2_CODRET"   , "3208"            , NIL \}\}
 \\
 SetFunName("FINA050") 
 MsExecAuto( \{ |x,y,z| FINA050(x,y,z)\}, aArray,, 3)  // 3 - Addition, 4 - Editing, 5 - Deletion
  \\
  \\
 If lMsErroAuto
  MostraErro()
 Else
  Alert("Bill successfully added")
 Endif
  \\
Return

OTHER INFORMATION

None available.

RELATED SUBJECTS

Reference document FINA050

Main value	BRL 6,000.00
PIS	BRL 0.00
COFINS	BRL 180.00
CSLL	BRL 0.00
Withholding Code	5960

Index

Objective

Mental Map

Main Fields

Automatic Execution

OVERVIEW

EXAMPLE OF USE

OTHER INFORMATION

RELATED SUBJECTS

Related Contents