Obligation Type - Main Information

Open Admin > Obligation Type to define core information about your obligation types.

Description of Page

Enter a unique combination of Division and Obligation Type for every obligation type.

Enter a Description for the obligation type.

Tax Type defines the tax type for the obligation type.

Fastpath: For more information about tax types, refer to Setting Up Tax Types.

Use an Obligation Business Object to define a BO that may govern additional rules related to obligations of this type.

Indicate if the Revenue Period Applicability for obligations of this type is Required or Not Allowed.

Select the Distribution Code and GL division that defines the receivable account for receivable-oriented obligations. For non-receivable oriented obligations, this distribution code depends on the obligation type's function. Refer to Designing Obligation Types for some examples.

Select the Revenue Class associated with the obligation type (and its obligations). The revenue class may affect the revenue account(s) generated by the obligation's rate.

Note: The revenue class field is only visible if your implementation has turned off the C1TB — Billing module. This information is used only for classic billing and rates functionality.
Fastpath: Refer to Rate Component - GL Distribution for more information about revenue class.

Set the Eligible for Pay Plan flag to Eligible if you want obligations of this type to be eligible to be covered by a pay plan.

Select the Payment Segment Type that defines how payment segments linked to obligations of this type affect the obligation's payoff and current balances and how the general ledger details for the payment are built.

Fastpath: For more information about payment segment types, refer to Setting Up Payment Segment Types.

When a tender is canceled, a cancellation reason must be supplied. If the cancellation reason indicates a NSF (non sufficient funds) charge should be levied, the system invokes the Levy an NSF Charge algorithm specified on the tender's account's account type. Because adjustments must be linked to an obligation, the algorithm must determine the appropriate obligation to use to levy the adjustment based on business rules. The charge is levied using the NSF Adjustment Type of the appropriate obligation's obligation type.

CAUTION:
You must specify adjustment type profiles on the obligation type (on the Adjustment Type window) to ensure that the adjustment type defined here is valid.
Fastpath: For more information about adjustment types, refer to Setting Up Adjustment Types.

Define the Payment Grace Days and Override Filing Grace Days applicable for obligations of this type. Refer to Due Dates for Filing Period Based Obligations for more information about due dates.

Select the Payment Priority. This field is available for use by the algorithms that distribute partial payments amongst an account's obligations. Higher priority obligations will have their debt relieved before lower priorities. Refer to Distribution Based on Payment Priority and Delinquent Payment Distribution Algorithm for information about payment distribution algorithms that use this field.

Note: The values for this field are customizable using the Lookup table. This field name is PAY_​PRIORITY_​FLG.
Fastpath: For more information about distribution priority, refer to Distributing A Payment Amongst An Account's obligations.

Select the Delinquent Payment Priority. This field is available for use by the algorithms that distribute partial payments amongst an account's obligations. Higher priority obligations will have their debt relieved before lower priorities. Refer to Delinquent Payment Distribution Algorithm for information about a payment distribution algorithm that uses this field.

Note:

The values for this field are customizable using the Lookup table. This field name is DEL_​PRIORITY_​FLG.

Define the default Debt Category to assign to bill segment type financial transactions for obligations of this type. Refer to Debt Categories and their Priorities for more information.

Note: Required for base algorithms. The base P&I calculation algorithm and the base Determine Detailed Balance algorithm require that every debit financial transaction reference a debt category. This field applies to both standard and classic bill segment financial transactions.

Define the default Debt Category Priority for credit financial transactions linked to obligations of this type. Refer to Debt Categories and their Priorities for more information.

Turn on Do Not Overpay if the system is not allowed to distribute an overpayment to this type of obligation (i.e., the obligation is not allowed to have a system-created credit balance). This field is available for use by algorithms that distribute overpayments. Refer to Overpayments Held On Highest Priority Obligation for information about an overpayment algorithm that uses this field.

Where Used

Follow this link to open the data dictionary where you can view the tables that reference CI_​SA_​TYPE.