| Purpose |
| Questions and Answers |
| Accounts Payable General Questions |
| Question 1: What causes the "Split Payment not Allowed" error on a Payment Term in Speed Voucher Entry (P0411SV)? |
| Question 2: When the Payment Terms are changed in a voucher, the Due Dates are not recalculated, why? |
| Question 3: Is it possible to set up discounts in Accounts Payable to be a reduction of the Gross Amount and therefore a reduction in the expense, rather than as Discount Taken revenue? |
| Question 4: What causes the General Ledger Post (R09801) to trigger an "Out Of Balance" error when a voucher is posted with a split payment term? |
| Question 5: Can the payment term be defined by LOB or Company in Accounts Payable? |
| Question 6: Why are errors triggered when entering a voucher using a Payment Term linked to a work day calendar that has a value in the Shift Code? |
| Question 7: Is there a way to set up a payment term where the discount will always be taken, regardless of the date the payment is made? |
| Accounts Receivable General Questions |
| Question 1: Is it possible to set up a payment term where a transaction is due upon receipt? |
| Question 2: Is there a global update program available to update the Payment Terms on existing, unpaid invoices in the Customer Ledger (F03B11) using the value in the Customer Master (F03012)? |
| Question 4: Why is the Update AR Invoices (R005142) failing to update all valid invoices for a company that has a multi-tier discount payment term? |
| Question 5: How do installment payment terms show in the customer ledger (P03B2002)? |
| Question 6: How does installments show up in terms of aging on an invoice? |
| Question 7: Is there a way for installment payment terms to create each installment with its own invoice number? |
| General Questions |
| Question 1: How can a payment term be set up that calculates 45 days from the invoice date and lands on the end of the month? |
| Question 3: Can a payment term be set up using both a Discount Due Date and a Proxy Date? |
| Question 4: Is it possible to set up a payment term that calculates the due date as the 10th of the following month? |
| Question 5: Can the Blank Payment Term be removed from P0014? |
| Question 6: Is it possible to set up a payment term 90 days end of month? |
| Question 7: What is signified by the value R in the Range or Tier field in Work with Due Date Rules (P00146)? |
| Question 8: Is it possible to set up a payment term that calculates a due date that is 60 days after the 1st of the following month? |
| Question 9: Is it possible to set up a payment term based on a quarter? |
| Question 10: After creating a new Advanced Payment Term, a new voucher was added but Advanced Payment Terms were not calculated, why? |
| Question 11: Is it possible to set up a payment term due on a certain day of the week (e.g. Friday)? |
| Question 12: How can an advanced Payment Term be configured to use a specific date (e.g. June 1, 2011)? |
| Question 13: How does the system determine the due date for tiers when using Multitiered Discounts? |
| Question 14: Is it possible to create a Payment Term with a Prox Date that exceeds 12 months? |
| Question 15: Why is a voucher with three installments of equal percentage not dividing into three equal parts? |
| Question 17: Does modifying a supplier payment terms have an impact on outstanding AP vouchers or AR invoices? |
| Question 18: Can you use the Multi-tiered discount process to create the following payment term? |
This document provides answers to frequently asked questions on payment terms and advanced payment terms within the JD Edwards EnterpriseOne Financial system.
Answer 1: This issue is caused by the Number of Split Payments and Days to Pay Aging on the Blank Payment Term setup in P0014. When using this option, the system creates multiple pay items on a voucher to account for the split payment". This occurs on the commit of the voucher. Speed Voucher Entry (P0411SV) was designed to be a simple and quick voucher entry program and does not have the capability to create multiple pay items on a single voucher. Vouchers entered through P0411SV can only be one pay item. Therefore, if using a Payment Term that has defined a Split Payment setup, the system throws the error because the program does not have the capability to create the split payment. This issue is functioning as designed. Consider using one of the following work arounds in this case:
Answer 2: If you change the Payment Terms to recalculate the Due Dates (Net Due Date or Discount Due Date), it is necessary to blank out the existing value from the Due Date field.
Answer 3: Working as designed. It is possible to add extra lines to the G/L Distribution details upon voucher creation, but this would require quite a bit of manual entry including journal entries to balance your accounts
Answer 4: The failure of post on vouchers with split payment terms are caused by soft rounding. To overcome this issue, it is advised to use Speed Status Change (P0411S) to efficiently split the vouchers.
Answer 5: Payment terms are set up at supplier master level. Since in Accounts Payable, there is no LOB (Line of Business) functionality, it is not possible to set up Payment Terms by company or business unit.
Answer 6: The Shift Code (data dictionary item SHFT) in not used in the Accounts Payable module. Workday calendars for use with the Accounts Payable or Accounts Receivable should only have the following fields populated:
Answer 7: The discount will always be taken when the net due date and the discount due date are the same. To do this, you can set up a due date rule in P00146 (Work with Due Date Rules). Then go to P00145 (Work with Advanced Payment Terms) and create a new payment term. Set the Discount Due Date Rule and Net Due Date Rule as the same due date rule that was created in P00146. Now all vouchers created using this payment term should have the discount due date equal to the net due date, which should result in the discount always being taken.
Answer 1: Setting up payment term without any additional information yields a payment term where the due date is calculated as the receipt date.
Answer 2: Unfortunately, Speed Status Change (P03B114) is the only way to update the payment terms (PTC) on existing invoices in the Customer Ledger (P03B11). You can use the Global Update option to do more than one invoice at a time. However, there is no batch program that does this for you.
Answer 3: Create a special calendar, having the only working day on the 1st of May. The Branch/Plant you used in the calendar must exist in the Business unit master table (F0006). (Be sure this calendar is defined for all the years) Create a due date rule using this calendar and use this due date rule to create a payment term. Create an invoice with two lines, one with the initial payment and the second one with the license payment. Important: in the first line the due dates (for invoice and discount) has to be overwritten with the invoice date (or with the due date one wants). The GL distribution will have two lines. When one will recycle this invoice, one will get a one-line invoice for the second next year (1st of May calendar has to be set for 2008 also).
Answer 4: If the Update AR Invoices (R005142) is failing to update any invoice in a company, it may be related to the Company's Tax Rule (P0022). If a Company's Tax Rule (P0022) is set to Calculate Taxes Based on Gross Amount EXCLUDING Discount, then the Update AR Invoices (R005142) is hardcoded to skip any invoices in that company. The reason for skipping these invoices is because changing the discount amount would also require a recalculation of taxes. Therefore, if you plan to use multi-tier discounts for a company, ensure that the Tax Rule (P0022) is set up to Calculate Taxes Based on Gross Amount INCLUDING Discount.
Answer 5: When you have installment payment terms, what the system does is it breaks up your invoice into multiple pay items. So, let's say you enter an invoice with one pay item for 100 dollars and the new payment term. During the save, the system breaks out the 100 pay item to two pay items, one for 90 and the other pay item line for 10. Each will have the 45 and 90 day out due dates, respectively. When you query on the batch in the Customer Ledger (P03B2002) and without summarize on, the system displays two lines for this invoice.
Answer 6: In terms of aging, the system ages each pay item separately. For example, if you run AR Details with Aging (R03B4201B), the invoice is pulled and displays as two separate lines. Both are the same invoice number, but they have a different Pay Item Number. If you have one of the lines that is still current, it would show its amount in the Current column, while if the other is past due, it would appear in the 1-30 column, and so on.
Answer 7: Installment payment terms splits an invoice into various pay items with different due dates. There is no way to create multiple invoices using a payment term, but you may wish to consider using recurring invoices instead if you are billing customers the same amount on a regular basis. See <KM Note 1466797.1> for more information.
Answer 1: In payment terms, you can set up Days to Add or Months to Add but there is no functionality to round to the last day of a month. Advanced payment terms, however, does allow you to set up payment terms by date range, so you could set up a date range for every day of the month. Depending on your business requirements, you may need to set up several payment terms since each month has a different number of days.
There are two possible ways to get the desired result:
Answer 2: Setup a Due Date rule with:
The system calculates the date based on the Due Date rule and then it will apply the Due Date Range rules.
Answer 3: A payment term can only be configured with a Discount Due Date or a Proxy Date. One payment term cannot use both.
Answer 4: This type of payment term is possible when using the Prox Date Month (data dictionary item PXDM) and Prox Date Day (data dictionary item PXDD) in the Payment Terms Revisions (P0014) program.
Answer 5: The Blank (default) Payment Term can be removed from P0014. However it is not recommended to remove it if there are Historical records containing this value.E1 Distribution programs might stop working when the BLANK value is deleted from Payment Terms. This occurs because of the DD edit behind PTC against BSFN IsColumnInPymtTermsTable. The Edit is executed in Tools Code beneath the Application layer of code. So in any given program if a variable is declared based on PTC and the variable is not populated, the underlying DD edit may trigger an error.
Answer 6: Using standard payment terms, prox date month 3 and day 31 is a close approximation to 90 days end of month, but does not always provide the correct result. Using advanced payment terms, you can have a Due Date Rule with a Days to Add of 90 and a Range attached with one record for days 1-31.
Answer 7: The Range or Tier (data dictionary item EV01) field is set to R when a date range is attached to the due date rule.
Answer 8: The Advanced Payment Terms (P00145) would need to be used to configure this type of payment term. The Due Date Rule (P00146) used by the advanced payment term should be based on invoice date. When setting up the Due Date Rule in Due Date Rules Revisions (P00146):
Answer 9: Neither Standard Payment Terms (P0014) nor Advanced Payment Terms (P00145) have the capability to calculate due dates based on fiscal quarters.
Answer 10: After creating a new Advance Payment Term the user must restart E1 (Log out/ Log in) as the table F00144 is part of database cache. Any changes made to F00144 table will be added to the cache only after restarting E1. This cache is used from Tools Release 8.95 onwards.
Answer 11: Although there is not a specific option to calculate a due date on a specific day of the week, a workday calendar could be used to define that day of the week to be a working day only. For additional information on the Work with Workday Calendar (P00071), see knowledge How To Set Up Standard and Advanced Payment Terms in the JD Edwards EnterpriseOne Financial System (P0014, P00145, P00146, R005142, R005141).
Answer 12: To identify a specific date that should be used as a due date in an advanced payment term, follow these steps:
Answer 13: The discount due date for the first tier is calculated using the information provided in the Due Date Rule. To determine the discount due date for subsequent tiers, the system adds the value in the To field of the tier to the Based on Date (data dictionary item DABS) being used. To calculate new discount percentages and discount due dates for subsequent tiers, the Batch Update for Multitiered A/P (R005141) UBE must be run.
Answer 14: The Prox Date Month (data dictionary item PXDM) field in the Payment Terms Revisions (P0014) is limited to 12. As a workaround, create an Advanced Payment Term (P00145).
Answer 15: The system uses soft rounding when amounts do not divide evenly. A workaround to this would be to use Splits functionality instead of installments. Split functionality is defined in Work with Payment Terms (P0014). When entering vouchers, each split amount is determined by dividing the amount entered by the number of splits.
Answer 16: Date Rule Revisions-Due Date Rules Revision, P00146/W00146B form's fixed date should be <blank> as this information is already setup on the Due Date Rule Date Range. This was also populated with a "10" which was causing the system to not use the Adv Pymt Term correctly.
Answer 17: Changes to a supplier payment terms in the Supplier Master or Customer Master do not impact existing vouchers because the discount amount, due dates and any installments have already been calculated.
4% discount if paid in 15 days, or 2% discount if paid by the 25th of the following month, with net due in 61 days?
Answer 18: No, the multi-tiered process cannot have different fixed days or months to add per tier level, the Due Date Rule determines this for all tiers. The tier can be set up for the Day Range (From and To) and the Discount Percentage.