Guidelines for Using Prospective Accounting with Subscription Products

Keep the following points in mind when you use prospective accounting in Oracle Subscription Management to reflect minor unit selling price changes:

• Subscription Management lets you use prospective accounting only for recurring charges. Price revisions of one-time and usage charges are always sent using retrospective accounting.
• Revenue Management supports prospective accounting only when the satisfaction plan is Daily rates partial periods. Because the satisfaction plan is defaulted from the Manage Source Document Types page, you must set the default value of the satisfaction plan to Daily rates partial periods for the source document type Subscription Management.
• Any revisions performed as a one-time charge trigger retrospective accounting on the customer contract.
• A new one-time charge added to an existing contract triggers retrospective accounting on the customer contract.
• If any of the revenue lines with a satisfaction measurement model of Quantity or Percent aren't fully satisfied in the contract, this scenario always triggers retrospective accounting on the customer contract.
• If you perform a backdated price adjustment on a customer contract on which the application previously performed prospective accounting, the backdated price adjustment triggers retrospective accounting on the customer contract.