Last Update: May 2026
Every month, someone on your finance team opens Microsoft Dynamics GP and manually re-enters the same journal entries. Rent. Depreciation. Prepaid amortization. Insurance allocations. The accounts don’t change and the amounts rarely change, but the entries get keyed in from scratch anyway, checked, and posted, month after month.
That’s the kind of work that should be running itself. GP recurring batches exist specifically for this reason. You set them up once, post them each month, and the system resets and queues the next one automatically. Your team stops re-entering the same monthly data and starts reviewing it instead, which is a much better use of their time during close.
Here’s how to set it up correctly and what to watch for.
What Are Recurring Batches in Microsoft Dynamics GP?
A recurring batch in Dynamics GP is a General Ledger batch that, once posted, doesn’t disappear. Instead, the system resets it for the next posting period based on a frequency you define. The transactions inside stay intact. The posting date rolls forward. Your team posts it again when the time comes.
This is different from a standard single-use batch, which clears entirely after posting. With a recurring batch, you’re building a template that the system reuses on whatever schedule fits the entry: monthly, bimonthly, quarterly, weekly, or even daily if needed.
The most common use case is monthly journal entries that repeat with little or no variation. Straight-line depreciation entries, fixed lease payments, deferred revenue amortization, and intercompany allocations are all strong candidates.
How Do You Set Up a Recurring Batch in Dynamics GP?
The setup lives in the General Ledger module. Navigate to Financial >> Transactions >> Batches to open the Batch Entry window.
Create a new batch and give it a name that makes its purpose obvious. Something like “RECUR-RENT-MONTHLY” or “RECUR-DEPRECIATION” works better than a generic label when your team is scanning a batch list during close. Ambiguous batch names cause confusion, especially when multiple recurring batches are running simultaneously.
In the Frequency field, select the interval that matches how often this batch should post. For standard monthly entries, select Monthly. Once you make that selection, the Posting Date field and the Days to Increment field become relevant. The posting date you enter becomes the date for the current period’s entries. After posting, Dynamics GP advances that date by the increment you set.
Mark the “Use last day of the month” checkbox if your entries need to land on the last day of each month. Without it, Dynamics GP defaults to incrementing by day count, which creates problems in months of different lengths. A batch set to post on January 31 would otherwise default to February 30, which doesn’t exist. With the checkbox marked, the system handles that automatically and posts to the correct last day every time.
Once the batch header is configured, save it and open the batch to add your journal entry lines. Navigate to Financial >> Transactions >> General and assign those transactions to your recurring batch ID. Enter your accounts, debits, and credits exactly as they should appear each period. If amounts vary month to month, you’ll update the lines before posting. If they’re fixed, you won’t need to touch them at all.
What Frequency Options are Available for GP Recurring Batches?
Dynamics GP gives you several frequency options beyond monthly. The full list includes Daily, Weekly, Bi-weekly, Semi-monthly, Monthly, Bi-monthly, Quarterly, Semi-annually, and Annually.
Most finance teams working with recurring journal entries stick to Monthly or Quarterly. The bi-monthly option is useful for entries that need to post every other month, though it’s less common. Quarterly works well for entries tied to quarterly accruals or tax provisions.
One thing to be aware of: the frequency setting controls when the batch is ready to post again, not when it posts automatically. Dynamics GP does not auto-post recurring batches without additional configuration. Your team still needs to open the batch and post it manually each period. The automation is in the reset, not the posting trigger. That distinction matters for how you build your monthly close checklist.
How Do You Post and Reset a Recurring Batch in Dynamics GP?
Posting a recurring batch works the same way as posting any other GL batch. Go to Financial >> Transactions >> Batches, select your recurring batch from the list, review the transactions, and post.
After posting, Dynamics GP resets the batch automatically. The same transaction lines remain, the batch status returns to Available, and the posting date advances to the next period based on your frequency setting. The batch is ready for next month without any manual rebuild.
Before posting each month, check two things. First, confirm the posting date is correct for the current period. If a batch was delayed or skipped, the date may need a manual adjustment. Second, if any transaction amounts change period to period, update the lines before posting. A batch with a stale amount, posts incorrectly and creates a correction entry, which is exactly the kind of noise you’re trying to avoid during close.
If you need to review who posted a recurring batch after the fact, that information is available through the Journal Entry Inquiry. We wrote a great blog on how to track that down – check it out: Tracking Journal Entries in Dynamics GP.
What Mistakes do Dynamics GP Teams Make with Recurring Batches?
We see a few patterns consistently when recurring batches cause problems.
- The first is forgetting to update amounts before posting. A monthly accrual that should be $12,500 posts at last quarter’s $10,000 because no one updated the line. Always review variable-amount entries before posting, even when the routine feels automatic.
- The second is poor batch naming. If three accountants are each managing recurring batches and none of the names indicate frequency or purpose, the batch list becomes a guessing game during close. Establish a naming convention and stick to it.
- The third is skipped batches. If a recurring batch isn’t posted in a given month, the posting date doesn’t advance. The next time someone opens it, the date is still in the prior period. That entry either gets posted with the wrong date or gets adjusted manually, neither of which is a clean outcome. Build a close checklist that includes every recurring batch and who owns it.
How Do Recurring Batches Fit into Your Monthly Close Process?
Recurring batches work best when they’re part of a documented close sequence. Your team should know which batches need to post, in what order, and by what date. Entries that feed downstream reports or that other modules depend on need to post before those reports run.
If your team is also handling entries that come from outside Dynamics GP, for example from a spreadsheet, the copy-paste GL transaction method is a useful complement to recurring batches for one-time or variable entries that don’t fit a recurring template.
Between recurring batches handling fixed monthly entries and a clean process for variable entries, most finance teams can shave meaningful time off their close without changing systems at all.
If you’re running Microsoft Dynamics GP and want help getting your recurring batch setup right, or tightening up your close process overall, we can help. Contact CAL Business Solutions to talk through what your team needs.
CAL Business Solutions is a Microsoft Dynamics GP implementation and support partner serving manufacturers, distributors, and professional services businesses across the northeastern United States. Our team helps Dynamics GP users get more out of the system they already have.
