## (ARG) Generating Legal Reports

This chapter discusses how to:

- Produce CITI reports.

- Process the SICORE withholding magnetic report.

- Work with the account ledger book.

- Work with the Fixed Asset Legalized Book report.

- Generate the Gross Income Perception report.

### Producing CITI Reports for Argentina

This section provides overviews of the CITI (Cruzamiento Informático de Transacciones Importantes) report, the Split Tax Validation program, the Process Purchase Documents program, the Company's Credit Notes program, and the CITI Report Text File program; and discusses how to:

- Run the Split Tax Validation report.

- Set processing options for Split Tax Validation (R76A8900).

- Run the Process Purchase Documents program.

- Set processing options for Process Purchase Documents (R76A8092).

- Run the Process Own Credit Notes report.

- Set processing options for Process Own Credit Notes (R76A8093).

- Run the Generate Text File program.

See Also

Setting Up Credit Invoice Status Rules for Argentina

Reclassifying Fiscal Credit for Argentina

#### Understanding the CITI Report

The Public Income Federal Agency (AFIP), through General Resolution 781/00, established the need for companies to report their fiscal credit on a monthly basis.

You must report fiscal credit information for these transactions:

- Purchase transactions, including credit notes whose fiscal credit has been reclassified as final.

- Credit notes issued by the company.

You submit fiscal credit information to the fiscal authority using the CITI (Cruzamiento Informático de Transacciones Importantes) Purchase V2.0 application provided by the AFIP, which allows you to import data from a personal computer.

Considerations for Credit Notes

The system determines which vouchers should be included in the CITI report. Only those transactions whose fiscal credit has been considered final for the month being considered are included in the report.

Not all credit invoices are included in the monthly CITI report because some may have been sent to a loss account instead of to the final fiscal credit account.

Note. It is recommended that you run the AP Credit Invoice V.A.T. Restatement program (R76A0052) to reclassify all the vouchers for the month that you are processing before you generate the CITI report.
It is also recommended that you run the V.A.T. Purchasing Ledger program (R760499A) in final mode before you generate the CITI report.

You must set up a credit invoice status rule for the CITI event, with the status in the Credit Invoice Status From field that is required to include the credit invoices in the CITI, and the status in the Credit Invoice Status To field to which the credit invoices are changed after being included in the CITI report. The Credit Invoice Status From status is applied after the credit invoices have been reclassified.

The CITI report verifies that credit invoices have the required status defined in the Credit Invoice Status From field. Credit invoices without this status are excluded and are listed in the Work Center.

When you generate the CITI report in final mode, the status of the credit invoice is updated. If you need to regenerate the CITI report, you must create a new status rule to include credit invoices that have already been processed.

Considerations and Limitations of the AFIP CITI Application

You can import data in the AFIP CITI application in either of these modes:

- File with no processing

- Grouping and ledgering file

The AFIP CITI application considers the file to be a file with no processing if the information that is being imported was generated in detail. That is, the import file contains a record for each transaction, regardless of the amount of fiscal credit. This option requires more processing time because the AFIP CITI application has to summarize those transactions with a fiscal credit lower than 500.

The AFIP CITI application considers the file to be a grouping and ledgering file if the information that is being imported was generated from the summary of the transactions with fiscal credit does not exceeding 500. This option uses less processing time because the AFIP CITI application imports the information only.

You can choose which of these two options to use by completing the processing options for the minimum amount of fiscal credit for the Process Purchase Documents program (R76A8092) and the Process Own Credit Notes program (R76A8093). If you specify 0 in these processing options, the AFIP CITI application processes the file with no processing. If you specify 500,00 in these processing options, the AFIP CITI application processes the file as a grouping and ledgering file.

Beginning and Final Positions

This table shows the beginning and final positions of the information in the text file that you must indicate the first time that you import data in the AFIP CITI application:

Denominación del campo | Desde | Hasta
Tip de Comprobante | 001 | 002
No de Comprobante | 003 | 014
Fecha del Comprobante | 015 | 022
C.U.I.T. del Informado | 023 | 033
Apelido y Nombre o Denominación | 034 | 058
Impuesto Liquidado | 059 | 070
C.U.I.T. Vendedor | 071 | 081
Denominación Vendedor | 082 | 106
IVA Comisión | 107 | 118

Fiscal Credit Determination

Tax percentages to be taken are defined as indicated:

- For purchases, the tax percentage to be taken corresponds to bucket 1 of the voucher tax area.

  This tax is also reported on the V.A.T. Purchasing Ledger as fiscal credit. Other kinds of taxes that are connected to the voucher, such as perceptions, internal taxes, and nonregistered VAT, are not reported.

- For the company's credit notes, the tax percentage to be taken corresponds to the tax codes for which a 1 is entered in the Sales Report Group Column field (ASGC) in the Tax Definitions program (P76A10).

Frequency and Number of Presentations

Resolution RG 781/00 established that each company (taxpayer) should submit the CITI report for every month, including January, February, and March. Therefore, you must run the complete process (process purchase documents, process the company's credit notes, and generate the text file) before beginning the process for the next month.

Processing Option to Delete the Output File

The Process Purchase Documents program (R76A8092) allows the CITI Report - ARG - 04 table (F76A8014) to be purged and then regenerated. The Process Own Credit Notes program (R76A8093) adds information to the transactions that were created by the Process Purchase Documents program. Therefore, you must run the Process Purchase Documents program first and the Process Own Credit Notes program second.

Error Messages

The error messages that might appear on the report act as warnings; they do not stop the process of importing the file from a personal computer. However, if the errors continue to appear, the application does not import the file successfully. You must correct the errors and reprocess the entire cycle.

#### Understanding the Split Tax Validation Program

You must run the tax split process before running any legal report in the JD Edwards EnterpriseOne Accounts Receivable or JD Edwards EnterpriseOne Sales Order Management system.

Tax rates have one or more tax codes that are associated with them and are used to calculate the tax amounts for specific taxes. These tax codes each have a defined account, and the tax rate has a global account.

The tax total is calculated when the voucher is generated and is assigned to the global account. You run the Split Tax Validation program (R76A8900) to reclassify the tax amounts from the global account to the accounts of the corresponding tax codes.

When you split taxes, the system updates the Business Unit (MCU), Object Account (OBJ), Subsidiary (SUB), Account ID (AID), and Processed (Y/N) (PRCS) fields in the Taxes - Tax Amount by Invoice Suffix table (F76A19) and the Processed (Y/N) (PRCS) field in the Invoice Total - ARG - 03B table (F76A09).

#### Understanding the Process Purchase Documents Program (R76A8092)

The Process Purchase Documents program (R76A8092) selects the purchase transactions for the period and processes them according to the rules established by RG 781 and the specifications of the AFIP CITI Purchase V2.0 application.

The Process Purchase Documents program generates the CITI Report - ARG - 04 table (F76A8014), which contains the selected transactions and the detail of the fiscal credits for the period. The system selects records from this table when you run the Generate Text File program (R76A8094) to create the CITI file that you process with the AFIP CITI application.

The Process Purchase Documents program includes credit invoices in the CITI report. Not all of the credit invoices are included because some of them might have been assigned to losses instead of to the final tax credit account and should not be included in the monthly CITI figures.

The credit invoices that are included must have the appropriate status. An error report lists vouchers that were not included because they had a different status.

When you run the Process Purchase Documents program in final mode, the system updates the credit invoice status. If you want to rerun the Process Purchase Documents program, you must create a new CITI rule that includes credit invoices which have already been processed.

This process runs in batch mode and uses data selection that is based on the supplier's current account.

You can run the Process Purchase Documents program in summary or detail mode, depending on how you want to process the report in the CITI application.

The Process Purchase Documents program generates a report containing information about the transactions that will be included in the CITI file.

Any errors that occur during processing are listed in the report:

- Invalid Company CUIT

- Invalid Supplier CUIT

- Check Transaction Sign

  This error indicates that a transaction with a legal document type of 42 and a positive sign has been processed. The AFIP uses legal document type 42 to identify transactions that deduct fiscal credit. The legal document type or the transaction sign cannot be corrected. In this case, correct the mistake and reprocess the transaction.

- Salesperson Data is Missing

  If a transaction with a legal document of 60 or 63 (transactions with middlemen) is being used, the AFIP requires that information about the salespersons who are related to the middlemen be included. No established and standard method exists about how each company records this information. Each company should obtain the relevant information according to its own process.

Note. You must run the Split Tax Validation program before you run the Process Purchase Documents program.

Data Selection for Process Purchase Documents (R76A8092)

This table shows the minimum data selection to include:

Where | Left Operand | Comparison | Right Operand
Where | BC Document Type (F0411) (DCT) | is not equal to | "$A,$B,$G,$I,$S,P1,PP"
And | BC G/L Posted Code (F0411) (POST) | is equal to | "D"
And | BC A/R - A/P - Miscellaneous Code 1 (F0411) (RP1) | is not equal to | "1"
And | BC Date - For G/L (and Voucher) - Julian (F0411) (DGJ) | is equal to | <Specify the appropriate date range.>
And | BC Company (F0411) (CO) | is equal to | <Specify the appropriate companies. The CITI application enables only one taxpayer a time. Therefore, all of the selected companies must have the same CUIT.>
And | BC Voucher included in VAT report - ARG (F760411A) (AINC) | is equal to | "Y"

You can add to or change this data selection, if necessary.

#### Understanding the Company's Credit Notes Program

The Process Own Credit Notes program (R76A8093) selects the credit notes that add fiscal credit to include them in the CITI report. These credit notes are taken from JD Edwards EnterpriseOne Accounts Receivable. The selected information is added to the CITI Report - ARG - 04 table (F76A8014).

This process runs in batch mode and uses data selection that is based on the supplier's current account.

You can run the Process Own Credit Notes program in summary or detail mode, depending on how you want to process the report in the CITI application.

The Process Own Credit Notes program generates a report containing information about the transactions that will be included in the CITI file.

Any errors that occur during processing are listed in the report. The report lists these errors:

- Invalid Company CUIT

- Invalid Customer CUIT

- Check Transaction Sign

  This error indicates that a transaction with a positive sign has been processed. According to the AFIP, only those sales operations that increase fiscal credit should be included. The problem might be that other kinds of transactions, in addition to credit notes, have been selected or the sign on a credit note is wrong. Correct the mistake and reprocess the transactions.

Note. You must run the Split Tax Validation program before running the Process Own Credit Notes program.

Data Selection for Process Own Credit Notes (R76A8093)

This table shows the minimum data selection to include:

Where | Left Operand | Comparison | Right Operand
Where | BC G/L Posted Code (F0411) (POST) | is equal to | "D"
And | BC Date - For G/L (and Voucher) - Julian (F0411) (DGJ) | is equal to | <Specify the appropriate date range.>
And | BC Company (F0411) (CO) | is equal to | <Specify the appropriate companies. The CITI application allows only one taxpayer a time. Therefore, all selected companies must have the same CUIT.>
And | BC Processed (Y/N) (F76A09) (PRCS) | is equal to | "Y"

This table shows the minimum data selection to include to process voided transactions:

Where | Left Operand | Comparison | Right Operand
Where | BC G/L Posted Code (F0411) (POST) | is equal to | "D"
And | BC Void Date - For G/L - Julian (F03B11) (VDGJ) | is equal to | <Specify the appropriate date range.>
And | BC Company (F0411) (CO) | is equal to | <Specify the appropriate companies. The CITI application allows only one taxpayer a time. Therefore, all of the selected companies must have the same CUIT.>
And | BC Processed (Y/N) (F76A09) (PRCS) | is equal to | "Y"

You can add to or change this data selection, if necessary.

#### Understanding the CITI Report Text File

The Generate Text File program (R76A8094) writes records to the Text Processor Header (F007101) and Text Process Detail (F007111) tables. You use the Text File Processor (P007101) to copy the text files from the F007101 and F007111 tables to text files that you can submit for tax reporting.

The Generate Text File program also creates a report containing information about the transactions that are included in the text file.

You can run the Generate Text File program in summarized or detail mode. The mode that you choose should correspond to the mode you will use in the AFIP Purchasing application.

Note. You must run the Split Tax Validation program before you run the Generate Text File program.

#### Running the Split Tax Validation Program (R76A8900)

Select Legal Reports (G76A03B2), Split Tax Validation.

#### Setting Processing Options for the Split Tax Validation Program (R76A8900)

Processing options enable you to specify the default processing for programs and reports.

Default

Mode | Enter 1 to run the program in final mode. Leave this processing option blank to run the process in proof mode.

#### Running the Process Purchase Documents Program (R76A8092)

Select CITI - General Resolution 781 (G76A781), Process Purchase Documents.

#### Setting Processing Options for the Process Purchase Documents Program (R76A8092)

Processing options enable you to specify the default processing for programs and reports.

General

1. Enter Company | Specify the company that is submitting the report. This information is included in the CITI report.
2. Minimum Amount | Specify the minimum amount of fiscal credit. If an amount exceeds the minimum, the transaction is listed in detail. If an amount is below the minimum, the transaction is included in a global register where all transactions not reaching the minimum are listed.
3. AFIP Document Type | Specify the AFIP document type that is used to generate the summarized register. The RG 781 indicates that the document type should be 00. Therefore, you should specify 00 in this processing option. If its value does not exist in UDC 76/DT, the system displays an error message. This situation does not produce subsequent problems; but if you do not want the error message to display, add the value to UDC 76/DT.
4. Tax Explanation Code | Specify the tax explanation code. Enter 1 if you are processing transactions with tax explanation code S. Otherwise, leave this processing option blank.
5. Mode | Specify whether the system runs the report in proof or final mode. Enter 1 to run the report in final mode or leave it blank to run the report in proof mode.

Output

1. Delete the Output File | Specify whether the system deletes the output file. Specify 1 if you want to purge the contents of the CITI Report - ARG - 04 table (F76A8014) before the transactions. Leave this processing option blank to add additional information to table F76A8014.

#### Running the Process Own Credit Notes Program (R76A8093)

Select CITI - General Resolution 781 (G76A781), Process Own Credit Notes.

#### Setting Processing Options for the Process Own Credit Notes Program (R76A8093)

Processing options enable you to specify the default processing for programs and reports.

General

1. Company | Specify the company that is submitting the report. This information is included in the CITI report.
2. Minimum Amount | Specify the minimum amount of fiscal credit. If an amount exceeds the minimum, the transaction is listed in detail. If an amount is below the minimum, the transaction is included in a global register where all of the transactions not reaching the minimum are listed.
3. Legal Document Type | Specify the legal credit note type A if you want the process to select the records. If you want to process all of the records that are based on the data selection, leave this processing option blank.
4. Processing Mode | Specify whether the system processes the records in proof or final mode. If you specify 1 in this processing option, the system updates the Processing Flag field (PFLG) in the Invoice Total - ARG - 03B table (F76A09) to indicate that the transaction has been included on a report. If you leave this processing option blank, the field is not updated.

Dates

5. Month | Specify the month for which you are submitting the CITI report.
6. Year | Specify the year for which you are submitting the CITI report. Enter the year as a four-digit number (for example, 2005).

#### Running the Generate Text File Program (R76A8094)

Select CITI - General Resolution 781 (G76A781), Generate Text File.

### Processing SICORE Withholding Magnetic Report for Argentina

This section provides overviews of SICORE processing, required data for accounts payable withholdings, required data for accounts receivable data, the Numeration by Payment Order for Profit Withholding requirement, the Step I – A/P Transaction program, the Step III – Self Withholding program, the Final Step (RG 738) program, and the SICORE text file; lists a prerequisite, and discusses how to:

- Run the Step I – A/P Transaction (RG 738) program.

- Set processing options for Step I – A/P Transaction (RG 738) (R76A8081).

- Run the Step II – A/R Transactions (RG) 738) program.

- Set processing options for Step II – A/R Transactions (RG) 738) (R76A94).

- Run the Step III – Self Withholdings program.

- Set processing options for Step III – Self Withholdings (R76A96).

- Run the Final Step (RG 738) program.

- Set processing options for Final Step (RG 738) (R76A8002).

- Run the Text File Processor (P007101) program.

#### Understanding SICORE Processing

AFIP General Resolution 738/99, which was published on December 20, 1999, in the Argentinean Legal Newspaper, establishes a new application through which withholdings, perceptions, or both, are reported. This AFIP SICORE application also provides the ability to print withholding certificates.

Companies must use the AFIP SICORE application to report their withholdings and perceptions to submit a sworn declaration on a monthly or per semester basis, and to generate payment forms and certificates. The AFIP SICORE application allows you to submit a file on a diskette or through electronic transmission.

Article II of RG 738/99 establishes required data that is related to perception certificates and must be submitted.

Note. You do not use the AFIP SICORE application to print perception certificates. You print perception certificates in JD Edwards EnterpriseOne along with the vouchers that originated them. You can substitute another document (for example, the legal invoice) for a perception certificate, if the other document contains the information that is required in RG 750.

Complete these general steps to generate SICORE:

1. If you are using the JD Edwards EnterpriseOne Accounts Payable system, run the Step I - A/P Transactions (RG 738) program (R76A8081).

2. If you are using the JD Edwards EnterpriseOne Accounts Receivable system, run the Step II - A/R Transactions (RG 738) program (R76A94).

3. If you make self withholdings, run the Step III - Self Withholdings program (R76A96).

4. Run the Final Step (RG 738) program (R76A8002).

5. Run the Text File Processor program (P) to create the flat file.

6. Use the Text File Processor (P007101) program to copy files from the F007101 and F007111 tables to text files that you submit for tax reporting.

#### Understanding Required Data for Accounts Payable Withholdings

This table shows the data that is required when reporting Accounts Payable withholdings to the fiscal authority:

Required Data Existing in UDC Tables

Set up these UDC table to supply required data:

See Setting Up UDCs for SICORE for Argentina.

UDC | Description
State & Province Codes (00/S) | The city, state, and postal code of the supplier must be set up in the JD Edwards EnterpriseOne Address Book system for correct exposition in SICORE.
ARG-DGI Transaction Doc. Type (76/DT) | You use the values in the ARG-DGI Transaction Doc. Type (76/DT) UDC to associate SICORE document types with AFIP legal document types by specifying the AFIP legal document type in the Codes field and the associated SICORE document type in the Special Handling Code field.
ARG-Profit WH Condition (76/03) | Add condition codes to the Special Handling Code field in the ARG-Profit WH Condition (76/03) UDC table.
Address Book Category Code (01/01-30) | To correct report VAT condition codes in the SICORE, set VAT Condition Codes in an Address Book Category Code (UDC 01/01-30). Set up the AFIP Condition Codes in the Special Handling Code field of the category code UDC that you choose.
ARG-A/B Legal Document Type (76A/A0) | You must set up these AFIP document types in the ARG-A/B Legal Document Type (76A/A0) UDC table.
Country's CUIT (76A/FJ) | For profit withholdings that are made to foreign beneficiaries, you must report the CUIT for the supplier's country. The system retrieves the CUIT from UDC 76A/FJ where they are set up for physical persons or entities.

Voucher Emission Date

The voucher emission date is the date of the voucher that generates the withholding. For profit withholdings that are generated by the payment of more than one voucher, you can use the date from any of the vouchers.

Document Number

The document number is the invoice legal number from the voucher that generates the withholding. For profit withholdings that are generated by the payment of more than one voucher, use the payment order number.

Voucher Amount

This data is the amount from the vouchers that generate the withholding.

Withholding Code

This table shows the AFIP withholding codes that are used in the JD Edwards EnterpriseOne Accounts Payable system:

Code | Description
217 | Profit Withholding
218 | Profit Withholding - Foreign Beneficiaries
767 | VAT Withholding

Regime Code

The regime code is required in the SICORE and is validated when the data is imported in the application.

Regime codes are derived from the legal concepts, which are connected to the withholding concepts that you set up for VAT and profit withholdings percentages. Therefore, you must verify the setup for VAT and profit withholdings.

Operation Code

For all withholdings, the operation code is 1.

Calculation Base

This data is the withholding calculation base.

For the credit note document type, report the difference between the original withholding and the proper withholding. With this document type, you must report:

- Credit note withholdings

- Withholdings that are generated by adjustment payments which were entered by documents that discount the withholding generated

For example, if the original withholding value was 100 ARS and the user entered a withholding adjustment value of 20 ARS, the withholding value would have been 80 ARS. In the Calculation Base field, specify 20 ARS (100 - 80).

Condition Code

In addition to setting up UDCs for condition codes, specify the category code that you are using for VAT condition codes for suppliers in the Code of VAT Withholding processing option on the Final Step (RG 738) program (R76A8002).

Withholding Amount

This withholding amount is made to the supplier. For the credit note document type, this field contains the withholding amount that should have been reported. For example, for a withholding of 100 ARS followed by a rectification of 20 ARS, the withholding amount to be reported is 80 ARS.

Excluded Percentage and Bulletin Date

After the withholding has been made, you must report the supplier excluded percentage for the tax. To report the excluded percentage correctly, you must set up an exempt percentage in the V.A.T WH - Exempt Percentages program (P760416A).

When you run the Step I - A/P Transactions (RG 738) program (R76A8081), the system verifies, based on the withholding type, that the withholding date is between the effective date and the expiration date to get the official bulletin emission date.

Supplier Document Type and Number

Set up AFIP document types in the ARG-A/B Legal Document Type (76A/A0) UDC table; and then you must specify both the AFIP document type and the document number on the A/B Additional Information - Revision form when you set up address book records for suppliers.

For foreign suppliers, specify the foreign document number that is defined by AFIP for each country. Do not enter the CUIT from the country to which the supplier belongs.

Original Certification Number

This field must be completed only for rectifications that increase or decrease a withholding made, or for withholdings from credit notes. The certification number that corresponds to the one given to the withheld subject must be reported.

You must correctly report the original certification number because the system uses this number to retrieve the legal invoice, the taxable amount, and the gross amount of the voucher that generated the original withholding.

You can review the relationship between the original withholding certificate and the rectification by choosing Rectification from the Row menu on the Work with Voucher Additional Information form of the F0411 Tag File Maintenance program (P760411A).

Increase Growth

Enter 0 in the Increase Growth field if a growth increase does not exist. Enter 1 if the voucher that originated the profit withholding was made to a foreign supplier who has a fiscal area defined in UDC 76A/AC.

Supplier Number and Document Type

The number and document type from the supplier for whom the withholding amount was retained must be reported.

Trade Name

This data is the trade name of the supplier. The system retrieves the alpha name from the supplier's address book record.

#### Understanding Required Data for Accounts Receivable Self Withholdings or Perceptions

This data is required when reporting Accounts Receivable self withholdings or perceptions to the fiscal authority.

Required Data Existing in UDC Tables

The system retrieves some required data from UDC tables.

See Setting Up UDCs for the Perception Report for Argentina.

UDC | Description
State & Province Codes (00/S) | You must include the state when supplying data about the perceived client. You specify the state in the client's address book record. AFIP has established a special codification for each state. You set up the special codification in the Special Handling Code field of UDC 00/S.
ARG-DGI Transaction Doc. Type (76/DT) | Set up values to associate SICORE document types with AFIP legal document types by specifying the AFIP legal document type in the Codes field and the associated SICORE document type in the Special Handling Code field.
ARG-Concept Code (76A/CI) | The general resolution includes a categorization of taxes. List these categories in the ARG-Concept Code (76A/CI).
ARG- Concept Code (76A/CR) | Use UDC 76A/CR to set up the activity codes under which the company can operate. Enter the codes and corresponding descriptions in conformity with General Resolution 738/99. The description is the concept of the perception certificate.
Perception Code SICORE (76A/PE) | You must associate the tax codes for the tax areas with the regime codes and the DGI tax code in the Perception Code SICORE (76A/PE) UDC table.

Percentage of Exclusion

You must include the percentage of exclusion for perceptions and the date of the government report when they were published. You set up this information in the Perception Exempt Percentages program (P76A8050).

See Setting Up Exclusion Percentages.

#### Understanding Numeration by Payment Order for Profit Withholding (RG 814/00)

The implementation of RG 738 - Phase III requires that certificates of tax withholding and profit withholding be numbered by issue place and fiscal year.

The new resolution impacts RG 814 as indicated:

1. AFIP provided a new software application to read the SICORE. This application is called SICORE - Withholding System Control - Version 3.0 - Update and can be downloaded from the internet.

   Resolution 814/00 does not require the use of this version, although you should always use the latest version which, at this time, is Version 4.0. This version meets the requirements of resolution 814/00.

2. The new numeration is optional so the tax withholding and profit withholding can be reported in the SICORE with the JD Edwards EnterpriseOne internal number. If you choose to use the JD Edwards EnterpriseOne internal number in the SICORE, you must use Version 3.0 - Update or Version 4.0. If you choose to use the numeration established by Phase III, you can use Version 3.0, Version 3.0 - Update, or Version 4.0. It is recommended that you use the latest version of the software.

3. A new valid value of Payment Order has been added to the Voucher Type field to the import file for SICORE. This value is used when a withholding includes several invoices (such as profit). This new value is optional.

JD Edwards EnterpriseOne software includes these modifications to meet these new requirements:

- The RG814 - Profit Withholding & Payment Order - ARG - 04 table (F76A8015) now stores the payment order number corresponding to profit withholding by supplier and company in the Payment Order Number - Argentina field (AOP).

- Step I of SICORE new populates the Payment Order field with the payment order number in the Payment Order Number - Argentina field (AOP) of the A/P Payment Detail Tag Table - ARG - 04 table (F760414A).

#### Understanding the Step I - A/P Transactions Program

The Step I - A/P Transactions (RG 738) program (R76A8081) generates the Company Relation RG 738/99 - ARG - 04 table (F76A8081) with information about the withholdings made to suppliers. The F76A8001 table, which conforms to the structure that is required by AFIP for the SICORE, is also generated and contains this information:

- Invoice letter.

- JD Edwards EnterpriseOne internal supplier.

- Withholding number.

- Company.

This information is not supplied during this step because this information is retrieved during the final step:

- Supplier document type.

- Supplier document number.

- Supplier country CUIT.

- Withholding condition of the subject for VAT tax.

The Step I - A/P Transactions (RG 738) program generates an error report and a report that lists the selected records.

After you run this program for purchase transactions, you must run a version for voids. When you run the version for voids, set up the processing options in the same way as you did on the version for purchase transactions, with these exceptions:

- Specify 1 in processing option 4 to process voids.

- Leave processing option 5 blank to avoid erasing the exit file.

- Specify 3 in processing options 9 and 10 on the Adjustment tab to process voids.

Data Selection for Step I - A/P Transactions (RG 738) (R76A8081)

Set the data selection for the Step I - A/P Transactions (RG 738) program as shown in this table:

Operator | Left Operand | Comparison | Right Operand
Where | BC Document Type (F0414) (DCT) | is equal to | "$G,$I"
And | BC Document Type - Matching (F0414) (DCTM) | is not equal to | "PG"

#### Understanding the Step III - Self Withholdings Program

You run the Step III - Self Withholdings program (R76A96) if you make self withholdings. This program adds records to the Generation SICORE's - Last Step -RG 738/99 - ARG - 04 table (F76A8001).

General Resolution 830/00 established in Anexo VII, point D, that companies subject to the exceptional regime must report an amount that is equal to the withholding amount which would have been made to them if they were not part of the exceptional regime. This information and amount must be reported according to the procedures, terms, and conditions that are defined by General Resolution 738/99 and its modifications (SICORE).

If the company is subject to the exceptional regime, you must run the Step III - Self Withholdings program.

#### Understanding the Final Step (RG 738) Program

The TXT Generation program (R76A8082) writes text files to the Text Processor Header (F007101) and Text Process Detail (F007111) tables. You use the Text File Processor (P007101) to copy the text files from the F007101 and F007111 tables to text files that you can submit for tax reporting.

See Working with the Text File Processor.

#### Prerequisite

Run the Split Tax Validation program (R76A8900).

#### Running the Step I - A/P Transactions (RG 738) Program (R76A8081)

Select SICORE RG 738/99 (G76A738), Step I - A/P Transactions (RG738).

#### Setting Processing Options for the Step I - A/P Transactions (RG 738) Program (R76A8081)

Processing options enable you to specify the default processing for programs and reports.

General

1. Date from: and 2. Date to: | Enter the beginning and ending dates for the date range.
3. Proof or Final Mode | Enter 1 to run the report in final mode. Leave this processing option blank to run the report in proof mode.
4. Enter '1' if you want to process void withholdings | Enter 1 to process voided withholdings. Leave this processing option blank to prevent the system from processing voided withholdings.
5. Enter '1' if you want delete all withholding records of output file. | Enter 1 to delete all records in the output file. Enter 2 to delete withholding records for the range of dates specified in the Date From and Date To processing options. Leave this processing option blank to preserve the records in the output file.

Tax AP

6. Enter the VAT Tax Code. | Enter the VAT tax code.
7. Enter the Profit Tax Code for Local Suppliers | Enter the profit tax code for local suppliers.
8. Enter the Profit tax Code for Foreign Suppliers. | Enter the profit tax code for foreign suppliers.

Adjustment

Document Type of Invoices | Specify the document type for adjusted or voided invoices.
Document Type of Credit Notes | Specify the document type for adjusted or voided credit notes.

Legal Number

Withholding Legal Number | Enter 1 to use the withholding legal number.
Voids | Enter 1 to generate in the work file the voids from the same month.

#### Running the Step II - A/R Transactions (RG 738) Program

Select SICORE RG 738/99 (G76A738), Step II - A/R Transactions (RG 738).

#### Setting Processing Options for the Step II - A/R Transactions (RG 738) Program (R76A94)

Processing options enable you to specify the default processing for programs and reports.

General Option

1. Column of VAT | Enter a value that exists in the ARG - Item ASGC Allowed Values (76A/B4) UDC table to specify the column to which VAT amounts are written. Generally, VAT amounts are written to column 3.
2. Initial Date | Enter the beginning of the range of dates for which you process records.
3. Final Date | Enter the final date of the range of dates for which you process records.
4. AR or AP Final Mode | Specify whether the system processes both accounts receivable and accounts payable records in final mode. Specify 1 if you are processing accounts receivable records only in the final process. Leave this processing option blank if you are including accounts payable records in the final process.
5. Final Mode or Proof Mode | Specify whether the system processes records in proof or final mode. Enter 1 to run the process in final mode. When you run the process in final mode, the system enters a 1 in the Processing Flag field (PFLG) in the Invoice Total - ARG - 03B table (F76A09).
6. RG 738 | Enter Y to run the process according to RG 738.
7. Deleting Records | Specify whether the system deletes all of the existing records between the initial and final dates before running the process. Enter Y to delete records within the processing date range. Leave this processing option blank to delete all existing records.

#### Running the Step III - Self Withholdings Program

Select SICORE RG 738/99 (G76A738), Step III - Self Withholdings.

#### Setting Processing Options for the Step III - Self Withholdings Program (R76A96)

Processing options enable you to specify the default processing for programs and reports.

General

1. Date From and 2. Date Thru | Specify the date from or the date through which transactions should be included for processing.
3. Final Mode or Proof Mode | Specify whether the system processes records in proof or final mode. Enter 1 to run the process in final mode. When you run the process in final mode, the system updates the User Reserved Amount field (URAT) in the Receipts Header table (F03B13), which prevents the records from being processed again.

RG 830

4. RG 830 - SICORE Generation | Specify whether the system runs the process as part of SICORE. Enter Y to run the process as part of SICORE. Leave this processing option blank to run it as an independent process.
5. Add Rows or Delete | Specify whether the system adds rows to existing records or deletes existing records. Enter 1 to add to the existing records. Leave this processing option blank to delete existing records before adding new ones.
6. Tax Code | Specify 217, which is the profit code.

#### Running the Final Step (RG 738) Program

Select SICORE RG 738/99 (G76A738), Final Step (RG 738).

#### Setting Processing Options for the Final Step (RG 738) Program (R76A8002)

Processing options enable you to specify the default processing for programs and reports.

General

1. Add Records or Delete | Specify whether the system adds to existing records. Enter 1 to add to the existing records. Leave this processing option blank to delete existing records before adding new ones.
2. Category Code | Specify the address book category code in which you define the AFIP supplier or customer condition.
3. Tax ID | Specify the generic Tax ID for taxpayers who have not provided a tax ID number.

Default Codes A/P

1. Code of VAT Withholding | Specify the VAT withholding code.
2. With Address in the Country | Enter the VAT code for a domestic supplier.
3. With Address in the exterior | Enter the VAT code for a foreign supplier.

Default Codes A/R

1. Enter V.A.T. Perception Code and 2. Profit Perception | Specify the tax code that is defined in the system.

#### Running the TXT Generation Program (R76A8082)

Select SICORE RG 738/99 (G76A738), TXT Generation.

### Working with the Account Ledger Book for Argentina

This section provides an overview of registration information and discusses how to:

- Add registration information for the Account Ledger Book.

- Generate the Account Ledger Legalized Book (R76A8020).

- Set processing options for the Account Ledger Legalized Book program (R76A8020).

#### Understanding Registration Information for the Account Ledger Book

The Legal Journal Book lists the general ledger transactions for a period of time. You run the Account Ledger Legalized Book program (R76A8020) to generate the Legal Journal Book.

You must set the general ledger registration information before you generate the Legal Journal Book. The general ledger registration information includes the beginning credit and debit balances for each period.

#### Forms Used to Set Up the Legal Journal Book

Form Name | FormID | Navigation | Usage
Work With G/L Registration | W094041A | Account Ledger Legalized Book (G76A09), Registration Number | Verify that the registration information exists for the company.
G/L Registration Revision | W094041B | On the Work With G/L Registration form, click Add. | Add registration information for the company.

#### Adding Registration Information

Access the G/L Registration Revision form.

Calendar Year | Enter the calendar year for this calendar.
Century | Enter the calendar century associated with the year. Enter is the first two digits of the year. For example, 19 indicates any year beginning with 19 (1998, 1999), 20 indicates any year beginning with 20 (2000, 2001), and so on.
Registration Number | Enter the number of the last Legal Journal Book that you generated. The system assigns the next number when you generate the Legal Journal Book for the next period.
Debit and Credit | Enter the debit amounts or the credit amounts that are the balances at the beginning of the periods that are defined in the Date Fiscal Patterns table (F0008).

#### Generating the Account Ledger Legalized Book

Select Account Ledger Legalized Book (G76A09), Account Ledger Legalized Book.

#### Setting Processing Options for Account Ledger Legalized Book (R76A8020)

Processing options enable you to specify the default processing for programs and reports.

Mode

1. Processing Mode | Leave this processing option blank to generate the report in proof mode. When run in proof mode, the report does not update any tables. Enter 1 to generate the report in final mode and update the page numbers, journal entries, and balances in the G/L Registration Balance table (F70404), and to print the report with titles and page numbers. Enter 2 to generate the report in final mode and update the page numbers, journal entries, and balances in table F70404, and to print the report without page numbers.
2. Pending transactions | Enter 1 to check for transactions that are dated before the current period and do not have journal numbers assigned. If you leave this processing option blank, the system does not check for pending transactions. Warning! The system verifies pending transactions in proof mode only.
3. Process by Batch Number | Specify whether the system processes by batch number. Values are: Blank: Does not process by batch number. 1: Processes by batch number. Important! If you have summarized batches, you must set this processing option to 1.
3. Ledger Type Check Pending Transactions | Enter a value that exists in the Ledger Type (09/LT) UDC table to specifies the type of ledger. You can set up multiple, concurrent accounting ledgers within the general ledger to establish an audit trail for all transactions.

Dates

1. From Date and 2. Thru Date | Specify the beginning or the end of a range of dates that the system uses to select records to process.

Company

Legal Company | Specify the company that is generating the report. This company must be set up in the Registration Number program (P094041). The report assigns the journal number, based on information that is set up in this program. If you leave this processing option blank, the report uses the information for company 00000 in the Registration Number program.

Options

1. Select Account Number Category Code | Specify the Account Number Category Code to print on the report. The only values are 21, 22 and 23. Leave this processing option blank to print the account number.

Registration

Registration Number Assignment | Leave this processing option blank to assign a registration number for each document. Enter 1 to assign registration numbers for each journal entry line.

Adjustments

Registration Date | Specify the date to use to complete the Date - Updated field (UPMJ) in the Account Ledger table (F0911) when the report is run in final mode. If you leave this processing option blank, the report does not update this field.
Registration Number | Specify the method the system uses to assign registration numbers. Values are: Blank: Use the next available registration number for the current fiscal year. 1: Number the adjustments starting with the next available number for the previous fiscal year. This method is not recommended.

Page

1. Page Numbering | Specify the method the system uses for page numbering. Values are: Blank: Number pages using the next number setup. 1: Number pages from 1 to N.
2. Document Type | Enter a value that exists in the Document Type (00/DT) UDC table to specify the document type setting for the page number.
3. Number Pages by Company | Specify whether the page number setting is by company. Values are: Blank: Company and fiscal year. 1: Company.
4. Enter Lines Per Page | Specify the printer parameter for the number of lines per page. The default is 46 lines for paper size A4.

### Working with the Fixed Asset Legalized Book for Argentina

This section provides an overview of the Fixed Asset Legalized Book, lists a prerequisite, and discusses how to:

- Run the Fixed Asset Legalized Book program.

- Set processing options for the Fixed Asset Legalized Book program (R76A1244).

#### Understanding the Fixed Asset Legalized Book

You use the Fixed Asset Legalized Book program (R76A1244) to generate the Annex A report.

Technical Resolution 9 and the General Inspection of Justice require a monthly presentation of the accumulated depreciation or appreciation of goods of use. The report must include different fixed assets groups, including the advance payments to vendors by purchase of goods of use and works in progress. For each of these items, the report must list the beginning balance, additions, disposals, transfers of works in progress, transfers of fixed assets, and the accumulated depreciations.

The Annex A is a legal report that lists, by fixed assets group (lands, machineries, vehicles, works in progress, and so on), the beginning balance for the fiscal year and a summary of the movements of the year through the report date, classified in columns by additions, disposals, receipted transfers, completed transfers. These columns are grouped by movements on original value/asset cost accounts and accumulated depreciation accounts.

#### Prerequisite

Before completing the tasks in this section, set up the Anexo A Column Type (76A/12) UDC table.

#### Running the Fixed Asset Legalized Book Program (R76A1244)

Select Fixed Asset Legalized Book (G76A12), Fixed Asset Legalized Book.

#### Setting Processing Options for the Fixed Asset Legalized Book Program (R76A1244)

Processing options enable you to specify the default processing for programs and reports.

Dates

1. Beginning Date for Report and 2. End Date for Report | Specify the beginning or the end of a range of dates that the system uses to select records from the Account Ledger table (F0911).

Accounts

In the first two ranges (original value), specify the range of the original value accounts to use to select transactions from the F0911 table. In the second two ranges (depreciation value), specify the range of accumulated depreciation accounts to use to select transactions from the F0911 table. In both cases, specify the object accounts.

3. First Range Original Value - From Account | Specify the beginning of the first range for the original value accounts.
3. First Range Original Value - Thru Account | Specify the end of the first range for the original value accounts.
3. First Range Depreciation - From Account | Specify the beginning of the first range for the depreciation accounts.
3. First Range Depreciation - Thru Account | Specify the end of the first range for the depreciation accounts.
3. Second Range Original Value - From Account | Specify the beginning of the second range for the original value accounts.
3. Second Range Original Value - Thru Account | Specify the ending of the second range for the original value accounts.
3. Second Range Depreciation - From Account | Specify the beginning of the second range for the depreciation accounts.
3. Second Range Depreciation - Thru Account | Specify the ending of the second range for the depreciation accounts.

Participation

Specify the participate percentage for the company.

4. Percentage of Participation | Specify the percentage the system uses to multiply the amounts. The default value is 1.

Outfile

5. Save data to outfile | Enter 1 to have the system save the data in the F76A1244 table to a file. Leave this processing option blank to prevent the system from saving the data to a file.

Ledger Type

6. Ledger Type | Enter a value that exists in the Ledger Type (09/LT) UDC table to specify the type of ledger. If you leave this processing option blank, the system uses ledger type AA. You can set up multiple, concurrent accounting ledgers within the general ledger to establish an audit trail for all transactions.

Business Unit

7. Business Unit | Specify the business unit that is submitting the report.

### Generating the Gross Income Perception Report for Argentina

This section provides an overview of the Gross Income Perception (R76A93) program, lists prerequisites, and discusses how to:

- Run the Gross Income Perception program.

- Set processing options for the IIBB Perception program (R76A93).

#### Understanding the Gross Income Perception (R76A93) Program

The IIBB Perception program (R76A93) generates a list of vouchers that is issued with gross income (IIBB) perception. This report lists the amounts that have been deposited in AFIP accounts for the trimester.

The IIBB Perception program generates a printed report and an optional flat file named F76A93.

Structure of the F76A93 Flat File

This table describes the structure for record type 1:

Record | Content
cRecordNumber | Record code (1)
szIIBBCompanyNumber | Informant company gross incomes number
mnInformedYear | Year to be informed
mnInformedMonth | Month to be informed
mnWithholdingAmount | Withholding amount
mnIIBBDocNumbMonth | Voucher number
cFortnightNumber | Quarter
cCheckDigit | Voucher security digit
szIIBBPerceptionTapeArgentina0 | Filler (white spaces)

This table describes the structure for record type 2:

Record | Content
cRecordNumber | Record code (2)
szIIBBCompanyNumber | Informant company gross incomes number
mnInformedYear | Year to be informed
mnInformedMonth | Month to be informed
cFortnighNumber | Quarter
szIIBBCustomerNumber | Customer gross incomes number
szVATNumber | Address book CUIT number
mnWithholdingAmount | Amount total perceived
szIIBBPerceptionTapeArgentina0 | Filler (white spaces)

#### Prerequisites

Before completing the tasks in this section, set up these UDCs:

- State & Province Codes (00/S).

- ARG-DGI Transaction Doc. Type (76/DT).

- ARG-Concept Code (76A/CI).

- ARG- Concept Code (76A/CR).

- Perception Code SICORE (76A/PE).

See Setting Up UDCs for the Perception Report for Argentina.

#### Running the IIBB Perception Program (R76A93)

Select Legal Reports (G76A03B2), IIBB Perception.

#### Setting Processing Options for the IIBB Perception Program (R76A93)

Processing options enable you to specify the default processing for programs and reports.

General Option

1. Enter the Tax Code corresponding to IIBB perception. | Specify the tax code UDC 76A/TC that corresponds to IIBB perception.
2. Enter the fortnight number. | Specify the fortnight number.
3. IIBB D.G.I. voucher number including security digit. , 5. IIBB D.G.I. voucher number including security digit. , and 7. IIBB D.G.I. voucher number including security digit. | Specify the IIBB D.G.I. voucher number (including security digit) for the first through third months of the quarter to be processed.
4. Security deposit Amount. , 6. Security deposit Amount. , and 8. Security deposit Amount. | Specify the security deposit amount for the first through third months of the quarter to be processed.
9. Enter '1' if you want to generate both report and output file. | Specify 1 to generate both a flat file and a printed report. The flat file is named F76A93. If you leave this processing option blank, the program generates a printed report only.
10. Enter the quarter number that is processed. | Specify the number of the quarter that the system processes for the report.