This is an older post but I just ran into the same situation with one of our clients. It's not really a Financials Suite issue but I wanted to reply to the post. Tech Support's answer was to re-enter the credit note which is "fine" but not if you use the OECRDH & OECRDD tables for reporting. Wanted to let others know what I did to include the transaction in Day End. When an OE credit note is entered, a sequential day end number is assigned to OECRDH.DAYENDNUM, the OECRDH.CRDSTATUS is set to 1 (document shipped and not costed) and the OECRDH.COMPDATE is 0. This particular day end number has nothing to do with the official Day End number that is also the "Next Day End Number" in the OE and IC Options screens. As far as I could tell, the day end numbers increment between OECRDH and OESHIH transactions. I ordered the .DAYENDNUM fields in both tables and identified the last assigned number. Then I incremented the number and entered it in the OECRDH.DAYENDNUM field for the record of the "stuck" credit note. After I ran Day End Processing, the credit note was in the OEAUDH & OEAUDD tables as well as the usual AR and GL places. I don't recommend editing SQL tables but in this case it seemed pretty safe - and always test in testing data first. I also want to note that my client has 40,000 transactions and only one had this problem.

Just adding my experience. Shauna's answer worked for me. I ran day-end, looked that the last values in OECRDH and OESHIH and then incremented my wayward credit note DAYENDNUM values to one higher than the largest DAYENDNUM value. I had two missing credit notes so I updated the second credit note DAYENDNUM by one higher again. Ran day-end and both credit notes appeared in AR.