Station 7 of 10
The close and reporting in Dynamics 365 F&O
What you leave this station with
A written close checklist with steps and owners, the separation of revaluation from translation from consolidation, and choosing the right reporting layer.
Station six settled the cost. This station turns everything before it into financial statements.
The close here is an order rather than a button. Break it and you close a month then reopen it, and a reopened period is logged and asked about at audit.
The close order
| # | Step | Why here |
|---|---|---|
| 1 | Stop entry in the subledgers | Nothing closes while it still moves |
| 2 | Clear the exceptions: held invoices, missing settlements, unsettled payments | Each is a number missing from the statements |
| 3 | Reconcile bank, accrual and intercompany | Differences surface here |
| 4 | Revalue foreign currency | After every journal, before the close |
| 5 | Inventory close | Before the period closes, not after |
| 6 | Review the trial balance and missing dimensions | The last chance to catch a journal with no dimension |
| 7 | Close the ledger period | After the six above |
| 8 | Translation and consolidation | After the close, not before |
Step two is what actually lengthens a close. Which is why the previous three stations were written as they were: run the holds and settlements daily and you close in two days; defer them and you close in twelve.
The financial period close workspace turns this list into tasks with an owner, a due date and a status. Use it instead of a side spreadsheet: a checklist living outside the system gets neglected, and one living inside it gets followed.
Three processes that always get conflated
| Process | What it does | Does it create a journal? |
|---|---|---|
| Revaluation | Adjusts foreign currency balances to the closing rate | Yes |
| Translation | Presents ledger balances in another currency for reporting | No, in the source ledger |
| Consolidation | Combines group entities and eliminates intercompany | Yes, in the consolidation entity |
The difference between the first two is the commonest interview question in this field, and the most commonly failed.
Revaluation creates a journal because an exchange difference on an open balance is a real gain or loss. Translation is a presentation rather than an event. Conflate them and translation differences get booked as profit — a guaranteed audit note.
Intercompany sales specifically are eliminated at consolidation and not from any entity’s own ledger. Eliminate them from the source ledger and you distort the statutory accounts of a company that stands on its own.
Where this product sits against its alternatives on a multi-entity close is in the Dynamics 365 Finance & Operations guide.
Missing dimensions — the check that precedes the close
A journal with no dimension posts successfully and appears in no analytical report. It is the commonest reason a report does not agree with the ledger.
The check is simple and runs before step seven.
- Produce the trial balance grouped by dimension, then compare its total against the ungrouped balance. The difference is the value of journals carrying no dimension.
- If the difference is zero, the close proceeds. If it is not, those journals are corrected before the close rather than after — because once the period closes, correcting means a reversal plus a new entry.
Prevention beats detection: the account structure you designed at station three is what makes the dimension mandatory so the journal is never created.
Three places leak dimensionless journals, and none of them is manual entry: bulk imports, automatic journals from the subledgers, and system-generated adjustments such as exchange differences. Check manual entry alone and you are checking the least likely source.
The three reporting layers
| Layer | For whom | What it suits |
|---|---|---|
| Financial reporting on balances | Finance | Income statement, balance sheet, dimension reporting |
| Inquiries and workspaces | Operations | Transaction lists and daily indicators |
| Electronic reporting | Compliance | A document in a format an authority imposes: invoice, return, tax file |
The third layer is this product’s entire compliance engine, and e-invoicing in the next station rests on it. Understand it here and e-invoicing costs you nothing tomorrow.
Choosing the wrong layer is the commonest cause of a slow report. Build an income statement on a transaction inquiry and you aggregate millions of rows every run, while the balances are already computed.
What you actually do in this station
- Write a close checklist with the eight steps, an owner and a due time for each.
- Run it in the trial environment over a full month of the transactions you created.
- Run a foreign currency revaluation and read the journal it produces.
- Produce an income statement analysed on one dimension, and verify every journal carries it.
- Finish the official “budgeting and forecasting” path — 3 hours 3 minutes.
- Revisit the finance cycle for the general principle.
The three commonest mistakes
One: closing the period before inventory close. Cost adjustments fall into the following month.
Two: conflating revaluation and translation. Translation differences booked as profit.
Three: a close checklist in a side spreadsheet. Neglected within three months, and the close reverts to one employee’s memory.
The acceptance test for this station
- Show the close checklist in order, and explain where inventory close sits and why.
- Distinguish revaluation, translation and consolidation, and say which creates a journal.
- Explain what is eliminated at consolidation and where it is not eliminated.
- Name the three reporting layers with an example of each.
- Pick the right layer for three reports: an income statement, a held-invoice listing, and a printed tax invoice.
What comes next
The statements are out. The next station puts the product in front of the state: ZATCA and e-invoicing — a service the vendor ships itself, and where it stops in the UAE.