Configuring a Virtual Thirteenth Month Using a Closing Period
Short answer
D Create a closing period to accommodate the virtual thirteenth month for year-end transactions in the fiscal calendar.
Question
What should you do?
Key Takeaways
The question tests knowledge of fiscal calendar configuration, specifically using a closing period to handle year-end adjustments separately from standard operating months.
Learn how to configure a virtual thirteenth month in Dynamics 365 Finance by creating a closing period for year-end adjustments, ensuring accurate monthly reporting.
Common mistake: Many candidates might choose to add an additional period (C) or divide the twelfth period (B). Adding a standard period doesn't handle the closing logic correctly, and dividing the twelfth month distorts its financial data.
Expert Analysis
Virtual Fiscal Year
The scenario requires accommodating a "virtual thirteenth month" for year-end transactions. In Microsoft Dynamics 365 Finance, the standard fiscal structure consists of twelve periods per year. When business processes require additional time for closing entries or adjustments that do not belong to any specific operating month, a closing period is used.
Create a Closing Period
Option D is correct because creating a closing period allows you to designate a specific period at the end of the fiscal year for these adjustments. This period is typically excluded from standard monthly reporting and is used solely for finalizing the year's financials without skewing the results of the regular twelve months. This aligns with the requirement for a "virtual thirteenth month."
Why Other Options Are Incorrect
- Option A (Add an additional fiscal year) is incorrect because this would create a new calendar year, not an extra period within the current one.
- Option B (Divide the twelfth period) is incorrect because splitting the last month would distort the financial data for that month, making it difficult to report accurate monthly performance.
- Option C (Add an additional period to ledger calendars) might seem plausible, but simply adding a thirteenth period without designating it as a "closing" type can lead to confusion in reporting and budgeting. The specific term and functionality required here is a "closing period," which handles the logic for year-end adjustments differently than a standard operating period.
- Option E (Create a new fiscal calendar) is unnecessary if the goal is to extend the existing year's closing process rather than starting a completely new fiscal framework.
Operational Consequence
Failing to use a closing period may result in year-end adjustments being posted directly into the last operating month (Period 12), which inflates that month's expenses or revenues and makes month-over-month analysis inaccurate. By using a closing period, you ensure clean separation between operational activity and administrative closing tasks.
Exam Strategy
When encountering questions about 'extra' time or 'virtual' months in fiscal calendars, always look for 'closing period' as the solution. This feature is specifically designed for year-end adjustments without affecting operating months. Avoid options that suggest altering the number of years or splitting existing months, as these disrupt standard reporting cycles.
Frequently Asked Questions
What is the purpose of a closing period in Dynamics 365 Finance?
Can I use a standard period instead of a closing period for year-end transactions?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
Peachtree2022 👍 7Should be D
-
RPC112 👍 2 Answered DAnswer= D Standard practice for supporting year-end adjustments (the "virtual 13th month") is to create a closing period. This closing period is: A designated period at the end of the fiscal year. Used only for year-end adjustments. Excluded from standard monthly reporting. Ensures that normal period 12 results aren't skewed by closing entries.
-
Mukhtartij 👍 1 Answered DThe case study requirement states: "A virtual thirteenth month is required for year-end transactions." In Dynamics 365 Finance, this "13th month" is implemented as a closing period within the fiscal calendar. According to Microsoft documentation, a closing period is used to separate general ledger transactions generated when a fiscal year is closed. If a fiscal year is divided into 12 fiscal periods, the closing period is usually the 13th period . This allows year-end adjustment entries to be posted separately from normal operating transactions, making it easier to create financial statements that either include or exclude different types of closing entries .
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All MB-310 Questions
Access 100 questions with complete answers and detailed explanations.
View Full MB-310 Practice Test →