Disbursement system options are system-wide payment options that control disbursements made by the first party payer to suppliers. Oracle Payments provides two levels of system options; enterprise-level system options and organization-level system options, by operating unit or legal entity.
The first party payer, or deploying company, that disburses payments, can set system options for payment features. Oracle Payments seeds one enterprise-level system option on the Disbursement System Options page. When you access this page, you can view the default system options for the entire enterprise. Enterprise-level system options are updateable if you have been assigned security update permission.
You can also view the system options for each organization to which you have access in your security profile. This means that you can only view and update those organizations to which you have security access. For information on security access for multiple organizations, see Define Multiple Organization Security Profile.
Upon initial implementation, the enterprise-level settings display the seeded settings for enterprise-wide options, which are used for the enterprise and all organizations within the enterprise. Once you change a value on the Update Disbursement System Options: Enterprise-wide page, the user interface displays the existing values in the database. If you have update access, you can change the system options at the enterprise-level or the organization-level. Making a change at an organization level creates a record for the organization. After that, any changes made to the enterprise-level do not update the organization-level.
Note: Only some system options, such as default payment method, can be set at the organization- level.
Note: The Disbursement System Options are treated as defaults. Source products can override these settings when a payment process request is submitted.
The purpose of setting up disbursement system options is to specify how the payment process runs at the enterprise and organization-levels.
The table below describes the default payment method system options.
Description of Default Payment Method System Options
| Default Payment Method Region | Features | Description |
|---|---|---|
| Based Only on Payment Method Defaulting Rules Setup. | Radio button | This option uses the payment method defaulting rules set up in Step 12 in Oracle Payments. |
| Override Defaulting Rules when Default Method Set for Payee. | Radio button | This option uses the default payment method set for each supplier, or payee, in iSupplier Portal. |
The table below describes selected payment processing system options.
Selected Payment Processing System Options
| Region/Field Name | Features | Description |
|---|---|---|
| Validation Failure Results Region | ||
| Document | Drop-down list | These options either direct Oracle Payments to stop payment processing for review of the applicable documents if validation failures occur or to reject some or all of the documents. |
| Payment | Drop-down list | These options either direct Oracle Payments to stop payment processing for review of the applicable payments if validation failures occur or to reject some or all of the payments. |
| Proposed Payments Region | ||
| Review Proposed Payments after Creation | Drop-down list | This field determines whether the payment process is stopped after payments are created and validated, to give the Payment Administrator the ability to review and potentially remove payments. |
| Allow Payee Bank Account Override on Proposed Payments | Check box | If the check box is selected, you can change the bank account to which you are making a payment on the Review Proposed Payments page. If Review Proposed Payments after Creation is set to No, this field is not used. If the check box is deselected, you cannot change the bank account to which you are making a payment. |
| Payment Process Request Status Report Region | ||
| Format | List of values | Oracle Payments seeds one Status report format, which you can select from the list of values. You can also create your own Status report formats. If you create your own Status report formats, they are available as options from the list of values. |
| Automatically Submit at Payment Process Request Completion | Check box | If the check box is selected, Oracle Payments automatically runs the Status report after the Build Payments program completes. If the check box is deselected, Oracle Payments does not run the Status report after the Build Payments Program completes. |
| Payment Instructions Region | ||
| Save Formatted Payment File in Database | Check box | If the check box is selected, the formatted payment file created from the payment instruction is stored in the database. |
The table below describes the default payment specifications for payee system options.
Default Payment Specifications for Payee System Options
| Field Name | Features | Description |
|---|---|---|
| Bank Charge Bearer | Drop-down list | When funds are sent by EFT, the bank that does the processing charges a fee. By selecting an option from the Bank Charge Bearer drop-down list, you can indicate the party who is responsible for paying the EFT fee. This field may not be used by all banks in all countries. |
| Pay Each Document Alone | Check box | If the check box is selected, each document payable submitted to Oracle Payments is built into its own payment. That is, documents payable are not combined with others to create payments. |