This chapter contains the following topics:
Section 3.5, "Setting Up Corresponding Versions of Programs for Argentina"
Section 3.7, "Setting Up Localizations Additional Information for Argentina (Release 9.1 Update)"
Section 3.8, "Setting Up Print Authorization Codes for Argentine Suppliers"
Section 3.9, "Setting Up to Print Invoices and Shipment Notes for Argentina"
Section 3.10, "Setting Up the System to Generate the Text Payments File for Argentina"
Section 3.12, "Setting Up the System for Deferred Payments for Argentina"
Section 3.13, "Setting Processing Options for Additional A/B Information (P760101A)"
Section 3.15, "Entering Supplier Information for Small Contributors"
Section 3.17, "Specifying that Withholding Applies to a Small Contributor"
Section 3.18, "Setting Up Invoice Type M for Voucher Processing for Argentina"
Section 3.19, "Setting Up Credit Invoice Constants for Accounts Payable for Argentina"
Section 3.20, "Setting Up Tax Area Relationships for Credit Invoices for Argentina"
Section 3.21, "Setting Up Credit Invoice Status Rules for Argentina"
Section 3.22, "Setting Up Credit Invoice Constants for Accounts Receivable for Argentina"
Section 3.23, "Setting Up Payment Instruments for Credit Invoices for Argentina"
Setting up Argentina-specific UDCs enables you to use Argentine functionality. You also set up some base software UDCs with Argentina-specific values.
Set up UDCs for:
Foreign suppliers and supplier withholding
Credit invoice processing
SICORE
Fixed assets and inventory management
Perception reports
Accounts receivable drafts
Tax processing
Accounts payable
Shipment notes
VAT Reports
Set up Argentina-specific values in the base software UDCs, and set up these Argentina-specific UDCs.
The Administracion Federal de Ingresos Publicos (AFIP) has established a special codification for each state. You must set up the special codification in the Special Handling Code field of UDC 00/S as shown in this table:
Codes | Description 01 | Special Handling Code |
---|---|---|
CF | Capital Federal | 0 |
BA | Buenos Aires | 1 |
CA | Catamarca | 2 |
CO | Cordoba | 3 |
COR | Corriente | 4 |
ER | Entre Ríos | 5 |
JY | Jujuy | 6 |
MZ | Mendoza | 7 |
LR | La Rioja | 8 |
SA | Salta | 9 |
SJ | San Juan | 10 |
SL | San Luis | 11 |
SF | Santa Fe | 12 |
SE | Santiago del Estero | 13 |
TU | Tucumán | 14 |
CH | Chaco | 16 |
CHU | Chubut | 17 |
FOR | Formosa | 18 |
MI | Misiones | 19 |
NEU | Neuquen | 20 |
LP | La Pampa | 21 |
RN | Río Negro | 22 |
SC | Santa Cruz | 23 |
TF | Tierra del Fuego | 24 |
Note: Special Handling Code 15 does not exist. |
This UDC table enables you to define regional tax codes, and it is used on generic objects. To work with RG 3164 withholding, you must set up the value VAT RG3164 in this UDC table.
You set up gross income agreement codes to identify agreement types. The system uses these values when you process gross income withholding for suppliers.
For example, you might set up these gross income agreement codes:
Codes | Description |
---|---|
00 | Multilateral |
01 | Unilateral |
02 | Multilateral Agreement |
03 | Not Registered |
04 | Exempt |
05 | Special Regime |
99 | Without Agreement |
Set up value-added tax (VAT) withholding concepts to identify groups of items according to their withholding percentages. The system uses these values when you process VAT withholding for suppliers.
You must set up a code for invoice type M for voucher processing.
For example, you might set up these VAT withholding concepts:
Codes | Description |
---|---|
BIE | Goods |
CER | Cereals |
FLT | Shipment |
NO | No concept |
SER | Services |
IVM | Invoice M - VAT |
Note: You should include a value of blank so that you can assign that value to the records that are not subject to this withholding. |
You set up profit withholding condition codes as provided by the AFIP to define different supplier conditions for profit withholding. The system uses these values when you process profit withholding for suppliers.
For small contributor profit withholding, the system uses the values in the Description 2 field to determine if the supplier is registered, not registered, or is a small contributor. These codes must exist in the Description 2 field for codes used for small contributors:
M (Monotributista [small contributor])
N (No inscripto [not registered])
I (Inscripto [registered])
You assign a value from this UDC table when you set up suppliers in the A/B Tag File Maintenance – ARG program (P760101A). The system calls the A/B Tag File Maintenance – ARG program from the Supplier Master program (P04012).
This table shows the AFIP condition codes that you use to set up the profit withholding condition codes. You associate the AFIP condition codes with the profit withholding codes by entering the AFIP code in the Special Handling Code field of the 76/03 UDC table:
Code | Description 1 |
---|---|
1 | Registered |
2 | Not Registered |
3 | Not Categorized |
6 | Hourly or Daily Contract |
7 | Monthly Contract |
8 | Included in the Grains Fiscal Regime |
9 | Not Included in the Grains Fiscal Regime |
10 | Other Subjects Registered |
11 | Gas Stations Registered VAT Withholding |
12 | Public Services |
13 | General Rate - Sales or Rent Movable Things |
14 | Reduced Rate - Sales or Rent Movable Things |
15 | Substitute Withholding |
This table shows example of how you might set up codes in this UDC table.
Codes | Description 01 | Description 02 | Special Handling Code |
---|---|---|---|
. | |||
INS | Registered | I | 1 |
NOI | Not Registered | N | 2 |
NOR | No Withholding | 3 | |
MON | Small Contributor | M | 7 |
You set up profit withholding concepts to identify groups of items according to their profit withholding percentages. The system uses these values when you process withholding profits for suppliers.
You must set up a code for invoice type M.
For example, you might set up these codes:
Codes | Description |
---|---|
10 | Services |
20 | Rental income |
30 | Goods |
40 | Professional |
50 | Service location |
60 | Invoice type M - profit |
70 | Professional fees |
80 | Decentralized regime |
99 | No withholding |
Note: You should include a value of blank so that you can assign that value to the records that are not subject to this withholding. |
To meet the requirements of RG 830/00, you must set up UDC 76/04 to identify the concept that is used to withhold taxes for copyright, and set up the special handling code with the amount up to which no withholding will occur. According to RG 830, this amount is ten thousand pesos. For example, you might set up this concept code for RG 830/00:
Codes | Description 01 | Description 02 | Special Handling Code |
---|---|---|---|
60 | Derechos de Autor | NA | 10000 |
You set up gross income concept source codes to identify groups of items according to their gross income withholding percentages. The system uses the values in this UDC when you process gross income withholding for suppliers.
For example, you might set up these gross income concept source codes:
Codes | Description |
---|---|
BIE | Goods |
FLT | Shipment |
NOR | No withholding |
SER | Services |
Note: You should include a value of blank so that you can assign that value to the records that are not subject to this withholding. |
You set up gross income concept destination codes to identify groups of items according to their gross income withholding percentages. The system uses the values in this UDC when you process gross income withholding for suppliers.
For example, you might set up these gross income concept destination codes:
Codes | Description |
---|---|
BIE | Goods |
FLT | Shipment |
NOR | No withholding |
SER | Services |
Note: You should include a value of blank so that you can assign that value to the records that are not subject to this withholding. |
You set up contract concept codes to identify groups of items according to their contract withholding percentages. Set up the values in this UDC before processing withholdings for contractors.
For example, you might set up these contract concept source codes:
Codes | Description |
---|---|
ARC | Architecture |
ENG | Engineering |
Note: You should include a value of blank so that you can assign that value to the records that are not subject to this withholding. |
You set up gross income state source codes to identify the states that are the source of gross income taxes. The system uses the values that you set up in this UDC when you process gross income withholding for suppliers.
For example, you might set up these gross income state source codes:
Codes | Description |
---|---|
01 | Cordoba |
02 | Mendoza |
03 | Catamarca |
04 | Neuguen |
05 | Santa Fe |
30 | Buenos Aires |
31 | Buenos Aires - Branch 0001 |
32 | Buenos Aires - Branch 0002 |
99 | No withholding |
You set up gross income state destination codes to identify the states that are the destination of gross income taxes. The system uses these values when you process gross income withholding for suppliers.
For example, you might set up these gross income state destination codes:
Codes | Description |
---|---|
01 | Cordoba |
02 | Mendoza |
03 | Catamarca |
04 | Neuguen |
05 | Santa Fe |
30 | Buenos Aires |
31 | Buenos Aires - Branch 0001 |
32 | Buenos Aires - Branch 0002 |
99 | No withholding |
Set up codes for eventual concepts. Enter 1 in the Special Handling Code field for cleaning services concepts. The system uses the values that you establish when you process withholding for sistema único de seguridad social (SUSS) and cleaning services.
For example, you might set up these values:
Codes | Description 01 | Special Handling Code |
---|---|---|
(Blank) | (Blank) | N/A |
ABC | Professional | N/A |
DEF | Administrative | N/A |
LIM | Cleaning Services | 1 |
NOR | No withholding | 1 |
SER | Servicios de Limpieza | 1 |
Note: You should include a value of blank so that you can assign that value to the records that are not subject to this withholding. |
You set up values in this UDC table to identify small-contributor suppliers as those providing goods or services. You assign a value from this UDC table when you set up suppliers in the A/B Tag File Maintenance – ARG program (P760101A). The system calls the A/B Tag File Maintenance – ARG program from the Supplier Master program (P04012). You also enter a value from this UDC table when you set up the small contributor limits in the Small Contributor Limits program (P76A050).
Note: You should include a value of blank so that you can assign that value to suppliers who are not classified as small contributors. |
Examples of values are:
Codes | Description |
---|---|
(blank) | |
BIE | Goods |
SER | Services |
Set up values in this UDC table to specify the base amount on which the system applies the withholding percentage. You assign these values in the Contract Services Withholding Percentages program (P760405A) and the system uses them during the Update process of the automatic payment process.
The codes in this UDC table are not hard-coded. However, the system assumes that UDC codes are set up as shown in this table:
Codes | Description |
---|---|
1 | Gross amount |
2 | Taxable amount |
3 | Taxable + Tax amount |
4 | Taxable + nontaxable amount |
You use the values in the ARG-DGI Transaction Doc. Type (76/DT) UDC to associate SICORE document types with AFIP legal document types by specifying the AFIP legal document type in the Codes field and the associated SICORE document type in the Special Handling Code field.
The SICORE data structure defines the special codes shown in this table for document types that generate withholding:
Special Handling Code | Description |
---|---|
1 | Voucher |
2 | Receipt |
3 | Credit Note |
4 | Debit Note |
5 | Other Document |
6 | Payment Order |
In this example for RG 1415, the SICORE document type 1, shown in the Special Handling Code column, corresponds to type A and B vouchers:
Codes | Description 01 | Special Handling Code |
---|---|---|
01 | Invoice A | 1 |
02 | Debit Note A | 4 |
03 | Credit Note A | 3 |
04 | Receipts A | 2 |
06 | Invoice B | 1 |
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.
The SICORE data structure defines the special codes shown in this table for document types that generate withholding:
Special Handling Code | Description |
---|---|
1 | Voucher |
2 | Receipt |
3 | Credit Note |
4 | Debit Note |
5 | Other Document |
6 | Payment Order |
In this example for RG 1415, the SICORE document type 1, shown in the Special Handling Code column, corresponds to type A and B vouchers:
Codes | Description 01 | Special Handling Code |
---|---|---|
001 | Invoice A | 1 |
002 | Debit Note A | 4 |
003 | Credit Note A | 3 |
004 | Receipts A | 2 |
006 | Invoice B | 1 |
Set up VAT legal concepts to identify different types of legal activities. VAT legal concept codes are defined by the Administración Federal de Ingresos Públicos (AFIP). The system uses these values when you process VAT withholding for suppliers.
You must set up code 499 for invoice type M.
For example, you might set up these VAT legal concepts:
Codes | Description |
---|---|
110 | Services |
12 | Goods |
250 | Shipment |
76 | Cereals |
499 | Invoice type M - VAT |
Set up gross income legal concepts to identify different types of legal activities. Gross income legal concept codes are defined by the AFIP. The system uses the values in this UDC when you process gross income withholding for suppliers.
For example, you might set up these gross income legal concepts:
Codes | Description |
---|---|
25 | Goods |
55 | Shipment |
77 | Services |
Set up profit legal concept codes to identify types of legal activities. Profit legal concept codes are defined by the AFIP. The system uses these values when you process profit withholding for suppliers and when you print the SICORE reports.
For example, you might set up these codes:
Codes | Description |
---|---|
019 | Service location |
027 | Rental income |
110 | Services |
115 | Professionals |
116 | Professional fees |
128 | Goods |
Set up contract legal concepts to identify types of legal activities. Contract legal concept codes are defined by the AFIP. The system uses the values that you enter in this UDC when you process withholding for contractors.
Set up eventual legal concepts to identify types of legal activities. Eventual legal concept codes are defined by the AFIP. The system uses the values that you establish when you process withholding for SUSS and cleaning services.
Set up legal document types to classify tax ID numbers, including foreign tax IDs.
This table shows the AFIP valid document types:
Code | Description |
---|---|
80 | C.U.I.T. |
86 | C.U.I.L. |
87 | C.D.I. |
83 | Foreign Tax ID |
84 | Foreign ID |
This table provides an example of how you might set up UDC 76A/A0:
Codes | Description 01 | Special Handling Code | Hard Coded |
---|---|---|---|
080 | CUIT | 1 | Y |
084 | CUIT prov del exterior | na | N |
085 | DNI | na | N |
Note: When you set up document type CUIT, you must enter 1 in the Special Handling Code field so that the system validates the CUIT (clave única de identificación tributaria) number when it is entered or modified. |
You set unchangeable pay status codes to specify the pay statuses at which vouchers cannot be changed.
This table provides an example of how you could set up UDC 76A/EI:
Codes | Description 01 |
---|---|
# | Payment Process |
A | Approved |
P | Paid |
Set up the CUIT numbers for the country of origin of foreign suppliers.
This UDC code consists of the country of origin and the person/corporation code. Use the Description 01 field to set up the country CUIT, as shown in this example:
Codes | Description 01 |
---|---|
FRC | 55-00000430-7 |
FRP | 50-00000412-7 |
USP | 50-0000301-5 |
The system uses this table to define tax codes for Argentina, and it is used in Argentina objects. To work with RG 3164 withholding, you must set up the value VAT RG3164 in this UDC table.
The system uses these values to determine whether to compare the minimum amount to the taxable amount or the withholding amount. Required values are:
Codes | Description 01 |
---|---|
Blank | No minimum withholding. |
1 | Taxable amount is greater than or equal to the minimum amount. |
2 | Taxable amount is greater than the minimum amount. |
3 | Withholding amount is greater than or equal to the minimum amount. |
4 | Withholding amount is greater than the minimum amount. |
Set up values in this UDC table to identify the voucher document types that the system exempts from VAT and profit withholding validations. When you run the Create Payment Groups program (R04570) for Argentina or enter a manual payment in the Payment with Voucher Match program (P0413M), the system uses the values in this UDC table to exclude transactions from the determination of whether a transaction exceeds the limits established for a 12-month period.
Set up values in this UDC table to identify the tax rate areas that the system exempts from VAT and profit withholding validations. When you run the Create Payment Groups program or enter a manual payment, the system uses the values in this UDC table to exclude transactions from the determination of whether a transaction exceeds the limits established for a 12-month period.
Set up values in this UDC table to identify the legal form code that the system uses to process SUSS withholdings and profit withholdings for foreign beneficiaries. The legal form codes are assigned by the AFIP. When you run the S.U.S.S. TXT File - Withholding Information report (R76A4002) and the F2003 Profit Withholding to External Beneficiaries report (R76A4005), the system uses the values in this UDC table to identify the legal form for which the flat file is generated. For example, to process SUSS withholdings, create a code 2003, and to process profit withholdings for foreign beneficiaries, create a code 2004.
Set up values in this UDC table to identify the legal tax code that the system uses to process SUSS withholdings and profit withholdings for foreign beneficiaries. The legal tax codes are assigned by the AFIP. When you run the S.U.S.S. TXT File - Withholding Information report (R76A4002) and the F2003 Profit Withholding to External Beneficiaries report (R76A4005), the system uses the values in this UDC table to identify the legal tax code for which the flat file is generated.
Set up values in this UDC table to identify the legal document type that the system uses to process SUSS withholdings and profit withholdings for foreign beneficiaries.
The system uses the values in this UDC table to determine the SIRE (Sistema Integrado Retenciones Electronicas) country code of the supplier when processing profit withholdings to external beneficiaries.
Set up values in this UDC table to determine the withholding rate when CDI is applicable to profit withholdings for foreign beneficiaries.
Set up values in this UDC table to determine the withholding rate when CDI is not applicable to profit withholdings for foreign beneficiaries.
Set up values in this UDC table to determine whether the profit withholdings are grossed up when you process profit withholdings for foreign beneficiaries.
Before you process credit invoices, set up these UDCs.
You must specify a value of 1 in the Special Handling Code field for the document types that might require credit invoices.
Note: You should set up one or more new document types for vouchers that have credit invoices attached. |
You must specify a value of 1 in the Special Handling Code field for the document types that might require credit invoices.
Note: You should set up one or more new document types for vouchers that have credit invoices attached. |
The document type that is used for voucher acceptance (for example, FX) must be set up in the Document Type (00/DT) and the Document Type - Vouchers Only (00/DV) UDCs.
You must define an address book category code to identify the suppliers and customers who issue or receive credit invoices.
You can use any category code, but you must specify the number of the category code that you are using in the General Constants program (P76A20).
You must set up a code for the category code that you specify. You can use any code. If the supplier or customer has a code other than blank in this category code, the system assumes that a credit invoice must be issued.
Credit invoice status codes represent the current status of a credit invoice and determine the event to be processed. For example, you might set up these credit invoice status codes:
Code | Description 01 | Special Handling Code |
---|---|---|
(Blank) | (Blank) | N/A |
01 | Initial | N/A |
05 | To Accept | N/A |
10 | Accepted | A |
15 | Pay with Cash | N/A |
Note: The values in the Special Handling Code field do not apply to the JD Edwards EnterpriseOne Accounts Payable system; they are used by the JD Edwards EnterpriseOne Accounts Receivable and JD Edwards EnterpriseOne Sales Order Management systems, except in the case of a value of 1, which is used to specify a reclassification of losses. |
Events are the different points in the life cycle of a credit invoice. Use them to determine which valid status the invoice credit must have to pass through that event. JD Edwards EnterpriseOne software provides hard-coded values for this UDC.
You use special payment instrument codes to identify the payment instruments (for example, X) that cancel the original voucher and automatically generate another voucher with the document type that is specified in this UDC (for example, FX) for the voucher amount less the withholding amount.
In the Description 02 field, specify the type of document to generate, followed by the credit invoice class and the payment term to assign to it. For example, you could specify FXACEPCDO in the Description 02 field, where:
FX is the credit invoice document type.
ACEP is the supplier classification that identifies the liability account for credit invoices.
You must set up the corresponding PCxxxx AAI.
CDO is the payment term of the acceptance voucher.
You would set up this special payment instrument code like this:
Code | Description 01 | Description 02 |
---|---|---|
X | Credit invoice accepted | FXACEPCDO |
Set up these UDCs before you run the Step III - Self Withholdings program (R76A96).
You must enter 1 in the Description 02 field on UDC 76/04 to allow the columns to appear in the SICORE, as shown in this table:
Codes | Description 01 | Description 02 |
---|---|---|
None | . | None |
10 | Services | 1 |
20 | Rental Income | 1 |
30 | Goods | 1 |
40 | Professional | 1 |
50 | Service Location | 1 |
70 | Professional Fees | 1 |
80 | Decentralized Regime | 1 |
99 | No Withholding | None |
Set up profit legal concept codes to identify types of legal activities. Profit legal concept codes are defined by the AFIP. The system uses these values when you process profit withholding for suppliers, and when you print the SICORE reports.
You must set up code 099 for invoice type M.
For example, you might set up these codes:
Codes | Description |
---|---|
019 | Service location |
027 | Rental income |
099 | Invoice M - profit |
110 | Services |
115 | Professionals |
116 | Professional fees |
128 | Goods |
Set up these UDCs before processing fixed assets and inventory adjustments.
You must use Chart of Accounts Category Code 15 to specify the Asset Type for each account that is used in the JD Edwards EnterpriseOne Fixed Assets system. The transactions from the Account Ledger table (F0911) are grouped, and Annex A is generated based on the Asset Type from Category Code 15. You must define asset types in UDC 09/15 before you set up accounts.
You use UDC 76A/12 to set up the relationship between document types and the column on the Annex A report in which they will be printed. You might set up this UDC as shown in this table:
Codes | Description 01 | Special Handling Code |
---|---|---|
AD | Disposals | B |
AT | Transfers | T |
Set up these UDCs that the system uses when you produce the Perception report:
ARG - Concept Code (76A/CI)
ARG - Concept Code (76A/CR)
Perception Code SICORE (76A/PE)
Use UDC 76A/CI to set up tax category codes in conformity with General Resolution 738/99. The system uses these values when you run the Perception Report (R76A8050) program.
This table provides an example of how you might set up UDC 76A/CI:
Codes | Description 01 |
---|---|
217 | Impuesto a las ganancias |
767 | Impuesto al valor agregado |
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 system uses these values when you run the Perception Report (R76A8050) program.
Important: This description is the concept of the perception certificate. |
This table provides an example of how you might set up UDC 76A/CR:
Codes | Description 01 |
---|---|
493 | Importaciones |
663 | Importacion de carnes |
You must associate the tax codes from UDC 76A/TC with the perception activity codes from UDC 76A/CR and the tax categories from UDC 76A/CI. You set up this association in UDC 76A/PE. The system uses these values when you run the Perception Report (R76A8050) program.
You specify the tax codes in the Codes field, the activity code in the Description 01 field, and the tax category in the Description 02 field, as shown in this example:
Codes | Description 01 | Description 02 |
---|---|---|
FTIMP01 | 663 | 767 |
IVA21PIA | 248 | 767 |
IVAPERA | 248 | 767 |
PER | 663 | 217 |
PER1 | 265 | 767 |
PER2 | 267 | 767 |
PRU | 463 | 217 |
REB-PER | 663 | 217 |
Set up these UDCs for standard tax processing and to meet the requirements of RG 1361 for sales and purchase transactions.
Set up this UDC for the VAT Purchasing Ledger. You must add the currency code that AFIP requires in the Description 02 field of this UDC, as shown in this example:
Codes | Description 01 | Description 02 |
---|---|---|
ARS | Argentine Peso | ARS |
USD | U.S. Dollar | USD |
Set up this UDC for the for the Sales VAT Ledger. As established by general resolution, the fiscal authority (AFIP) states that the different invoices which are reported in the Sales VAT Ledger must have this codification:
Document types that correspond to exempt operations must be listed in UDC (00/DI) with Z, X, or E in the second position of the Special Handling Code field.
Document types that correspond to nontaxable operations must be listed in UDC (00/DI) with N in the second position of the Special Handling Code field.
This example shows a document type with Z in the second position of the Special Handling Code field:
Codes | Description 01 | Special Handling Code |
---|---|---|
RI | Invoice | 1Z |
Document types of printed invoices that originated in the JD Edwards EnterpriseOne Sales Order Management system or the JD Edwards EnterpriseOne Accounts Receivable system and that have an exempt concept must be configured in this UDC. Documents with VAT must have a blank value in the second position of the Special Handling Code field.
If the same invoice has a combination of different concepts (for example, a VAT rate with exempt or nontaxable concepts) and this UDC contains a Z, X, E, or N in the Special Handling Code field for the document type, the system writes a blank in the Sales VAT Ledger magnetic file.
If the Special Handling Code field in the UDC contains an invalid value or is blank and the invoice concept is exempt, the program generates a warning message in the Work Center and writes an E in the Sales VAT Ledger magnetic file.
If the Special Handling Code field in the UDC contains an invalid value or is blank and the invoice concept is nontaxable, the program generates a warning message in the Work Center and writes an N in the Sales VAT Ledger magnetic file.
If the Special Handling Code field in the UDC contains an invalid value or is blank and the invoice has both exempt and nontaxable concepts, the program generates a warning message in the Work Center and writes an E in the Sales VAT Ledger magnetic file.
In addition, the fiscal authority requires that the program validate that the tax amount is less than the taxable amount and that the taxable amount must be less than the gross amount of the invoice. If these conditions are not met and the invoice has lines with tax explanation code VT, the program generates a message in the Work Center.
Set up this UDC for the VAT Purchasing Ledger and the Sales VAT Ledger. For the VAT Purchasing Ledger, use an Address Book category code (01/xx) to list the VAT condition of subjects. Enter these AFIP codes in the Special Handling Code field:
AFIP Code | Description |
---|---|
01 | VAT inscript |
02 | Non-inscript VAT |
03 | Non responsible VAT |
05 | Final consumer |
This table is an example of UDC 01/24 for the VAT Purchasing Ledger:
Codes | Description 01 | Special Handling Code |
---|---|---|
. | . | . |
INS | Registered | 01 |
NOI | Not registered | 02 |
NOR | No withholding | 03 |
You specify the address book category code that you are using in the processing options of the V.A.T Purchasing Ledger program (R760499A).
For the Sales VAT Ledger, use an address book category code (01/xx) to list the responsible types. Enter the values that are defined by AFIP in the Special Handling Code field as shown:
Codes | Description 01 | Special Handling Code |
---|---|---|
. | . | . |
INS | Inscripto | 01 |
NOI | No Inscripto | 02 |
NOR | No retener | 03 |
You specify the address book category code that you are using in the processing options of the Sales VAT Tax Subsidiary program (R76A8060). The Sales VAT magnetic file lists the value from the Special Handling Code field for the responsible type.
Set up this UDC table with values that you use to specify whether tax is calculated on tax. You use the values that you setup when you set up tax constants.
Use Item ASIB codes to specify the allowed values that define the invoice buckets for tax codes. The invoice bucket is the line on which the invoice tax will be printed. All tax codes with the same invoice bucket number appear on the same invoice line.
You assign invoice buckets to tax codes when you set up tax definitions.
Set up this UDC table with codes that you use when you specify a tax group in the tax constants.
Set up this UDC for the VAT Purchasing Ledger. Set up this hard-coded value in UDC 76A/CF:
Codes | Description 01 | Hard Coded |
---|---|---|
(blank) | Default | N |
C | Fiscal Controller | Y |
Set up this UDC for the VAT Purchasing Ledger. Set up these hard-coded values in UDC 76A/DE:
Codes | Description 01 | Hard Coded |
---|---|---|
(blank) | Default | N |
CORI | Rpt Deposit Earning Correction | Y |
DIS4 | Simplified Import Destination | Y |
DIS5 | DAP Simplified Import Dest. | Y |
EC01 | Export to Consumption | Y |
EC02 | Expt to Consmptn w/DIT | Y |
EC03 | Exp to consmptn/minerals conc | Y |
EC09 | Exp to Cons w/DIT wo/trnsfrm | Y |
IG01 | Imp to cons ige ops wo/trans | Y |
Set up this UDC for the Sales VAT Ledger. List the external CUITs that are defined by AFIP for foreign countries in UDC (76A/FJ):
Codes | Description 01 |
---|---|
FRC | 55-00000430-7 |
FRP | 50-00000412-7 |
USP | 50-0000301-5 |
The system retrieves the CUIT from this UDC based on the Country and Person/Corporation Code of the supplier or customer in the JD Edwards EnterpriseOne Address Book system. For example, if the supplier's Country code is FR and the Person/Corporation Code is C, the system retrieves the CUIT for the FRC code in this UDC.
Set up this UDC for the VAT Purchasing Ledger. Set up these hard-coded values in UDC (76A/OC):
Codes | Description 01 | Hard Coded |
---|---|---|
(blank) | Default | N |
E | Exempt Opt | Y |
X | Foreign Export/Import | Y |
Z | Export/Import Tax Free zone | Y |
In addition to the standard software UDCs for accounts payables, set up these Argentina-specific UDCs and these base UDCs with Argentina-specific values.
Set up this UDC before you generate the text payments file. You use this UDC when working with RG 1547 and RG 1361. RG 1547 uses the value in the Code and the Special Handling Code fields, while RG 1361 uses the value in the Code and the Description 02 fields. This example illustrates possible values for UDC 00/CC:
Codes | Description 01 | Description 02 | Special Handling Code |
---|---|---|---|
ARA | Pesos Argentinos | ARS | 002 |
ARS | Pesos | ARS | 123 |
USD | Dolares | USD | 001 |
Set up UDC 00/PY to include the deferred check payment instrument (D), entering 1 in the first position of the Special Handling Code field as illustrated in this example:
Codes | Description 01 | Special Handling Code |
---|---|---|
D | Draft by Invoice (A/R and A/P) | 1 |
The system uses these values when you process deferred payments.
In addition to setting up payment instruments for standard payment processing, specify that no withholding takes place if withholding vouchers are written off when payments are made in bonds.
The system stores unfulfilled withholding in a table so that you can generate a report showing these amounts when required by the fiscal authority.
You specify whether withholding is saved in permanent files or in unfulfilled withholding tables by completing the Special Handling Code field for the payment instrument in UDC 00/PY. This UDC does not affect withholding calculations.
The value in the Special Handling Code field consists of these parts:
Position | Description |
---|---|
First Position | Specifies whether the payment is deferred. Values are:
|
Second Position | Specifies whether VAT is withheld. Values are:
|
Third Position | Specifies whether profit taxes are withheld. Values are:
|
Fourth Position | Specifies whether taxable amounts and profit withholding is stored in the Profit Withholding - Payments Done table (F760406A). Values are:
|
Fifth Position | Specifies whether the system applies withholding taxes for security services. Values are:
The system treats a blank value as a Y. |
Sixth position | Specifies whether the system accumulates the withholding taxes in the F76A0456 table. Values are:
The system treats a blank value as a Y. |
This table lists the results of various special handling code combinations. The underlined character represents a blank space:
Special Handling Code | Explanation |
---|---|
_YYYY | All withholding is made and the profits are accrued. This code is the same as leaving the Special Handling Code field blank. |
_YYN | VAT is withheld, but profits are not accrued. |
_YNY | VAT is withheld, but profits taxes are not withheld. The taxable amount is accrued for the unfulfilled withholding calculation. |
_YNN | VAT is withheld, but profits taxes are not; profits are not accrued. |
_NYY | VAT is not withheld; but profit taxes are withheld, and profits are accrued. |
_NNN | No taxes are withheld. The VAT and profit tax withholding are saved in temporary files, and profits are not accrued. |
Note: If you include a 1 in the first position in any of the preceding combinations, the payment is considered to be a deferred payment. |
This table is an example of payment instruments for Lecops payments:
Codes | Description 01 | Description 02 | Special Handling Code |
---|---|---|---|
J | Lecops | No retiene ni acumula RET | NNN |
N | Cheque dif con Lecops | No RET si acumula Gcias | 1YNN |
Use this UDC to identify the issue place of legal documents. For example, you might set up codes for each of your warehouses and for your main office.
Set up this UDC before you generate the text payments file. You must set up these payment types:
Codes | Description |
---|---|
01 | Finance entities accounts deposits |
02 | Draft or bank transfers |
03 | Checks or cancellation checks |
04 | Credit cards |
05 | Credit invoice |
06 | Endorsable checks |
07 | Other |
Set up this UDC before you generate the text payments file. You must set up two classifications of the operations:
01 - Cash
02 - Future Payment Term
The payment terms that are considered cash (01) must be listed in the UDC. Those that are not in the UDC are considered future payment terms (02).
Set up standard software UDCs for sales order processing, and set up these Argentina-specific UDCs to print shipment notes.
Set up these values to work with shipment notes:
Code | Description |
---|---|
R | Remito |
X | Shipment note |
Set up this value to work with shipment notes:
Code | Description |
---|---|
091 | Remito |
Set up the UDCs for standard tax processing and these UDC tables to meet the legal requirements for VAT reports.
When you work with VAT reports, you specify if the report that you are generating is the original version, or if it is an amendment. In case you need to submit amendments more than once, you must specify the sequence number of the current report.
You assign a value from the Presentation Sequence UDC table in the processing options for the RG 3685 Purchase and Sales Information program (R76A010) when you run the program to generate the header for the VAT reports that you want to submit to the fiscal authorities.
The JD Edwards EnterpriseOne system provides hard-coded values for this UDC table. Some valid values are:
Codes | Description |
---|---|
00 | Original |
01 | Amendment 1 |
02 | Amendment 2 |
You can add additional records to this UDC table if needed.
The system uses this UDC table to establish relationships between the tax rates that your company uses and the codes that the fiscal authority sets for those rates.
When you generate VAT reports, the system checks if the VAT rate in the transaction is listed in this UDC, and reports the code published by AFIP in the output file.
The code is the four-digit value that the system uses when processing transactions, to identify the percentage that is calculated for a specific VAT rate, expressed without commas or periods. When you run VAT reports, the system searches for this code in the transaction record, automatically. If the value is listed in the Relationship Tax AFIP UDC table, the report displays the tax area for the transaction using the one-digit number assigned to the rate in this table. You can use the Description 01 field to enter a description for the code (the system does not use the information in this field). The data in the Description 02 field is the code listed in the catalog published by the government.
The JD Edwards EnterpriseOne system provides hard-coded values for this UDC table. Verify that the following codes are set up in your system:
Codes | Description 01 | Description 02 |
---|---|---|
NOGR | Non taxable | 1 |
EXEN | Exempt | 2 |
0000 | 0% | 3 |
1050 | 10,50% | 4 |
2100 | 21% | 5 |
2700 | 27% | 6 |
0500 | 5% | 8 |
0250 | 2,50% | 9 |
VAT Commission is a specific VAT rate applicable to companies that work with third parties as commission agents for specific economic activities. When you work with the VAT reports required by the RG 3685, the information about this rate must be specified in the text files generated.
Set up this UDC with the codes you use to identify the VAT Commission Tax Rate areas that your company uses. The tax area must exist in the Tax Areas (F4008) and the Additional Tax Areas - Arg (F764008A) tables.
For example, you might set up a record like this, where the Code field is the code for the Commission VAT tax rate:
Codes | Description 01 |
---|---|
GRALCOM | Commission VAT Rate |
You can use the Description 01 field to enter a description for the code for your own references. The system does not use the information in this field.
RG 3685 requires that you report the transactions that include service imports in a separate file. The transactions must also specify if the document for such transactions is a voucher, a contract or other type of document, according to a code system.
Set up the Service Imports Document Types UDC table with the document types that your company uses to identify service imports transactions. Use the Special Handling Code field to identify the document according to the following list:
1: Enter 1 for the document types that are vouchers. If you leave the SHC field blank, the system assumes the document is a voucher.
2: Enter 2 to specify that the document is a contract.
3: Enter 3 for all other document types.
The system uses this information when you work with the Service Import VAT report for RG 3685.
For example, you might set up a record like the following:
Codes | Description 01 | Special Handling Code |
---|---|---|
FT | Service Imports | 3 |
In this example, the Code field is the internal document type, the Special Handling Code indicates that this is not a voucher or a contract, but "other" document, and the Description 01 is a description of that document.
The system only uses the information in the Description 01 field when the Special Handling Code is set to 3.
This section discusses how to set up AAIs for:
Supplier withholding
Deferred payments
Credit invoice processing
Accounts receivable draft processing
Inventory inflation adjustment
See Also: |
You must set up these AAIs for VAT, gross income, contract, cleaning, and eventuals withholding and associate them with the appropriate accounts:
$I: VAT withholding account
$G: Profit withholding account
$Bxx: Gross income withholding account
The variable xx in this AAI specifies the state.
$S: Contract withholding account
$A: Eventuals withholding account
As an alternative, you can set up $ADEF (eventual services including the withholding concept).
$L: Cleaning services
As an alternative, you can set up $LLIM (cleaning services including the withholding concept).
$Q: SUSS withholding
PC$I: VAT withholding control account
PC$G: Profit withholding control account
PC$L: Cleaning services control account
PC$Bxx: Gross income withholding control account
The variable xx in this AAI specifies the state.
PC$S: Contract withholding control account
PC$A: Eventuals withholding control account
When setting up $B and PC$B for gross income, you must append the state number to the suffix. For example, if the state number is 01, the AAI becomes $B01 and PC$B01.
For VAT, profits, eventuals, and contract accounts, the system can associate current accounts by concept. For example, you might set up $IEL. If the system does not find specific accounts, it uses the generic withholding codes ($I, $G, $A, and $S).
Set up AAI PD for the control account that will be charged for deferred checks, as illustrated in this example:
Seq No. | Item. No. | Description | Co | Bus Unit | Obj Acct | Sub | Install System |
---|---|---|---|---|---|---|---|
4.041 | PD | Deferred Checks Control Acct. | 00028 | 28 | 1115 | CTRL | 04 |
You must set up the PT and PC AAIs to process credit invoices.
You must create a PTxxxx AAI for the original tax area and one for the temporary tax area. The PTxxxx AAI for the original tax area must specify the tax fiscal credit account. The PTxxxx AAI for the temporary tax area must specify a temporary tax account.
When vouchers that require a credit invoice are posted, the offset of the temporary tax area is charged.
The reclassification process uses the Credit Invoice Tax Area Relationship (F76A25) table to cancel the temporary fiscal credit and charge the final one.
The PCxxxx AAI identifies the supplier class that corresponds to the debts from credit invoices that are represented by the voucher that is defined for credit invoices. This AAI must use a liability account.
This offset is charged during acceptance and then canceled when the accepted credit invoice is paid.
When you process accounts receivable drafts, you can use the government-issued Provincial Obligation Letters (Lecops) as the payment instrument.
Set up these AAIs for Lecops:
RDL (RD + payment instrument)
RD1L (RD1 + payment instrument)
RD2L (RD2 + payment instrument)
You must set up the following Distribution AAIs to process inflation inventory adjustment:
3910: Inventory Stock Valuation - Adjustment
Use this AAI to identify the inventory account for the inflation adjustment process.
3911: Expense or Cost of Goods Sold - Stock Valuation Adjustments
Use this AAI to identify the results account, which serves as the offset to the inventory adjustments account.
This section discusses how to set up next numbering for withholding taxes and for profit withholding certificates (traceability codes).
You also set up next numbering for legal document numbering and VAT and profit withholding certificates.
You must set up next numbers by company, fiscal year, or both, for the tax withholding document types $A, $G, $I, $L, and $S. The system uses this setup to obtain the numbering for supplier tax withholding certificates.
This table includes examples of next numbering setup:
Document Company | Document Type | Description | Check Digit | Next Number Range |
---|---|---|---|---|
00028 | $G | Profit Withholding | N/A | 115 |
00028 | $I | VAT Withholding | N/A | 111 |
00028 | $S | Contract Withholding | N | 5 |
00028 | $A | Eventuals Withholding | N | 26 |
0028 | $L | Cleaning Services Withholding | N | 40 |
Note: Next numbers for gross income withholding are assigned according to state specifications. Therefore, the only gross income document type for which you must set up next numbers is gross income rectifications. |
You set up temporary next numbers for traceability codes (for profit withholding certificates) in the standard software Next Numbers program (P0002). The system uses the temporary next numbers when you run the F2003 Profit Withholding to External Beneficiaries (R76A4005) and the S.U.S.S. TXT File- Withholding Information (R76A4002) programs.
After you submit the report to the fiscal authorities and receive the official traceability code in return, you use the Withholding Certificates Legal Number Maintenance - 76A program (P76A001) to relate the internal certificate number with the certificate number issued by the AFIP.
See Processing SIRE Withholding Reports (Release 9.1 Update)
Form Name | Form ID | Navigation | Usage |
---|---|---|---|
Set Up Next Numbers by System | W0002C | In the Fast Path field, enter nn.
On the Work With Next Numbers form, select system 76A. |
Set up next numbers for traceability codes in profit withholding certificates. |
Access the Set Up Next Numbers by System form.
In the sixth row, enter 76A.
For the sixth position under the Use column, enter a next number in the corresponding Next Number field. For example, enter 1.
Do not select this check box for traceability codes.
You must set up the document types and the corresponding AAIs that are used in the process of adjusting works in progress for inflation. You adjust for inflation to manage your inventory.
This section discusses how to set up AAI document types.
Access the Set Up AAI Document Type form.
Figure 3-1 Set Up AAI Document Type form
Enter a value that exists in the Document Type (00/DT) UDC table.
Enter a value that exists in the Document Type (00/DT) UDC table.
Enter a number used to specify sequence and retrieve accounting information.
Some country-specific functionality requires that you create versions of the same name for a country-specific program and a base software program. For example, to have the system access the processing options for a country-specific voucher program, you might need to set up a version named XYZ for the country-specific voucher program and a version named XYZ of the Standard Voucher Entry (P0411) program.
Set up corresponding versions for these programs:
Argentina Program | Base Software Program |
---|---|
AR SOP Print Credit Invoice (R76A0023) | Invoice Print (R03B505)
See Understanding How to Process Credit Invoices for Accounts Receivable and Sales Orders for Argentina. |
PO - Update Receipt Register from Electronic Input (R76A551D) | Update Receipts Header (R03B551)
See Understanding How to Upload Automatic Receipts for Argentina. |
PO Interest Invoice (R76A03B2) | Generate Delinquency Fees (R03B525) |
PO - Invoice Print A/R (R76A03B5) | Invoice Print (R03B505)
See Understanding How to Process Credit Invoices for Accounts Receivable and Sales Orders for Argentina. |
PO Invoice/Shipment Note Print (R76A565) | Invoice Print (R42565)
See Understanding How to Process Credit Invoices for Accounts Receivable and Sales Orders for Argentina. |
Perception Report (R76A8050) | PO Invoice/Shipment Note Print (R76A565)
PO - Invoice Print A/R (R76A03B5) |
F0411 Tag File Maintenance (P760411A) | Standard Voucher Entry (P0411)
Voucher Entry MBF Processing Options (P0400047) Note: The Standard Voucher Entry (P0411) program and the Voucher Entry MBF Processing Options (P0400047) program must also have identically named versions. |
Additional A/B Information (P760101A) | Address Book Revisions (P01012) |
PO Sales Order Entry (P76A4210) | Sales Order Entry (P4210) |
A/P Auto Payment Register (R76A0476)
F0411 Tag File Maintenance (P760411A) See Understanding Credit Invoices for Accounts Payable for Argentina. |
Credit Invoice Acceptance (P04571) |
Print PCG Detail - ARG (R760476A) | Work With Payment Groups (P04571) |
This section provides an overview of legal numbering, lists prerequisites, and discusses how to:
Establish relationships between document types.
Set up next numbers for legal numbering.
Legal numbering complies with the legal requirements that are stipulated in General Resolution 1415.
Legal numbering can be set up for invoices and shipment notices, and is assigned by issue place and DGI (Direccion General Impositiva) document type.
The legal number has these parts:
The document type assigned by the Administracion Federal de Ingresos Publicos (AFIP). For example, the document type might be 01-Invoice.
The invoice letter (A, B, C, E, and so on).
The issue place (where the voucher was issued).
A next number.
To set up legal numbering, you set up a relationship between document types and you set up next numbers.
Set up AFIP document type relationships to cross-reference JD Edwards EnterpriseOne document types and legal invoice groups to legal document types. The AFIP defines both legal invoices groups and legal document types.
The JD Edwards EnterpriseOne document type and the legal invoice group (which is assigned based on the tax area that is used during voucher entry) determine the legal document type of the invoice by using the AFIP document type relationship that you set up.
Before you complete the tasks in this section:
Set up the Document Types - All Documents in UDC (00/DT).
Set up the ARG-DGI Transaction Doc Type in UDC (76/AF).
Access the Rel Type Doc./Group/Doc DGI Maintenance form.
Enter a user-defined code from 00/DT that identifies the origin and purpose of the transaction. The system reserves several prefixes for document types, such as vouchers, invoices, receipts, and time sheets. The reserved document type prefixes for codes are:
P: Accounts payable documents
R: Accounts receivable documents
T: Time and Pay documents
I: Inventory documents
O: Purchase order documents
S: Sales order documents
Enter a code that identifies the invoice group. Values are:
A
B
C
Enter the legal document type given by DGI (Direccion General Impositiva) for documents.
Access the Next Number Maintenance form.
Enter a value that exists in the ARG-DGI Transaction Doc. Type (76/AF) UDC table to specify the legal document type given by DGI for documents.
Enter the location where the invoice or the shipment note is printed.
You must specify the issue place of the invoice or shipment note that you want to print in the Issue Place processing option of the PO - Invoice / Shipment Note Print program (R76A565) or in the PO - Invoice Entry (P03B11) - ARG - 03B program (P76A03B1).
Enter Y (yes) to specify that the document is a shipment note. Enter N (no) to specify that the document is not a shipment note.
Enter a value that exists in the Document Type - All Documents (76/AF) UDC table to specify a document type for which the system uses the same numbering scheme as the document type that you entered in the AFIP Doc Type field.
If you set up next numbers by company or by company and fiscal year, a document type can share the same next number sequence as another document type. Same As Document Type refers to the document type that controls the next number the system uses.
For example, you create a document with a document type of RR. The document that you create should use the same next number sequence as regular invoices or RI document types. In this case, define the RR document type setup record with a Same As Document Type of RI.
Note: In Argentina, due to legal restrictions, you cannot use the Same As functionality with a different document ID. You must set up the document type that matches the AFIP doc type document ID. |
Enter the number that the system will assign next. The system can use next numbers for voucher numbers, invoice numbers, journal entry numbers, employee numbers, address numbers, contract numbers, and sequential W-2s. You must use the next number types already established unless you provide custom programming.
This section provides an overview of localizations additional information setup, lists a prerequisite, and discusses how to:
Run the Additional Info Setup program.
Set processing options for Additional Info Setup program (R7000100).
Localizations Additional Information is a tag-table methodology that captures and stores country-specific information. The system uses this information for different purposes.
Before you can start working with Localizations Additional Information, you must run the Additional Info Setup program (R7000100) to generate the required tables that store the additional data.
This setup also generates the forms where you enter the pre-defined information that is saved to the Localizations Additional Fields tables.
The system launches the Localizations Additional Information forms from the Regional Info row menu option from the specific programs that require additional data when your user profile country preference is set to AR (Argentina).
When you run the Additional Information Setup program, the system also generates all the additional fields required in the appropriate Regional Info forms. The forms for Localizations Additional Information, group the pre-defined data fields into the following tabs, according to the type of data that you enter:
String Data: The information that you enter in the pre-defined fields listed in this tab is a set of alpha-numeric characters.
Numeric Data: The information that you enter in the pre-defined fields listed in this tab is a set of numeric characters.
Date: The information that you enter in the pre-defined fields listed in this tab are dates.
Character: The information that you enter in the pre-defined fields listed in this tab are single characters.
For Argentina, the tables that the Additional Info Setup program (R7000100) generates to work with additional information are:
Header Localization Additional Data (F7000100)
Base Object / Tag Table Definition (F7000120)
Detail Localization Additional Data (F7000110)
Localizations Additional Fields Accounts Payable Ledger - 04 (F700411)
Localizations Additional Fields Tax Areas - 04 (F704008)
Every time you run the Additional Information Setup program, the system regenerates the tables required to work with the solution. You do not need to run this program multiple times but if you do, the existing data that you entered and that is saved in the Additional Information tables, is not affected.
Before you complete the task in this section, verify that the Localization Country Code field in your user profile is set to AR (Argentina).
Select System Administration Tools (GH9011), Batch Versions.
Alternatively, enter BV in the Fast Path field.
In the Work With Batch Versions - Available Versions form, enter R7000100 in the Batch Application field to work with Additional Info Setup program.
This section provides an overview of the Print Authorization Code (CAI) and discusses how to:
Enter the autoprinter company status.
Enter the CAI number.
General Resolution 100 (RG100) requires that a numerical Print Authorization Code (CAI) with an expiration date be printed on the bottom-right margin of type A and B vouchers that are issued by companies in the course of business. Type C vouchers are not affected by the regulation.
RG100 establishes that issuance of invoices or equivalent documents, as well as their printing by companies that are authorized to do so, is essential for tax purposes and also ensures the transparency of business principles. To work within RG100 parameters, you must indicate whether the company prints its own invoices.
Likewise, for taxpayers whose operations are significant in terms of volume and quality, the ability to print their own vouchers is beneficial because it helps facilitate their business operations and administrative tasks.
The CAI number is assigned by the AFIP, as stipulated in RG100. This number is assigned to all companies that print their own invoices. These companies must be registered and authorized by the fiscal authority to print their own invoices. Once registered and authorized, the company is given a CAI number, which must be printed on all legal invoices.
The CAI number is unique for each company.
Access the RG 100 - Autoprinter Supplier Control form.
Figure 3-4 RG 100 - Autoprinter Supplier Control form
Specify whether the system verifies if the supplier is set up as an autoprinter.
Access the RG 100 - CAI Company - ARG - 00 form.
Enter the legal document type given by DGI for documents.
Enter the location where the invoice or the shipment note is printed.
Enter a number assigned to a supplier by legal authorities in Argentina, as stated in General Resolution 100. It is a unique ID given to all the companies that are autoprinters (that is, companies that print their own invoices).
These companies must be registered and authorized by legal authorities to print their invoices. Once they are registered and authorized, they are given a CAI (autoprinter inscription number), which they must print on every invoice.
Enter the date when a transaction, contract, obligation, preference, or policy rule becomes effective or ceases to be in effect.
This section provides overviews of issue places and bar codes, lists prerequisites, and discusses how to:
Add the CIF code.
Add record type $C.
Relate issue places to address book records.
Article 11 of General Resolution 3434 stipulates that the commercial address that appears on the invoice or equivalent document must be the business or physical location where the invoice is issued.
In the case of shipment notes or equivalent documents, the location where goods are issued (warehouse or depot) must be the business address. The address of the place where goods are dispatched must be the same as the issue place address.
CIF codes relate the issue place with an address book record, which stores the address and other data about the issue place.
Setting up this relationship causes the invoice printing programs to retrieve the issue place address instead of the company address.
If this relationship is not defined, the business address is printed instead of the issue place address.
To set up the issue place relationship:
Add the CIF code.
Add record type $C.
Relate the issue place to the address book record.
When you generate a legal document with a document type of A, B, E, or M, you must print a bar code on the document. The bar code includes the:
C.U.I.T number
AFIP legal document type
Issue place
C.A.I. number
C.A.I. due date
Check digit
When you set up the ARG - Item ARGP - Allowed Values UDC (76/B1), you must specify Y in the Special Handling Code field for document types A, B, E, and M. A value of Y indicates that the document type requires the system to print the bar code information.
When you run the Print Invoices (R42565) program or the Invoice Print (R03B505) program, the system calls the Print Invoice / Shipment Note - ARG - 42 (R76A566) program. The Print Invoice / Shipment Note - ARG - 42 program calls the N76A510 (Bar Code String Generator) business function to print the bar code as well as the numeric equivalent of the bar code.
Note: You must install the Interleaved 2 of 5 ITF font for the bar code. JD Edwards EnterpriseOne software does not provide this font. |
The Bar Code String Generator - ARG - 42 business function obtains the data required for the bar code from these fields, and then generates a check digit:
C.U.I.T number (11 numeric characters obtained from data item TAX in the F76AUI20 table).
AFIP legal document type (three numeric characters obtained from the first three characters in data item VINV in the F76A09 table).
Issue place (five numeric characters obtained from data item ACEM1 in the F76AUI20 table).
C.A.I. number (14 numeric characters obtained from data item ACAI in the F76AUI20 table).
C.A.I. due date (eight numeric characters obtained from data item CXPJ in the F76AUI20 table).
The business function concatenates the values of the five data fields in the order listed and then adds the check digit to the end of the string to produce the numeric value of the bar code. To calculate the check digit, the system:
Sums the characters in the odd number positions (positions 1, 3, 5, and so on), beginning from the left of the string of characters.
Multiplies the sum obtained in the first step by 3.
Sums the characters in the even number positions (positions 2, 4, 6, and so on), beginning from the left of the string of characters.
Sums the values obtained in steps 2 and 3.
Determines the check digit to be the lowest number which, when added to the value that was determined in step 4, equals a multiple of 10.
Suppose the values for the five data fields are:
C.U.I.T number: 23467812399
AFIP legal document type: 003
Issue place: 12222
C.A.I. number: 65432165432111
C.A.I. due date: 06062005
The business function concatenates the characters to produce this string: 23467812399003122226543216543211106062005
Sums the characters in the odd positions to produce a value of 69.
Multiplies 69 by 3 to equal 207.
Sums the characters in the even positions to produce a value of 58.
Sums 207 and 58 to equal 265.
Determines the check digit to be five because five is the lowest number, which when added to 265, returns a number which is divisible by 10.
Produces a numeric value for the bar code that is equal to the original string with the check digit of five added to the end of the string for a value of: 234678123990031222265432165432111060620055.
Before you complete the tasks in this section:
Create a record for each issue place in the Address Book Revisions program (P01012).
Add issue place codes to the Issue Place (76A/LE) UDC table.
Access the Supplemental Database Setup form.
Enter AB in this field to specify the JD Edwards EnterpriseOne Address Book system.
Select this option to use the data that you enter in the Generic Alphanumeric Key 1 field as a key field for supplemental data.
If you select this option, you must enter a valid data dictionary alias in the corresponding DD Alias (SAL1) field. Before you can use the data dictionary alias, you must set up the alias in UDC Valid Alphanumeric Aliases (00/S2).
When you select Generic Alphanumeric Key 1, and you enter a valid alias, the field appears with the data dictionary name as a key field on the Work With Supplemental Data form. If you enter data in the corresponding Row Description (SBD1) field, the data that you enter appears as the key field name on the Work With Supplemental Data form.
Enter AN8 in this field to specify the address number alias.
Access the Data Type Revisions form.
Enter $C in this field to group data by categories.
This is a required field for setting up any data type. You can use an existing data type, or you can create a new data type by entering one or two characters for the code.
Enter 76A (Argentina) in this field to identify the system for the UDC that is related to the data type. This field works with the Record Type field to identify the code type table that the system uses to verify the data type. When you leave both fields blank, the system does not verify the data type.
For example, a valid code for data type SKILL (skills) must exist in the table for system 08 and code type SK. If you enter a skill code that is not in the table, the system displays an error message.
This field applies only to the code format (C) data types.
Enter LE in this field.
The Record Type and Product Code fields work together to associate a UDC table to the UDC (alias GDC1) field. The system uses the UDC table to verify data that you enter in the UDC (alias KY) field on the General Description Entry form.
For example, if you enter 08 in the Product Code field and SK in the Record Type field, the data that you enter in the UDC (alias KY) field on the General Description Entry form must exist in UDC table 08/SK.
If you leave the Record Type and Product Code fields blank, you can enter any data in the data entry field for the UDC (alias KY) column on the General Description Entry form.
This is an optional field for setting up supplemental data types in code format.
Access the General Description Entry form.
Enter the issue place code for each issue place.
Enter the effective date for each issue place.
Enter the address book number for each issue place.
Note: The data that you enter in the Remark (alias RMK) field depends on how you set up the Remark 1 (alias GDC2) and corresponding System Code (alias SY1) and Record Type (alias RT1) fields on the Data Type Revisions form. If you associated the Remark 1 (alias GDC3) field with a record, the data that you enter in the Remark (alias RMK) field must be a value in the associated record. If you did not associate the Remark 1 (alias GDC3) field with a record, the system accepts any data (within the size constraints) that you enter in the Remark (RMK) field. |
This section provides overviews of the text (TXT) payment file and the required bank account information for text payments; and lists a prerequisite.
The AFIP, through RG 151, requires that companies provide documentation of payments greater than 10.000,00 ARS in the form of a check, automatic debit, credit card receipt, credit invoice acceptance, and so on. If you cannot provide this documentation, you must prove the validity of the payment in another way to receive the fiscal credit.
If you use unauthorized documents as evidence of payments that are greater than 10.000,00 ARS, you cannot reduce your taxes by the fiscal credits from these transactions.
RG 1547 enables you to document the fiscal credit by the following means:
Preserve information about the means of payment in the invoice or receipt.
Submit a monthly record of payments that are made through computerized systems to the AFIP.
You must associate the CUIT number of the bank account with the bank account information by creating an address book record for the bank account and entering the bank's address book number in the Bank Account Information program (P0030G).
Create an address book record for the bank of each supplier for which you use the text payments file. Set up the address book record with a search type of V (Supplier), and specify the CUIT number of the bank account in the Tax ID field. of the Bank Account Information program (P0030G).
Set up UDCs for bank processing.
This section provides an overview of payment formats for Argentina and discusses how to set processing options for payment formats for Argentina.
JD Edwards EnterpriseOne software provides these payment formats for Argentina:
Format | Description |
---|---|
R760472A | Check and payment order. |
R76A04722 | Deferred check and payment order. |
R7604721A | Cash-payment order without a check. |
All three payment formats use the same processing options.
Processing options enable you to specify the default processing for programs and reports.
This processing option is not used.
This processing option is not used.
Enter 1 to register the payment under the check number. Leave this processing option blank to register the payment under the payment order number. This processing option is valid when you print only the payment order.
Enter 1 to suppress printing of the GL distribution account.
This processing option is not used.
This section provides an overview of the payment print programs for deferred payments and discusses how to set up the deferred check table.
Set up these print programs for the deferred-check payment instrument (D):
Form Name | Form ID | Navigation | Usage |
---|---|---|---|
Account Relationship | W76A0421C | Additional Features - Set Up (G76A116), Deferred Check Table | Specify the control account that is charged when the debt that is incurred with the supplier is written off and the final bank account from which the payment is made. |
Set this processing option before you enter company, customer, and supplier information for Argentine companies and individuals. The system uses the values in this processing option for country-specific processing.
This processing option specifies whether the system allows duplicate tax identification.
Specify whether the system allows duplicate tax identification. Values are:
Blank: The system does not allow duplicate tax identification.
1: The system allows duplicate tax identification.
This section provides an overview of setup for suppliers and discusses how to:
Set up additional address book information for suppliers.
Set up autoprinter numbers for suppliers.
In addition to the standard setup for suppliers, for Argentine suppliers:
Set up additional address book information for suppliers.
Set up the processing options for the Additional A/B Information program (P760101A) to allow duplicate CUIT numbers.
See Setting Processing Options for Additional A/B Information (P760101A).
If you are setting up foreign suppliers, set up the CUIT numbers for the countries of origin in the Country's CUIT (76A/FJ) UDC table and set up the document type for foreign tax IDs in the ARG-A/B Legal Document Type (76A/A0) UDC table.
See Setting Up UDCs for Foreign Suppliers and Supplier Withholding for Argentina.
Set up suppliers for withholding, if you process supplier withholding.
Set up supplier autoprinter (CAI) numbers.
Access the A/B Additional Information - Revision form.
Enter a value that exists in the ARG-A/B Legal Document Type (76A/A0) UDC table to specify the legal document type (CUIT, DNI, DNRP, and so on).
Enter a value that exists in the ARG-Custom Code (76/08) UDC table to specify whether customs fees apply to the supplier.
Enter a description of the payment.
Enter the VAT Withholding Concept. Values are:
Category code Argentina 93 - Profit Withholding Condition.
Category code Argentina 94 - Profit Withholding Concept.
Access the CAI Definition form.
Enter a value from the ARG-DGI Transaction Doc. Type (76/AF) UDC to specify the legal document type given by DGI for documents.
Enter the physical location where the invoice or the shipment note is printed.
Enter the number assigned to a supplier by legal authorities in Argentina, as stated in General Resolution 100. It is a unique ID given to all the companies that are autoprinters (that is, companies that print their own invoices).
These companies must be registered and authorized by legal authorities to print their invoices. Once they are registered and authorized, they are given a CAI (autoprinter inscription number), which they must print on every invoice.
Enter the date when a transaction, contract, obligation, preference, or policy rule becomes effective.
Enter the date when a transaction, contract, obligation, preference, or policy rule ceases to be in effect.
The A/B Withholding Information – Revision form in the A/B Tag File Maintenance – ARG program (P760101A) includes fields in which you identify suppliers as small contributors and specify if the supplier provides goods or services.
This section discusses how to enter supplier information for small contributors.
Form Name | Form ID | Navigation | Usage |
---|---|---|---|
A/B Additional Information - Revision | W760101AB | Supplier & Voucher Entry (G0411), Supplier Master Information
Enter supplier master and address book information, and then click OK on the Address Book Revision form. Select an existing record for an Argentinean supplier and select Regional Info from the Row menu. |
Enter supplier master information for Argentina. |
A/B Withholding Information - Revision | W760101AC | Click OK on the A/B Additional Information - Revision form. | Enter withholding information for Argentina. |
Access the A/B Withholding Information – Revision form.
Enter a value from the ARG-Profit WH Condition (76/03) UDC table to specify whether the supplier is registered, not registered, or is a small contributor. Examples of values are:
MON: Small contributor
NRE: Not registered
REG: Registered
Note: This field is present only when the value in the Profit Withholding Condition – Argentina field includes a code from UDC 76/03 that contains a value of M (Monotributista) in the first character of the Description 2 field of the UDC code. |
Enter a value from the Small Contributor Classific. (76/13) UDC table to specify if the supplier provides goods or services. Examples of values are:
Blank: Not a small contributor
BIE: Goods
SER: Services
This section provides an overview of small contributor limits and discusses how to set up small contributor limits
You use the Small Contributor Limits program (P76A050) to specify the accumulated invoice limits for goods and services when those goods and services are provided by a supplier who is registered as a small contributor. You set up the limits by effective date and small contributor classification.
Important: If you have existing vouchers in your system when you set up the small contributor limits, you must set up the limits with an effective date that is prior to the voucher date of the voucher that you process. If the effective date is a date that is after the voucher date, the system assumes that no limit exists. |
Form Name | Form ID | Navigation | Usage |
---|---|---|---|
Work With Small Contributor Limits | W76A050C | Small Contributor Withholding – Setup (G76A130), Small Contributor Limits | Review and select existing records. |
Small Contributor Limits Revision | W76A050D | Click Add on the Work With Small Contributor Limits form. | Specify the 12-month period and unit price limits by date and classification. |
Access the Small Contributor Limits Revision form.
Enter a value from the Small Contributor Classific. (76/13) UDC table to specify whether the limit applies to goods or services.
Enter the starting date of the limit. The effective date must be prior to the date of the oldest voucher that you need to process.
Enter the amount over which withholding applies. For example, if you enter ARS 72,000, the system calculates withholding for the supplier if the total of the paid and unpaid invoices that you process for the supplier in a 12-month period exceeds 72,000.
Enter 0 in this field. The unit price limit is no longer used to determine whether VAT and profit withholding apply to small contributors.
This section provides an overview of when withholding applies to a small contributor and lists the forms used to specify that withholding applies to small contributors.
Regulations in Argentina exempt suppliers who generate a limited amount of transactions from having VAT and profit withholding amounts withhold from the payments that you make to the suppliers. These suppliers are known as small contributors.
The AFIP maintains a website that enables you to verify if a supplier is registered as a small contributor. If a supplier is registered as a small contributor and the supplier does not exceed the annual limits on the purchases that you make from the supplier, you do not process VAT and profit withholding when you generate payments to the supplier. If the AFIP website does not show a supplier as being registered as a small contributor, you must process the VAT and profit withholdings and deduct those amounts from the payments that you make to those suppliers.
You use the Small Contrib.under Withhold Obligation program (P76A405) to add unverified small contributors to the Small Contributors that Exceeded the Limit table (F76A405), which the system uses to determine whether to apply VAT and profit withholding for small contributors.
When you process automatic or manual payments, the system accesses the F76A405 table to determine whether to process withholding for the payment. The system processes withholding for small contributors for which a record exists in the F76A405 table.
Occasionally, you might need to remove a supplier record from the F76A405 table. You use the Small Contrib. under Withhold Obligation program to delete records from the F76A405 table
Form Name | Form ID | Navigation | Usage |
---|---|---|---|
Work With Small Contributors under Withholding Obligation | W76A405A | Small Contributor Withholding – Setup (G76A130), Small Contrib. under Withhold Obligation | Review and delete existing records. |
Small Contributors under Withholding Obligation Revision | W76A405B | Click Add on the Work Small Contributors under Withholding Obligation form. | Enter the address book number for small contributors for whom withholding applies. |
This section discusses how to set up to work with invoice type M for vouchers.
Invoice type M is used for the emission of documents with tax discrimination. General Resolution 1575 defines these withholding requirements for vouchers with invoice type M:
The withholding is calculated when the taxable amount of the transaction is equal or greater than 1000 USD.
In this case, the transaction is excluded from other withholding or perception requirements that might be applied (except Guía Fiscal Ganadera, Harinera, or both).
If the taxable amount of the transaction is less than 1000 USD and the payer is a withholding agent in any other regime that makes withholdings for less than 1000 USD, the withholding must occur.
The withholding amounts are calculated as follows:
VAT
The net transaction amount multiplied by 100 percent of the corresponding tax rate. This amount is calculated for each payable voucher.
Profit
The net transaction amount multiplied by three percent. This calculation does not consider the accumulated profit for the month. This calculation must be done for each payment.
To perform these calculations:
Create a document type in UDC 00/DT and UDC 00/DV to identify type M vouchers.
Create a tax area exclusively for type M vouchers.
Specify invoice group M for this tax area on the Additional Tax Information form.
Add these legal withholding regimes, which are reported in the SICORE report and in the withholding certificate:
UDC | Code | Description |
---|---|---|
76/L3 | 99 | Invoice M - Profit - Emission of documents with tax discrimination. |
76/L1 | 499 | Invoice M - VAT - Emission of documents with tax discrimination. |
Add these legal withholding concepts, which are used during voucher entry:
UDC | Code | Description |
---|---|---|
76/04 | GAM | Invoice M - Profit - Emission of documents with tax discrimination. The code is just an example. |
76/02 | IVM | Invoice M - VAT - Emission of documents with tax discrimination. The code is just an example. |
Note: These concepts must be different from those already defined in the system. The existing concepts cannot be reused because they have different withholding calculations. |
For VAT withholdings, set up a withholding percentage in the V.A.T WH - Percentages program (P760402A).
See Setting Up VAT Withholding for Argentina.
For profit withholdings, set up a withholding percentage in the Profit W/H - Percentages program (P760403A)
Note: You must specify 1 in the Misc Code field to indicate to the system that it does not have to consider the accumulated amounts from the month in the profit withholding calculation for the payment group. |
See Setting Up Profit Withholding for Argentina.
When you enter a voucher into the system, assign the withholding concepts corresponding to the operation on the Withholdings tab of the Voucher Additional Information - Revision form, as shown in this example:
Field | Code | Description |
---|---|---|
VAT Withholding Concept | IVM | Invoice M - VAT |
G.I. Agreement Code | 02 | Multilateral Agreement |
G.I. Concept Source | BIE | Goods |
G.I. State Source | 04 | Neuquen |
G.I. Concept Destination | FLT | Shipment |
G.I. State Destination | 02 | Mendoza |
Profit Withholding Condition | INS | Registered |
Profit Withholding Concept | GAM | Invoice M - Profit |
Contract Concept | 500 | More than 500 square meters |
S.U.S.S. Concept | LIM | Cleaning Services |
Note: When a transaction with invoice type M is less than 1000 USD, specify the appropriate profit withholding concept (regardless of the general withholding method). If the transaction is greater than 1000 USD, specify the withholding concept of RG 1575. |
See Working with Voucher Entry and Review for Argentina.
If you are adhering to General Resolution 1575, you generate certificates before you update the payment group in the same way as if you were not adhering to this resolution.
For General Resolution 1575, you report withholdings using the SICORE report.
This section provides an overview of credit invoice constants for the JD Edwards EnterpriseOne Accounts Payable system setup and discusses how to set up credit invoice constants for the JD Edwards EnterpriseOne Accounts Payable system.
You set up credit invoice constants by company. These constants control the credit invoice process.
You must specify this information when you set up credit invoice constants for the JD Edwards EnterpriseOne Accounts Payable system:
The gross amount limit, below which a voucher does not require a credit invoice.
Any voucher with a gross amount in excess of this amount requires a credit invoice.
The payment time limit in days, below which a voucher does not require a credit invoice.
Any due date that exceeds this limit requires a credit invoice.
The category code that is used to identify suppliers that issue credit invoices.
Whether the company accepts credit invoices.
The payment instrument for vouchers that require credit invoices.
The initial status that is assigned to the credit invoice when it is entered in the system.
Access the Enter Credit Invoice Constants form.
Figure 3-8 Enter Credit Invoice Constants form
Enter the amount that the system adds to the account balance of the associated account number. Enter credits with a minus sign (−) either before or after the amount.
Enter the number of days that the fiscal authority has established as a difference between the shipment confirmation date and the invoice due date. The specified number of days must pass before you can issue a credit invoice. If fewer than the specified number of days have passed between the shipment confirmation date and the invoice due date, then you cannot issue a credit invoice.
Enter the code that specifies the Customer Category code number to use to determine the tax.
Select to specify that a company must issue a credit invoice.
Enter a value that exists in the ARG - Item ARGP-Allowed Values (76/B1) UDC table to specify the legal number group for credit invoices.
Enter a value that exists in the ARG - Item ARGP - Allowed Values (76/B1) UDC table to specify the legal number group for receipt invoices.
Select to specify that a company must receive credit invoices from its vendors.
Enter a value that exists in the Credit Invoice Valid Status (76A/CS) UDC table to specify the status of the credit invoice.
You must set up a temporary tax area for each tax area that your suppliers who issue credit invoices use. The temporary tax areas must have the same percentage as the original tax area and an offset that uses the temporary fiscal credit account.
You cross-reference the original tax areas to the temporary tax areas by using the AP Tax Areas Relationship program (P76A25). You can cross-reference only one temporary tax area to each original tax area. The system stores area cross-references in the Credit Invoice Tax Area Relationship (F76A25) table.
This section provides an overview of the setup of credit invoice status rules, lists prerequisites, and discusses how to set up credit invoice status rules.
Status rules establish a validation of the credit invoice status that is required for processing a particular event. You can also specify the next status that should be used when the event has been completed.
For example, for the ACCEPTANCE event, the credit invoice must have a status of TO ACCEPT. After processing, the credit invoice status is updated to ACCEPTED.
These rules should be set up by an advanced user and offer great flexibility for defining the steps that your company wants to follow to process credit invoices.
Important: You must define the status rules correctly when you install the credit invoice module because making changes other than adding additional steps to the process is difficult. |
Status rules consist of these elements:
Accounts Payable Event
These values are hard-coded in the Credit Invoice A/P Events (76A/EV) UDC table and represent different possible actions in the JD Edwards EnterpriseOne Accounts Payable system.
Credit Invoice Status From
This is the initial valid status that is necessary for the event to run.
Credit Invoice Status To (optional)
Some events require you to complete this field to change the credit invoice status manually or automatically. If the Credit Invoice Status To field is blank, no status change occurs for the event.
Note: You cannot leave the Credit Invoice Status To field blank for events that update the status automatically. Leaving this field blank for these events might cause the system to act erratically.Regardless of the code system that you decide to use, you skip numbers or codes so that you can add intermediate status in the future, if necessary. |
This list gives a detailed explanation of the significance and behavior of each event code (in alphabetical order):
ACCEPTANCE
The Create Payment Control Groups program (R04570) uses this event and represents acceptance of the credit invoice. The Create Payment Control Groups process verifies that the vouchers that are selected have credit invoices with the appropriate Credit Invoice Status From code. When the payment is updated, the credit invoice is updated with the status indicated in the Credit Invoice Status To field.
ACEPTAVOID
This event is used when you void a payment that was made with the acceptance payment instrument. The system verifies that the invoice credit has the appropriate status in the Credit Invoice Status From field. If no errors are found and the voiding takes place, the credit invoice is updated with the status that is indicated in the Credit Invoice Status To field.
CHECK
The Create Payment Control Groups program uses this event when the acceptance payment instrument is not used. The Create Payment Control Groups process verifies that the selected vouchers have credit invoices with the appropriate Credit Invoice Status From code. When the payment is updated, the credit invoice is updated with the status that is indicated in the Credit Invoice Status To field.
CHECKVOID
You use this event when you void a payment. When you void a payment that was made without the acceptance payment instrument, the system verifies that the invoice credit has the appropriate status in the Credit Invoice Status From field. If no errors are found and the voiding takes place, the credit invoice is updated with the status that is indicated in the Credit Invoice Status To field.
CITI
The CITI report uses this event to determine whether a credit invoice should be included. The status of the credit invoice must correspond to the status that is indicated in the Credit Invoice Status From field. When the credit invoice has been included in the CITI, the credit invoice is updated with the status that is indicated in the Credit Invoice Status To field.
FACCREDCHG
The AP Review Credit Invoice program (P76A24) uses this event when you change information on the credit invoice, including a manual change of status. The Credit Invoice Status From field indicates the status that the credit invoice must have for you to manually change some of its information. The Credit Invoice Status To field indicates the status to which the credit invoice can be changed manually.
FACCREDDEL
Credit invoice review uses this event to eliminate information from a credit invoice. The Status From field indicates the status that the credit invoice must have to be able to eliminate it. The Status To field is not used by this event, so leave this field blank.
IVACOMPRAS
The V.A.T. Purchasing Ledger program (R760499A) uses this event to determine whether the credit invoice should be included in this ledger. The status of the credit invoice must correspond to the status in the Credit Invoice Status From field. When the credit invoice has been included in the V.A.T. Purchasing Report (R760499A), the credit invoice is updated with the status that is indicated in the Credit Invoice Status To field.
RECIBOFC
You use this event when you set up information about the credit invoice receipt. The status of the credit invoice must correspond to the status in the Credit Invoice Status From field. When the information has been entered, the credit invoice is updated with the status that is indicated in the Credit Invoice Status To field.
RECIBOCHG
You use this event when you modify the information of a previously recorded receipt. The status of the credit invoice must correspond to the status in the Credit Invoice Status From field. When the receipt information has been changed, the credit invoice is updated with the status that is indicated in the Credit Invoice Status To field.
RECLASIF
The system uses this event when the temporary fiscal credit tax is reclassified to a definitive tax credit account. The credit invoice must have the status that is specified in the Credit Invoice Status From field for reclassification to take place. When the reclassification is complete, the credit invoice is updated with the status that is indicated in the Credit Invoice Status To field.
RECLAPERD
This event is used when a temporary fiscal credit tax is not reclassified to a definitive tax account and, instead, is assigned to losses directly. The credit invoice must have the status specified in the Credit Invoice Status From field for this reclassification to occur. When the reclassification to losses is complete, the credit invoice status is updated to the status that is indicated in the Credit Invoice Status To field. This event is optional. If you do not set up the Credit Invoice Status From field, the reclassification process uses the relationship that is established for the RECLASIF event.
VOUCHERCHG
You use this event when you modify a voucher that has credit invoice information. The system verifies that the status of the credit invoice is the same as the one that is specified in the Credit Invoice Status From field to allow the change. This event does not change status. You must leave the Credit Invoice Status To field blank.
VOUCHERDEL
You use this event when you void a voucher that has credit invoice information. The system verifies that the status of the credit invoice is the same as the one that is specified in the Credit Invoice Status From field to allow the void. This event does not change status. You must leave the Credit Invoice Status To field blank.
Before you complete the tasks in this section:
Set up event codes in the Credit Invoice A/P Events (76A/EV) UDC table.
Set up status codes in the Credit Invoice Valid Status (76A/CS) UDC table.
Access the Update Tax Area Relationship Information form.
Figure 3-9 Update Tax Area Relationship Information form
Enter a value that exists in the Credit Invoice A/P Events (76A/EV) UDC table to identify the event to set up.
Enter a value that exists in the Credit Invoice Valid Status (76A/CS) UDC table to specify the beginning of the range of status codes to which the event applies.
Enter a value that exists in the Credit Invoice Valid Status (76A/CS) UDC table to specify the end of the range of status codes to which the event applies.
This section provides an overview of credit invoice constants for the JD Edwards EnterpriseOne Accounts Receivable system and discusses how to set up credit invoice constants.
You set up credit invoice constants by company. These constants control the issuance rules for the credit invoice documents.
You must specify this information when you set up credit invoice constants for the JD Edwards EnterpriseOne Accounts Receivable system:
The invoice minimum amount, which is the invoice amount (included taxes) above which a credit invoice must be issued.
The credit invoice limit days, which is the maximum number of days that an invoice must be overdue before it is considered to be expired, thus requiring issuance of a credit invoice.
The category code identifies customers that accept credit invoices. To generate the credit invoice, the value of the address book category code must not be blank.
Whether the company issues credit invoices.
The status that the credit invoices will have after they are printed.
The internal document type of credit invoices, which the system uses to assign legal numbers to credit invoices.
The DGI letter to assign legal numbers to credit invoices.
The DGI letter to assign legal numbers to receipts.
Access the Enter Credit Invoice Constants form.
Figure 3-10 Enter Credit Invoice Constants form
Select the General tab.
Enter a number that identifies the amount that the system will add to the account balance of the associated account number. Enter credits with a minus sign (−) either before or after the amount.
Enter the number of days that the fiscal authority has established as a difference between the shipment confirmation date and the invoice due date. The specified number of days must pass before you can issue a credit invoice. If fewer than the specified number of days have passed between the shipment confirmation date and the invoice due date, then you cannot issue a credit invoice.
Enter a code that specifies the Customer Category code number to use to determine the tax.
Select the A/R and SOP tab.
Select to indicate you must print a credit invoice.
Enter a value that exists in the Credit Invoice Valid Status (76A/CS) UDC table to specify the status of the credit invoice.
Enter a value that exists in the ARG - Item ARGP-Allowed Values (76/B1) UDC table that identifies the invoice group.
Enter a value that exists in the ARG - Item ARGP-Allowed Values (76/B1) UDC table that identifies the invoice group.
You must set up the acceptance payment instrument (defined in the Special Payment Instruments [76A/PY] UDC table) in the Payment Instrument Defaults program, using these parameters:
Payment Form | Print Program |
---|---|
Payments | P7604721A (Print Payment - Only Payment Order - ARG - 04 - 04) |
Payment Register | P76A0476 (A/P Auto Payment Register) |
Attachments | P760473A (A/P Print Payment - Payment Order - ARG - 04 - 04) |
Debit Statements | P04574 (Print A/P Payments Debit Statements) |