Scanned bank account check

Scanned bank account check compares the incoming scanned bank account number or IBAN on an invoice with the available primary bank account number or IBAN on the vendor site. If a match is found, validation is passed and the workflow continues normally without placing a hold. If the vendor site's bank account number or IBAN is different or does not exist, after import and validation, a bank account hold is placed on the invoice and a superuser is notified.

If no bank account is transferred, the invoice workflow follows the standard process.

These symbols are disregarded during bank accounts check comparison:

Scanned bank account check is disabled as default. It is enabled and setup in the Configuration Manager.

Scanned bank account check configuration

Scanned bank account check is controlled by seven configuration parameters.

Enable scanned bank account check

Enable or disable scanned bank account check functionality. Valid values are Yes or No.

XML tag storing scanned bank account

Xml tag storing scanned bank account. Valid value is free text.

Remember to transfer the XML tag from the capture part.

DFF Attribute to store scanned bank account

Select an Invoice header Descriptive flexfield attribute. If this parameter is not empty, the scanned bank account is stored in an invoice header descriptive flexfield attribute, and is imported to ERP.

Bank account hold name

This value should be taken from Oracle Payable setup. (R)Payable > (M) Setup > (M)Invoice > (M)Hold and Release Names > (F)Name. If the hold is not setup or is misspelled, PROCESSIT does not apply the hold to the invoice.

Bank account hold reason

If parameter is empty, the value is taken from hold description. Valid value is free text.

Time to wait until next bank account hold check is performed

Define a wait time value in days before checking if the hold has been released in Oracle E-Business Suite. Default value is 1. For example, 1 = 1 day; 0.04 ≈ 1 hour; 0.021 ≈ 30 min; 0.002 ≈ 3 min.

Bank account hold human task subject

Defines the Human task subject visible to the user in the Console. Default value is Bank account hold has been applied to the invoice. Captured bank account: <CAPTURED_BANK_ACCOUNT>. The code <CAPTURED_BANK_ACCOUNT> shows the value of the scanned bank account value on the invoice. Valid value is free text, inclduing the <CAPTURED_BANK_ACCOUNT> code.

Bank Account Hold

A superuser has these options for handling a Bank Account Hold. The hold is handled in the Hold task window.

  1. Keep hold - The hold is not released and remains on the invoice.
  2. Release hold - The hold is released.
  3. The workflow administrator (or any other user with the required permissions depending on hold setup in Oracle) can release the hold in Oracle payables. The workflow continues automatically after the time defined in Time to wait until next bank account hold check is performed.

Custom callout for bank account check

There is custom callout available for customized bank account checks in the Customization Workbench. The interface name is Check bank account number. This callout has two incoming parameters:

The customization callout is triggered at the end of the bank account check logic.