Nakumatt R12 Implementation

ORACLE R12 FINANCIALS IMPLEMENTATION

Advance Collection User Manual

Author: Mahesh Kulkarni

Creation Date: July 1, 2014
Last Updated: Aug 27, 2014

Version: V 1.0

1
 Nakumatt R12 Implementation

Table of Contents
1. Define Customer Statement Cycle 3
2. Print statements 4
3. Print Dunning Letters (Demand Letters) 8

2
 Nakumatt R12 Implementation

1. Define Customer Statement Cycle

1.1 Receivable Manager Responsibility  Setup Print Statement Cycles
To define a statement cycle:
1. Navigate to the Statement Cycles window.
2. Enter a Name and Description for this statement cycle.
3. Enter the Interval for this statement cycle to indicate how often Receivables will generate your
statements. You can choose Weekly, Monthly, or Quarterly.
4. Select an operating unit.
5. Enter Statement Dates for this statement cycle. Receivable uses the statement date to determine past due
items and calculate late charges.
6. To prevent Receivables from printing a statement on a specific statement date, check the Skip box.

1.2 Define Statement Cycle

Note: The Date Printed field displays the last date you printed statements from the Print Statements window
for each statement date within a statement cycle. Receivables does not display a printed date for statement
dates that you have either elected to skip or have not yet selected for a statement submission.
Receivable populates this field only if you print statements for all customers who are assigned to this statement
cycle.

3
 Nakumatt R12 Implementation
2. Print statements

2.1 Receivable User Responsibility  Print Documents Statments

1. Navigate to the Print Statements window.

2. Select an operating unit.

3. Enter a print Option. Choose from the following:

Print Statements: Print statements for either a specific customer, customer site, or all of the customers
and customer locations that have the statement cycle that you specify in their credit profiles. This option
includes activity from the last statement date to the current statement date.
Print A Draft Statement: Print a draft statement for a customer or site to review before sending it to this
customer.
Reprint Statements: Reprint any statements that you have previously printed.

4. Enter the aging Bucket to use

5. Enter the Customer name or Number and the billing Location for this submission. Alternatively, you can
specify a customer name range or customer number range.

Note: You can enter either a customer name range or a customer number range but not both. When you
Enter a customer name or number range, the location field is disabled and the statement cycle does not
default.

If you do not select a customer, then:

Receivables will print statements for all customers for the statement cycle that you specify.

Suggestion: To print statements for all customers by transaction type, submit a subsequent request using
the Reprint Statements option. To conserve paper, do not send the first request to a printer.

4
 Nakumatt R12 Implementation

6. Enter a statement Cycle.

7. If you are printing a draft statement, enter an As of Date. This date determines the transactions to include
in your draft statement. The default is today's date.

8. Enter the Statement Date for this submission. When you enter a statement cycle, the default statement
date is the next available statement date for this cycle. You can choose another date from the list of
values.
Note: Statement dates that you defined but chose to skip will not appear in the list of values.

9. To include only specific transactions in this statement, enter a Transaction Type.

This field is not enabled when printing statements for all customers for a specific statement cycle.
Note: All On-Account and Unapplied receipts appear on the statement that you print. Since On-Account
and Unapplied receipts are not linked to any transactions, they cannot be excluded from the statement
because of transaction type.

10. To a standard message on your statement, enter the Name of the standard message, or select from the list
of values. You can only select messages that have start and end date ranges that include the current date.

5
 Nakumatt R12 Implementation

11. Save your work. Receivable assigns this submission a unique Request ID. You can use this number to check
the status of your request in the Requests window.

12. Note: Receivables creates your statement output file and requires that you send this file to your printer
using your operating system's landscape print command. When you send this file to your printer,
Receivables prints one sample page of Xs to show you how your statement will print. This lets you make
any necessary adjustments before you start printing your statements.

13. Go to View Request and View ‘AR Customer Balance Statement Letter (AR Customer Balance Statement
Letter)’ Out Put

6
Nakumatt R12 Implementation

7
 Nakumatt R12 Implementation
3. Print Dunning Letters (Demand Letters)

Nakumatt Dunning Letters are based on Aging Bucket ( Days Overdue )

Days Overdue: Letters are based on the total number of days that debit items are past due. This method generates
letters for a specific customer based on a range of days overdue that you define for each dunning letter set.
Receivables takes into account the number of receipt grace days defined for a customer (if any) when calculating
the number of days items are past due.

Collection Agent Responsibility Run following Requests

1. IEX: Promise Reconciliation

Verifies if payments were posted for invoices with promises; creates broken promise items for UWQ

Completed & Normal

2. IEX: Scoring Engine Harness

Scores and creates delinquencies, and scores customers, accounts, or bill-to locations

8
 Nakumatt R12 Implementation

IEX__Scoring_Engine
_Harness_270814.pdf

Will get report with Customer and Customer Score.

Collection Agent Responsibility Run following Requests

OR

Receivable User Responsibility  Print Documents IEX: Send Dunning For Delinquent Customer

Select Customer if we need run for specific customer, if blank it will run for all.

9
Nakumatt R12 Implementation

View output of ‘Oracle Collections Delivery XML Process (IEX: Bulk XML Delivery Manager)’ Request.

10
Nakumatt R12 Implementation

IEX__Bulk_XML_Deliv
ery_Manager_270814.pdf

11