This chapter contains the following topics:
Section 16.1, "Understanding VAT Reports in Argentina (Release 9.1 Update)"
Section 16.3, "Generating VAT Reports for RG 3685 (Release 9.1 Update)"
The fiscal authorities in Argentina regulate how companies issue legal documents for their transactions, how they maintain those records, and the format that companies must use to generate reports depending on the characteristics of the company and economic activity.
You can use JD Edwards EnterpriseOne Localizations for Argentina to generate the VAT reports that your company is required to generate and present. The V.A.T. Purchasing Ledger (R760499A) program and the Sales VAT Tax Subdiary program (R76A8060) process the information of your transactions and generate reports that meet the format and content requirements for different regulations. You can use these programs to generate the following reports:
You run the V.A.T. Purchasing Ledger program (R760499A) to produce the V.A.T. Purchase Ledger RG 1361 magnetic file, and you run the Sales VAT Tax Subdiary program to generate the Sales VAT Ledger file. You must specify in the processing options on the RG 1361 tab, that you want to generate the text files according to RG 1361.
See Section 16.2.1.1, "Understanding the V.A.T. Purchasing Ledger Program for RG 1361"
See Section 16.2.2.1, "Understanding the Sales V.A.T. Ledger Program for RG 1361".
Companies included in this regime can run the V.A.T. Purchasing Ledger program (R760499A) and the Sales VAT Tax Subdiary program (R76A8060) to generate the RG 1672 C.I.T.I. (Cruzamiento Informático de Transacciones Importantes) magnetic files. You must specify this in the processing options for the programs in the Magnetic Support tab. The system generates a text batch in the Text Processor Header (F007101) and Text Process Detail (F007111) tables. You use the Text File Processor (P007101) program to create a text file with the information from these tables.
The regulation requires that all companies reached by it must report information about their transactions in several text files through a web application using the website for AFIP (Administracion Federal de Ingresos Públicos, the national fiscal authority in Argentina). Use these programs to generate the following required reports:
Use the V.A.T. Purchasing Ledger program (R760499A) to generate:
The purchases text file with voucher information
The purchases VAT text file with VAT amounts by voucher and tax rate
The Imports text file with VAT amounts by tax rate
The services imports text file with voucher and payment information
See Section 16.3.3, "Generating VAT Purchases Reports for RG 3685".
Use the Sales VAT Tax Subdiary program (R76A8060) to generate:
The Sales text file with invoice information
The Sales VAT text file with VAT amounts by invoice and tax rate
See Section 16.3.4, "Generating VAT Sales Reports for RG 3685".
Use the RG 3685 Purchase and Sales Information program (R76A010) to generate the Header text file with information about the company and the period.
See Section 16.3.5, "Generating the RG 3685 Purchases and Sales Information Text File".
You must submit the value-added tax (VAT) report to the AFIP tax authority every month. You run the V.A.T. Purchasing Ledger program to produce a report of the fiscal credit for the period. This report includes information about the vouchers upon which the VAT was charged.
|
Note: Vouchers must be posted to be included in the V.A.T. Purchasing Ledger. The version of the Post Vouchers to GL program (R09801) that you use must have the Update Tax File processing option set to 3 to update the Taxes (F0018) table for all tax explanation codes. |
The V.A.T Purchasing Ledger program includes credit invoices. Only credit invoices with fiscal credit that is considered definitive for the month are included. Not all credit invoices are included because they might have been assigned to losses instead of the final credit account.
After you print the Sales VAT Subledger, you can issue a magnetic version for backup.
Leave the Transaction Date - From processing option blank so that invoices from previous periods that might still be pending in accepted or rejected status are included.
When you run the V.A.T Purchasing Ledger program in final mode, the system updates these fields:
The Voucher included in the VAT report - ARG field (AINC) in the A/P Ledger Tag Table - ARG (F760411A) table.
The Voucher Included in the RG 1361 field (AIRG) in the F760411A A/P Tag File - ARG (F76A411T) table.
Use data selection to specify which document types should be excluded from the V.A.T. Purchasing Ledger. For example, you might set up this data selection:
| Operator | Left Operand | Comparison | Right Operand |
|---|---|---|---|
| Where | BC Document Type (F0411) (DCT) | is not equal to | $I, $B, $G, PP |
| And | BC GL Posted Code (F0411) (POST) | is equal to | D |
| And | BC Voucher included in VAT report - ARG (F760411A) (AINC) | is equal to | <Blank> |
| And | BC AR - AP - Miscellaneous Code 1 (F0411) (RP1) | is not equal to | 1 |
Processing options enable you to specify the default processing for programs and reports.
Specify whether the system calculates the VAT withholding percentage or the percentage is taken from the tax area master file. Values are:
Blank: Use the percentage from the tax area master file.
1: Calculate VAT withholding percentage.
Enter a value that exists in the Document Type (00/DT) UDC table to specify the document type that will identify the prepayment of the final invoice voucher.
Specify whether to run the report in proof or final mode. Values are:
Blank: Run V.A.T. purchasing report in proof mode.
1: Run V.A.T. purchasing report in final mode.
Specify whether to print the withholding amount column in the report. Values are;
Blank: Print withholding amount column.
1: Do not print withholding amount column.
Specify the company for which you run the report.
Specify the sucursal code for the report.
Specify the company number for which exists the next numbering scheme for the next page number.
Enter a value that exists in the Document Type (00/DT) UDC table to specify the document type to assign to the next page number.
Specify the first date of the range, or the last date of the range used to select transactions.
Specify if the system generates an output file according to the format specified for RG 3419, the format for RG 1361, or the format for RG3685. Values are:
1: The system uses the RG 3419 format.
2: The system uses the RG 1361 format.
3: The system uses the RG 3685 format. If you enter 3, the system generates a text batch in the text file processor tables.
If you enter any other value or leave the field blank, the system does not generate any output files.
Specify if you want to generate the Purchase VAT Report files for RG3685 or if you want to generate the Service Imports file for RG3685.
When you work with VAT reports for RG3685 you must enter a value of 3 in the processing option Output Format and set this option to the correct value.
Values are:
Blank: The system generates the following files:- The purchases text file with voucher information (RG3685 Purchase Voucher)- The purchases VAT text file with VAT amounts by voucher and tax rate (RG3685 VAT Rate Voucher)- The purchases imports text file with VAT amounts by tax rate (RG3685 VAT Imports).
1: The system generates only the services imports text file with voucher and payment information (RG3685 Service Imports).
If you enter the value 1 in this option, the system uses the From and Thru Dates entered in the Dates tab as the period when the payment takes place.
Select a value from the Service Imports Document Type UDC table (76A/SI) to specify the document type for Service Imports transactions that the system uses when you run the report to generate the 3685 Service Imports file.
Specify how to print details. Values are:
Blank: Print only details.
1: Print details and totals by operation.
2: Print only totals.
Enter 1 to print date of execution.
Enter 1 to print the Tax Area Description from the Tax Area of the Supplier Master (F0401) table. Leave this processing option blank to print the Tax Area description from the Tax Area of the document.
Enter the Address Book Category Code number in which the vendor responsible type is stored.
Enter 1 to include additional information in the output file.
You use the Sales VAT Tax Subdiary program to generate the Sales VAT Ledger and to generate the text files to report fiscal information according to RG 1361, RG 1672, and RG 3685.
The Sales VAT Ledger is a legal report that you submit monthly to report the fiscal debits. All sales transactions for the month are included in the report. Transactions must be posted and reclassified to be included in the report.
You can use the Sales VAT Tax Subdiary program to generate a magnetic file that you can submit to the fiscal authority. You specify the format of the magnetic file in the processing option 8 on the Magnetic Support tab:
If you specify 2 in this processing option to run the Sales VAT Ledger RG 1361 magnetic file, the system creates a text file in the location that you specify in the processing options.
See Section 16.2.2, "Generating the Sales VAT Ledger for RG 1361".
If you specify 3 in this processing option to run the RG 1672 C.I.T.I. magnetic file, or 4 to generate the RG 3685 text files, the system generates a text batch in the Text Processor Header (F007101) and Text Process Detail (F007111) tables. You use the Text File Processor (P007101) program to create a text file with the information from these tables.
You can view any errors that occurred during processing in the Work Center.
The Sales VAT Ledger report includes the following information, which you can check in the PDF file that the process generates:
| Column | Description |
|---|---|
| Invoice Date | The emission date of the invoice. |
| Invoice Number | The invoice legal number. |
| Customer Name | The trade name or customer name. |
| DGI Document Type | The document type assigned by AFIP-for example, 080 for CUIT. |
| Fiscal Identification | A number that is assigned by AFIP that identifies the customer-for example, the CUIT number. |
| Tax Rate Description | A description of the tax rate that is used in the operation. |
| Gross Amount | The total gross amount. |
| Taxable Amount | The tax calculation base. |
| Non Taxable Amount | The amount on which taxes are not calculated (column 05). |
| Tax Amount | The calculated tax amount. |
| Tax Rate | The tax rate percentage by purchase order. |
The rest of the columns list the taxes that are calculated for each tax code. Typically, the tax codes are listed in this order:
Liable Registered
Liable Non Registered
VAT Perception
Exempt Operations
Non-taxable Amounts
Internal Taxes
Processing options enable you to specify the default processing for programs and reports.
Specify the company that must appear on the page header of the report.
Specify the issue place for the company.
Enter 1 to include VAT in the VAT percentage.
Enter 1 to include non-registered VAT in the VAT percentage.
Enter 1 to include VAT perception in the VAT percentage.
Enter 1 to include exempt operations in the VAT percentage.
Enter 1 to include non-taxable amounts in the VAT percentage.
Enter 1 to include external taxes in the VAT percentage.
Specify the column number to print the invoice non-taxable amounts with explanation code E and tax area with percentage not equal to zero (values 01 – 06).
Specify the beginning of the date range, or the end of the date range.
Enter 1 to run the program in final mode, or leave this processing option blank to run in proof mode. When you run the program in final mode, the system enters 2 in the Processing Flag field (PFLG) in the F76A09 table.
Specify the document type that the system uses to assign page numbers. The value that you enter must exist in the (00/DT) UDC table.
Specify if the system generates an output file according to the format specified for RG 3419, the format for RG 1361, or the format for RG3685. Values are:
1: The system prints the Sales VAT Ledger report.
2: The system uses the RG 1361 format.
3: The system uses the RG 1672 C.I.T.I. text file format. If you enter 3, the system generates a text batch in the text file processor tables.
4: The system uses the RG 3685 format. If you enter 4, the system generates a text batch in the text file processor tables (Release 9.1 Update).
Specify whether to print totals or details. Values are:
Blank: Print only details
1:Print totals and details by operations.
2: Print only totals.
Enter 1 to print the system date as the date of execution.
Enter 1 to print the description from the customer's tax area. Leave this processing option blank to print the description from the tax area of the document.
Specify the address book category code that you use to record the condition of the client.
Enter 1 to include the information from these fields in field 30 in the magnetic file:
Document Type (DCT)
Document (Voucher, Invoice, and so on) (DOC)
Document Company (KCO)
Document Company (KCO)
If you leave this processing option blank, the system completes field 30 in the magnetic file with zeros.
This section provides an overview of VAT reports requirements for RG 1361 and a detailed description of the record structure for each text file generated, and discusses how to:
Generate VAT Purchases Reports for RG 1361.
Generate VAT Sales Reports for RG 1361.
This section provides an overview of the V.A.T. Purchasing Ledger report and discusses how to:
Run the V.A.T. Purchasing Ledger program.
Set processing options for V.A.T Purchasing Ledger (R760499A).
You run the V.A.T. Purchasing Ledger program (R760499A) to produce the V.A.T. Purchase Ledger RG 1361 Magnetic File. To run this program for RG 1361, you must complete the processing options on the RG 1361 tab.
|
Note: You must run the AP Credit Invoice VAT Restatement program (R76A0052) to reclassify all of the vouchers for the month before you run the V.A.T Purchasing Ledger program. For companies that submit the CITI report, it is recommended that you generate the CITI report after you run the V.A.T. Purchasing Ledger program. |
See Section 8.5, "Reclassifying Fiscal Credit for Argentina".
You must set up credit invoice activity rules (for example, IVACOMPRAS) with the From status that is required to include credit invoices in the V.A.T. Purchasing Ledger and the To status that will be applied after the credit invoices has been included in the report. The From status must be the status that is applied by the AP Credit Invoice V.A.T. Restatement program.
The V.A.T. Purchasing Ledger program verifies that the credit invoices have the required From status defined in the activity rule. Any credit invoice without the correct status are omitted from the report and listed in the Work Center.
When you run the V.A.T Purchasing Ledger program in final mode, the system updates these fields:
The Credit Invoice Status field (ACIS) in the Credit Invoice Information (F76A24) table.
|
Note: If you want to rerun the V.A.T. Purchasing Ledger program, you must create a new IVACOMPRAS rule that includes credit invoices that have already been processed. |
The Voucher included in the VAT report - ARG field (AINC) in the A/P Ledger Tag Table - ARG (F760411A) table.
The Voucher Included in the RG 1361 field (AIRG) in the F760411A A/P Tag File - ARG (F76A411T) table.
|
Note: The magnetic file cannot display negative amounts. Instead, negative amounts are identified in the magnetic file with these legal document types:37 - Credit Note Voids. 38 - Invoice / Debit Note Voids. For example, the magnetic file cannot include a negative amount as: 01 10000- Instead, the amount is included as: 37 10000 This indicates that the amount is a Credit Note Void and is, therefore, a negative amount. |
Before you generate the RG1361 magnetic file, verify that each voucher in invoice group A, B, or C contains a CAI number and the expiration date for the CAI number.
When you generate the VAT RG1361 magnetic file, the system validates these conditions:
If the supplier issued the voucher with fiscal controller, the CAI number must exist in the F76A411H table and must not be blank. If this condition is not met, the system generates an error message.
If the supplier did not issue the voucher with fiscal controller, the system uses the default CAI number and expiration date for the supplier. If this information does not exist, the system generates an error message.
If the supplier did not issue the voucher with fiscal controller, and if table F76A411H has CAI information that is different from the supplier's default CAI information, the system generates an error message.
This table describes the design structure for record type 1:
| Field number | Type | Length | Decimals | Description |
|---|---|---|---|---|
| 1 | Alpha | 1 | 0 | Record type |
| 2 | Alpha | 8 | 0 | Voucher date |
| 3 | Alpha | 2 | 0 | Voucher type |
| 4 | Alpha | 1 | . | Fiscal controller |
| 5 | Alpha | 4 | 0 | Sales point |
| 6 | Alpha | 20 | 0 | Voucher number |
| 7 | Alpha | 8 | 0 | GL date |
| 8 | Alpha | 3 | 0 | Custom code |
| 9 | Alpha | 4 | . | Destination code |
| 10 | Alpha | 6 | 0 | Shipment number |
| 11 | Alpha | 1 | 0 | Shipment number verification digit. |
| 12 | Alpha | 2 | 0 | Vendor identification document code |
| 13 | Alpha | 11 | 0 | Vendor identification number |
| 14 | Alpha | 30 | . | Vendor name and surname |
| 15 | Alpha | 15 | 2 | Operation total amount |
| 16 | Alpha | 15 | 2 | Total concepts amount that are not part of the taxable amount |
| 17 | Alpha | 15 | 2 | Taxable amount |
| 18 | Alpha | 4 | . | VAT percentage |
| 19 | Alpha | 15 | 2 | Tax calculated |
| 20 | Alpha | 15 | 2 | Exempt operations amount |
| 21 | Alpha | 15 | 2 | Perceptions or VAT payment on account amount |
| 22 | Alpha | 15 | 2 | Perception amounts or National taxes payment on account |
| 23 | Alpha | 15 | 2 | Gross income perceptions amount |
| 24 | Alpha | 15 | 2 | City Council tax perception |
| 25 | Alpha | 15 | 2 | Internal tax amount |
| 26 | Alpha | 2 | 0 | Responsible type |
| 27 | Alpha | 3 | . | Currency code |
| 28 | Alpha | 10 | 6 | Exchange rate |
| 29 | Alpha | 1 | 0 | VAT percentage quantity |
| 30 | Alpha | 1 | . | Operation codes |
| 31 | Alpha | 14 | 0 | CAI |
| 32 | Alpha | 8 | 0 | Expiration date |
| 33 | Alpha | 75 | . | Additional information |
| . | . | 369 | . | . |
This table describes the design structure for record type 2:
| Field number | Type | Length | Decimals | Description |
|---|---|---|---|---|
| 1 | Alpha | 10 | . | Period |
| 2 | Alpha | 12 | 0 | Filled |
| 3 | Alpha | 31 | . | Record type 1 quantity |
| 4 | Alpha | 11 | 0 | Filled |
| 5 | Alpha | 30 | . | Company CUIT |
| 6 | Alpha | 15 | 2 | Filled |
| 7 | Alpha | 15 | 2 | Total operation amount |
| 8 | Alpha | 15 | 2 | Total concept amount that are not part of the taxable amount |
| 9 | Alpha | 4 | . | Taxable amount |
| 10 | Alpha | 15 | 2 | Filled |
| 11 | Alpha | 15 | 2 | Tax calculated |
| 12 | Alpha | 15 | 2 | Exempt operations amount |
| 13 | Alpha | 15 | 2 | Perceptions amounts or VAT payment on account |
| 14 | Alpha | 15 | 2 | Perceptions amount or national taxes payment on account |
| 15 | Alpha | 15 | 2 | Gross incomes perceptions |
| 16 | Alpha | 15 | 2 | City council tax perceptions |
| 17 | Alpha | 114 | . | Internal Tax amount |
| 18 | Alpha | 369 | . | Filled |
Before you complete the tasks in this section:
Run the AP Credit Invoice V.A.T. Restatement program (R76A0052) to reclassify all the month's vouchers that you want to process.
See Section 8.5, "Reclassifying Fiscal Credit for Argentina".
Set up status rule IVACOMPRAS to specify the status that credit invoices must have to be included in the subledger, as well as the status that should be assigned after the credit invoice has been incorporated in the report.
See Section 3.21, "Setting Up Credit Invoice Status Rules for Argentina".
Set up user-defined code (UDC) (76A/CS) to identify the codes that represent reclassified to losses by entering a 1 in the Special Handling Code field.
Select Monthly Reports (G76A121), V.A.T Purchasing Ledger.
This section provides overviews of the Sales VAT Tax Subdiary program and printing the Sales VAT Tax Subdiary report for RG1361, lists prerequisites, and discusses how to:
Run the Sales VAT Tax Subdiary program.
Set processing options for Sales VAT Tax Subdiary (R76A8060).
You can use the Sales V.A.T. Tax Subdiary program to generate a magnetic file to meet the requirements of RG 1361. To generate the Sales V.A.T. Ledger RG 1361 magnetic file, specify 2 in processing option 8 on the Magnetic Support tab.
Transactions must have been posted and reclassified to be included on the report.
When run in proof or final mode, the Sales V.A.T. Tax Subdiary program generates records in the Sales V.A.T. Tape File - ARG (F76A0394) table, and produces a paper report and a magnetic file. You can view any errors that occurred during processing in the Work Center. When you run the Sales V.A.T. Tax Subdiary program in final mode, the program marks the records as having been processed.
These error messages are warnings, which means that they do not prevent the magnetic file from being generated; they warn the user of problems that occurred during processing.
This is a partial list of possible error messages:
Error in the amount of operation.
The total of the gross amount line does not reconcile with the tax detail. You must verify the sum of the line and determine which amount is in error.
Error in taxable amount.
The taxable amount is incorrect. This amount must be greater than the VAT of the voucher and less than the gross amount. This validation is mandated by AFIP (Administracion Federal de Ingresos Públicos).
Difference in the amount of perception.
The amount calculated by the program for a VAT perception to a non-registered or un-categorized liability does not match the amount calculated by JD Edwards EnterpriseOne software. This error is generally caused by rounding differences due to the formula that AFIP uses.
The Sales V.A.T. Ledger RG 1361 magnetic file contains two types of records. Record type 1 lists each invoice by tax rate, and record type 2 lists totals.
This table describes the design structure for record type 1:
| Field Number | Type | Length | Decimals | Description |
|---|---|---|---|---|
| 1 | Alpha | 1 | 0 | Record type |
| 2 | Alpha | 8 | 0 | Invoice Date |
| 3 | Alpha | 2 | 0 | Invoice type |
| 4 | Alpha | 1 | . | Fiscal Controller |
| 5 | Alpha | 4 | 0 | Emission Serial |
| 6 | Alpha | 20 | 0 | Invoice number |
| 7 | Alpha | 20 | 0 | Invoice number thru |
| 8 | Alpha | 2 | 0 | Customer document type |
| 9 | Alpha | 11 | 0 | Customer document number |
| 10 | Alpha | 30 | . | Customer name |
| 11 | Alpha | 15 | 2 | Total Amount |
| 12 | Alpha | 15 | 2 | Total concepts amount that are not part of the taxable amount |
| 13 | Alpha | 15 | 2 | Taxable amount |
| 14 | Alpha | 4 | 2 | Tax Rate |
| 15 | Alpha | 15 | 2 | Tax calculated |
| 16 | Alpha | 15 | 2 | Tax calculated to RNI or perception to non- categorized |
| 17 | Alpha | 15 | 2 | Exempt operations amount |
| 18 | Alpha | 15 | 2 | Perceptions amount or national taxes payment on account |
| 19 | Alpha | 15 | 2 | Gross incomes perceptions amount |
| 20 | Alpha | 15 | 2 | City council perception amount |
| 21 | Alpha | 15 | 2 | Internal taxes amount |
| 22 | Alpha | 2 | 0 | Responsible type |
| 23 | Alpha | 3 | . | Currency code |
| 24 | Alpha | 10 | 6 | Exchange rate |
| 25 | Alpha | 1 | 0 | VAT percentages quantity |
| 26 | Alpha | 1 | . | Operation code |
| 27 | Alpha | 14 | 0 | CAI |
| 28 | Alpha | 8 | 0 | Expiration date |
| 29 | Alpha | 8 | 0 | Voucher void date |
| 30 | Alpha | 75 | . | Additional information |
This table describes the design structure for record type 2:
| Field Number | Type | Length | Decimals | Description |
|---|---|---|---|---|
| 1 | Alpha | 1 | 0 | Record type |
| 2 | Alpha | 6 | 0 | Period |
| 3 | Alpha | 29 | . | Filled |
| 4 | Alpha | 12 | 0 | Record type 1 quantity |
| 5 | Alpha | 10 | . | Filled |
| 6 | Alpha | 11 | 0 | Company CUIT |
| 7 | Alpha | 30 | . | Filled |
| 8 | Alpha | 15 | 2 | Operation total amount |
| 9 | Alpha | 15 | 2 | Total concepts amount that are not part of the taxable amount |
| 10 | Alpha | 15 | 2 | Taxable amount |
| 11 | Alpha | 4 | . | Filled |
| 12 | Alpha | 15 | 2 | Tax calculated |
| 13 | Alpha | 15 | 2 | Tax calculated to RNI or perception to non categorized |
| 14 | Alpha | 15 | 2 | Exempt operations amount |
| 15 | Alpha | 15 | 2 | Perceptions amount or national taxes payment on account |
| 16 | Alpha | 15 | 2 | Gross incomes perceptions |
| 17 | Alpha | 15 | 2 | City council perceptions amount |
| 18 | Alpha | 15 | 2 | Internal taxes amount |
| 19 | Alpha | 122 | . | Filled |
Run the Split Tax Validation (R76A8900) program to reclassify all of the month's transactions that you want to process.
See Chapter 5, "Setting Up the System for Argentinian Taxes".
See Section 15.1.6, "Running the Split Tax Validation Program (R76A8900)".
Select Legal Reports (G76A03B2), Sales VAT Tax Subdiary.
This section provides an overview of VAT reports requirements for RG 3685 and the process to work with these reports, a detailed description of the record structure for each text file generated, and discusses how to:
Generate VAT Purchases Reports for RG 3685.
Generate VAT Sales Reports for RG 3685.
Generate the Header text file for the RG 3685 VAT reports.
Companies in this regime are required to submit the RG 3685 VAT reports on a monthly basis. They must submit different text files with specific content and format requirements to the fiscal authorities through their website. JD Edwards extracts the information to populate the reports from your existing transaction and documents information.
In these reports, every record is informed as a line of characters that concatenate the information of the fields you must report. Every field has a specific amount of characters and a position in the line.
The amounts use fifteen positions, without including periods or commas. The last two positions out of the fifteen digits for an amount are reserved for decimals (cents). If an amount is a negative number, the first digit must be a minus symbol ("-").
The system completes with spaces or zeroes any piece of information that does not use all the positions reserved for the fields in the report.
To work with the VAT reports required by RG 3685, you:
Set up your system with standard information for your transactions. Information about and documents for the transactions must be entered and posted.
Set up the UDC tables to work with VAT reports.
The system collects the information and lists records according to your setup.
See Section 3.1.3, "Setting Up UDCs for SICORE for Argentina".
See Section 3.1.9, "Setting Up UDCs for VAT Reports (Release 9.1 Update)".
Generate the Purchases VAT Reports by running the VAT Purchasing Ledger program (R760499A). Ensure to set up the processing options to use the RG 3685 format files.
The system populates the Text Processor Header table (F007101) and Text Process Detail table (F007111) with the information about your transactions.
See Section 16.3.3.2, "Running the V.A.T. Purchasing Ledger Program for RG 3685".
See Section 16.1.1.2, "Setting Processing Options for V.A.T Purchasing Ledger (R760499A)".
Generate the RG3685 Service Imports text file by running the VAT Purchasing Ledger program (R760499A) setting the following parameters for the processing options:
Set the program to generate the RG3685 format files.
Set it to generate the RG3685 Service Imports file.
Set the system to use the document type that your company uses for service imports.
The system populates the Text Processor Header table (F007101) and Text Process Detail table (F007111) with the information about your transactions.
See Section 16.3.3.2, "Running the V.A.T. Purchasing Ledger Program for RG 3685".
See Section 16.1.1.2, "Setting Processing Options for V.A.T Purchasing Ledger (R760499A)".
Run the Split Tax Validation (R76A8900) program to reclassify all of the documents for the period before you run the Sales V.A.T Subdiary program.
See Section 15.1.6, "Running the Split Tax Validation Program (R76A8900)".
Run the Sales VAT Subdiary program (R76A8060) to generate the Sales VAT reports. Ensure to set up the processing options to use the RG 3685 format files.
The system populates the Text Processor Header table (F007101) and Text Process Detail Table (F007111) with the information about your transactions.
See Section 16.3.4.2, "Running the Sales V.A.T. Subdiary Program for RG 3685".
See Section 16.1.2.2, "Setting Processing Options for Sales VAT Tax Subdiary (R76A8060)".
(Optional) Generate the Header Text File for your VAT reports by running the RG3685 Purchase and Sales Information program (R76A010). Ensure to set up the processing options correctly.
See Section 16.3.5.2, "Running the Purchases and Sales Information Program for RG 3685".
Check the Work Center to ensure there are no errors that you must correct.
Use the standard Text File Processor program to convert JD Edwards EnterpriseOne data from the VAT report programs into text files in the formats that are required by the fiscal authority.
Submit the text files generated by the system to the fiscal authorities. Companies are required to generate these files and submit them to the fiscal authorities on a monthly basis. You can change the name of the text files generated by the system to meet the naming conventions specified by the fiscal authorities before you submit them.
|
Important: Submitting the XML files to the fiscal authorities is a step of the process that takes place outside of the JD Edwards EnterpriseOne for Argentina Localizations system and processes. |
This section provides an overview of VAT reports requirements for RG 3685 and the process to work with these reports, a detailed description of the record structure for each text file generated, and discusses how to run the V.A.T. Purchasing Ledger program (R760499A) to produce the Purchases V.A.T. reports required for RG 3685.
You run the V.A.T. Purchasing Ledger program (R760499A) to produce the required Purchases VAT reports. To run this program for RG 3685, you must complete the processing options correctly in the tab Magnetic Support.
According to your setup of the processing options, the program can generate four different required reports for RG 3685:
The purchases text file with voucher information (RG3685 Purchase Voucher)
The purchases VAT text file with VAT amounts by voucher and tax rate (RG3685 VAT Rate Voucher)
The purchases imports text file with VAT amounts by tax rate (RG3685 VAT Imports)
The services imports text file with voucher and payment information VAT Rate Voucher (RG3685 Service Imports)
To produce all four reports, you must run the program twice.
When you run the report to generate Purchase Voucher file, the VAT Rate Voucher file and the VAT Imports file, the logic that the system uses is the following:
The system searches for all the posted qualifying purchase transactions for the period specified in the processing options (tab Dates).
The transactions with a document type included in the Service Imports Document Type UDC table (76A/SI) are picked out and excluded from the files that the system generates.
All other transactions are included in the Purchases Text File with Voucher Information. This includes national transactions and goods imports, with any legal document type that must be included according to the regulation.
The system identifies the transactions where VAT amounts are discriminated and:
The system generates the Purchases Imports Text File with VAT Amounts by Tax Rate if there are transactions that involve imported goods. The system assumes that all transactions with an associated dispatch number assigned by the Customs Office are goods imports.
The system only generates the Purchases Imports VAT file if there are transactions that include a dispatch number. Otherwise, it only generates the text files for purchases with voucher information, and for VAT amounts.
|
Note: Before the system can generate the report files correctly, ensure to enter the dispatch numbers assigned by the Customs Office to your documents for imported goods. You enter this information in the Supplier Ledger Additional Information program.See Section 6.2.1.4, "Understanding Voucher Additional Information for RG 3685 (Release 9.1 Update)" |
The system generates the Purchases Text File with VAT Amounts by Voucher and Tax Rate using the information about all the transactions for legal documents type A that are national transactions (without a dispatch number associated).
When you run the report to generate the RG3685 Service Imports file, the logic that the system uses is the following:
You must set the processing options to:
Use the RG3685 Output Format
Enable the RG3685 Service Imports File option
Use the document type specified in the Service Imports Document Type UDC (76A/SI) that your company uses for service imports transactions
All three conditions must be set to produce the report.
The report includes paid transactions only, so the system uses the From and Thru dates in the Dates tab as the period for the payment. The payment must be posted.
The system lists in the final report all the transactions with the document type specified and with a payment date included in the period specified.
The system ignores any additional criteria included using data selection.
If no transactions that meet this criteria are found, no file is generated.
The RG3685 Service Imports report that the system generates includes only the transactions with the document type specified in the processing options. If you use more than one document type for services imports, you must run the report for each one of those document types and manually combine the output of the files generated into a single file that you can submit to the fiscal authorities.
Every record in this file corresponds to a document for a transaction and summarizes the information included in it to display the total amounts for the document.
This file is related to the Purchases VAT text file with VAT Amounts by Voucher and Tax Rates. In the records for the Purchases VAT Text File with Voucher Information, the system displays how many different tax rates the document includes, but it does not provide details for them. The details for the tax rates included in a document are displayed in the Purchases VAT text file with VAT amounts by voucher and tax rate.
This table describes the design structure for every line in the TXT output file:
| Field number | Length | Initial Position | Final Position | Description |
|---|---|---|---|---|
| 1 | 8 | 1 | 8 | Voucher Date |
| 2 | 3 | 9 | 11 | Voucher Type |
| 3 | 5 | 12 | 16 | Issue Place |
| 4 | 20 | 17 | 36 | Voucher Number |
| 5 | 16 | 37 | 52 | Dispatch number |
| 6 | 2 | 53 | 54 | Supplier Identification Document Code |
| 7 | 20 | 55 | 74 | Supplier Identification Number |
| 8 | 30 | 75 | 104 | Supplier Name and Surname |
| 9 | 15 | 105 | 119 | Transaction total amount |
| 10 | 15 | 120 | 134 | Total concepts amount that are not part of the taxable amount |
| 11 | 15 | 135 | 149 | Exempt transactions amount |
| 12 | 15 | 150 | 164 | Perceptions on VAT payment on account amount |
| 13 | 15 | 165 | 179 | Perception Amount or National taxes payment account |
| 14 | 15 | 180 | 194 | Gross income Perceptions amount |
| 15 | 15 | 195 | 209 | City Council tax perception |
| 16 | 15 | 210 | 224 | Internal tax amount |
| 17 | 3 | 225 | 227 | Currency Code |
| 18 | 10 | 228 | 237 | Exchange Rate |
| 19 | 1 | 238 | 238 | Quantity of VAT Rates |
| 20 | 1 | 239 | 239 | Transaction code |
| 21 | 15 | 240 | 254 | Computable Fiscal Credit Amount |
| 22 | 15 | 255 | 269 | Other Taxes |
| 23 | 11 | 270 | 280 | Commission Agent Tax ID |
| 24 | 30 | 281 | 310 | Commission Agent Name |
| 25 | 15 | 311 | 325 | Commission VAT |
This report provides detailed information about the different VAT rates in the documents included in the Purchases VAT Text File with Voucher Information that are national transactions. The vouchers that do not discriminate VAT are not included.
This table describes the design structure for every line in the TXT output file:
| Field number | Length | Initial Position | Final Position | Description |
|---|---|---|---|---|
| 1 | 3 | 1 | 3 | Voucher type |
| 2 | 5 | 4 | 8 | Issue place |
| 3 | 20 | 9 | 28 | Voucher number |
| 4 | 2 | 29 | 30 | Supplier identification document code |
| 5 | 20 | 31 | 50 | Supplier Identification number |
| 6 | 15 | 51 | .65 | Taxable amount |
| 7 | 4 | 66 | 69 | VAT Aliquot code |
| 8 | 15 | 70 | 84 | VAT Amount |
This report provides detailed information about the different VAT rates in the documents included in the Purchases VAT Text File with Voucher Information that are transactions for imported goods. The vouchers that do not discriminate VAT are not included. The transactions that do not have an associated dispatch number are also excluded.
This table describes the design structure for every line in the TXT output file:
| Field number | Length | Initial Position | Final Position | Description |
|---|---|---|---|---|
| 1 | 16 | 1 | 16 | Dispatch Number |
| 2 | 15 | 17 | 31 | Taxable amount |
| 3 | 4 | 32 | 35 | VAT Aliquot code |
| 4 | 15 | 36 | 50 | VAT Amount |
Every record in this file identifies services imports that occurred during the presentation period. The program identifies the transactions based on the document type, as listed in the Service Imports Document Types UDC table (76A/SI).
|
Note: You must have exclusive document types for services imports. A single document type must not include records for imported goods and services because the system defines the records included in this report based on the document type.See Section 3.1.9.4, "Service Imports Document Types (76A/SI)" |
This table describes the design structure for every line in the TXT output file:
| Field number | Length | Initial Position | Final Position | Description |
|---|---|---|---|---|
| 1 | 1 | 1 | 1 | Document type |
| 2 | 20 | 2 | 21 | Description |
| 3 | 20 | 22 | 41 | Document Identification code |
| 4 | 8 | 42 | 49 | Transaction Date |
| 5 | 15 | 50 | 64 | Original currency amount |
| 6 | 3 | 65 | 67 | Currency code |
| 7 | 10 | 68 | 77 | Exchange rate |
| 8 | 11 | 78 | 88 | Supplier CUIT |
| 9 | 20 | 89 | 108 | Supplier NIF |
| 10 | 30 | 109 | 138 | Supplier Name |
| 11 | 4 | 139 | 142 | Applicable VAT rate Code |
| 12 | 8 | 143 | 150 | Tax Date |
| 13 | 15 | 151 | 165 | VAT Amount |
| 14 | 15 | 166 | 180 | Computable VAT Amount |
| 15 | 20 | 181 | 200 | Identification of the payment/settlement/document |
| 16 | 11 | 201 | 211 | Payment Entity Tax ID |
Select RG 3685 Information (G76A3685), Purchasing V.A.T. Tax Subdiary.
Set the processing options to generate the RG 3685 reports.
See Section 16.1.1.2, "Setting Processing Options for V.A.T Purchasing Ledger (R760499A)".
This section provides an overview of Sales VAT reports requirements for RG 3685, of the process to work with these reports, a detailed description of the record structure for each text file generated, and discusses how to run the Sales V.A.T. Subdiary program (R76A8060) to produce the RG 3685 Sales V.A.T. reports.
You run the Sales VAT Tax Subdiary program (R76A8060) to produce the VAT reports required by the RG 3685. To run this program for RG 3685, you must complete the processing option correctly in the tab Magnetic Support.
When you run the program for the RG 3685, the system generates two different text files that comply with the content and format specifications regulated by the RG 3685:
The Sales text file with invoice information
The Sales VAT text file with VAT amounts by invoice and tax rate
Every record in this file corresponds to a document for a transaction and summarizes the information included in it to display the total amounts for the document. This file is related to the Sales VAT text file with VAT amounts by Invoice and Tax Rates: In the records for the Sales VAT Text File with Invoice Information, the system informs how many different tax rates the document includes, but it does not provide details for them. The details for the tax rates included in a document are displayed in the Sales VAT text file with VAT amounts.
This table describes the design structure for every line in the TXT output file:
| Field number | Length | Initial Position | Final Position | Description |
|---|---|---|---|---|
| 1 | 8 | 1 | 8 | Document date |
| 2 | 3 | 9 | 11 | Document type |
| 3 | 5 | 12 | 16 | Issue Place |
| 4 | 20 | 17 | 36 | Document number |
| 5 | 20 | 37 | 56 | Document number "Thru" |
| 6 | 2 | 57 | 58 | Buyer Document Code |
| 7 | 20 | 59 | 78 | Buyer ID number |
| 8 | 30 | 79 | 108 | Buyer's name |
| 9 | 15 | 109 | 123 | Total amount of the transaction |
| 10 | 15 | 124 | 138 | Total amount of concepts not included in the net taxable amount. |
| 11 | 15 | 139 | 153 | Tax calculated to RNI or perception to non- categorized |
| 12 | 15 | 154 | 168 | Total of exempt amounts |
| 13 | 15 | 169 | 183 | Amount of perceptions or payments to National Taxes account |
| 14 | 15 | 184 | 198 | Total perceptions of gross income |
| 15 | 15 | 199 | 213 | Total amount of Municipal taxes perceptions |
| 16 | 15 | 214 | 228 | Internal taxes amount |
| 17 | 3 | 229 | 231 | Currency code |
| 18 | 10 | 232 | 241 | Exchange rate |
| 19 | 1 | 242 | 242 | Quantity of tax rates |
| 20 | 1 | 243 | 243 | Transaction code |
| 21 | 15 | 244 | 258 | Other taxes |
| 22 | 8 | 259 | 266 | Invoice due date |
This report provides detailed information of the different VAT tax rates in the documents included in the Sales VAT Text File with Invoice Information. Every line summarizes and reports the totals for a VAT rate in a document. For example, if you have an invoice with multiple records and three different tax rates, the system creates three lines, one for each tax rate, and displays in each line the sum of the amounts of all the records for the rate.
The invoices that do not discriminate VAT taxes are not included.
This table describes the design structure for every line in the TXT output file:
| Field number | Length | Initial Position | Final Position | Description |
|---|---|---|---|---|
| 1 | 3 | 1 | 3 | Document Type. The three-digit code for the document according to the official code list provided by AFIP. |
| 2 | 5 | 4 | 8 | Issue Place |
| 3 | 20 | 9 | 28 | Document number. It includes the serial number and invoice number. |
| 4 | 15 | 29 | 43 | Taxable Net Amount |
| 5 | 4 | 44 | 47 | VAT Tax Rate. |
| 6 | 15 | 48 | 62 | Tax calculated |
Select RG 3685 Information (G76A3685), Sales V.A.T. Tax Subdiary.
Set the processing options to generate the RG 3685 reports.
See Section 16.1.2.2, "Setting Processing Options for Sales VAT Tax Subdiary (R76A8060)".
This section provides an overview of the RG 3685 Purchases and Sales Information program (R76A010), a detailed description of the record structure for the text file generated, and discusses how to:
Run the RG 3685 Purchases and Sales Information program.
Set the processing options for the RG 3685 Purchases and Sales Information program.
You run the RG 3685 Purchases and Sales Information program (R76A010) to generate a text file that you use as a header for the reports you submit. This file consists of a single line record that identifies the reporting company and summarizes information from the Purchases V.A.T. Tax Subdiary report and the Sales V.A.T. Tax Subdiary report that was run last.
Before you run this program, you must generate the Purchases VAT reports and/or the Sales VAT reports for RG 3685. Otherwise, the report generated does not show any data.
This table describes the design structure for the one line in the TXT output file:
| Field number | Length | Initial Position | Final Position | Description |
|---|---|---|---|---|
| 1 | 11 | 1 | 11 | Tax ID of the reporting company. The system uses the company identified in the processing options. |
| 2 | 6 | 12 | 17 | Period and year of the presentation, in format YYYYMM. The system uses the month and year identified in the processing options. |
| 3 | 2 | 18 | 19 | Presentation sequence number. The system uses the company identified in the processing options. |
| 4 | 1 | 20 | 20 | No movements flag. This field indicates if there are no movements or changes in the period of the presentation.The program sets an S if there are no movements and an N if there are changes. |
| 5 | 1 | 21 | 21 | Prorate Computable Tax Credit. The field specifies whether the Computable Tax Credit is prorated for the period stated or not. The system sets an S if the Computable Tax Credit is prorated, and an N if it is not prorated. |
| 6 | 1 | 22 | 22 | Computable Fiscal Credit Method. This digit indicates the grouping criteria for computable tax credit amounts. The value 1 in this field indicates that the system groups all the amounts together (Global method), and the value 2 that it groups the amounts by document. The system always uses the method By Document (2) and informs the computable tax credit in each document that you report. |
| 7 | 15 | 23 | 37 | Computable Global Fiscal Credit Amount. The system uses the Computable Fiscal Credit method "by document"; therefore it populates this field with zeroes. |
| 8 | 15 | 38 | 52 | Fiscal Credit Amount of direct allocation. The field indicates the total of computable tax credit amounts. The system used the Computable Fiscal Credit method "by document"; therefore it populates this field with zeroes. |
| 9 | 15 | 53 | 67 | Computable Fiscal Credit by Proration. It indicates the computable tax credit amount, as defined by proration. Since the system used the Computable Fiscal Credit method "by document", it populates this field with zeroes. |
| 10 | 15 | 68 | 83 | Global Fiscal Credit Amount not Computable. The field indicates the global total amount of non-computable tax credit amounts. The system used the Computable Fiscal Credit method "by document"; therefore it populates this field with zeroes. |
| 11 | 15 | 84 | 98 | Fiscal Credit generated by Contributions to Social Security and Others. The system uses the amount specified in the processing options. |
| 12 | 15 | 99 | 113 | Computable Fiscal Credit generated by Contributions to Social Security and Others. The system uses the amount specified in the processing options. |
Select RG 3685 Information (G76A3685), RG 3685 Purchase and Sales Header Information.
Processing options enable you to specify the default processing for programs and reports.
Enter the code that identifies a specific organization, fund, or other reporting entity. The company code must already exist in the Company Constants table (F0010) and must identify a reporting entity that has a complete balance sheet. At this level, you can have intercompany transactions.
Enter the four-digit calendar year for the presentation
Enter the two-digit number that identifies the month of the presentation.
Select a code from the RG3685 - Presentation Sequence UDC table (76A/SE) that specifies if the report that you are generating is the original version, or if it is an amendment. If you need to submit amendments more than once, select the code that specifies the sequence number of the current report.
Enter the total amount of the Fiscal credit generated by Contributions to Social Security and other items not covered in the detailed information (Computable or not computable).
A number that quantifies the amount of the computable Fiscal credit generated by Contributions to Social Security and other items not covered in the detailed information.
If you set the Computable Fiscal Credit field to use the Global method, then the system populates this field with zeroes.
This section provides an overview of the Withholdings Ledger program and discusses how to:
Run the Withholdings Ledger program.
Set processing options for Withholdings Ledger (R760465A).
You run the Withholdings Ledger program to generate a report of tax withholding information for a certain period. The report lists all of the profit, eventual, VAT, gross income, or contract withholdings for the period, based on the document types that are specified in the data selection.
For withholding for small contributors, the program:
Uses the first character of the Description 2 field of the 76/03 UDC table to determine whether to calculate profit withholding.
Retrieves the amounts for the Gross Amount and Taxable Amount columns from the voucher related to the withholding document.
Specify the document types to include on the report as:
| Operator | Left Operand | Comparison | Right Operand |
|---|---|---|---|
| Where | BC Document Type (F0414) (DCT) | is equal to | USD I |
| And | BC Company (F0414) (CO) | is equal to | 00001 |
| And | BC Document Type - Matching (F0414) (DCTM) | is not equal to | PG |
Run the Split Tax Validation (R76A8900) program.
See Section 15.1.6, "Running the Split Tax Validation Program (R76A8900)".
Select Monthly Reports (G76A121), Withholdings Ledger.
Processing options enable you to specify the default processing for programs and reports.
Specify the date from or the date until you want to execute the process.
Enter 1 to print the last period. Leave this processing option blank to print an actual period as specified in the dates in the processing options.