This chapter contains these topics:
Many fields in the Accounts Receivable system accept only user defined codes. For example, when you enter an invoice, you can enter a user defined code to specify the payment instrument. The system does not accept a payment instrument that is not in the user defined list of valid payment instruments.
Each user defined code is either soft-coded or hard-coded. You can customize any user defined code that is soft-coded to accommodate your specific business needs, and you can set up additional ones. You cannot customize a user defined code that is hard-coded.
User defined code types are identified by the system code and the user defined code list. For example, 00/DV represents system 00 and user defined code list DV.
The following user defined codes are available:
Document type codes
Payment status codes
Payment instrument codes
Tax calculation codes
Aging vocabulary codes
Adjustment reason codes
Valid credit message codes
Collection reason codes
Credit reporting payment terms codes
Receipt type input codes
Dun & Bradstreet rating codes
TRW rating codes
Autocash algorithm codes
Language preference codes
Bank Type Code
When you enter a transaction, you may specify the document type, such as an invoice or credit memo, or let the system default the document type based on your set up or hard-coded values.
The document type code, document number and company, and G/L date are the link between the Accounts Receivable system and the General Accounting system.
The system maintains two groups of document type codes:
Invoice document types
All document types
Invoice document types are also known as original documents. Original documents can exist by themselves as a record without a matching document type. All original documents:
Represent the initial transaction
Stand alone in the system
Can be soft-coded; some are hard-coded.
You must set up a code for each type of original document that you use when you enter invoices. When a user defined code is hard-coded, you cannot change it.
The system uses this document as the default when you enter an invoice. This is soft-coded to allow user-defined alternative invoice document types.
The system creates this hard-coded document when you enter an invoice to be recycled (copied) for a specified amount, time period, and number of payments.
The system uses this document as the default when you issue a credit to a customer. This is soft-coded to allow user-defined alternative credit memo document types.
The system creates this hard-coded document when you enter an invoice for a discrepancy or a disputed amount on an original invoice.
For example, a customer pays 60 of an original 100 invoice amount. You might apply the full 100 to close the invoice and create a chargeback (a new invoice) for the difference of 40.
The system creates this hard-coded document when you enter an invoice to assess interest or finance charges for delinquent invoices and late payments.
The system creates this hard-coded document when you place money in a clearing account until you determine how to apply the payment (that is, which customer accounts to apply it to, and so on).
The system creates this hard-coded original document when you use draft processing.
|NO||A/R netting Invoice
The system uses this hard-coded document when reclassifying A/P open transactions to an open receivable.
The system creates this original document when you summarize individual documents to one invoice.
These document types are also known as matching document types The matching document type records cannot exist by themselves; each must match to a corresponding original document record. For example, a receipt is a matching document that must always have a corresponding invoice as the original document. A matching document is hard- coded and has its own type and number.
The system provides the following codes for the matching documents that you use when you enter invoices:
|RE||Void or Charge to Invoice Amount
The system creates an audit trail when you change the amount of a posted invoice or when you void an invoice.
The system creates this document for a payment when you enter a receipt.
The system creates this matching document when you summarize detailed documents to one invoice. This is the matching document corresponding to each detailed document being summarized..
The system creates this document when you void a posted payment.
The system creates this document to correct bad debts, minor write-offs, or adjustments.
The system creates this document in conjunction with the RB document when you enter a chargeback invoice.
The system creates this document when you distribute unapplied receipts (an RU document) or a credit memo (an RM document) to an open invoice amount.
The system creates this document when a bank cannot cover a customer's payment. This reopens the original invoice and voids the corresponding RC document.
The system creates this matching document when you enter a draft. This is the matching document that corresponds to each original document being paid by the draft.
Payment status codes indicate if an invoice is approved, pending, paid, and so on. You assign a payment status code if you need to change the status that the system has assigned. The following payment status codes are hard-coded:
|A||Approved for payment|
|P||Paid in full|
|S||Balance forward, summarized|
Payment instrument codes indicate various methods of payment. You assign a payment instrument code to each invoice. Examples are:
You can assign codes for various methods of calculating taxes. Examples of commonly used tax explanation codes are below. For a complete list of available tax explanation codes, see the JD Edwards World Tax Reference Guide:
|B||VAT + use tax|
|C||VAT + sales tax|
|U||Use (self-assessed) tax|
You can assign codes to specify the terminology on your A/R aging reports. Examples are:
You can assign codes to specify the reason you adjusted an invoice amount and point each code to a separate expense account using AAIs. Examples are:
You can assign codes to notify you of a customer's credit status. These credit messages are used throughout all JD Edwards World systems. Examples are:
|*||Bypass temporary credit hold (hard-coded)|
|B||Bad credit risk|
|C||Cash basis only or C.O.D. (collect on delivery)|
|1||Over credit limit|
You can assign codes to explain why an invoice is delinquent. Examples are:
|BK||Customer in bankruptcy|
|DP||Disputed by customer|
You can assign codes to indicate the payment terms for discounts, discount percentages, and the net amount.
|Blank (default)||Net amount due in 30 days|
|1||1/10, net 30|
|2||1/20, net 30|
Type input codes indicate how receipts are applied to invoices. The following examples are hard-coded:
|A||Adjustment to receivables|
You can assign codes to identify the Dun & Bradstreet credit rating for a customer. Examples are:
You can assign codes to specify the TRW credit ratings. Examples are:
Autocash algorithm codes define the methods for applying receipts. The batch receipts process uses these codes. The following examples are hard-coded: