Updated February 6, 2026 – Because even legacy systems can run fast
One of our clients called us recently with a frustrating problem: creating check batches in Dynamics GP was taking longer and longer each month. What used to be a quick 30-second process was now stretching into several minutes. And getting worse every pay cycle.
Sound familiar? If you’re paying vendors through EFT in Dynamics GP and noticing your check batch creation slowing to a crawl, you’re probably dealing with the PM20100 remittance table issue. The good news? It’s an easy fix that takes about five minutes.
The Problem: When EFT Payments Create Digital Clutter
Here’s what’s happening behind the scenes. When you create a check batch in Dynamics GP, there’s an option called “Print Previously Applied Documents.” This setting tells the system to include remittance information about which invoices are being paid on the check stub.
For companies printing physical checks, this works perfectly. The remittance information prints on the check stub, and once printed, the system removes those records from the PM20100 table (the remittance holding table). Clean and simple.
But if you’re paying vendors through EFT (which is increasingly common and makes good business sense), you never actually print those checks. The EFT payments go out electronically, but the remittance records just sit there in the PM20100 table. Forever.
Every month, you create more EFT payments. More remittance records pile up in that table. And every time you try to create a new check batch, Dynamics GP has to wade through all those accumulated records, checking each one to see if it needs to be included.
Month one: 50 records to check through. Month six: 300 records. Month twelve: 600 records and counting. Your check batch creation keeps getting slower and slower.
The Real-World Impact
This isn’t just a minor annoyance. We’ve seen many of our clients dealing with:
- Check batch creation that takes 5-10 minutes instead of seconds
- Frustrated AP staff who can’t understand why the system keeps slowing down
- Delayed payment processing because the batch creation is so time-consuming
- Unnecessary “zero dollar” checks being created just to clear out old remittance data
One client was considering a complete system upgrade because they thought their GP installation was fundamentally broken. Turns out, they just needed to change one checkbox setting.
The Simple Solution: Two Ways to Fix It
Quick Fix: Change Your Batch Creation Setting
When you’re building your check batch in the Select Checks window, look for the “Print Previously Applied Documents” checkbox. Simply uncheck it.
That’s it. By unchecking this option, you prevent GP from creating those remittance records in PM20100 for your EFT payments. No records created means nothing to slow down your batch processing.
Better Fix: Change the Default Setting
If you want to prevent this from happening automatically, you can change the default setting in Payables Setup so “Print Previously Applied Documents” is unchecked by default. This ensures the problem doesn’t creep back in if someone forgets to uncheck the box during batch creation.
To do this:
- Go to Microsoft Dynamics GP > Tools > Setup > Purchasing > Payables
- Look for the default settings for check processing
- Set “Print Previously Applied Documents” to unchecked by default
Now every new check batch will automatically have the correct setting without anyone needing to remember to change it.
What If You Already Have Records Stuck in PM20100?
Here’s the thing: if you’ve been running with this setting enabled for months or years, you probably have hundreds or thousands of remittance records clogging up your PM20100 table. Changing the checkbox setting prevents new records from accumulating, but it doesn’t clear out the existing ones.
That’s where the performance problem persists even after you fix the setting. GP still has to check through all those old records every time you create a batch.
The solution is to clear out those stuck remittance records from the PM20100 table. This requires some careful SQL work to remove only the appropriate records without affecting your legitimate payment data.
If you’re dealing with existing performance issues from accumulated PM20100 records, contact our support team at CAL. We can safely clear out those stuck records and get your check batch processing back to normal speed.
Understanding the PM20100 Table (Without Getting Too Technical)
Think of the PM20100 table as a temporary holding area for remittance information (the details about which invoices are being paid). It’s designed to hold this information just long enough to print it on a check stub, then clear itself out.
The table was designed with the assumption that most payments would eventually result in a printed check. EFT payments broke that assumption. The system creates remittance records for EFT payments just like it does for check payments, but those EFT records never get the “print event” that would normally clear them out.
It’s like a waiting room that keeps filling up with people who never get called for their appointments. Eventually, the waiting room gets so crowded that it’s hard to move through it.
The Bigger Picture: EFT Best Practices in Dynamics GP
This remittance table issue is just one small piece of optimizing EFT payments in Dynamics GP. If you’re using EFT (and you should be, because it saves money and speeds up vendor payments), make sure you’re following best practices:
- Keep “Print Previously Applied Documents” unchecked for EFT payments
- Regularly review your Payables Setup defaults
- Monitor system performance during routine tasks like batch creation
- Work with knowledgeable support partners who understand these nuances
Look, Microsoft has extended Dynamics GP support through 2029. That means investing in optimization and best practices for your current system makes good business sense. You don’t need to replace a perfectly good ERP just because one checkbox is slowing you down.
Small Settings, Big Impact
If your Dynamics GP check batch creation is getting slower, don’t assume you need a new system or a major overhaul. Check that “Print Previously Applied Documents” setting first. You might solve your performance problem in the time it takes to read this article.
Need Help?
Whether you’re dealing with existing PM20100 performance issues or want to optimize your Dynamics GP EFT processes, our team at CAL Business Solutions has the expertise to help. We’ve been supporting Dynamics GP for decades and know these systems inside and out.
Contact us today: 860-485-0910 x4 or sales@calszone.com
By CAL Business Solutions, Connecticut Acumatica & Microsoft Dynamics 365 BC/GP Partner, www.calszone.com
