Year-end in Microsoft Dynamics GP is a task most finance teams perform only once every twelve months, and that is precisely why it causes difficulty. The steps are rarely fresh in anyone’s mind, the person who handled it last year may have changed roles, and the Fixed Assets module is far less forgiving than most other parts of the system. Close it in the wrong order, or with depreciation only partly complete, and your team may spend the first weeks of the new year correcting asset records instead of reporting results.
In this Blog, I will walk you through the Fixed Assets year-end the way we would explain it to a client in a meeting room: what has to happen first, how depreciation fits into the picture, and how to recognize the errors we see most often. At Nevas Technologies, our Dynamics GP consultants carry out this process for clients every year, so the guidance below is based on practice rather than theory.
Why the Fixed Assets Year-End Needs Special Attention
In Payables or Receivables, year-end is largely about resetting summary figures. Fixed Assets is different. The year-end close moves each asset book into a new fiscal year, clears year-to-date depreciation and sets the starting point for every calculation that follows. Until the close is complete, Dynamics GP will not let you depreciate assets into the new year. Once it is complete, reversing it usually means restoring a backup.
For this reason, we always emphasize preparation over speed. An extra hour spent checking figures before the close is far cheaper than a day spent repairing them afterwards.
There is also a wider timing point. Microsoft has confirmed that sales of new Dynamics GP licenses ended in 2026, that product updates and technical support finish on 31 December 2029, and that security patches continue until 30 April 2031. Most GP users therefore have only a handful of fiscal year-ends left on the platform. Each of those closes should be clean, because these asset records will eventually move into whatever system comes next.
The Correct Module Closing Sequence
Dynamics GP modules feed into one another, so the order in which you close them matters. The sequence we recommend for most organizations is:
- Inventory
- Receivables Management
- Payables Management
- Fixed Assets
- Analytical Accounting (if your company uses it)
- General Ledger – always last
Fixed Assets must close before the General Ledger because it posts depreciation, additions, transfers and retirements into GL accounts. If the General Ledger is closed first, any late Fixed Assets entries either land in a closed year or have to be posted as historical-year adjustments, which complicates the audit trail.
Fixed Assets also depends on Payables. If your team records capital purchases through Payables Management and passes them across to Fixed Assets, make sure every capital invoice for the year has been brought into the Fixed Assets module before you begin. A purchase left sitting in the interface will not be depreciated, and the asset register will understate the year’s additions.
Preparation: What to Complete Before You Close
Good preparation removes most of the risk. Before anyone opens the year-end window, work through the following points.
Set up the new fiscal year: The next fiscal year must exist in Fiscal Periods Setup. Fixed Assets cannot roll forward into a year the system does not know about.
Build the Fixed Assets calendar: Fixed Assets keeps its own calendar, separate from the company fiscal periods. Build the calendar for the new year in Fixed Assets Calendar Setup, and confirm that its periods and quarters match your financial year.
Complete all asset activity: Every addition, transfer, retirement and change for the current year should be entered and reviewed. Retirements are particularly important, because a retired asset that is still active will continue to depreciate.
Apply updates in a test company first: Microsoft’s year-end updates sometimes include Fixed Assets fixes. Install them in a test company, run a trial close there, and only then repeat the process in live data.
Print and save your reports: Keep the Annual Activity report and the additions, retirements and transfers reports for the year. Auditors will ask for them, and they become your reference point if anything needs investigating later.
Take a full backup: Ask all users to log out and take a complete backup of the company database. This is the step people are most tempted to skip, and it is the one that matters most if the close goes wrong.
Running Depreciation Correctly
Depreciation is where most year-end problems begin, so it deserves careful handling.
Depreciate through the last day of the fiscal year: In the Depreciate window, set the depreciation target date to the final day of the year, not the final day of the last period you happened to run. Every asset in every book should be depreciated through that date.
Treat each book separately: Most companies maintain a corporate book that posts to the General Ledger and one or more tax books that do not. Each book needs depreciation brought fully up to date before it can be closed. A common oversight is updating the corporate book and forgetting the tax book entirely.
Run GL Posting and post the batch: Once depreciation is complete, run GL Posting for the corporate book. This creates a batch in the General Ledger, which must then be posted. Until it is posted, your asset register and your balance sheet will disagree.
Reconcile Fixed Assets to the General Ledger: This is the step that separates a reliable close from a hopeful one. Compare cost and accumulated depreciation from your Fixed Assets reports with the balances in the corresponding GL accounts. When analyzing any difference, look first for manual journal entries posted directly to fixed asset accounts, unposted batches, and assets assigned to the wrong account group. Explain every variance before moving on.
Review unusual assets: Assets acquired late in the year, assets with mid-year changes to cost or useful life, and assets using unusual averaging conventions often produce unexpected figures. A quick review of these items now prevents questions from auditors later.
Performing the Year-End Close
With depreciation complete and reconciled, the close itself is straightforward. Open the Fixed Assets Year-End window under Routines, select the book or books to close, and process.
Afterwards, check Book Setup to confirm that the current fiscal year has moved forward for each book you closed. Run a sample of asset inquiries to confirm that year-to-date depreciation now shows zero and that life-to-date figures have carried forward correctly. Only after these checks should you move on to closing the General Ledger.
Common Errors and How to Recognize Them
Even well-run finance teams meet the same problems again and again. Here are the ones we see most often, with the likely cause and the remedy.
“The calendar or fiscal year has not been set up.” This message appears when the new year is missing from Fiscal Periods Setup or the Fixed Assets calendar has not been built. Create the missing year, build the calendar, and run the close again.
Assets not depreciated through year-end: Dynamics GP checks that depreciation is current before closing. If assets were added after the last depreciation run, or have acquisition dates near the year-end, the close will stop. Run depreciation again through the final day of the year for the affected book.
Fixed Assets and General Ledger out of balance: Usually caused by an unposted GL Posting batch, journal entries made directly to asset accounts, or an incorrect account group on individual assets. Reconcile before closing, not after.
Year-end run for the wrong book, or run twice: Because the close cannot simply be reversed, this normally means restoring the backup taken beforehand and repeating the process. This is why the backup step matters so much.
Batches stuck in posting or users still logged in: An interrupted posting can leave batches locked or records held. These situations can be cleared, but it should be done carefully, ideally with an experienced partner, to avoid losing or duplicating transactions.
Conflicts with customization or third-party products: Modified reports, custom scripts and add-on products from independent software vendors can behave differently after year-end updates are applied. Any customization that touches Fixed Assets should be tested in a test company before the live close.
Expired registration keys: Dynamics GP relies on registration keys tied to your license. If they lapse, modules may become unavailable at exactly the wrong moment. Confirm your keys are current well before year-end; our Dynamics GP support team can review your license position as part of year-end planning.
Summarizing the Process
Summarizing the whole procedure in a single list:
- Close Inventory, Receivables and Payables, and move all capital purchases into Fixed Assets.
- Set up the new fiscal year and build the Fixed Assets calendar.
- Enter all additions, transfers and retirements for the year.
- Print year-end reports and take a full backup.
- Depreciate every book through the last day of the fiscal year.
- Run GL Posting and post the resulting batch.
- Reconcile Fixed Assets to the General Ledger.
- Run the Fixed Assets year-end close for each book.
- Verify the results, then close the General Ledger.
Keep this list with your internal procedures so the next person to perform the close has a clear reference.
Planning Beyond This Year-End
With the Dynamics GP lifecycle now fixed, it is sensible to treat each remaining year-end as preparation for the next platform. A clean, reconciled asset register is one of the most valuable things you can carry into a migration, whether that is Dynamics 365 Business Central or another system. If you are still on an older release, an upgrade to a current version of Dynamics GP keeps you on supported software and receiving year-end updates until that move is complete.
How Nevas Technologies Can Help
For more than a decade, Nevas Technologies has helped organizations across the United States and Asia Pacific run Dynamics GP with confidence. Our team can review your fixed asset setup, perform or supervise the year-end close, resolve errors when they arise, and help you plan your long-term ERP direction.
If your Fixed Assets year-end is approaching and you would like an experienced second pair of eyes, contact our Dynamics GP team. A short conversation before the close is almost always quicker than a recovery afterwards.
Frequently Asked Questions
In what order should Dynamics GP modules be closed at year-end? Close Inventory first, then Receivables Management, Payables Management and Fixed Assets. If your organization uses Analytical Accounting, close it next. The General Ledger is always closed last, because the other modules post into it.
Can the Fixed Assets year-end close be reversed? Not through a standard window. If the close is run for the wrong book or run twice, the usual remedy is to restore the backup taken before the close and repeat the process. This is why a full backup is essential.
Do tax books need a separate year-end close? Yes. Each book, whether corporate or tax, must have depreciation brought up to the last day of the fiscal year and must be closed. Updating only the corporate book is a common oversight.
Why will Dynamics GP not let me close the Fixed Assets year? The most common causes are that depreciation has not been run through the final day of the fiscal year, the next fiscal year has not been set up in Fiscal Periods Setup, or the Fixed Assets calendar for the new year has not been built.
Should we still perform careful year-end closes if we plan to move off Dynamics GP? Yes. Microsoft support for Dynamics GP ends on 31 December 2029, so most companies will migrate in the coming years. A clean, reconciled asset register makes that migration faster and far easier to audit.
