This is one of R12.2.5 Enhancement in EBS AR.

The Automatic Cash Application improves accuracy and on-time application of cash receipts with the introduction of two new methods for automatically applying cash receipts.

• The first method generates match scores using the Levenshtein distance algorithm and automatically applies the receipt based on a score threshold.
• The second methods applies receipts by knap sacking the receipt amount and the open transactions of the customer.

Both methods provide suggested matches when a receipt cannot be applied automatically

Background information on the Levenshtein distance algorithm [ From Wikipedia, the free encyclopedia ]

In information theory and computer science, the Levenshtein distance is a metric for measuring the amount of difference between two sequences (i.e., the so called edit distance).

The Levenshtein distance between two strings is given by the minimum number of operations needed to transform one string into the other, where an operation is an insertion, deletion, or substitution of a single character. A generalization of the Levenshtein distance (Damerau–Levenshtein distance) allows the transposition of two characters as an operation. Some Translation Environment Tools, such as translation memory leveraging applications, use the Levenhstein algorithm to measure the edit distance between two fuzzy matching content segments.

The metric is named after Vladimir Levenshtein, who considered this distance in 1965.It is often used in applications that need to determine how similar, or different, two strings are, such as spell checkers.
For example, the Levenshtein distance between “kitten” and “sitting” is 3, since the following three edits change one into the other, and there is no way to do it with fewer than three edits:

1. kitten -> sitten (substitution of ‘s’ for ‘k’)
2. sitten -> sittin (substitution of ‘i’ for ‘e’)
3. sittin -> sitting (insert ‘g’ at the end).

You need to consider these points when you are trying setup Legal Entity Document Sequencing in Receivables

You can set up your primary ledger to allow document sequencing at the legal entity level instead of at the ledger level.

This means if you have more than one legal entity assigned to the same ledger, you can assign separate document sequences to each of your Receivables transactions, adjustments, and receipts belonging to each legal entity.

Legal entity level document sequencing helps you conform to local and governmental authority requirements, while still being able to organize multiple legal entities under the same primary ledger.

These are key points you need to consider if you want to use document sequencing at the legal entity level for Receivables:

• Document Sequencing in Receivables
• Receivables Document Categories
• Gapless Document Sequencing
• AutoInvoice Processing

Oracle Cloud Receivables setup is very similar to Oracle R12 EBS looks for and assigns a legal entity to a transaction according to this hierarchy:

• Legal entity of the transaction type assigned to the transaction.
• Legal entity of the transaction source assigned to the transaction.
• Default legal entity assigned to the business unit.

Reader question

Is it , possible to share document sequences across ledgers or business units?

If you maintain document sequencing at the legal entity level, it is not recommended to share the same document sequence across ledgers or business units.

Document sequencing at the legal entity level uses the accounting date as the document sequence date. Because ledgers can have different accounting periods open, each ledger could derive a different accounting date for the same document sequence.

Because Receivables creates a document category for each transaction type you create, it is recommended to create and maintain a separate set of transaction types in each business unit.

Hope this helps , next will discuss more in details.

Multi-element arrangement aka occurs when a vendor agrees to provide more than one product or a combination of products and services to a customer in an arrangement.

Multi-element arrangements may include additional software products, rights to purchase additional software products at a significant incremental discount, specified upgrades or enhancements, hardware, PCS or other services.

Multiple-element arrangements must be evaluated for separation to determine whether there are multiple units of accounting within the multiple-element arrangement.

Definition of “Arrangement” – A group of contracts or agreements may be so closely related that they are, in effect, parts of a single arrangement.

The form of an arrangement is not necessarily the only indicator of the substance of an arrangement.

The existence of any of the following facts but not limited to may indicate that a group of contracts should be accounted for as a single arrangement:

• The contracts or agreements are negotiated or executed within a short time frame of each other.
• The different elements are closely interrelated or interdepent in terms of design, technology, or funtion.
• The fee for one or more contracts or agreements is subject to refund or forfeiture or other concession if another contract is not completed satisfactorily.
• One or more elements in one contract or agreement are essential to the funtionality of an element in another contract or agreement.
• Payment terms under one contract or agreement coincide with performance criteria of another contract or agreement.

Sometimes the simplest way to manage a credit transaction is to credit and rebill.

You credit the entire balance of an invoice, duplicate the original invoice and update the duplicate with the correct information, then resubmit to the customer.

Common scenarios for credit and rebill include:

• A customer indicates that an invoice does not reflect the correct price of a product or service. The customer requests a new invoice with the correct information.
• A customer wants to correct their accounting directly in the subledger, instead of making a manual journal entry in general ledger. With credit and rebill, the credit memo reverses the accounting of the original invoice, and the updated duplicate invoice creates new accounting for posting to general ledger.
• The customer wants to change the bill-to information on a posted transaction.

Usually, The credit and rebill actions are performed in few steps and will create the credit bill and the new rebill.

If you are not using these ACcounting method, then you can use Merged Distributions feature in AR.

• Cash Basis accounting , that mean accounting is created only at the time of receipt of cash.[ Release 12 seeds Subledger accounting methods: Encumbrance Cash and Standard Cash]
• Multi-Fund Accounts Receivable accounting , that means where receivable accounting lines for an invoice are created at the level of invoice line.[ Release 12 seeds Subledger accounting methods: Multi-Fund Accrual – Account Method and Multi-Fund Accrual – Balancing Method]
• Line Level Cash Applications

Merge Distribution Feature

When the Merge Distributions feature is enabled, thereceivable distributions for a transaction are created at the Invoice Header level instead of the Invoice Line level.

All subsequent adjustments and applications against the transactions are also not maintained at the invoice line level , as understood below:

Adjustments and receipt applications are not pro-rated across the invoice lines. This is same way the receivable distributions are created in Release 11i.

The summarized distributions will significantly reduce the volume of data generated for adjustments and applications in Receivables and reduces the volume of data passed to Subledger Accounting for generation of accounting.

Benefits of Business Solution

• This solution will result in significant performance gain for creating accounting entries for receipts.
• This solution will limit the growth of data volume.
• Summary distributions are easier to interpret.

This solution is specially recommended for customers with very large number of lines per invoices, as large number of invoice lines correspond to significantly higher number of distribution lines which are passed for each accounting event to the accounting engine for generation of accounting entries.

How to Enable the Merge Distribution Feature

The merged distributions feature is controlled by the following:

• In the AR System Options form, there is a new checkbox “Create Detailed Distributions” as below:

The checkbox was released as part of Patch 7559194 LINE LEVEL DISTRIBUTIONS NOT NEEDED FOR HEADER LEVEL CASH APPLICATION/ADJUSTMENT, as part of the “Merge Distributions Enhancement”.

• By default the checkbox will be checked indicating that AR will create detailed distributions
• To enable Merge Distribution, you need to Uncheck the checkbox

When should the Checkbox be UNCHECKED

When the checkbox is UNCHECKED, Oracle Receivables will create summarized distributions.

The receivable distributions for adjustments and applications are not maintained at the invoice line level, instead a summarized receivable distribution is created at the invoice header level. Adjustments and receipt applications are not pro-rated across the invoice lines. This is same way the receivable distributions are created in Release 11i.

Following is the impact of having the checkbox UNCHECKED: [ source Metalink Doc ID 1081657.1 ]

• When you create Batch Sources (Navigation: Setup > Transactions > Sources), in the Batch Source tab, the checkbox Generate Line Level Balances will be disabled.
• When you create Receipt Applications (Navigation: Receipt > Receipts) in the Applications form, the Apply in Detail button will be disabled.
• When you create Adjustments against transactions (Navigation: Transactions > Transactions, Toolbar Menu Actions > Adjust) in the Account, IDs tab, the Line column will be disabled.
• When using the Receipt or Adjustment APIs, you cannot create line level applications.

Additional Refrence :

• What is the Checkbox ‘Create Detailed Distributions’ for? Doc ID 1081657.1

When you need to process a Credit Memo against an Invoice that has already been paid by a receipt, you need to define how you want to handle the funds from the Receipt payment.

In that case, you have the option of putting the receipt amount On-Account to be applied to a future invoice of the same customer, or you can choose to refund the payment back to the customer upfront .

With this Out of box featue in AR , this process involves unapplying the receipt payment against the invoice, and then handling the receipt to either:

• Generate a refund, or
• Put funds on account to use as payment for a later time

The process of automating what will be done to the receipt is what Automated Receipt Handling for Credits feature handles.

If you want to use this Feature , You must ensure that you set up your feeder systems with business processes that support this assumption.

SETTINGS THAT AFFECT AUTOMATED RECEIPT HANDLING FOR CREDITS

These five settings affect automated receipt handling for credits:

1. Transaction Source: you need to define an imported transaction source and set the Receipt Handling for Credits option to indicate your enterprise policy. Assign this transaction source to the applicable imported credit memos.
2. Minimum Refund Amount system option: If you plan to process refunds, specify in the Minimum Refund Amount system option the minimum amount necessary for AutoInvoice to create a refund.
3. Receivables Activity: If you plan to process refunds, define a Credit Card Refund receivables activity for credit card refunds and a Refund receivables activity for non-credit card refunds. The receivables activity identifies the general ledger clearing account to use to clear the refund amounts.
4. Credit Card Transaction Remittance Method: On the original credit card transactions, use a receipt class with a remittance method of Standard.
5. Transaction Type: The transaction type assigned to the debit items must be set to Natural application only. If the transaction type of a debit item is set to Allow overapplication, then you must process the credit manually.

HOW AUTOMATED RECEIPT HANDLING PROCESSES CREDITS

During AutoInvoice import, the process flow for automated receipt handling for credits is as follows:

1. AutoInvoice verifies that the transaction source assigned to the credit memo has automated receipt handling enabled.
2. AutoInvoice evaluates each credit memo and its associated transaction to determine eligibility for automatic receipt handling. To be eligible:
   • The transaction type of the paid transaction must be set to allow natural application only.
   • The transaction must not be in doubt.
3. If eligible, then AutoInvoice unapplies the paid transaction from the receipt to be credited.
4. AutoInvoice creates thecredit memo in the amount of the requested credit, and applies the credit to the transaction.
5. If your policy is to automatically refund your customers, then AutoInvoice evaluates the receipt for refund eligibility. To be eligible, the receipt must not be in doubt.
6. If eligible for refund, AutoInvoice creates the refund for all credit request amounts that are greater than or equal to the value entered in the Minimum Refund Amount system option.
   • AutoInvoice places on account any credit amount that is less than the specified minimum.
7. AutoInvoice applies the appropriate receivable activity to the receipt, as determined by the transaction source.

TRANSACTIONS AND RECEIPTS IN DOUBT

There may be few senarios , when autoInvoice rejects a credit memo from automated receipt handling if one of the following conditions exists on the transaction to be credited:

• The transaction type of the transaction is set to allow overapplication.
• An on-account credit memo was previously applied against the transaction.
• A regular or chargeback adjustment already exists against the transaction.
• The credit memo is imported against a transaction with a negative creation sign.

If the credit memo is ineligible due to one of these conditions, AutoInvoice processes the credit memo using standard validation. This way you can evaluate the appropriateness of the credit request before taking action.

For refund requests, AutoInvoice automatically places on account the amount of a refund request if one of the following conditions exits:

• The receipt to be refunded has not yet been remitted.
• Receipts with different payment types (ACH, cash, credit card) were used to pay the same transaction to be credited.
• Installments exist on the transaction and are not fully paid.
• The receipt has an on-account credit memo against it.

KNOWN BUG

Automatic receipt handling for direct debits is not working as expected. When running the Autoinvoice program, a credit memo is created correctly, then instead of creating a Refund application against the receipt, it creates an On-Account application instead.

You need to apply the patch #The issue is addressed in Bug 9473751

Under Generally Accepted Accounting Principles (GAAP), deferred revenue, sometimes called unearned revenue.

Deferred revenue is a liability that is created when monies are received by a company for goods and services not yet provided.

What is the deferred revenue?

Deferred revenue is a liability that is created when monies are received by a company for goods and services not yet provided.

Revenue will be recognized, and the deferred revenue liability eliminated, when the services are performed.

Deferred revenue stems from the accounting concept of revenue recognition, under which revenues are recognized only when the earnings process is complete. If funds are received and no goods or services have yet been provided, the process is not complete; thus revenue cannot be recognized, and a deferred revenue liability is recorded.

Specifically, the deferred revenue account is credited, and cash (or otherassets) are debited. Please take a note deferred revenue is recorded in specific industries under particular circumstances.

Deferred Revenue Example

Like many subscription businesses, A internet Hosting company offers a plan to pay upfront for whole year.

Since deferred revenue represents the value of the services that are left to be delivered at a point in time, if you purchased the annual plan, $2400 would be added to both the cash account of the balance sheet and the deferred revenue line. Every month $200.00 would be moved out of deferred revenue and reported as revenue on the income statement.

Understand why you need to defer revenue.

Why can’t you just record the revenue when you actually receive the cash payment? By doing so , this would violate the principles of accrual-based accounting.

There are 2 principles which provide the foundation for accrual accounting.

1. The first is the matching principle. Under the matching principle, revenues and expenses that correspond to each other must be recorded in the same accounting period. Using the insurance example above, you cannot recognize all the revenue in January, because there will be expenses associated with that insurance coverage incurred throughout the year. These expenses must be matched with their corresponding revenues.
2. The second is the revenue recognition principle. This principle dictates that revenues should only be recorded when they are both realized (or realizable) and earned. “Realized” revenues are those for which a claim to cash has been received, and “earned” revenues are those for which a good or service has been rendered.

The implication, then, is that you cannot simply record a revenue whenever cash is paid to your company. If, for example, a client is prepaying for a continuing service, then you cannot recognize that payment as revenue until you actually render the service. Until then, the payment represents a liability, or an obligation to the client. This makes sense to you.

Governing Rule

For revenue to be recognized (earned), SEC have SAB 101/104 sets four key conditions that must be met:

1. Persuasive evidence of an arrangement exists,
2. Delivery has occurred or services have been rendered,
3. The seller’s price to the buyer is fixed or determinable, and
4. Collectability is reasonably assured

Understanding the Deferred Revenue Accounting Process

You can create and send invoices for products or services that you will deliver in the future or over a range of time.

Invoice details:

• Bill line amount: 6000.00 USD.
• Invoicing Rule = Bill in Advance
• Invoice Date 2-DEC-12
• GL Date 2-DEC-12
• Accounting Rule:Type: Accounting, Fixed Duration
• Period : Monthly
• Number of Periods : 6

Here is accounting Posting

Finally

Keep in mind that deferred revenue generally means that cash has been received by the seller, so the remaining concern is determining when the cash is recognized as earned revenue. Within GAAP, there are multiple methods that can be used to recognize revenue. Depending upon which method is chosen, the financial statements may look drastically different even though economic reality remains the same.

Are you aware about the top three concerns for finance teams as

1. Financial closing and reporting process
2. Excessive use of spreadsheets
3. and revenue recognition.

In key finding of survey conducted by www.RevenueRecognition , it was observed

• 92% of public companies rely on manual processes to perform key revenue recognition and reporting functionality (nearly the same percentage is true for private companies).
  • 68% of all companies stated their Financials/ERP systems DO NOT automate all their revenue recognition and reporting activities.
  • 84% of companies that initially stated Financials/ERP systems DO automate revenue accounting are actually using spreadsheets for these activities.
• The finance processes that are most difficult to establish internal controls for are contract management and revenue recognition.
• Companies want to spend less time on data aggregation, manipulation, and validation and more time on business performance analysis.

Issue with EXCEL

Using Excel as the “system of record” for managing revenue

The problems were…

• Excessive time and effort to:
  • analyze and arrange an enormous amount of data
  • close the books
  • create journal entries
  • ensure accuracy
• Increased time and effort to manage accounting controls
• Inflexible reporting and analysis and the volume of data was growing

Missing Link

92% of companies said above, they are using spreadsheets for one or more of the following key revenue recognition and reporting tasks:

• Applying revenue allocation rules
• Redistributing revenue (e.g. based on SOP 97-2, EITF 00-21)
• Creating revenue recognition schedules for future periods
• Reviewing sales orders to identify deferred items
• Performing revenue contribution analysis
• Reporting on future revenue streams
• Creating accounting entries

Regardless of whether your company is private or public, does your organization recognize the importance of consistent and reliable revenue recognition ?

Revenue Recognition

Revenue Recognition is Principle of accrual accounting that determines the period in which revenue is recognized

• Revenue recognition is an earning process
• There are rules and regulations on how and when you can recognize revenue
• Under GAAP, there are four basic criteria:
  • Evidence of an arrangement exists (governing contract & PO)
  • Delivery has occurred (transfer title and risk of loss)
  • Fee is fixed or determinable (normal payment terms)
  • Collection is probable (customer has ability to pay)

Accounting terminology you may hear – FASB and IFRS guidelines, evidence of an arrangement, delivery, fixed fees, collection, software and non-software rules, multiple element arrangements, fair value (VSOE, BESP, TPE), relative selling price, revenue allocation, linked arrangements, acceptance, release events, contingencies, future upgrades, significant discounts, extended terms, software is essential to functionality, deferred revenue release, and so on….In other words – it’s HIGHLY TECHNICAL

Revenue Requirements

Challenge that software companies face results from the volume and complexity of the revenue recognition guidance that exists.in such case, software arrangements include both software and services. The services could include installation, training, software design, or customization and modification of the software. If the services involve significant customization or modification of the software, then contract accounting under SOP 81-1 should be used for the arrangement.therefore , under such senario , Revenue Requirement should mainly focus on .

1. Compliance
   • Calculate VSOE(Vendor-Specific Objective Evidence / ESP (Estimated Selling Price)
   • Manage VSOE/ TPE(Third Party Evidence)/ESP
   • Tolerances
2. MEA (Multiple Element Arrangements)
   • Track MEA from multiple sources
   • Classify elements
3. Revenue Recognition
   • Standalone sales
   • MEA
   • Rev rec carveouts according to VSOE/TPE/ESP
   • Deferrals & rev rec timing
   • COGSs
   • GL Posting
4. Reporting
   • Revenue compliance
   • Billing and revenue reconciliation
   • Revenue forecasts
5. Notifications
   • VSOE reference during pricing
   • Rev rec related notifications (approved exceptions, renewals, collectability status, etc.)

Key Aspects in Revenue Requirements

• User-defined Revenue Contingencies
• Fair Value Analysis
• Auto Accounting Rules
• Amortization Methods

EBS R12 Revenue Management Enhancements, filling the Gap of Missing Link

Organizations will also find that Oracle Financials R12 allows them to manage revenue with greater flexibility and improved accuracy.

• Partial Period Revenue Recognition enables the generation of revenue recognition associated with contracts
• Revenue Deferral Reasons based on events specific to an enterprise’s business practices
• COGS and Revenue Matching synchronize the recognition of revenue with the associated COGS in compliance with Generally Accepted Accounting Principles

If you do not use an AutoInvoice clearing account and enable the Create clearing option on the transaction source, AutoInvoice requires that the revenue amount be equal to the selling price times the quantity for all of the transactions it processes.

AutoInvoice rejects any transaction line that does not meet this requirement.

AutoInvoice Clearing Account

During AutoInvoice processing, Receivables uses the AutoInvoice clearing account to store any differences between the specified revenue amount and the (price * quantity) for imported invoice lines.

Receivables only uses the AutoInvoice clearing account if you enabled the Create clearing option on the transaction source assigned to imported transactions. However, you must define a clearing account in any case.

You can use constant value, customer bill-to site, salesperson, transaction type, and standard item for your AutoInvoice clearing account. If you select salesperson or standard item, Receivables uses the specified Revenue Flexfield.

The Calculation

The AutoInvoice Clearing Account is used when the supplied Amount does not match Unit Selling Price times the Quantity.

The calculation is the following:

• AutoInvoice Clearing Account = (quantity * unit_selling_price) – amount
• Tax(rate based tax) = (quantity * unit_selling_price) * tax_rate
• Revenue = amount

Account Receivables = Sum of all
1. Revenue Lines
2. Tax lines
3. AutoInvoice Clearing Account

Dunning Plans in Advanced Collections replaced the Receivables Dunning Letter processing in Release 11i. Dunning Plans are relatively “simpler” way of implementing Advanced Collections.

If Dunning letters are used as part of the standard collection process, the Dunning Plans in Release 12 helps achieve the same result but adds more functionality by combining the score calculated using the scoring engine to pick the correct Dunning letter format.This implementation option also lets users create call back tasks in addition to sending the Dunning letters.

Dunning Letters in Release 12 are defined in the BI Publisher.

In 12 the word “delinquency” is new to most 11i users and this means an overdue item. .

There are 2 types of Dunning Plans that you may setup.

1. Days Overdue Method – based on the aging buckets you are using to collect your payments

You will setup the Dunning Plan and include Aging Bucket lines for each Aging Bucket Line you have assigned in your Aging Bucket.
For Example – if you are using a 7 Bucket Aging, then the Dunning Plan will have at least 6 Aging Bucket Lines.

2. Staged Method – based on the date of the last letter sent or Dunning Stage

When a Delinquency is created, the Staged Dunning Level is null. Once you run the Staged Dunning and that Delinquency is included in a letter, the Staged Dunning Level count is incremented. You may see this on the Transaction Tab if you bring up the Transaction and show the Staged Dunning Level count.

Dunning plans limitations

• Delinquency scoring engine and dunning plan scoring engine is one and same
• Scoring engine values are used both for delinquency status determination and aging bucket line determination so it can be tricky to obtain desired functionality
• A transaction can only be scored using one scoring engine – if you add a new scoring engine only new transactions will be scored with this
• AR Aging Buckets are used for days overdue determination only – unless you customise scoring components
• Only one aging bucket can be used per dunning plan

Running Concurrent Programs for Dunning Plans

You must run the following concurrent programs in Oracle Advanced Collections to execute dunning plans:

• IEX: Promise Reconciliation: This program updates the open promise information in Advanced Collections with payments received in Oracle Receivables to determine outstanding items.
• IEX: Territory Assignment: This program assigns collectors to customers who are using Oracle Territory Manager. You can assign collectors at the customer, account, or bill-to level. This program retrieves a list of available collectors for each territory and assigns the first collector on the list. If you are using Territory Assignment, it is advisable to run this concurrent program first whenever you run the IEX: Scoring Engine Harness.
• IEX: Scoring Engine Harness: You can select up to five scoring engines to run at the same time. The scoring harness assigns a value to an object such as a customer, account, or bill to location. Another score determines whether transactions are delinquent, pre-delinquent, or current.
• IEX: Send Dunnings for delinquent customers: This program sends the results of the scoring engine harness to Oracle XML Publisher to send out dunning correspondence.
• IEX: Create Dunning And Broken Promise Call Backs: If you have dunning callbacks as part of your dunning plan, run this program to create callback work items to a collector’s task list in the Collector’s Work Queue.

Dunning in Correspondence History

When you select the Correspondence history type on the History tab, Oracle Advanced Collections provides a review of all dunning events initiated by the dunning process. You can view this information by customer, account, bill to location, or delinquency data level. Summary level information on all dunning events are also displayed in the All history.

Want to Preview the Dunning Letters Before They are Sent to Customers with Dunning Plans

Collections supports preview and selective dunning with “IEX: Send dunning for Delinquent customers” concurrent program ONLY.

There is no Preview/Draft functionality for Strategies when submitting the IEX: Bulk XML Delivery Manager manually.

Added the following parameters to “IEX: Send Dunnings for delinquent customers” concurrent program.
a. Preliminary : possible values are Yes/No
b. Process errors only : possible values are Yes/No
c. No of workers :

Following parameters can be used to process only particular/set of customer/account/bill to locations.
d. Customer name low :
e. Customer name high :
f. Account number low :
g. Account number high :
h. Billto location low :
i. Billto location high :

“IEX: Send Dunnings for delinquent customers” concurrent program always spawns the “Oracle Collections Delivery XML Process (IEX: Bulk XML Delivery Manager)” to process/send the dunning letters.

Migrating 11i Dunning Letter Sets to R12 Staged Dunning

• Concurrent program “IEX: Dunning Letter Sets Migration for Staged Dunning”
• and a profile option called ‘IEX: AR Dunning to IEX Dunning Migrated’ in 12.1.3

will allow you to migrate the dunning letter sets from 11i AR Dunning to R12 Advanced Collections.

Know five most common Dunning Plan Issues

• Missing Corresponding Template – you are missing a template name on an aging line or stage line in the Dunning Plan setup. See Note: 466328.1
• AgingBucketLineId NotFound – you are missing an aging line in your Dunning Plan setup or you have not covered the range from 1-100 for each Aging line.
• The send dunning flag in customer profile is set to no – The Send Dunning flag must be checked on the Customer Account or Bill To depending on your Business Level.
• Missing Score – You have not run the IEX: Scoring Engine Harness for the scoring engine that you linked in the Dunning Plan. That Dunning Plan uses the scores created by the linked engine to send the Dunning Letters.
• Required min Dunning amount in customer profile – You must set the minimum Dunning on the Account or Bill To depending on the Business Level.

Next Post will more focus on Scoring .