Direct Debit Has Invalid Authorizations After the Batch Settlement is Created
(Doc ID 1983821.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Receivables - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Receipts Related
You are using AR Direct Debit in SEPA.
SEPA payments have some conditions to meet e.g. an IBAN, a valid authorization etc.
You find the Debit Authorization in error just after the Batch settlement is created.
That is to late because the receipts are already created and you can only get rid of the error and run a successful Create Settlement batch after direct table update.
Users cannot edit debit authorization before the Batch settlement is created.
Steps to Reproduce:
Steps in Direct Debit are:
1. Create an Automatic Receipt Batch
2. Create a Remittance Batch
3. Create a Settlement Batch
In case the debit authorization is invalid you will know it in step 3, when it runs on error.
And is to late to change the Batch, after the settlement is created.
The issue has the following business impact:
Due to this issue, users cannot edit debit authorization before the Batch settlement is created.
The system does not check if:
Customer Bank BIC, Customer Bank Account IBANInternal Bank BIC, Internal Bank Account IBAN are not null.
The check could be done, before the Batch settlement is created, when transaction is created (Payment Instrument form, Payments DEV team), or when receipt is created (Automatic receipt creation process, Receivables DEV team).
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Still Have Questions?|