A Practical Model for Future and Current Assets Without Polluting the General Ledger

When organizations plan capital expenditures, they want accurate forward-looking depreciation in their budgets. But they do not want forecast entries contaminating financial statements.
Inside Microsoft Dynamics 365 Business Central, that tension is real. The system was built to calculate depreciation from posted acquisition cost. It was not built with a separate “forecast acquisition ledger.”
So how do we model future depreciation cleanly?
Here is a structured, defensible approach that:
• Produces monthly depreciation budget entries
• Keeps financial statements untouched
• Avoids duplicate Fixed Asset cards
• Allows clean transition from forecast to real asset
Core Assumptions
• One Fixed Asset card per physical asset
• Two depreciation books: FORECAST and COMPANY
• Monthly accounting periods exist
Phase 1 – Initial Setup
1. Create a Forecast Depreciation Book
Code: FORECAST
Description: Forecast Modeling Book
On Depreciation Book setup:
• G/L Integration = Off
• No FA Posting Setup mapped to G/L
• Uncheck “Use Same FA + G/L Posting Date”
That last setting matters.
When you later cancel forecast acquisition entries, Business Central will not force the FA posting date to match a G/L posting date. Since this book does not post to G/L anyway, tying those dates together only creates friction during reversal.
The FORECAST book now:
• Creates FA Ledger Entries only
• Never posts to G/L
• Supports clean reversals
2. Confirm the Company Depreciation Book
Code: COMPANY
• G/L Integration = On
• FA Posting Setup mapped correctly
• Follows actual accounting policy
This is the only book that impacts financial statements.
3. Fixed Asset Card Setup
On the Fixed Asset card:
• Assign both depreciation books
• Mark Budgeted Asset = Yes
• Use a dimension such as FA Status = Forecast
Do not rely solely on the Budgeted Asset toggle for reporting. Dimension tagging improves filtering clarity. Alternatively, use a dedicated FA Class Code or naming convention for forecasted assets.
On the FA → Depreciation Books line for FORECAST:
• Set Depreciation Method
• Set Depreciation Starting Date
• Set useful life according to plan
Phase 2 – Forecast Acquisition
4. Post Forecast Acquisition
Use FA Journal.
Select Depreciation Book = FORECAST.
Post acquisition cost.
Result:
• FA Ledger Entry in FORECAST
• No G/L Entry
• Forecast Book Value populated
Important:
This does not create acquisition budget entries in the G/L Budget.
If acquisition needs to appear in the budget:
Enter it separately in G/L Budget or FA Budget.
Phase 3 – Run Monthly Depreciation Projections
5. Run Projected Value Report
Filters and request page settings:
• Depreciation Book = FORECAST
• Date Filter = Full fiscal year (example 07/01/26..06/30/27)
• Number of Days = 30
• Copy to G/L Budget Name = [Budget Name]
• Filter: Fixed Asset → Budgeted Asset = Yes
These are report parameters, not setup fields.
Using a full fiscal year ensures proper distribution across reporting periods. In this example, the fiscal year begins 07/01.
Setting Number of Days = 30 normalizes monthly depreciation for planning purposes and prevents uneven day-based distribution.
Selecting a G/L Budget Name causes the report to write entries to that G/L Budget.
Result:
• Monthly G/L Budget entries for depreciation
• No G/L Entries created
• Financial statements remain untouched
Clarification:
The Projected Value report creates depreciation budget entries only.
It does not create acquisition budget entries.
Additional Purpose: Budgeting Depreciation for Real Assets
The same Projected Value report can be used for assets already in service.
Simply run the report again:
• Depreciation Book = COMPANY
• Date Filter = Future fiscal year
• This allows you to generate forward-looking depreciation budget entries for your existing asset base.
In other words:
• Depreciation Book = FORECAST, Budgeted Asset = Yes → forecasted future acquisitions
• Depreciation Book = COMPANY, Budgeted Asset = No → real assets already capitalized
One report. Two use cases. Clean segregation.
Phase 4 – Transition to Real Asset
You cannot remove Budgeted Asset while FA Ledger Entries exist.
So follow this controlled sequence.
6. Reverse Forecast Acquisition
Go to FA Ledger Entries.
Select acquisition entry.
Choose Cancel.
This writes a reversal line to FA Journal.
Post it.
Confirm:
FORECAST Book Value = 0
This is mandatory.
7. Remove Budgeted Asset Toggle
Now Business Central allows removal because no forecast value remains.
8. Clean Forecast Book Line
On Depreciation Books Fasttab for FORECAST:
• Clear Depreciation Starting Date
• Optionally clear Depreciation Method
This prevents accidental future depreciation calculations using the Forecast Depreciation Book.
Leave the FORECAST book attached for historical clarity.
Update FA Status dimension from Forecast to an active class such as TANGIBLE or INTANGIBLE.
9. Post Real Acquisition
Use FA Journal.
Select Depreciation Book = COMPANY.
Post acquisition cost.
Begin depreciation under COMPANY book.
Reporting Guidelines
Financial Statements
Always driven by COMPANY book only.
Book Value Reports
For external reporting:
Filter Depreciation Book = COMPANY
For internal forecast review:
Filter Depreciation Book = FORECAST
FA Ledger Reports
Always filter by Depreciation Book.
Why This Design Works
• One asset number
• Two controlled depreciation engines
• Forecast fully reversible
• No G/L contamination
• Clean audit trail
• Monthly depreciation budget entries
The only non-negotiable rule:
Forecast Book Value must be zero before lifecycle transition.
Forecasting inside Business Central is not about creating shadow assets. It is about disciplined use of depreciation books and controlled reporting filters.
When implemented intentionally, this model gives finance forward visibility without compromising accounting integrity.
