My Oracle Support Banner

Debit Memo is Created with different Document Date than the Invoice (Doc ID 2316868.1)

Last updated on MARCH 08, 2019

Applies to:

Oracle Retail Invoice Matching - Version 16.0.1 and later
Information in this document applies to any platform.


Debit memo is being created with different document date than the invoice.

   Terms date - 31
   Debit memo send days-1
   Debit memo send indicator - L (Only when credit note is late)
   Hold invoices - 'Y'

1. Create PO(Purchase Order) and receive it.
2. Create Invoice for the PO with Cost/quantity discrepancy, Let Invoice document date be 01-Aug-17, system calculated due date is 01-Sep-17
3. Resolve the discrepancy on 29-Aug-17 with CBC/CBQ reason code, run the rollup batch and notice credit note request is created with document date as 01-Aug-17, due date as 01-Sep-17 (Both same as the invoice).
4. On 31-Aug-17, reimposting batch voids the Credit note request and generates the debit memo with document date as 31-Aug-17, due date as 01-Oct-17
    (Both the dates are different from the invoice document date).

In the above example the debit memo is created with different document date than the invoice.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.