Home › Forums › General Topics and Best Practices › Increase in EOD processing time after EOY

  • This topic is empty.
Viewing 1 reply thread
  • Author
    Posts
    • 02/27/2020 at 9:38 am #286 Reply
      Pam Kaur
      Guest

      Over the last two years, we have noticed a significant increase in EOD processing time after EOY. One of our main data libraries for our Bancorp banks (not primary bank) has grown substantially, each time after our EOY processing has occurred.

      Has any other in-house processing bank experienced this? We have had a JHA case open for over a year on this topic, with no progress made. EOD processing starts taking an additional hour or so after every EOY.

    • 03/05/2020 at 4:53 pm #293 Reply
      Pam Kaur
      Guest

      After 2+ years this issue is finally resolved for us! Some JHA case notes in case anyone comes across this in future. Our case # was 11422896.

      This is an issue for the holding company only due to applications not being ran for this bank. ACH and DDA applications are turned off so the files are never being cleared during EOD processing. This files are increasing each year due to the EOY process where the files are copied to the TN* files and then added back to production. So for example:

      EPNSFT after 12/31 processing is copied to TNEPNSFT during the EOY (TNRUN) processing. Then it is added back to the EPNSFT file during the 1/1 accrual run. This is causing the files to double each 1/1 processing.

      We will clear the below files that are currently stale data that is not used.

  • Author
    Posts
Viewing 1 reply thread
Reply To: Increase in EOD processing time after EOY
Your information:





<a href="" title="" rel="" target=""> <blockquote cite=""> <code> <pre class=""> <em> <strong> <del datetime="" cite=""> <ins datetime="" cite=""> <ul> <ol start=""> <li> <img src="" border="" alt="" height="" width="">