In order to enable pay plan functionality, you will need to define an obligation type that is suitable for a pay plan. Depending on the business rules of the tax authority, you may need multiple pay plan types, which will require you to define multiple obligation types. For example you might want to create a pay plan type for individual taxpayers, and a different pay plan type for a business.
The following points provide guidelines for creating a pay plan obligation type:
Obligation Type - Pay Plan Recommendation Rule
Add the recommendation rules defined above that are valid for obligations of this type. Also, indicate which recommendation rule should be used as the default.
Tax Type should either reference a specific tax type or a generic tax type (e.g. miscellaneous fees) depending on your authority's business rules.
Revenue Class should be set to N/A. (Revenue classes are not applicable because pay plans do not apply a rate and revenue classes are only relevant for obligation types that use a rate.)
The Payment Segment Type should reference the Normal Payment.
Do Not Overpay should be on. Payments are not distributed directly against the pay plan.
Special Role is Pay Plan.
Renewal may be optional, not allowed, or required depending on your business processes.
If Renewal is required, specify the Days Before Expiration for Renewal.
Eligible for Billing flag should be off, as pay plans do not get billed.
Characteristic Location Required should not be checked for pay plans.
Eligible for Pay Plan should be set to Ineligible. This option only applies to the obligation types that can be covered by a pay plan.
Pay plans do not use rates, so the Rate Required flag should be off.
Plug in any algorithms defined above for the following system events:
Break Pay Plan
Initiate Stop
Obligation Activation
Obligation Cancel
Obligation Renewal
Obligation Stop
Process Pay Plan Scheduled Payment
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]