Defining Receivables Business Units

This chapter provides an overview of Receivables business units and discusses how to:

• Create a receivables business unit.

• Set up business unit defaults by setID.

• Define defaults for individual business units.

Note. This chapter is required. You must complete the tasks discussed in this chapter to implement Receivables.

Understanding Receivables Business Units

A business unit represents a high-level organization of business information that can be shared across a set of applications. You can use a business unit to define regional or departmental units in an organization.

To understand how Receivables uses business units, consider how General Ledger uses them. A business unit in General Ledger is a subset of your organization that keeps its own set of books or ledgers. A receivables business unit is a subset of your organization that has its own set of customer balances. Each receivables business unit has its own defined group of valid customer balances, its own way of aging and reporting on those customers, and its own item and payment processing guidelines.

The system stores each business unit’s financial transactions, such as invoices and payments, in tables that are keyed by business unit ID. This ensures that the data for one business unit remains separate from the data for other business units—even though the data exists in the same physical database table.

This section discusses:

• Types of business units.

• PeopleSoft Enterprise Tree Manager.

• TableSets.

• Default hierarchies.

• Business unit setup process flow.

See Also

Business Unit Structure

Types of Business Units

How you define a business unit depends on your industry, statutory requirements, regulatory reporting demands, and operating responsibilities. For example, a bank might treat different branches as separate business units, but a manufacturer might segregate the finances of each plant or division. Multinational organizations might separate their operations into geographic business units because of the necessities of conducting business globally. Highly diversified organizations might define each subsidiary or cost center as a business unit.

PeopleSoft Enterprise Tree Manager

You use a tool called Tree Manager to group business units together into a hierarchical structure. Tree Manager and your business unit structure provide a mechanism for defining reporting parameters.

A business unit is the smallest structural unit that can be represented in Tree Manager. This is important because certain reports use the relationships defined in Tree Manager to sort and sum amounts. These amounts can include:

• Receivables subtotals for each business unit at the lowest level.

• Further subtotals for each grouping of business units—that is, for each level of the tree.

• A grand total of an organization’s receivables.

Example

Suppose that an organization consists of 12 different companies, each represented by a business unit. You group these companies into three lines of business. Each business line is a subsidiary of the organization. In addition, you have a separate corporate business unit. All of these units—the 12 in 3 subsidiaries and the corporate business unit—roll up into the organization at the top of the hierarchy. You can report at any level of the hierarchy.

Tree Manager enables you to establish hierarchical structures called trees. Using this tool, you can group business units together and define the relationships between them.

Note. Receivables uses trees to define corporate customer structures and to summarize information for aging reports.

See Also

Enterprise PeopleTools PeopleBook: PeopleSoft Tree Manager

TableSets

When you plan your business unit structure, you need to be familiar with TableSets, which are used in all PeopleSoft Enterprise Financials products.

The accounting structure and processing rules for each PeopleSoft application are defined in a series of control tables. A TableSet is a group of rows across control tables, identified by the same setID, on which you define the accounting structure for each of your business units, aging rules, entry types and reasons, payment terms, credit and receivables personnel, and so forth. For a business unit to process transactions, it must have an associated TableSet.

You can think of business units and TableSets in the following simplified terms:

• A business unit contains all the actual data.

• A TableSet contains the rules by which the data is processed.

A setID identifies each TableSet. You can have as many setIDs as you want. However, using numerous setIDs creates complex TableSet sharing. You must create at least one setID, even if you do not use TableSet sharing.

Important! Create setIDs and business unit names that are exactly five characters long. Depending on the operating system, performance degradation can occur if setIDs and business unit names have fewer than five characters.

Default Hierarchies

A business unit is the highest level in the hierarchy and you must set default values for business units. All other entities fall beneath them in the hierarchy. Some of the attributes set at the business unit level may be set at lower levels in the hierarchy, such as the customer or item level, but are not required.

Default hierarchies exist throughout the system. Any time that a default hierarchy exists, you can:

• Leave information blank at lower levels, because defaults are inherited from the next higher level.

• Override information set at higher levels by entering different information at the lower levels.

Example

To understand default hierarchies, consider the example of payment terms. When you enter a pending item, you can specify payment terms on the Pending Item 1 page. If you do not specify payment terms there, the system checks the customer level to see if payment terms are defined for the customer. If payment terms do not appear at the customer level, the system uses the payment terms that you defined at the business unit level on the Receivables Options - Payment Options page.

Business Unit Setup Process Flow

Follow these steps to set up business units:

1. Create the receivables business unit and its associated TableSet on the Receivables Definition - Business Unit Definition page.

2. Set up a general ledger business unit.

3. Set up an accounts payable business unit if you use refund processing.

4. Set up the common application tables and core Receivables tables.

5. Define the default processing values for each business unit at the setID level and for individual business units.

   Use the Receivables Options component (BUS_UNIT_OPT_AR1) to define defaults at the setID level. All business units assigned to a setID use the defaults that you provide there. Use the Receivables Definition component (BUS_UNIT_TBL_AR) to define defaults for specific business units.

Creating a Receivables Business Unit

You must define a business unit and associate it with a setID before you set up other tables.

This section lists prerequisites and discusses how to create a business unit.

Prerequisites

Before you set up business units, you must decide on your TableSet structure and set up setIDs.

See the documentation on planning records and TableSets in the Enterprise PeopleTools PeopleBook: PeopleSoft Application Designer.

Page Used to Create a Receivables Business Unit

Creating a Business Unit

Access the Business Unit Definition page.

Defining Business Unit Defaults by SetID

To define business unit defaults, use the Receivables Options component (BUS_UNIT_OPT_AR1).

This section discusses how to:

1. Define general options.

2. Define additional general options.

3. Define payment options.

4. Define value-added tax (VAT) defaults.

5. Define Payment Predictor options.

6. Select default currency options.

7. Define defaults for customer historical trends.

Pages Used to Set Up Business Unit Defaults by SetID

Defining General Options

Access the Receivables Options - General 1 page.

Aging ID	Select an aging ID that you set up on the Aging page. The Aging Application Engine process (AR_AGING) uses this identifier for the aging rules for all business units associated with the TableSet.
Calendar ID	Select the calendar ID used to perform history calculations. You define the calendars on the Calendar Periods page.
AR Specialist (accounts receivable specialist)	Select the AR specialist who you want to be the initial owner for deduction and disputed items. The system assigns the specialist when you create a deduction on the payment worksheet and when you mark an item as disputed or as a deduction on the View/Update Item Details - Detail 1 page. You can override the default specialist for individual customers on the Bill To Options page and for the deduction or dispute reasons on the Deduction Reason page and the Dispute Reason page. Note. You must assign an AR specialist to each business unit. To assign all deductions or disputed items initially to a specific AR specialist, such as a manager, use the same specialist for each business unit and do not override the specialist for individual customers or reasons. Managers can use the Item List page to search for items assigned to them and drill down to the items to assign them to someone else. Alternatively, you can set up an assessment rule to create an action for the AR specialist when you run the Condition Monitor Application Engine process (AR_CNDMON). The manager can then assign each deduction or disputed item to individual AR specialists on the Reassign Action page.
Automatic Maintenance Method	Select the automatic maintenance method containing the rules that you want to use by default to match items when you run the Automatic Maintenance Application Engine process (AR_AUTOMNT). You can override the method for individual run controls if needed.
Year and Period	Enter dates that the Receivable Update Application Engine process (ARUPDATE) uses to determine which period to update for days sales outstanding history. These dates appear on the Receivables Update - Request page. The system calculates, summarizes, and stores all monetary transactions that fall in the date range for the defined periods.
Statement ID and Dunning ID	Select the IDs that determine the conditions and parameters that the system uses to prepare customer statements and dunning letters. The statement ID also defines the default statement type to generate. You define these IDs in the Statement (STATEMENT_TABLE) and Dunning (DUNNING_TABLES) components.
Admin ID (administrative ID), Finance ID, and Penalty ID	Select an overdue charge ID for each of these fields whose overdue charge type matches the field name. These IDs determine the conditions and parameters that the system uses to generate overdue charge invoices. The system also uses these IDs to determine when not to prepare an overdue charge invoice. You define these IDs in the Overdue Charging component (OVRDUE_CHG_TABLE2). Note. Override the identifiers for statements, dunning letters, and overdue charges for individual customer on the Correspondence Options page.
Bank	Select the bank of the business unit whose remit to address will appear on correspondence.
Bank Account	Enter the bank account number of the business unit whose remit to address will appear on correspondence.
(USF) Billing ALC (billing agency location code)	Enter the agency location code for the billing agency that is sending data. The federal IPAC interface uses the business unit agency location code when transmitting data.
(USF) Sender DO (sender disbursing office)	Enter the disbursing office symbol for the agency location that is sending the transaction using the IPAC interface. This is the five-character ID assigned by the U.S. Department of Treasury.

Note. The Billing ALC and Sender DO fields are available only if you select the AR IPAC Interface check box on the Installation Options - Receivables page.

Write-off Tolerances

You must specify the tolerances that the maintenance worksheet and Automatic Maintenance process use to write off items.

You can also define the tolerances for each customer on the Bill To Options page. The default tolerances for customers is no limit. You must define tolerances for each entry reason on the Automatic Entry Type - Selection page for the following entry types:

• Write off a credit (MT-02).

• Write off a debit (MT-03).

• Write off remaining credit (MT-06).

• Write off remaining debit (MT-07).

Because the system always uses the most restrictive tolerance requirement regardless of the level for which you define tolerances, you will probably want to use the least restrictive tolerance at the business unit level. For example, suppose that you set up the following write-off tolerances for the deduction write-off amount:

In this example, the system uses the write-off tolerance for the customer to determine the maximum write-off amount because it is the most restrictive.

Defining Additional General Options

Access the Receivables Options - General 2 page.

Bank Holiday Options

Accounting Date Option

Revenue Estimate Options

ChartField Editing

See Editing ChartField Combinations.

Item Entry Display Options

Defining Payment Options

Access the Receivables Options - Payment Options page.

Payment Method	Select the default payment method for items. Options are: Check, Credit Card, Direct Debit, Draft, Electronic Funds Transfer, or Giro - EFT. Override the value for individual customers, items or payments. Note. If you receive payments using a payment interface, such as an electronic data interchange (EDI), lockbox, or bank statement, select Check or Electronic Funds Transfer. If you receive electronic payments for acceptgiro attachments, select Giro - EFT.
Payment Predictor Method	Select the method that the Payment Predictor process uses if you do not specify a method at the customer level. The payment predictor method defines the rules that the process uses to apply payments and to make adjustments such as write-off items. See Defining Payment Predictor Methods. If you want to use Payment Predictor to apply all payments from a particular bank account, select the Payment Predictor check box on the External Accounts - Account Information page. Override this default, and select or clear Payment Predictor for individual payments, using the deposit entry pages.
Format Currency	Select the default currency that the system uses for receivables processing.
Rate Type	Select the exchange rate type that the system uses to perform currency conversion. Override the default at the customer level or when you enter pending items, enter deposits, create maintenance worksheets, or create customer-initiated drafts.
Payment Terms ID	Select the default payment terms for the business unit. Override the default at the customer level or when you enter pending items. Define payment terms on the Payment Terms page. The payment terms determine the item due date and discount information.
Partial Payment Disabled	Enter a value that determines whether you can modify the amount on the payment worksheet to create a partial payment. The default is N, which enables users to create partial payments. Enter Y if you do not want users to create partial payments.
Due Grace Days	Enter the number of days beyond the due date that a customer can pay without the payment being considered late. The Overdue Charges Application Engine process (AR_OVRDUE) uses due grace days to determine whether an item is overdue. If the item's due date is May 1, 2003 and you run the process on May 2, 2003, the process does not create an overdue charge if you enter 5 for the due grace days. However, after the grace days pass, the system calculates overdue charges from the item's due date. The Aging process uses grace days to determine in which aging category to place an item. For example, you enter 5 days and an item is 22 days old. You have aging categories for 10, 20, and 30 days. The item would be in the aging category for 10 days, because the system subtracts five days from the age.
Discount Grace Days	Enter the number of days beyond the discount date that a customer is still eligible for an earned discount. Payment worksheets, express deposits, and the Payment Predictor process use discount grace days to calculate discounts. Override the due grace days and discount grace days for a customer on the Bill To Options page and for individual items during pending item entry or item maintenance.
Item Transfer Date	Select the option that the system uses to determine the accounting date for transfer activities when you transfer items from one customer to another. Options are: Item Date: The accounting date of the original item. System: The current system date.
Deduction Due Date	Select the type of date that the system uses to determine the due date of the new item created for a referenced deduction. Select Acctng Dt (accounting date) if the due date is to be the accounting date of the payment. Select Item Dt (item date) to carry over the original item due date.
Deduction Reason	Select the default deduction reason to assign to new deductions that the Payment Predictor process or payment and draft worksheet create. Users can override the reason when they create the deduction on the payment worksheet or on the View/Update Item Details - Detail 1 page. Use a generic reason as the default reason and override it as needed. Note. You can also create unique deduction reasons for each entry reason for the Deduction entry type. If you do this, the system assigns the appropriate deduction reasons for deductions that you create on the payment or draft worksheet. See Understanding Exception Reasons and Collection Codes.
Reference Qualifier Code	Select the type of remittance information generally provided by customers, such as document, item, or bill of lading. This is the default value for identifying items to include in the payment, draft, maintenance, and transfer worksheets. You can override the value at the customer level.
(USF) Entity Code and Receivable Type	Enter the default code that identifies the government agency to which you submit the Receivables Due from the Public report and the code that categorizes the types of receivables that are included on the report. This value is the default for items. These fields are available only if you select the Receivables Due From Public check box on the Installation Options - Receivables page.
Revaluation Process Level	Select the level where the revaluation process occurs. Options are: B (business unit), C (customer ID), or I (item). You must specify a revaluation level to summarize revaluation information by a specific level according to these rules: If you summarize at the business unit level, the values for customer ID and item ID are 0. If you summarize at the customer level, the value for the item ID is 0. If you summarize at the item level, each field contains a value.

Defining VAT Defaults

Access the Receivables Options - VAT Defaults page.

VAT Default

Click to access the VAT Defaults Setup page. The VAT Defaults Setup page is a common page used to set up VAT defaulting for all PeopleSoft applications processing VAT transactions. On this page you can define Receivables VAT business unit defaults as applicable.

VAT Service Treatment Setup

Click to access the Services VAT Treatment Defaults Setup page. The Services VAT Treatment Defaults Setup page is a common page used to set up VAT services treatment defaults for all PeopleSoft applications processing VAT transactions. If you are required to implement special handling for services, you can specify Receivables VAT service treatment defaults on this page as applicable. When defining service VAT treatment defaults for a specific service, you specify the defaults applicable to that service. When defining defaults for a driver higher in the hierarchy, such as a vendor, customer, or business unit, you specify the defaults that apply to the services most often supplied by or for that driver.

Note. The VAT Defaults Setup and Services VAT Treatment Defaults Setup pages are described in detail in the PeopleSoft Enterprise Global Options and Reports 8.9 PeopleBook.

See Also

Establishing VAT Defaults

Selecting Payment Predictor Options

Access the Receivable Options - Predictor Detail Options page.

The Payment Predictor process uses the tolerances that you specify to write off or adjust an underpayment or overpayment or to adjust the discount amount when you run a payment predictor method that executes the #DTL_TLR algorithm group. The system uses these tolerances for underpayments to determine whether to write off or adjust the balance, or make a partial payment if the Partial Payment Switch check box on the Bill To Options page for the customer is selected. If you clear the Partial Payment Switch check box, it only uses the tolerances to determine whether to write off or adjust the balance. The tolerances apply to individual items not to all invoices paid by the payment.

Assigning Default Entry Types and Reasons

Enter the entry type and entry reason codes that you want to use to override the defaults for the system function. The following table provides a list of conditions that are in the Exception Type field and the default system function that the Payment Predictor process uses for the condition. It also provides other system functions that you can use for the exception type and the entry type and reason to enter if you want the Payment Predictor process to use that system function.

Select Generate Worksheet on this page and in payment predictor methods where you use the #DTL_TLR algorithm group to generate a worksheet when the condition occurs. This enables you to review the payment application before you post it.

Note. If you use the #DTL_TLR algorithm group in a payment predictor method, the Payment Predictor process uses default entry types and reasons (for each system function) for underpayment, overpayment, and discount conditions. However, you can override the defaults by business unit based on their setID. You must assign these entry types and reasons to the system function on the Automatic Entry Type - Selection page.

See Also

Using #DETAIL and #DTL_TLR for Partial Payments and Deductions

Setting Up Automatic Entry Types

Selecting Default Currency Options

Access the Receivables Options - Currency Display Options page.

AR Display Currency

AR Display Currency in Worksheet Pages

The values that you enter here determine the default values that display on the Currency Conversion page for maintenance, payment, and transfer worksheets. You can override the values at the worksheet level if needed. The values are used to convert the item amounts to a different currency and they display in the Conversion Amount - Currency field if you use the Currency Conversion page to convert them.

Defining Defaults for Customer Historical Trends

Access the Receivables Options - Customer Trend Options page.

Enter the history ID that you want to use to calculate the historical data for each of the trend pages along with the heading label that you want to display for the data on the trend pages. You use the trend pages to compare historical data for different history IDs. Enter either system-defined or user-defined history IDs.

The Customer Trend 1 and Customer Trend 2 pages can display up to three historical statistics for history IDs that track amounts, such as High Balance Amount and the Customer Trend 3 page can display up to six historical statistics for history IDs that track the number of days, such as average days late.

Defining Business Unit Defaults for Individual Business Units

To define business unit defaults, use the Receivables Definition component.

This section discusses how to:

• Establish the general ledger business unit defaults.

• Define multicurrency processing options and distribution codes.

• Define additional accounting options.

• Select bank and payment interface options.

• (USF) Define debt management information.

Pages Used to Define Defaults for Individual Business Units

Establishing General Ledger Business Unit Defaults

Access the Receivables Definition - Business Unit Definition page.

Location Code	Designate the address of the business unit by selecting a location from the locations that are defined on the Location Definition page.
GL Unit (General Ledger business unit)	Select the general ledger business unit to associate with the receivables business unit.
Base Curr (base currency)	Displays the base currency of the general ledger business unit that you associated with the receivables business unit.
ID Numbers	Click to assign the business unit to a reporting entity such as a country registration number. Select from a list of values available for various reporting entities.
Default InterUnit Doc Type (default interunit document type)	Select the document type to use for document sequence numbers for interunit accounting entries when you unpost a group. This field is available only if you enabled document sequencing on the Installation Options - Overall page and for the general ledger business unit associated with the receivables business unit.
Deposit ID	Enter the last number used for deposits.
Group ID	Enter the last number used for item and payment groups—items, payments, transfers, maintenance, drafts, and unpost. The number that you enter is one less than the ID that the system assigns to the first deposit or group. During processing, the system displays the ID NEXT until you click Save. Override the automatic numbering by entering your own ID in place of NEXT.
Receipt Number	Enter the last number used for cash receipts that you enter for orders in Order Management. The number is one less than the next number that the system assigns to the next cash receipt when you record a payment for a counter sale in Order Management.

See Also

General Ledger Distribution

Defining Multicurrency Processing Options and Distribution Codes

Access the Receivables Definition - Accounting Options 1 page.

Update Open Periods	Click to access the Open Period Update page, where you update the opening and closing period for a business unit. You can use same period dates for all transactions or use different dates for specific types of transactions. You link the transaction type to group types on the Group Type page. The normal default opening and closing period dates for each Receivables business unit are the same as the General Ledger business unit with which it is associated. Use this option when you want an accounting period in Receivables to close at a different time than an accounting period in General Ledger. The system automatically issues a warning message if the closing date for an application business unit and transaction type is later than the closing date for the General Ledger business unit. Note. You receive a warning message if unapplied payments or unposted pending items exist and the accounting date falls in a closed period. See Defining and Updating Open Periods and Adjustment Periods.
AR Distribution Code (accounts receivable distribution code)	Enter the default accounts receivable distribution code for the business unit. This code determines the ChartFields that the system uses when generating system-defined accounting entries for pending items. For billing groups, override the default distribution code on the Pending Item 1 page, on the Item Entry Type - Selection page, or on the customer General Information - Bill To Options 1 page. For payment, draft, maintenance, and overdue charge groups, override the business unit default on the Automatic Entry Type - Selection page or on the customer General Information - Bill To Options 1 page.
Directly Journalled Template	Select the journal generator template that the Journal Generator Application Engine process (FS_JGEN) uses to create journal entries for directly journalled payments. Define the template on the Journal Generator - Defaults page.
Doubtful Distribution Code	Select a distribution code for items for which you do not expect to receive payments and to transfer those items to the Doubtful Receivable account.
Realized Gain Code	Enter a distribution code that maintenance and payment worksheets use to create adjusting entries for multicurrency processing. Each business unit can have only one realized gain code.
Realized Loss Code	Enter a distribution code that maintenance and payment worksheets use to create adjusting entries for multicurrency processing. Each business unit can have only one realized loss code.
Unrealized Gain Code	Enter a distribution code that the Revaluation Application Engine process (AR_REVAL) uses to create revaluation entries for unrealized gain.
Unrealized Loss Code	Enter a distribution code that the Revaluation process uses to create revaluation entries for unrealized loss.
Translate Distribution Code	Enter a distribution code that the Revaluation process uses to create accounting entries for adjustments to translation ledgers.
Translate Realized Gain Code and Translate Realized Loss Code	Enter distribution codes that the system uses to create accounting entries for multibook translation ledgers if there is a translation adjustment.
Default Revaluation Doc Type (default revaluation document type)	Enter the default revaluation document type for document sequencing.
Rounding Account Code	Enter the distribution code that the Receivable Update process uses when you: Apply a payment to an item with a currency different from the currency of the item. Apply a payment to an item with the same currency, but the payment and item currency differ from the base currency of the business unit. The process posts any leftover amount from the currency conversion to the ChartFields that are assigned to the distribution code. Note. The process does this only if there is not realized gain or loss on the transaction.
Journal Template	Select the journal generator template that the Journal Generator process uses to create journal entries for the accounting entries that the revaluation process produces.

Defining Additional Accounting Options

Access the Receivable Definition - Accounting Options 2 page.

Cash Control Method	Select a timing method, if you use cash control accounting, which records a debit to cash and a credit to cash control before the receipts are applied to accounts receivable. The methods differ only in the timing of the creation of the initial accounting entry that debits cash. All other aspects of cash control accounting are treated the same way under the methods. Options are: Bank Reconciliation: This method is used primarily in European countries. It requires the creation of the cash control entry when the payment is reconciled on a bank statement. Payment Entry: The preferred method in the U.S. It creates the cash control entry when the payment is received. None: The system always debits the Cash account and credits the Receivables account when you apply the payment. The system does not create cash control entries.
Auto-Remit Direct Debits	Select to have the Create Direct Debits Application Engine process (AR_DIRDEBIT) automatically change the status to Remitted for direct debits without exceptions in the run. If any of the direct debits that the process creates contain exceptions, their status is Pending Approval on the direct debit worksheet. Override this selection for each run request on the Request Parameters page.
Draft AR Distribution Code (draft accounts receivable distribution code)	Select the distribution code that the system uses to move the draft item from the original Receivables account to the Draft Receivables account. See Understanding Draft Setup.
Remitted Draft Receivable Code	Enter the distribution code that the system uses to identify the Receivables account when you remit a draft.
Draft Discount Receivable Code	Enter the distribution code that the system uses to identify the Receivables account for a discounted draft.
Draft Discount Liability Code	Enter the distribution code that the system uses to identify the Liability account when you discount a draft with or without recourse.
Dishonored Draft Code	Enter the distribution code that the system uses to identify the Dishonored Receivables account when you dishonor a draft.
Refund Distribution Code	Enter the distribution code that the system uses to create accounting entries for refunds. Note. If you have Payables installed, you must complete the Refund Distribution Code, AP Unit, and AP Origin ID fields before you can process refunds. If Payables is not installed, these fields are optional.
Control Distribution Code	Select the default distribution code for the offset entry for transactions in maintenance and transfer groups. You can override the value on maintenance or transfer worksheets. Enter separate codes for maintenance and transfer worksheets. Important! You cannot build the worksheets if you do not assign a default value to the business unit.
AP Unit (accounts payable unit)	Select the Payables business unit for which you want to create vouchers for credit items that you refund from the Receivables business unit. For payables refund processing, the receivables business unit and associated payables business unit must share the same General Ledger business unit.
AP Origin ID (accounts payable origin ID)	Enter the source of the voucher. Note. Before you can enter values in the AP Unit and AP Origin ID fields, you must select a General Ledger business unit on the Business Unit Definition page and click Save.

See Also

Setting Up Distribution Codes

Understanding the Create Direct Debits Application Engine Process

Defining Journal Generator Template Defaults

Selecting Bank and Payment Interface Options

Access the Receivables Definition - Bank/Payment Options page.

The Bank Holiday Options are the same as the ones on the Receivables Options - General 2 page. If you enter values for a specific business unit they override the values for the setID.

Bank Fees Entry Type

Payment Interface Options

Miscellaneous Payment Options

See Also

Defining Entry Types

(USF) Defining Debt Management Information

Access the DMS Definition page.

Agency ID	Enter the agency identifier code assigned by the DMS for the organization.
File Sequence Number	Enter the original sequence number for the files that you submit to the DMS. The system increments the number after each successful process.
Number of days and Basis Date	Enter the number of days past the date in the Basis Date field that the system uses to determine whether to automatically send the outstanding debt to the DMS. The default is 180 days. Values for the basis date are Accounting Date, As of Date, Due Date, or Item Date.
Primary private collection agency, Secondary private collection agency, and Judgement taken on debt	Enter a collection code that you defined on the Collection Code page to identify the collection agencies to which you submit collections for this business unit. If you enter values in these fields, the system sends a supplemental record to the DMS that includes the date and the amount of the debt that was sent to the collection agency.
Transaction Type, Entry Type, and Entry Reason	Select each transaction type that you receive in inbound files from the DMS and associate it with the entry type and entry reason that you want used to create items for the transactions in the Pending Item table (PS_PENDING_ITEM). Options are: Adjustment Transaction-Down: Negative adjustment transaction for amounts less than 0. Adjustment Transaction-Up: Positive adjustment transaction that is greater than 0. Offset: An offset that is treated as a payment in Receivables. Payment: Partial payment that is applied to the net balance.
Collection Code	Select the code for the collection agency that you assign to items that you do not send to the DMS.