What's a payment validation?

Payment validations are rules that ensure disbursements are correct before they are printed or transmitted to your bank or financial institution. Validations help find problems early in the payment process and decrease costs by preventing invalid data from reaching your bank.

During implementation, validations can be attached to payment methods, payment file formats, or both. Validations are handled differently at transaction time based on the object to which they are attached.

If the validation is attached to a payment method, it can be:

  • Executed early in the process. Problems can be identified as early as invoice entry in Oracle Fusion Payables.

  • Applied to a document payable, invoice installment, or a payment

Note: If the validation is attached to a payment method, it can't be applied to a payment file, because one payment file may span multiple payment methods.

If the validation is attached to a format, it can be:

  • Optionally executed only on transactions in a specific country

  • Optionally executed only on a specific combination of payment method and format

  • Executed on a document payable (although the validation won't happen during invoice entry), payment, or payment file

The following table describes characteristics of predefined and user-defined validations.

Predefined Validations

User-Defined Validations

Predefined for you

  • You define.

  • You configure.

Complex groupings of validations can be assigned to payment methods or formats

  • You can specify one attribute at a time during implementation.

  • You can make them completely granular.