This chapter contains the following topics:
Section 15.2, "Processing SICORE Withholding Magnetic Report for Argentina"
Section 15.3, "Processing SIRE Withholding Reports (Release 9.1 Update)"
Section 15.4, "Working with the Account Ledger Book for Argentina"
Section 15.5, "Working with the Fixed Asset Legalized Book for Argentina"
Section 15.6, "Generating the Gross Income Perception Report 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.
The Public Revenue 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.
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.
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.
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.
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:
| Name | 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 |
| Apellido 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 |
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).
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.
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.
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.
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).
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. |
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.
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. |
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.
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. |
Select Legal Reports (G76A03B2), Split Tax Validation.
Processing options enable you to specify the default processing for programs and reports.
Enter 1 to run the program in final mode. Leave this processing option blank to run the process in proof mode.
Select CITI - General Resolution 781 (G76A781), Process Purchase Documents.
Processing options enable you to specify the default processing for programs and reports.
Specify the company that is submitting the report. This information is included in the CITI report.
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.
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/AF, 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/AF.
Specify the tax explanation code. Enter 1 if you are processing transactions with tax explanation code S. Otherwise, leave this processing option blank.
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.
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.
Select CITI - General Resolution 781 (G76A781), Process Own Credit Notes.
Processing options enable you to specify the default processing for programs and reports.
Specify the company that is submitting the report. This information is included in the CITI report.
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.
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.
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.
Specify the month for which you are submitting the CITI report.
Specify the year for which you are submitting the CITI report. Enter the year as a four-digit number (for example, 2005).
Select CITI - General Resolution 781 (G76A781), Generate Text File.
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.
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 an electronic file 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:
If you are using the JD Edwards EnterpriseOne Accounts Payable system, run the Step I - A/P Transactions (RG 738) program (R76A8081).
If you are using the JD Edwards EnterpriseOne Accounts Receivable system, run the Step II - A/R Transactions (RG 738) program (R76A94).
If you make self withholdings, run the Step III - Self Withholdings program (R76A96).
Run the Final Step (RG 738) program (R76A8002).
Run the Text File Processor program (P) to create the flat file.
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.
This table shows the data that is required when reporting Accounts Payable withholdings to the fiscal authority:
Set up these UDC tables 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/AF) | You use the values in the ARG-DGI Transaction Doc. Type (76/AF) 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. |
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.
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.
For small contributors, the system includes the legal number of the voucher that generated the withholding document. The legal number field in the temporary table that is populated by the SICORE RG 738/99 program will include the data from the voucher related to the withholding documents.
This data is the amount from the vouchers that generate the withholding.
For small contributors, the gross amount field in the temporary table that is populated by the SICORE RG 738/99 program will include the data from the voucher related to the withholding documents.
This table shows the AFIP withholding codes that are used in the JD Edwards EnterpriseOne Accounts Payable system:
| Code | Description |
|---|---|
| 217 | Profit Withholding |
| 767 | VAT Withholding |
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.
For all withholdings, the operation code is 1.
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).
For additional information on VAT Withholding calculation base, see Understanding VAT Withholding by RG 3732 (Release 9.1 Update)
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).
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.
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.
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.
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).
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.
The number and document type from the supplier for whom the withholding amount was retained must be reported.
This data is the trade name of the supplier. The system retrieves the alpha name from the supplier's address book record.
This data is required when reporting Accounts Receivable self withholdings or perceptions to the fiscal authority.
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/AF) | 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. |
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).
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:
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.
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.
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).
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 AFIP requires 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.
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" |
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.
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.
Run the Split Tax Validation program (R76A8900).
Select SICORE RG 738/99 (G76A738), Step I - A/P Transactions (RG738).
Processing options enable you to specify the default processing for programs and reports.
Enter the beginning and ending dates for the date range.
Enter 1 to run the report in final mode. Leave this processing option blank to run the report in proof mode.
Enter 1 to process voided withholdings. Leave this processing option blank to prevent the system from processing voided withholdings.
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.
Enter the VAT tax code.
Enter the profit tax code for local suppliers.
This processing option is obsolete.
This option allows the system to process the report by tax code. Enter the VAT code that you set up for the VAT RG 3164 in UDC table Tax Codes (76A/TX).
Specify the document type for adjusted or voided invoices.
Specify the document type for adjusted or voided credit notes.
Enter 1 to use the withholding legal number.
Enter 1 to generate in the work file the voids from the same month.
Select SICORE RG 738/99 (G76A738), Step II - A/R Transactions (RG 738).
Processing options enable you to specify the default processing for programs and reports.
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.
Enter the beginning of the range of dates for which you process records.
Enter the final date of the range of dates for which you process records.
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.
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).
Enter Y to run the process according to RG 738.
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.
Select SICORE RG 738/99 (G76A738), Step III - Self Withholdings.
Processing options enable you to specify the default processing for programs and reports.
Specify the date from or the date through which transactions should be included for processing.
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.
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.
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.
Specify 217, which is the profit code.
Select SICORE RG 738/99 (G76A738), Final Step (RG 738).
Processing options enable you to specify the default processing for programs and reports.
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.
Specify the address book category code in which you define the AFIP supplier or customer condition.
Specify the generic Tax ID for taxpayers who have not provided a tax ID number.
Specify the VAT withholding code.
Enter the VAT code for a domestic supplier.
Enter the VAT code for a foreign supplier.
Specify the tax code that is defined in the system.
Select SICORE RG 738/99 (G76A738), TXT Generation.
This section provides an overview of the SIRE (Sistema Integrado Retenciones Electronicas) withholding reports processing and discusses how to:
Generate the flat file for SUSS withholdings.
Set processing options for the SUSS withholdings flat file generation program.
Generate the flat file for profit withholdings for foreign beneficiaries.
Set processing options for generating the flat file for profit withholdings for foreign beneficiaries.
Update the withholdings certificate legal numbers.
According to the AFIP's general resolution RG 3726, companies that are withholding agents must report SUSS withholdings and profit withholdings for foreign beneficiaries in a text file in a format that is specified by the AFIP. The AFIP then creates withholding certificates by using the SIRE software, and provides the 25-digit certificate number to the withholding companies.
You run the S.U.S.S. TXT File - Withholding Information report (R76A4002) to generate the text file to report SUSS withholdings in the format specified by the AFIP. You submit the text file to the AFIP.
When you run the S.U.S.S. TXT File - Withholding Information report, the system performs the following validations:
Legal Form Code, Legal Form Version, Legal Tax Code, and Regime Code
Company and Supplier Tax ID (CUIT)
Original Certificate Number
The original certificate information is required if the legal document type is credit note or debit note.
When you run the S.U.S.S. TXT File – Withholding Information report (R76A4002), the system writes data to the Text Processor Header (F007101) and Text Process Detail (F007111) tables, and generates the flat file. The flat file includes data from the Withholding Certificates Legal Number - 76A (F76A40) and Withholding Certificates Legal Number History Files - 76A (F76A55) tables.
When you run the S.U.S.S. TXT File - Withholding Information report in the final mode, the system stores the data in the F76A40 table.
If the system generates errors when you run the S.U.S.S. TXT File - Withholding Information report, you can view the errors in the Work Center.
When you run the report in proof or final mode, the system creates a text file for only those records without errors. When you run the report in final mode, the system also updates the F76A40 table and generates the traceability code.
After you submit the SUSS withholdings flat file to the AFIP, the AFIP issues a 25-digit certificate number. Use the Withholding Certificates Legal Number Maintenance - 76A program (P76A001) to import the certificate number.
The following table describes the fields that are included in the flat file generated by the S.U.S.S. TXT File - Withholding Information report (R76A4002):
| Record Name | Description | Position |
|---|---|---|
| Form | The AFIP legal form code. The system retrieves this value from the Legal Form Code processing option set up for the R76A4002 program. You define legal form codes in the Legal Form Codes UDC table (76A/FC). | 01-04 |
| Version | The version of the AFIP legal form code. The system retrieves this value from the Legal Form Version processing option set up for the R76A4002 program. | 05-08 |
| Traceability Code | The traceability code. The system retrieves this information from the next number set up for system 76A, line 6. The system uses this field to link the JD Edwards EnterpriseOne withholding document with the certificate number generated by SIRE. | 9-18 |
| Agent Tax ID | The withholding agent's tax ID as set up in the Address Book Master. | 19-29 |
| Tax | The legal tax code for the withholdings. | 30-32 |
| Withholding Legal Concept | The AFIP legal concept code. The system retrieves this value from the ARG-Profit Legal Concept UDC table (76/L3). | 33-35 |
| Payer Tax ID | The name, address, and fiscal ID (CUIT) of the payer. | 36-46 |
| Withholding Date | The date that the tax was withheld. The system retrieves this value from the Invoice Date field in the Accounts Payable Ledger table (F0411). | 47-56 |
| Document Type | The legal document type for the withholdings. The system retrieves this value from the Legal Document Type UDC table (76A/DV). | 57-58 |
| Document Date | The document date based on the document type:
|
59-68 |
| Document | The document number based on the document type:
|
69-84 |
| Base Amount | The base amount for the withholdings. The system retrieves this value from the Remark field in the Accounts Payable Matching Document Detail table (F0414). | 85-98 |
| Withholding Amount | The amount that was withheld. The system retrieves this information from the Accounts Payable Ledger table (F0411). | 99-112 |
| Original Document Number | The original document number. This is the document number associated with the original withholdings certificate, if you enter a rectification for the withholdings. | 113-137 |
| Original Withholding Date | The original withholding date. This is the date associated with the original withholdings certificate, if you enter a rectification for the withholdings. | 138-147 |
| Original Certificate Amount | The original withholdings amount. This is the withholdings amount on the original withholdings certificate, if you enter a rectification. | 148-161 |
| Others | The withholding document information (KCO/DCT/DOC). The system retrieves this information from the Accounts Payable Ledger table (F0411). | 162-191 |
When the system generates the flat file:
The system processes only non-voided documents for the period.
The system processes only the posted transactions.
It lists the amounts in domestic currency.
The system processes records with the following document types:
$A (eventual withholding)
$L (cleaning services withholding)
$P (security withholding)
$S (contract withholding)
$Q (SUSS withholding)
The document types processed depend on the data selection parameters associated with the version that you use to process the report.
The system obtains the legal concept for contractor withholding from the Contract Withholding Percentage table (F760405A).
The system obtains the legal concept for eventual services withholding from the Eventual Services Withholding table (F760410A).
The system produces a report listing the withholdings.
You run the F2003 Profit Withholding to External Beneficiaries report (R76A4005) to generate the text file to report profit withholdings for foreign beneficiaries in the format specified by the AFIP. The system uses Oracle's BI Publisher (Business Intelligence Publisher) to generate the text file. You submit the text file to the AFIP.
The process for reporting profit withholdings for foreign beneficiaries consists of the following steps:
Set up these UDCs:
ARG-Profit WH Concept (76A/04)
ARG-Profit Legal Concept (76/L3)
Legal Form Codes (76A/FC)
Legal Tax Code (76A/LC)
Legal Document Type (76A/DV)
SIRE Countries (76A/PS)
Aliquot With CDI (76A/WC)
Aliquot Without CDI (76A/WD)
Profit Gross Up (76A/AC)
Status (76A/ST)
Set up profit withholding percentages in the Profit W/H-Percentages program (P760403A).
See Section 4.8, "Setting Up Profit Withholding for Argentina".
Set up the Localizations Additional Information solution to be able to add credit note and debit note reasons to the information about your vouchers.
See Section 3.7, "Setting Up Localizations Additional Information for Argentina (Release 9.1 Update)".
Enter vouchers in the Standard Voucher Entry program (P0411) and pay the vouchers.
Run the F2003 Profit Withholding to External Beneficiaries report (R76A4005) to generate a flat file to report the profit withholdings.
Submit the flat file to the AFIP.
|
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. |
Use the Withholding Certificates Legal Number Maintenance - 76A program (P76A001) to import the 25-digit certificate number issued by the AFIP.
The F2003 Profit Withholding to External Beneficiaries report (R76A4005) uses data from the following tables to generate the text file:
Profit Withholding Percentage - ARG - 04 - 76A (F760403A)
Additional Profit Withholding (F76A0403)
Accounts Payable Matching Document Detail (F0414)
Accounts Payable Matching Document (F0413)
A/P Payment Detail Tag Table - ARG (F760414A)
Address Book Master (F0101)
Accounts Payable Ledger (F0411)
Address by Date (F0116)
Address Book - Who's Who (F0111)
When you run the F2003 Profit Withholding to External Beneficiaries report in the final mode, the system stores the data in the Withholding Certificates Legal Number - F76A table (F76A40).
If the system generates errors when you run the F2003 Profit Withholding to External Beneficiaries report, you can view the errors in the Work Center.
When you run the report in proof or final mode, the system creates a text file for only those records without errors. When you run the report in final mode, the system also updates the Withholding Certificates Legal Number - F76A table (F76A40) and generates the traceability code.
After you submit the flat file to the AFIP, the AFIP issues a 25-digit certificate number. Use the Withholding Certificates Legal Number Maintenance - 76A program (P76A001) to import the certificate number.
The system uses Oracle's BI Publisher to produce the required text file.
The BI Publisher creates files in a two-phase process:
Information extraction, generation, and data formatting
XSLT transformation
An Extensible Stylesheet Language Transformation (XSLT) is an .xsl script that maps a file schema to another file schema. The programs extract the required information and produce a TXT or PDF schema that is mapped to the schema provided by the government fiscal authorities.
The system uses specific templates and report definitions related to the version to produce a text file that complies with the output information and format, as required by the fiscal authorities.
The following table describes the relationship between the output, templates, and report definitions:
| Output | Batch Version Program | Version | Template | BI Publisher Report Definition |
|---|---|---|---|---|
| F2003 Profit Withholding to External Beneficiaries TXT | R76A4005 | ZJDE0001 | TP76A4005TE1 | RD76A4005A |
| F2003 Profit Withholding to External Beneficiaries PDF-Single | R76A4005 | ZJDE0002 | TP76A4005TP1 | RD76A4005B |
| F2003 Profit Withholding to External Beneficiaries PDF-Detailed | R76A4005 | ZJDE0002 | TTP76A4005TP2 | RD76A4005B |
|
Note: Before you run the TXT generation program, verify that the BI Publisher setup is correct in your system.See Also |
Follow these steps to view report output generated by BI Publisher for the F2003 Profit Withholding to External Beneficiaries report (R76A4005):
To access the flat text output file that you must submit to the fiscal authorities, view the submitted jobs.
To review a PDF version of the report with detailed information about its content:
In Submitted Jobs, select the record of the file that the report generated.
Select the Republish RD option on the Row menu.
Select the report definition RD76A4005B.
In Submitted Jobs, select the record for the same job.
Select the View RD Output option on the Row menu.
Depending on the data that you want to review:
Select the option F2003 Profit Withholding to External Beneficiaries PDF–Single to review a PDF version that identifies only the fields and values contained in the PDF that you submit to the fiscal authorities.
Select the report definition F2003 Profit Withholding to External Beneficiaries PDF–Detailed to review a PDF version that identifies the fields and values in the text flat file and all the additional information that the report processes to generate it.
You run the F2003 Profit Withholding to External Beneficiaries report (R76A4005) to generate a flat file to report profit withholdings for foreign beneficiaries.
The following table describes the fields that are included in the flat file:
| Record Name | Description | Position |
|---|---|---|
| Form | The AFIP legal form code. | 01-04 |
| Version | The version of the AFIP legal form code. | 05-08 |
| Traceability Code | The traceability code. The system retrieves this information from the next number set up for system 76A, line 6. The system uses this field to link the JD Edwards EnterpriseOne withholding document with the certificate number generated by SIRE. | 9-18 |
| Agent Tax ID | The withholding agent's tax ID as set up in the Address Book Master. | 19-29 |
| Tax | The legal tax code for the withholdings. | 30-32 |
| Concept | The AFIP legal concept code. The system retrieves this value from the ARG-Profit Legal Concept UDC table (76/L3). | 33-35 |
| Payer Tax ID | The name, address, and fiscal ID (CUIT) of the payer. | 36-46 |
| Withholding Date | The date that the tax was withheld. This value is retrieved from the Invoice Date field in the Accounts Payable Ledger table (F0411). | 47-56 |
| Document Type | The legal document type for the withholdings. The system retrieves this value from the Legal Document Type UDC table (76A/DV). | 57-58 |
| Document Date | The document date based on the document type:
|
59-68 |
| Document Number | The document number based on the document type:
The system retrieves this value from the Payment Order Number - Argentina field (AOP) of the A/P Payment Detail Tag Table - ARG - 04 table (F760414A). |
69-84 |
| Amount | The base amount for the withholdings. The system retrieves this value from the Remark field in the Accounts Payable Matching Document Detail table (F0414). | 85-98 |
| Filler | Filler description. | 99-112 |
| Original Document Number | The original document number. This is the document number associated with the original withholdings certificate, if you enter a rectification for the withholdings. | 113-137 |
| Original Document Date | The original withholding date. This is the date associated with the original withholdings certificate, if you enter a rectification for the withholdings. | 138-147 |
| Original Amount | The original withholdings amount. This is the withholdings amount on the original withholdings certificate, if you enter a rectification. | 148-161 |
| Credit/Debit Note Reason | The reason for the credit or debit note. If you define a credit or debit note reason in the String Data tab of the Work With Supplier Ledger Additional Information form, the system displays that information. Otherwise, the system displays the value of the Credit or Debit Note processing option for the F2003 Profit Withholding to External Beneficiaries program (R76A4005). If both of these values are blank, the system generates an error. | 162-191 |
| No Withholding | The value in this field indicates whether profit withholdings exist or not. The system retrieves this value from the Additional Profit Withholding table (F76A0403). | 192 |
| No Withholding Reason | The reason for not reporting profit withholdings. The system retrieves this value from the Additional Profit Withholding table (F76A0403). | 193-222 |
| Apply CDI | The value in this field indicates whether CDI is applicable to the profit withholdings or not. The system retrieves this value from the Additional Profit Withholding table (F76A0403). | 223 |
| CDI Code | A legal code to identify the rate with CDI if CDI is applicable to the profit withholdings. The system retrieves this value from the Additional Profit Withholding table (F76A0403). | 224-226 |
| Grossing Up | The system verifies whether the voucher that is being paid includes a tax area that has been defined in Profit Gross Up UDC table (76A/AC). If the tax area is defined in the UDC table, the system displays 1 in this field to indicate that the withholding is grossed up. Otherwise, the system displays 0. | 227 |
| NIF Key | The supplier's NIF (Numero de Identificacion Fiscal) information. The system retrieves this information from the Supplier NIF Information processing option setting for the F2003 Profit Withholding to External Beneficiaries report (R76A4005). The system first retrieves the Supplier Tax ID field and then the Additional Tax ID field in the supplier's address book record. If both of these values are blank, the system displays the legend ''No Disponible'' (Not Available) in the report. | 228-277 |
| Supplier Name | The name of the supplier. The system retrieves this value from the supplier's address book record. | 278-337 |
| Supplier Address | The address of the supplier. The system retrieves this value from the supplier's address book record. | 338-397 |
| Supplier Country | The supplier's SIRE country code. The system retrieves this value from the SIRE Countries UDC table (76A/PS). | 398-400 |
| Person/Corporation | The type of supplier. The system retrieves this value from the Person/Corporation Code field in the supplier's address book record. | 401 |
| Supplier Nationality/Constitution Country | The supplier's nationality. The system retrieves this value from the SIRE Countries UDC table (76A/PS) based on the Who's Who Category Code processing option set up for the TXT File - Profit to External Beneficiaries Withholding (R76A4005) report. If the category code has a blank value, the system displays the same value that is displayed for the Supplier Country field. | 402-404 |
| Supplier Nationality/Constitution Date | The supplier's date of birth. The system retrieves this value from the address book record of the supplier based on the Who's Who Type Code processing option set up for the TXT File - Profit to External Beneficiaries Withholding (R76A4005) report. | 405-414 |
When the system generates the flat file for profit withholdings for foreign beneficiaries:
The system processes only nonvoided documents for the period.
The system processes only the posted transactions.
The system processes records for all payments processed for foreign suppliers (the country code is not blank and has a value other than AR).
Select SIRE Withholding Reports (G76A3726), TXT File - SUSS and Contract WH Generation (R76A4002).
Processing options enable you to specify the default processing for programs and reports.
Specify a value assigned by the AFIP to identify the legal form code that the system uses to report SUSS withholdings.
Specify a value assigned by the AFIP to identify the version of the legal form code that the system uses to report SUSS withholdings.
Specify a value assigned by the AFIP to identify the legal tax code that the system uses to report SUSS withholdings.
Specify the Withholding Agent Address Number to retrieve the Agent Tax ID that the system uses to report SUSS withholdings.
Specify the legal code to identify invoices. The default value is 1.
Specify the legal code to identify withholding adjustment credit notes. The default value is 3.
Specify the legal code to identify withholding adjustment debit notes. The default value is 4.
Specify the legal code to identify payment orders. The default value is 6.
Enter the beginning of the date range of the records processed.
Enter the end of the date range of the records processed.
Specify whether the system should run the report in proof or final mode. Values are:
Blank: Proof Mode
1: Final Mode
If you run the report in final mode, the system updates the F76A50 table.
Select SIRE Withholding Reports (G76A3726), TXT File - Profit to External Beneficiaries Withholding (R76A4005).
Processing options enable you to specify the default processing for programs and reports.
Specify a value assigned by the AFIP to identify the legal form code that the system uses to report profit withholdings for foreign beneficiaries.
Specify a value assigned by the AFIP to identify the version of the legal form code that the system uses to report profit withholdings for foreign beneficiaries.
Specify the Withholding Agent Address Number to retrieve the Agent Tax ID that the system uses to report profit withholdings for foreign beneficiaries.
Specify the Payer Address Number to retrieve the Payer Tax ID that the system uses to report profit withholdings for foreign beneficiaries.
Specify a value assigned by the AFIP to identify the legal tax code that the system uses to report profit withholdings for foreign beneficiaries.
Specify the Who's Who Type Code to retrieve the supplier's date of birth and nationality. If you leave this processing option blank, the system uses the record with Line ID 0 (zero).
Specify the Who's Who Category Code to retrieve the supplier's nationality.
Specify the legal code to identify payment orders. The default value is 6.
Specify the legal code to identify withholding adjustment credit notes. The default value is 3.
Specify the legal code to identify withholding adjustment debit notes. The default value is 4.
Specify the reason for credit notes or debit notes, to report to the AFIP when the system cannot find this information for a specific credit or debit document.
Specify the supplier's NIF information. Values are:
Blank: Use the Supplier Tax ID field from the supplier's address book record.
1: Use the Supplier Tax ID2 field from the supplier's address book record.
|
Note: If there is no supplier NIF information available, the system will display "No Disponible" (Not Available) in the report. |
Specify the starting date and the ending date of a range of dates that the system uses when selecting records to process in this report.
Specify whether the system should run the report in proof or final mode. Values are:
Blank: Proof Mode
1: Final Mode
Specify a date (in the format YYYYMM) to identify the current period.
When you work with RG 3726 withholdings, the system generates a draft certificate when you process a payment with the applicable withholdings. To obtain the legal certificate, you must submit the RG 3726 flat files that the system generates to the fiscal authorities. You submit the information using the government-provided web application SIRE. The SIRE application generates the legal certificate and provides a 25-digit certificate legal number in return for each certificate record.
You use the Withholding Certificates Legal Number Maintenance program (P76A001) to associate the information in the legal certificate, which the authorities generate for your submitted withholdings, to the records generated by the system. When you enter the associations, you must update the certificate legal number, the certificate issue date, the withholding amount, and the status of the legal certificate.
The program lists the records for all the certificates processed by the system: Drafts that have not been associated to a legal number yet, certificates with a legal number associated, and replaced certificates.
You can update a single record manually or update multiple records simultaneously by copying and pasting information from a file.
| Form Name | Form ID | Navigation | Usage |
|---|---|---|---|
| Work with Withholding Certificates Legal Number | W76A001A | Select SIRE Withholding Reports (G76A3726), Withholding Certificates Legal Number (P76A001). | Review the withholdings information generated by the system after running the R76A4002 and R76A4005 reports. |
| Update Withholding Certificates | W76A001B | On the Work with Withholding Certificates Legal Number form, select a record and click Select. | Update the withholding certificate number issued by the AFIP. |
| Import Data | W76A001C | On the Work with Withholding Certificates Legal Number form, select Import Data from the Form menu. | Import withholdings information from a file. |
Access the Update Withholding Certificates form.
Review the traceability code. This is the code that the system generates when you run the S.U.S.S. TXT File - Withholding Information or the F2003 Profit Withholding to External Beneficiaries in the final mode.
Review the number that identifies the original document, such as a voucher, invoice, or journal entry. On entry forms, you can assign the document number or let the system assign it by using the Next Numbers program (P0002). Matching document numbers (DOCM) identify related documents in the Accounts Receivable and Accounts Payable systems. Examples of original and matching documents are:
Accounts Payable
Original document – voucher
Matching document – payment
Accounts Receivable
Original document – invoice
Matching document – receipt
Review the number that identifies the pay item for a voucher or an invoice. The system assigns the pay item number. If the voucher or invoice has multiple pay items, the numbers are sequential.
Review the number that the system assigns from the Next Numbers program (P0002) to identify and track payment records.
Enter the number provided by the tax authorities to identify the withholding certificate.
Enter the date the withholding certificate was issued by the tax authorities.
Enter the withholding amount.
Enter a value from UDC table Status (76A/ST) that identifies the status of the withholding presentation.
|
Note: When you update a record with the information provided by the fiscal authority, you must update the status to "Emitido" (Issued). The system does not update the information provided by the fiscal authorities if the status of the record for a certificate is set to "Draft".If the status of the legal certificate is Replaced, the program writes the information about the replaced certificate to the Withholding Certificates Legal Number History Files table (F76A55) and; in the Withholdings Certificates Legal Number table (F76A40), it changes the legal certificate number to a different number and sets its amounts to zero, but keeping the same traceability code. |
You can manually enter multiple records at a time or import data from a spreadsheet to enter withholdings information in multiple records.
Access the Import Data form.
Enter the records manually or copy and paste grid data from a spreadsheet that mirrors the grid in the form.
Correct errors (if any) and click OK to save the data to the table.
|
Note: If you import records from a file, the records must have a legal certificate number and must be sorted by issue date. |
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).
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.
| Form Name | Form ID | 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. |
Access the G/L Registration Revision form.
Enter the calendar year for this calendar.
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.
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.
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).
Select Account Ledger Legalized Book (G76A09), Account Ledger Legalized Book.
Processing options enable you to specify the default processing for programs and reports.
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.
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.
|
Caution: The system verifies pending transactions in proof mode only. |
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. |
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.
Specify the beginning or the end of a range of dates that the system uses to select records to process.
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.
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.
Leave this processing option blank to assign a registration number for each document. Enter 1 to assign registration numbers for each journal entry line.
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.
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.
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.
Enter a value that exists in the Document Type (00/DT) UDC table to specify the document type setting for the page number.
Specify whether the page number setting is by company. Values are:
Blank: Company and fiscal year.
1: Company.
Specify the printer parameter for the number of lines per page. The default is 46 lines for paper size A4.
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).
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.
Before completing the tasks in this section, set up the Anexo A Column Type (76A/12) UDC table.
Select Fixed Asset Legalized Book (G76A12), Fixed Asset Legalized Book.
Processing options enable you to specify the default processing for programs and reports.
Specify the beginning or the end of a range of dates that the system uses to select records from the Account Ledger table (F0911).
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.
Specify the beginning of the first range for the original value accounts.
Specify the end of the first range for the original value accounts.
Specify the beginning of the first range for the depreciation accounts.
Specify the end of the first range for the depreciation accounts.
Specify the beginning of the second range for the original value accounts.
Specify the ending of the second range for the original value accounts.
Specify the beginning of the second range for the depreciation accounts.
Specify the ending of the second range for the depreciation accounts.
Specify the participate percentage for the company.
Specify the percentage the system uses to multiply the amounts. The default value is 1.
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.
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.
Specify the business unit that is submitting the report.
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).
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.
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) |
Before completing the tasks in this section, set up these UDCs:
State & Province Codes (00/S).
ARG-DGI Transaction Doc. Type (76/AF).
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.
Select Legal Reports (G76A03B2), IIBB Perception.
Processing options enable you to specify the default processing for programs and reports.
Specify the tax code UDC 76A/TC that corresponds to IIBB perception.
Specify the fortnight number.
Specify the IIBB D.G.I. voucher number (including security digit) for the first through third months of the quarter to be processed.
Specify the security deposit amount for the first through third months of the quarter to be processed.
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.
Specify the number of the quarter that the system processes for the report.