Ran into an odd issue today. Everyone we’ve tested with is unable to retrieve recent payments in the Activity > Payments section of Supplier Tracker/Entry. It only returns 80 results from 2018-2019, which is when we reimplemented E10, so I’m assuming those are just the earliest payments made to the respective Supplier.
No one can retrieve or filter to recent Payments though.
Nice timing. I was just told about the same issue in Customer. Activity>Payments retrieves oldest data first and does a record limit. We can use the download button to retrieve more records but why would the default not be recent records, descending?
Does anyone know how to change this via settings or do I have customize this?
80 is an interesting number, there is an issue in the BAQ designer with trying to select more than 80 fields to move to display fields that’s been around a while. Sounds like a related bug
Confirmed. I’m seeing the same thing in both supplier and supplier tracker. Oldest results first, but with no record retrieve button. I’m told by my supply chain team its because Epicor hates purchasing.
This problem has been previously reported with the number PRB0310240. It has been accepted and is already fixed in the future release 2026.1.
The recommended workaround is to select Full Screen and then go back, and it will show the complete list of payments for the supplier.
Regarding the Customer Tracker → Payments, this is working as designed on Kinetic. If you click on the download icon, you can load all payments of the customer
If this process does not show all payments, you can click on the 3-dot button on the top right corner of the table, then select options, and change the maximum record of payments to load. (You can also go on full screen to have a better look at the payments, but the button needs to be clicked to load them)
In the meantime, we will place this case as “Suggested Resolution” stage. With the new EpicCare system, once an analyst sends a suggestion or solution to the customer, the state is set to Suggested Resolution. This does not mean the case is closed. When a case is set to Suggested Resolution, the customer receives an email notification asking them if they accept or decline the solution. If accepted, the case will be closed. If declined, the case will be reset to an “In Progress” state, and we then follow up with the customer to continue troubleshooting.
The workaround mentioned by support does not work for us. Also, the explanation for the Customer Payments is odd. Why not, like suggested earlier, return the most recent records like most other grids?
“Working as intended” for someone who has never spent a day in an actual business environment. Why would we want the oldest payments first? And the longer we spend in Epicor the more times we have to download the results? I’d be mad with the response if I wasn’t expecting it.
I was just getting ready to create a post and saw this topic.
We’re having the exact same issues on Supplier Tracker → Activity → Payments
Only 80 rows are returned for us and they are the oldest 80 rows which does us no good because they are years old by this point. Also the suggested workaround in a comment above is not working for us.
I created a ticket prior to seeing this post but I’m sure they will say the same thing about being fixed in 2026.1
I forgot to mention, when I export to Excel, all rows are returned not just the 80, so between this and the Payment Tracker screen are going to have to be our workaround.
Same thing here! I had fixed it before by updating the Transaction Log range - overflow menu at the top, but now it reverted back to pulling only old records.
Yeah they gave me the same response as @bparsons but there workaround doesn’t change the number of rows from 80. So I just closed the ticket out and plan to wait for version 2026.1 to correct it since the two workaround I suggested above can get our users by.
Blockquote
The issue was reported to Development under PRB0310240/ERPS-303336, which has been accepted and provided the fix version is 12.2.100 (2026.1). in this case this issue is not elegible for a hot fix for version 2025.2 or any lower patch, since the workaround is manageable and can be used until the fixed version is released.
The workaround would be to use the ‘Full Screen’ option.
development has rejected hot fix or update request for this issue, as for now , we could only work with the full screen option and wait for the 2026.1 to be released on March
as for now this case will be marked as suggested
Changing the number of days in the “Transaction History Range” works by changing the days and saving. Note that this has to be done for each time pulling a new vendor up and even in one that has been pulled up before when it worked.
