PR260 and PR261

Sort:
You are not authorized to post a reply.
Author
Messages
barb
Advanced Member
Posts: 33
Advanced Member

    We had to replace about 5 checks written in 2006 but replaced in 2008.  The PR297 is correct for 2006 and 2006 but the PR261 and PR260 is not, it does not  match the PR297.

    PR260 includes the manual checks in the 2008 report with the original 2006 dates. 

    PR261 includes the manual replacemnt checks in the 2008 report with the 2008 dates.

    None of the checks appear in 2006.

    Consequently, PR261 does not match our PR297.  To my way of thinking since we use the check replacement screen the system should include the checks in the PR260 and PR261 for the year the checks were origianlly created.  Do you think this is a bug?

    How do you deal with this as your totals could be off.

    Thanks for your help!

    Barbara

    Jimmy Chiu
    Veteran Member
    Posts: 641
    Veteran Member
      Description:
      We had a scenario where a payment was dated 01/04/07 and then we performed a Payment Replacement (PR86) on 01/12/07. The Payment Detail Listing (PR260) when run for Detail shows the payment with the 01/04/07 date. However; if the PR260 is run for Totals, the payment is reported with a date of 01/12/07 which is the replacement date.

      Example:

      01/04/07=Original check
      01/12/07=Replacement check

      1) Run PR260 for 'D'etail for entire year - Check reports on 01/04/07
      2) Run PR260 for 'D'etail for 01/04/07 - No check reported
      3) Run PR260 for 'D'etail for 01/12/07 - Check reports

      Why would running the PR260 in detail for the entire year report the check, but when run for one day it does not display the check even if the 01/04/07 date is held on the deduction detail?

      Resolution:
      In this scenario, the deduction detail history is retained on the original payment date of 1/04/07. The payment itself (the check) is now dated 1/12/07 causing disconnect in history. The end result is NOT the same as if you VOIDED the payment on the Bank Account Reconciliation (PR85) form with a date of 1/04/07 and re-issued a new identical payment for 1/12/07.

      When PR260 is run, it selects payments to be reported based on the payment date. In this scenario, the PR260 would use 1/12/07 to determine whether or not the payment will be included in the report based on date range parameters.

      The Detail listing will show the date of 1/04/07 because it is the date held on the deduction details. The Totals report should include the same information (without the detail) when run for the same parameter date range. The selection of what appears on the report is no different for the different report options -- and is based on the PAYMENT date, not the Detail date. The Detail date is what is printed on the report.

      Below is an example:

      The SELECTION of whether or not to include the payment on the report is based on the payment date.
      For a replaced check, that is the replacement date, not the original check date.

      In this example, the date parameters are compared to 1/12/07.
      1) Run for whole year, check is included (1/04/07 date DISPLAYS because it is on the detail.)
      2) Run for 1/04/07, check is not included. The payment date is no longer this date.
      3) Run for 1/12/07, check is included. This is the payment date.
      barb
      Advanced Member
      Posts: 33
      Advanced Member

        I am a little confused with your response.  ARe you saying that PR260 is supposed to show checks in the year issued with the original date?  That is what happened to me.

        The PR261 had the replacement date showing.

        If this is how the reports are to work, then we really can't use the PR260 or PR261 to verify wages for the year because sometimes you replace a check in a different year.

        Are there other reports to verify PR297?

        Jimmy Chiu
        Veteran Member
        Posts: 641
        Veteran Member

          If you run PR260 with 'D'etail for the year 2006, you should see it matches.

          You are not authorized to post a reply.