Guidelines for Defining Automatic Receipt Methods

Define the attributes of an automatic receipt method to determine how automatic receipts are processed against selected transactions.

Review these guidelines when defining the attributes of automatic receipt methods:

• Receipts Inherit Transaction Numbers

• ISO Direct Debit

• Number of Receipts Rule

• Receipt Maturity Date Rule

• Automatic Print Template

• Lead Days

• Customer Payment Method

Receipts Inherit Transaction Numbers

If you're using One per Invoice as the Number of Receipts Rule, you can enable the Receipts inherit transaction numbers option to ensure that the automatic receipt number is always the same as the transaction number that the receipt is applied to. Enabling this option helps track automatic receipts.

Note: Don't enable this option if you're using document sequencing with automatic receipts.

ISO Direct Debit

Enable the ISO direct debit option to create automatic receipts that automatically debit a customer bank account according to the standards of ISO 20022 direct debit.

Enabling this option assumes that you have created a debit authorization agreement with your customers for ISO 20022 direct debit.

Number of Receipts Rule

The Number of Receipts Rule determines the way in which the automatic receipt process creates and applies receipts against transactions.

Note: If you enable the ISO direct debit option, the Number of Receipts Rule is disabled. ISO 20022 direct debit creates one receipt for the prearranged debit amount from your customer and transfers this amount to the remittance bank account defined in the automatic receipt method.

Select one of these rules:

• One per Customer: Create one receipt for each customer.

• One per Customer Due Date: Create one receipt for each customer and due date. This option creates several payments for a customer if the invoices of the customer have several due dates.

• One per Invoice: Create one receipt for each invoice.

• One per Site: Create one receipt for each customer site.

• One per Site Due Date: Create one receipt for each customer site and due date.

Note: The Number of Receipts Rule assumes an additional grouping by payment instrument. For example, if you use the One per Customer rule, and two invoices belonging to the same customer are to be paid from different bank accounts, the automatic receipt process creates two receipts, one for each bank account number.

Receipt Maturity Date Rule

Use the Receipt Maturity Date Rule to pay invoices that have different due dates with a single receipt.

Select Earliest to use the earliest due date of all of the invoices that the receipt covers as the receipt maturity date. Select Latest to use the latest due date of all of the invoices that the receipt covers as the receipt maturity date.

When you remit a receipt, Receivables uses the maturity date to determine when to transfer funds from the customer bank account to your remittance bank account.

Automatic Print Template

Enter the automatic print template to use for transmissions using this receipt method.

Receivables provides one standard receipt print template to format the output of payment selection and creation programs when you create the receipt document. To use a different receipt print template, you must copy and modify this standard receipt print template.

Lead Days

The number of lead days is the number of days before the invoice due date that an invoice can be selected for application by the automatic receipt process using this receipt method.

This option is useful, for example, when customer approval is required. You can set the value to the number of days normally required to receive customer approval.

Customer Payment Method

Select the funds capture payment method that the customer will use to remit payment for automatic receipts using this receipt method.

Note: If you enable the ISO direct debit option, Bank Account Transfer is the only payment method available.

Oracle Payments provides predefined funds capture payment methods, but you can define your own.