Month-End Close Checklist for Microsoft Dynamics 365 Business Central
Build a reliable Business Central month-end close with clear cut-off, reconciliations, inventory checks, review evidence and ownership.
What is the quick answer?
A dependable Business Central month-end close combines an agreed cut-off, complete operational transactions, reconciled subledgers, supported adjustments and independent review. Assign owners and evidence to every task, investigate differences and control late postings. Monthly reporting is different from fiscal year-end closing: do not run Close Income Statement simply to finish an ordinary month. Adapt this operational checklist to your accounting policies and configured environment.
What should your month-end close checklist achieve?
The purpose of the close is to produce figures that the business can explain and use. A completed checklist is useful only if it supports that result. Start by defining the reporting entities, period, management pack and decisions that depend on the numbers. Agree which balances require reconciliation and who can accept an unresolved item.
Record each task with an owner, due point, evidence location and reviewer. “Check debtors” is too vague. A stronger task identifies the ageing report, the reconciliation to the control account, the differences investigated and the person approving the result. This makes cover during absence easier and exposes dependencies before they become late surprises.
If your design is still being established, our Business Central finance implementation services provide context for the ledger, reporting and process decisions involved. Treat the checklist as a controlled operating document. Update it when a new company, integration or transaction type changes the work required, rather than copying last month’s ticks without challenge.
↑ Back to contentsHow is month-end different from closing a financial year?
Microsoft’s overview of period-end activities makes clear that Business Central does not force a monthly close. The business organises the necessary reconciliations, adjustments and reports. Posting-date restrictions are a separate control over when users can post; they should match your approved close process.
Do not confuse that work with the fiscal year-end sequence. Microsoft describes closing accounting periods and transferring income statement balances in its year and period closing guidance. Close Income Statement belongs to the year-end process, not a routine instruction for clearing monthly profit and loss accounts.
Before changing dates or running a closing process, confirm the purpose, permissions and consequences in your environment. Your finance lead should approve the accounting treatment, while your Business Central specialist explains system behaviour. Record the decision so a substitute employee does not follow an inappropriate year-end instruction during a normal monthly reporting cycle.
↑ Back to contentsWho should own the close, and when should preparation begin?
Give one finance owner responsibility for the overall sequence, while keeping individual workstreams accountable. Sales operations may need to resolve unposted invoices. Purchasing may need to confirm receipts. Warehouse staff may need to finish stock movements. Finance cannot settle those questions reliably by looking only at the general ledger.
Begin preparation before the reporting cut-off. Circulate transaction deadlines, review outstanding documents and confirm when source data will arrive from payroll, expenses or connected systems. Build the calendar around dependencies: a margin report reviewed before inventory costing is complete may need to be produced again.
For a live system, agree how your Business Central implementation and support partner will handle blocking application issues during the close. Distinguish urgent technical incidents from accounting decisions and improvement requests. A support ticket should include the affected company, period, transaction reference and business impact so the right person can investigate without unnecessary exchanges.
↑ Back to contentsWhat should you check before the transaction cut-off?
Identify documents waiting for a business decision. An open order is not automatically missing revenue or cost, and an unposted invoice is not automatically ready to post. Ask whether the underlying activity occurred, whether the document is complete and whether it belongs in the reporting period under your accounting policy.
Review receipt and shipment backlogs with operations. Agree how disputed quantities, damaged goods, returns and goods in transit will be handled. Record unresolved items with a named owner and expected treatment. This is more useful than forcing all open documents through the system to achieve a visually empty queue.
Businesses with complex movements can use our Business Central supply chain guidance to frame the operational dependencies. Test that the warehouse and finance teams use the same cut-off definition. If one team recognises dispatch when a label is printed and another uses carrier collection, the disagreement needs a process decision before the numbers can be trusted.
↑ Back to contentsHow do you complete and review sales and receivables?
Review sales invoices, credit notes, returns and cash receipts expected for the period. Match the review to the actual order-to-cash process, including connected sales channels. Investigate a missing invoice through its source transaction rather than creating a manual journal simply to make a report resemble an expectation.
Reconcile customer balances to the relevant general ledger control accounts using consistent filters and dates. Keep a record of the reports used. If there is a difference, identify whether it comes from timing, posting configuration, a direct entry or an incorrect report scope. Escalate the cause instead of carrying an unexplained balancing figure into the next month.
For retailers, settlements, refunds and payment-provider deductions may add another layer. Our Business Central retail ERP services are relevant when designing those flows. Separate the reconciliation of sales activity from the reconciliation of money received. Both need an owner, and a match in one does not establish completeness in the other.
↑ Back to contentsWhat should purchasing and payables contribute to the close?
Review purchase invoices, credits, receipts and expected supplier charges with purchasing. Ask which goods or services were received but have not yet been invoiced. Use approved accounting policies to decide the treatment, retaining evidence from the responsible business owner instead of guessing from the date a supplier sends an email.
Reconcile supplier balances to general ledger control accounts with the same discipline used for receivables. Check report dates, currency and company filters before investigating individual entries. Document any differences and the action required. A reconciliation should let the reviewer understand both the result and the remaining uncertainty.
Keep payment processing separate from invoice completeness. A bill awaiting payment can still be a valid recorded liability. A payment proposal is not evidence that every relevant purchase has been captured. Include supplier statements, disputed invoices and unusual credits where they help assess completeness, but avoid treating a supplier statement as an instruction to post unsupported transactions.
↑ Back to contentsHow should you reconcile bank and cash positions?
Collect statements and confirm that all relevant bank accounts are included, including accounts used infrequently. Review imported lines, matched transactions and outstanding items. Automated suggestions can save effort, but somebody still needs to understand unusual matches, duplicate imports, missing periods and transactions posted to an inappropriate account.
Separate genuine timing differences from errors. A payment entered near month-end may clear later, while a duplicate entry requires correction. Keep supporting references and ageing for outstanding items so the next close starts with a clear explanation. Old reconciling items deserve investigation rather than indefinite rollover.
Review cash positions alongside customer and supplier activity. A settlement received net of fees can produce several related entries, and an inter-account transfer can appear on different statement dates. Use a consistent review process, with appropriate separation between preparation and approval. Confirm who can amend bank details or release payments; completing a bank reconciliation should not silently expand that person’s authority.
↑ Back to contentsWhy do inventory costs need attention before margin reporting?
A stock quantity report and a financial valuation answer different questions. Before accepting margins or inventory balances, confirm that the relevant movements are recorded and that costing processes have completed as intended. Review exceptions with someone who understands the configured costing method and operational workflow.
Manufacturers also need to understand production consumption, output, unfinished work and the timing of related costs. A production order left in an unexpected state can affect the explanation of results. Our Business Central manufacturing services are relevant where finance and production need a shared review of those dependencies.
Do not run a batch job merely because it appeared on another company’s checklist. Establish what your setup does automatically, what requires scheduling and how failures are reported. Retain evidence of completion and investigate unusual valuation changes. Produce final margin reports after the agreed cost processes, or clearly label earlier versions as provisional so management does not compare incompatible figures.
↑ Back to contentsWhat adjustments need evidence and approval?
Prepare accruals, prepayments, depreciation and other adjustments according to the accounting policies approved for your business. Retain the calculation, source evidence, period and explanation. A reviewer should be able to understand why the entry exists without asking the preparer to reconstruct the reasoning from memory.
Check recurring journals before posting. A recurring setup can carry an outdated amount, dimension or description just as easily as a manual entry. Where reversals are required, confirm the timing and mechanism in the configured process. Review what actually posted, including any exceptions, rather than treating successful preparation as successful completion.
Use meaningful descriptions and consistent supporting references. For an estimate, record the assumption and who approved it. When later evidence differs, the business can then distinguish an updated estimate from a processing mistake. Keep the authority to approve accounting judgements clear; an application support consultant can help investigate system behaviour without becoming the owner of your financial reporting policy.
↑ Back to contentsHow should projects, construction and intercompany activity be reviewed?
Identify reporting areas that do not fit a simple invoice-to-ledger reconciliation. Projects may require a review of time, expenses, commitments and work in progress under the relevant accounting policy. Construction businesses may have additional commercial processes that need specialist design. Our Business Central construction ERP services provide a starting point for discussing those operational requirements.
For intercompany activity, compare the corresponding entities’ records and resolve mismatched amounts, currencies or timing. Assign someone to coordinate both sides. Two teams can each believe their own ledger is correct while the group reporting still contains an unexplained difference.
Document which activities are complete and which depend on information from another team. Avoid giving a group reviewer a total that combines final figures with estimates without identifying the distinction. Where consolidation takes place outside the operational company, include a handover record showing the approved reporting version and any later adjustments requiring a coordinated update.
↑ Back to contentsWhich reports should reviewers compare before signing off?
Start with the trial balance and the reconciliations supporting material balances, then review financial statements and management analysis. Use the same company, period and dimensional scope. A change in filters can make two accurate reports appear inconsistent or conceal a missing business area.
Investigate movements that do not fit the business activity. Compare results with the prior period, budget and operational measures where relevant. An unexplained margin improvement deserves attention as much as a deterioration. Ask whether the cause is commercial performance, timing, classification or incomplete processing.
Keep review comments actionable. “Looks high” does not tell the preparer what to investigate. Identify the balance, expected explanation and evidence required. Record the conclusion and any accepted limitations. The objective is an understandable set of results, not a report pack containing so many pages that nobody can identify the decisions made during review.
↑ Back to contentsHow do you control late postings and reopening requests?
Agree when ordinary users stop posting into the reporting period and who can authorise an exception. Posting-date controls should follow that policy. Verify both system-wide settings and relevant user-specific arrangements with an administrator who understands their interaction, rather than assuming one visible date field covers every posting route.
Define a late-adjustment request with the amount, reason, affected reports and required approval. If an adjustment is accepted after management reports are issued, decide whether the pack must be revised and who must be informed. Keep the approved version identifiable so different teams do not work from conflicting results.
Test connected systems as part of this control. An integration may behave differently from a person entering a document, and a failed late posting may remain queued for another attempt. Establish how those exceptions are monitored and resolved. Restricting dates without explaining the exception route can encourage staff to use inappropriate workarounds or future-dated transactions.
↑ Back to contentsWhat changes after migrating from another finance system?
Treat the first closes after migration as controlled learning cycles. Reconcile opening balances, outstanding transactions and report definitions against the approved migration records. Establish how users access historical information that remains in the old system. A new dashboard cannot replace evidence that the starting position was agreed.
The migration starting point matters. Our Sage-to-Business Central migration service, Dynamics GP migration guidance and NAV 2013 migration guide describe different routes into the platform. Use the route relevant to your business to identify data and process questions that deserve extra attention during the first reporting periods.
If the move began because a smaller package no longer supported the operating model, our Xero versus Business Central guide helps frame that change. Avoid recreating every old spreadsheet by default. Preserve the financial control objective, then decide how the new system and agreed reports can support it with fewer manual handovers.
↑ Back to contentsWhat should the team do when a scheduled process fails?
Include scheduled processing in the close calendar where it supplies a necessary input. Record the expected completion time, monitoring owner and consequence of failure. An overnight process that nobody checks can move the discovery of a problem into the busiest part of the reporting day.
Before restarting anything, establish whether work completed partially and what evidence exists. Repeating an import or posting routine without understanding its state can create another problem. Capture the relevant company, process, timestamp and error details, then use the agreed support route. Avoid sending sensitive financial records through an unapproved channel simply because a deadline is close.
Maintain a fallback decision rather than an improvised workaround. The finance owner should know whether reporting must wait, can proceed provisionally or needs an approved manual adjustment. Record what remains uncertain and what follow-up is required. Once the incident is resolved, verify the financial and operational outcome before marking the checklist task complete.
↑ Back to contentsHow should you keep close evidence usable and secure?
Create a consistent evidence structure for each reporting entity and period. Use understandable file names, report parameters and version information. Keep the approved reconciliation separate from a working draft so the reviewer can identify which document supports the reported figure.
Decide what needs to be retained under your organisation’s policy and who can access it. Financial evidence can contain personal information, bank details or commercially sensitive data. Give reviewers the information required for their role without placing unrestricted copies in a broadly shared folder. Ensure the person providing absence cover can find the authorised records.
An evidence pack should support the story of the close: what was checked, what changed, what was accepted and who approved it. It need not preserve every temporary export created during preparation. Review the structure after the first cycle and remove unnecessary duplication through an agreed retention process. Better organisation makes later enquiries easier to answer and reduces reliance on the original preparer being available.
↑ Back to contentsHow do you improve the close without weakening controls?
After sign-off, hold a short review of what delayed the work, what required correction and which evidence was difficult to obtain. Separate one-off migration issues from recurring process defects. Give the highest-impact improvement an owner and a clear outcome before adding new tools or automation.
Measure both speed and quality. Useful indicators include the date reporting becomes decision-ready, unresolved reconciling items, late adjustments and repeated corrections. A quicker close with more unexplained balances is not necessarily an improvement. Explain changes in workload and scope when comparing one period with another.
Automate stable, understood steps where appropriate, while retaining monitoring and review. For example, a scheduled report can reduce preparation effort, but only if the filters are correct and someone notices failure. Update the checklist after approved changes and train the people providing cover. A dependable close should rely on an operating method the team can repeat, rather than the memory and overtime of one experienced individual.
↑ Back to contentsWhat else do businesses ask?
Does Business Central automatically close every month?
No. Your business organises period-end activities and controls posting dates according to its approved process. Confirm the behaviour of your configuration and integrations.
Should we run Close Income Statement every month?
No. It is part of fiscal year-end processing. An ordinary monthly close centres on completeness, reconciliations, adjustments, reporting and posting controls.
How many days should our month-end close take?
There is no universal target. Establish a realistic baseline for your entities, dependencies and reporting needs, then improve speed alongside evidence quality and control.
Who wrote this guide, and how was it checked?
Written by Caleb Adoh, Growth Marketing Manager at NetMonkeys. Reviewed 2 November 2026 against Microsoft’s period-end and year-end guidance. The checklist is original operational guidance, not a substitute for your accounting policies, professional judgement or environment-specific instructions.
How can NetMonkeys help your business?
Talk to our team about your priorities and agree a practical next step.
Speak to NetMonkeys
