Microsoft DynamicsFree checklistPDF, Excel, Word exportMicrosoft Dynamics GP

Dynamics GP Year-End Close Checklist

Year-end in Dynamics GP is routine until a batch is left unposted or the close runs twice. This checklist orders the steps so the books tie out before you run the final close, with the irreversible items marked critical.

0%

0 of 32 items complete

12 critical items still open - these are the highest-risk gaps.

Download checklist:

Before you start

Subledgers

Inventory and purchasing

General ledger

Close and sign-off

Tick every item before running Year-End Close. Critical items should never be skipped because the close is hard to reverse without a restore. Menu paths vary by GP version, confirm the exact steps in Microsoft's year-end documentation for your release.

Planning a final GP year-end?

An optional review of your close, archive and opening balance plan.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Work from the top and treat each group as a gate. Do not move to the General Ledger group until subledgers and inventory reconcile. Tick items as you complete them, and export the result to keep a record for the audit file. Assign an owner and date to each critical item.

  • Start the checklist at least a week before the close date
  • Run it first on a restored copy of production as a rehearsal
  • Keep a dated copy with the backups

Why the order matters

The GP Year-End Close transfers profit and loss balances to retained earnings and moves the year's detail into history. If subledger batches are still unposted, they will post to the wrong year or block the close. If inventory is not reconciled, the GL balance carried forward is wrong. The backup before the close is your only clean rollback.

Handling subledgers and history

Many sites close the GL year but leave subledger periods open for late invoices. That works, provided posting dates are controlled by series. Decide before removal utilities run how much transaction history stays online, because removing history reduces table sizes but also reduces what standard reports can show.

Common mistakes

The usual errors are skipping the backup, closing the year while users are posting, running the close twice, and forgetting to set up the new fiscal year first. A related risk is relying on a single person who knows the process. Write down the steps here and review them each year.

Frequently Asked Questions

Can the GP year-end close be reversed?

Not through a standard undo for the main close. The practical rollback is restoring the pre-close backup, which is why the backup step is marked critical. Some sites use the reopen year process for corrections, but that needs care and testing.

Do I need to close subledgers first?

You must post all subledger batches that belong in the year and reconcile them to the GL. You do not always need to close the subledger periods themselves, since many organisations keep them open for a short time.

What changes in a final year before migration?

Add steps for archiving detailed history, extracting opening balances, and freezing user posting after the cutover date. Keep the final database backup for the retention period your auditors require.

How long does the close take?

The system process itself often runs minutes to a few hours depending on data volume. Most of the elapsed time is reconciliation and approvals, so start those early.

If this is your last GP year-end before a move to a new ERP, we can help plan the final close, archive and opening balance extraction together.