Station 7 of 10
The close and the reports in Dynamics 365 Business Central
What you leave this station with
Closing a period step by step, building an income statement and a balance sheet with row and column definitions, and defending every figure by tracing it back to its document.
At the previous station the numbers settled. This station gathers them and closes them.
And it holds the skill that turns you from a user into someone useful in this product specifically — which is not programming.
The two date gates — and why there are two
Posting in this product is constrained by a date window, at two levels:
| Level | What it does | Who sets it |
|---|---|---|
| Company setup | A general window applying to everybody | The finance lead |
| User setup | A narrower window for one named user | The finance lead |
The narrower one wins.
The pair is not complexity; it is what makes a close practically possible. The company shuts the month on every user and opens a wider window for the accountant alone to finish the adjusting entries — which is exactly what happens at every company in the world in the first five days of the month.
And anybody leaving the window wide open issues a report in March and finds it changed in April, without a single person having made a mistake.
What comes before the statements — four reconciliations
A statement is not read before its sources are reconciled. Four of them, done in order:
| The reconciliation | What is compared | What a difference in it means |
|---|---|---|
| The bank | The bank statement against the bank account | An uncashed cheque, or an unrecorded movement |
| Receivables | The ageing against the account balance | Unapplied movements, usually |
| Payables | Vendor statements against their balances | An unapplied invoice or credit memo |
| Inventory | The inventory report against the stock account | A cost adjustment never run, or a posting setting left off |
The last row sends you back to stations four and six at once: the expected cost setting, and the cost adjustment routine. Most inventory differences in this product are not entry errors; they are settings never enabled or a routine never run.
That is what it means for the path to be connected: no station reads alone.
Entries that come from no document
Besides the reconciliations, there is work created at this station and not before:
Currency revaluation. Foreign-currency balances are revalued at the closing rate, and the difference is an exchange gain or loss. It is a routine that is run, not an entry written by hand — and anybody writing it by hand repeats it every month and gets it wrong once.
Deferrals. An expense bought for a whole year and paid once does not belong to a single month. The product provides deferral templates hung on the document line that spread it across the periods automatically — one of the cleanest functions in it and among the least used.
The year-end close — an entry with a date of its own
Closing the year produces an entry that zeroes the result accounts and carries their net into retained earnings.
The detail worth knowing: that entry is posted on a special closing date that falls after the last day of the year and does not fall in the next one.
Its purpose is to keep the opening entries separate from the first day’s activity in the new year, so the previous year’s reports stay readable both before and after the close.
That is one of the details known by somebody who has worked and not by somebody who has watched.
The skill that makes you useful here
In other products a report that does not exist is written as a query. Here it is built as a table.
A financial report in this product is defined in two parts:
The row definition — what appears on each line: an account, or a range of accounts, or a total of earlier lines, or a formula across them.
The column definition — from which perspective each line is measured: the period balance, or the cumulative one, or the same period last year, or a percentage of another line.
Their intersection produces the report.
What that means in practice: you build a comparative income statement with three columns — the month, the year to date, and last year — and a calculated variance percentage, with no line of code.
Add a dimension as a filter — the dimension designed at station three — and the same statement becomes readable for each branch separately.
This is the fastest skill that makes you useful on a real project on this product, the one most in demand in your first week at a partner, and it is entirely functional rather than technical — meaning it is available to you whichever track you chose.
What you actually do at this station
- Close a full month after running a purchase cycle and a sales cycle through it, with the four reconciliations in order.
- Set a company date window and a narrower one for a user, and prove which won.
- Run the cost adjustment before the fourth reconciliation, and record whether the difference changed.
- Build a complete financial report with a row definition and a column definition, with a last-year comparison column and a variance percentage.
- Read the same report filtered by a dimension, and verify the dimensions sum to the total. If they do not, you have entries with no dimension — station three’s lesson returning.
- Attach a deferral template to an annual expense and verify it spread across the periods.
The three commonest errors
One: reading the statements before cost adjustment. The numbers exist and look reasonable and are not final.
Two: building the reports before the dimensions are right. A handsome report gets built carrying an “unspecified” line that swallows half the numbers — and the remedy is at station three, not here.
Three: writing the revaluation and deferral entries by hand. They work, and they get repeated every month, and they go wrong once — while the ready routine neither errs nor is forgotten.
What the quality of the close does to reading a company’s numbers is set out in the Dynamics 365 Business Central guide, and the general logic of the financial cycle — from the entry to the statement — is in the finance and close cycle.
The acceptance test for this station
- Explain the two date gates and which one wins, and why the second exists.
- Close a month with the four reconciliations, and document every difference and its cause.
- Explain the year-end entry and why it carries a special date.
- Build a financial report with rows, columns, a comparison column and a percentage, and present it filtered by a dimension.
- Explain why the dimensions sometimes do not sum to the total, and how that is prevented at source.
What comes next
The numbers are right and closed. The next station is the most honest on this path and the hardest: localisation and Arabic — containing what must be said to a client before signature, and what most of the people selling this product in our region do not say.