Skip navigation

When customers are delinquent in paying their bills, you can send a delinquency notice on overdue invoices as a reminder to pay the delinquent balance. Delinquency notices are created by running the Print Delinquency Notices version (XJDE0002) of the Credit Analysis Refresh program (R03B525). This version has predefined processing options set for printing delinquency notices and calls either the AR Delinquency Notice Print (R03B20), or from release 8.9, the Global Reminders (R03B21) to generate the notices. The system generates notices based on the delinquency policy that is assigned to the customer. See Document 1490134.1 for further information on setting up delinquency policies and the system set up requirements for generating notices.

 

Prior to release 8.9, only the A/R Delinquency Notice Print (R03B20) program can be called from Credit Analysis Refresh to print notices. From release 8.9 onwards, there is a further option to use Global Reminders (R03B21), which is also referred to as Tiered Delinquency Notice Print.

 

More details on how this process works, common issues and troubleshooting tips could be found in:

  • E1: 03B: How To Process, Purge and Troubleshoot Delinquency Notices (R03B525, R03B20, R03B21, P03B202, P03B201, R03B5010) (Doc ID 644234.1)
  • E1: 03B: FAQ - Frequently Asked Questions about Delinquency Notice Processing and Purging (R03B525, R03B20, R03B21) (Doc ID 945005.1)
  • E1: 03B: How To Set Up and Run Credit Analysis Refresh In EnterpriseOne (R03B525) (Doc ID 1495853.1)

Statements are sent to customers to inform them of their account activities. For example, a statement can be printed for a customer to show their current open balance or a summary of their account. Statements can be printed or displayed online for review. Once statements are processed they can be reprinted or reset if necessary.

 

Statements are generated by running the Statement Notification Refresh (R03B500X) which uses data from the Customer Ledger (F03B11), the A/R Check Detail (F03B14) and the Invoice Revisions (F03B112) tables to print statements. Once this information is gathered, R03B500X uses this information to write records to the A/R Notification History (F03B20) and the A/R Notification History Detail (F03B21) tables. This then calls the A/R Statement Print Driver (R03B5005), which submits any print job or version for statements and calls the Statement Print Program. There are various standard Statement Print programs available, which are set up in user defined code (UDC) 03B/ST, and designated for use in the Statement Notification Refresh (R03B500X) processing options:                             

  • Statement Print (R03B5001)         
  • Kagami Invoice Statement (R03B5001JP)   
  • Italian Statement Print (R03B5002
  • Statement Print Credit Card (R03B5003)
  • Statement Print with Draft (R03B506)  

 

More details on how this process works, common issues and troubleshooting tips could be found in:

 

  • How To Set Up and Generate Accounts Receivable Statements In JD Edwards EnterpriseOne Accounts Receivable (Doc ID 625781.1)
  • FAQ - Frequently Asked Questions about A/R Statements (Doc ID 625842.1)

You can automatically debit (withdraw funds from) a customer’s bank account by updating an automatic debit file that you send to the bank that collects payment from the customer using Electronic Funds Transfer (EFT). The automatic debit process records the receipt at the time the file is updated. You run a program to format the file according to the bank’s specifications, and then send it to the bank by copying it to a medium or sending it electronically. The bank collects payment from the customer and then notifies you that the transaction is complete. Automatic debits work well in situations in which you invoice predefined amounts every month. You can also use automatic debits with invoice amounts that vary with each billing period. The steps involved in processing automatic debits are as follows:

  1. Create invoices
  2. Create a batch of automatic debits using Create Automatic Debit Batch (R03B571).
  3. Process automatic debits in final mode:
    • Creates Receipt Header (F03B13) and Receipt Detail (F03B14) records.
    • Updated the Automatic Debits Batch Control (F03B571).
  4. Update Automatic Debit Invoice Select & Build table (F03B575).
  5. Format the batch of Automatic Debits
  6. Update the Automatic Debits Standard Formatted Tape table (F03B57OW).
  7. Copy F03B57OW table to media (and send to the bank).
  8. Purge Automatic Debits

  style="margin-top:auto;margin-bottom:auto"

    • Select the customer invoices to be paid.
    • Build and update worktables that are sent to the bank.
    • Update customer invoices as paid.
    • Format automatic debit information to meet country-specific bank requirements.
    • Copy automatic debit information to a medium to send to the bank, or transfer automatic debit information electronically.
    • Purge automatic debit batches.

  style="margin-top:auto;margin-bottom:auto"

    • Auto Debit Invoice Select and Build (F03B575).
    • Auto Debit Standard Formatted Tape File (F03B57OW).

 

Note: Country-specific functionality for processing automatic debits exists for certain countries. For more information relating to EMEA globalizations, please visit the ‘JD Edwards EnterpriseOne Globalization site, Document 752291.1. This site provides details about country specific localizations, translations, announcements about upcoming plans and other helpful information.

 

More details on how this process works, common issues and troubleshooting tips could be found in:

  • How To Set Up, Process and Frequently Asked Questions Automatic Debits In EnterpriseOne Accounts Receivable (R03B571, R03B575) (Doc ID 655040.1)
  • Frequently Asked Questions on Automatic Debits (R03B571) (Doc ID 644179.1)

You can use credit reimbursements to reclassify credits in the JD Edwards EnterpriseOne Accounts Receivable system to open vouchers in the JD Edwards EnterpriseOne Accounts Payable system. For example, you can issue rebates and reimburse customers for overpayments. When you generate credit reimbursements, the system pays open credit memos and generates vouchers to reimburse the customer.

 

Credit reimbursements are generated based on the grouping of customer, company, and currency combination.

 

Note: In addition to the credit reimbursement process, you can use the AR/AP netting process to bilaterally reclassify transactions between Accounts Receivable and Accounts Payable. The difference between the two functionalities is that Credit Reimbursements is one-way, closing A/R transactions and creating A/P ones, whereas AP/AR Netting is two-way. See Document 8500361.1 for more information on AR/AP Netting.

 

More details on how this process works, common issues and troubleshooting tips could be found in:

  • How To Generate Credit Reimbursements In EnterpriseOne Accounts Receivable (R03B610/R03B620) (Doc ID 663716.1)
  • Frequently Asked Questions About Credit Reimbursements (R03B610, R03B620) (Doc ID 945017.1)

 

When you want to review account activity over several fiscal periods, as well as statistics such as delinquent days sales outstanding (DSO), weighted average days late, average invoice amount, percent of invoices paid late, and so forth, you can run the Statistics History Update (R03B16A) program. In addition to providing statistical information about the performance of collections over a period, the system enables you to review multiple customer accounts simultaneously for comparison purposes.

 

More details on how this report works, common issues and troubleshooting tips could be found in:

  • How To Process and Purge Statistical History Refresh Data In JD Edwards EnterpriseOne Accounts Receivable (Doc ID 625834.1)

  • Frequently Asked Questions about AR Statistical History (Doc ID 664021.1)

  • How To Calculate Statistical History Update Fields (Doc ID 656325.1)

 

As of JD Edwards EnterpriseOne Release 9.2, the Financial Management Fundamentals Implementation Guide has been updated to include information about entering translations for payment terms.

 

The AR reports, Statement Print Report (R03B5001) and Credit Card Statement Print Report (R03B5003), print the entered translations based on your customer language preference. The rest of the transaction reports print the entered translations based on your user profile language preference.

 

More information regarding this process can be found in solution New Enhancement – Address Book and Payment Term Translation EnterpriseOne 9.2 (Doc ID 2317467.1)


The new enhancements are also document in the
JD Edwards EnterpriseOne Applications Financial Management Fundamentals Implementation Guide:

The Accounts Receivable guide has been updated to include a new applications that enables users to schedule portions of an invoice for revenue recognition on specified dates.

  • Using a Schedule to Recognize Revenue (Release 9.2 Additional Update)

 

You can use a schedule to recognize specified portions of revenue on a pay item on different dates. When you create a schedule on a G/L distribution line on an invoice, you can:

  • Automatically split the remaining amount across a specified number of periods.
  • Manually enter schedule records.
  • Use a combination of these methods.

 

For example, you can automatically split the remaining amounts across a specified number of periods, and then manually update those records to reflect the distribution schedule you want to use. Alternatively, you can manually enter a record in the grid, and then split what is left of the remaining amount across a specified number of periods.

 

The new enhancement are also documented in the JD Edwards EnterpriseOne Accounts Receivable guides:

As of JD Edwards EnterpriseOne Release 9.1, Oracle delivers software updates to address new joint standards for recognition of revenue issued by the Financial Accounting Standards Board (FASB) and the International Accounting Standards Board (IASB).

 

Note: There is no Revenue Recognition solution available for releases lower than 9.1.

 

The new Revenue Recognition enhancement is available as of JD Edwards EnterpriseOne release 9.1 and delivered via ESUs.  Please see the following Knowledge Documents for more information:

  • New Enhancement For FASB – Revenue Recognition in Accounts Receivable For Release 9.1 (Doc ID 2030115.1)
  • New Enhancement Release 9.1 and 9.2 – FASB/Revenue Recognition (Doc ID 2165868.1)
  • New Enhancement Release 9.1 and 9.2 – FASB/Revenue Recognition Audit Applications (P03B118/P03B119) (Doc ID 2203596.1)

 

More information regarding this process can be found in solution JD Edwards EnterpriseOne Revenue Recognition Enhancement for Accounts Receivable (FASB) (Doc ID 2212312.2)

 

Note: This knowledge document is limited to Revenue Recognition setup and process for invoices created in the Accounts Receivable (G03B) module.  Cost of Goods Sold (COGS) functionality is not covered in this document.


The new enhancements are also document in the JD Edwards EnterpriseOne Accounts Receivable guides:

 

See JD Edwards:The Impact of Revenue from Contracts with Customers Frequently Asked Questions for more details.

You may have attended on September 13 th, 2016, Advisor Webcast: Revenue Recognition - A/R and Sales Accounting Changes are Coming. Whether you have or haven’t, I thought that it is an important enough topic to discuss here in the blog as well.

 

Business Problem

  • Currently revenue recognized when invoice is posted to G/L
  • Business processes and industry standards require the recognition of revenue separate from the invoice process
  • New Revenue Recognition Standard to be in effect in January 2018
    • Convergence of IFRS and US GAAP revenue recognition standards
    • Common standard from the International Accounting Standards Board (IASB) and the Financial Accounting Standards Board (FASB)
    • Replaces all existing revenue recognition standards
    • All industries and countries
  • Exceptions are the Insurance and Lease Vendor industries

 

The Financial Accounting Standards Board and the International Accounting Standards Board initiated a joint project to clarify the principles to recognize revenue and develop a common revenue standard for U.S. GAAP and IFRS that would:

  • Remove inconsistencies in revenue requirements.
  • Provide a more robust framework for revenue.
  • Standardize practices across entities, industries, and jurisdictions.
  • Provide more useful information through improved disclosures.
  • Simplify the preparation of financial statements.

 

More information can be found in knowledge document: ADVISOR WEBCAST: Revenue Recognition - A/R and Sales Accounting Changes are Coming (Doc ID 2153199.1).

Filter Blog

By date: By tag:

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see https://community.oracle.com/docs/DOC-1022508 for instructions.