A month-end pack is useful when a reviewer can follow each balance back to its source, understand every difference and see who accepted the result. In Dynamics 365 Business Central, the practical task is to connect receivables, payables, bank and inventory records to the general ledger at an agreed cut-off.
This guide sets out an illustrative control pack for that task. It is a suggested operating format, not a single standard Business Central feature. Your finance owner must approve its scope, accounting inputs, review rules and exceptions before use. Report availability and behaviour must also be confirmed in your Business Central version, localisation and installed applications.
Define the close before running the reports
Give the pack a period and version, and record the company, closing date, local currency, account ranges, posting groups and any dimension or location filters. State whether each extract shows a closing balance or movement during the period. Record when it was produced and which report or query produced it.
Set a named preparer, reviewer and final finance approver. Agree the sequence for completing imports, reviewing unposted documents, approving adjustments and producing the final extracts. A report run before the final adjustment and another run afterwards do not form a consistent reconciliation, even if both use the same closing date.
Microsoft documents posting-period restrictions in General Ledger Setup, with user-specific periods that can override them. Its current guidance also explains that date-formula boundaries use the work date, which users can change. Review the actual settings and authorised exceptions; do not assume a month-end date automatically prevents later postings into that month.
Build four reconciliations with a common evidence structure
For each reconciliation, retain the source total, corresponding general ledger total, difference, supporting detail and review record. Keep the original extracts alongside the working calculation so that a reviewer can distinguish system output from changes made in a spreadsheet.
1. Receivables to the general ledger
Compare the customer balance extract at the closing date with all relevant receivables control accounts. Use a consistent currency basis and check that the report includes the intended customers and posting groups. Keep the opening balance and period movement available to explain how the closing balance was reached.
Microsoft's Reconcile Cust. and Vend. Accs. report compares net changes in the general ledger and customer or vendor ledgers for a selected period and highlights differences. It is a useful movement check; the pack should still show the opening and closing balance comparison.
Investigate differences by document and ledger entry. Possible questions include whether the extracts use different dates, a posting group is missing from the account range, or a journal was posted directly to a control account. These are investigation prompts, not conclusions about the cause. Customer ageing helps explain outstanding balances, but an overdue invoice does not itself explain a subledger-to-general-ledger difference.
2. Payables to the general ledger
Apply the same structure to vendors, including each payables control account and the finance team's agreed treatment of debit balances, credits and foreign-currency amounts. Preserve enough detail to trace a difference to the underlying entry rather than comparing only two grand totals.
Distinguish an invoice missing from the books from a recorded vendor balance that does not reconcile. Both may need attention at close, but they require different investigations. The finance owner decides whether an adjustment is required, its accounting treatment and the appropriate posting period. Do not post a balancing journal simply to remove an unexplained difference.
3. Bank statements to bank entries and the general ledger
Keep the external statement, statement date and ending balance. Reconcile statement transactions to the bank account ledger, explain outstanding items, then establish the link to the relevant general ledger account on a consistent currency basis.
Business Central's bank reconciliation guidance describes manual and automatic matching and a Test Report for reviewing the reconciliation. It also warns that direct postings to the bank's general ledger account bypass the bank ledger connection. A completed matching exercise therefore needs the general ledger comparison too.
Give each outstanding item an owner, original date and evidence of follow-up. An old unmatched payment needs investigation even when it has appeared in several previous packs. Retain the pack used for sign-off: Microsoft's guidance notes that later backdated entries can affect how outstanding transactions compare with a previously posted statement report.
4. Inventory values to the general ledger
Confirm the inventory cut-off, included locations and the finance-approved basis for actual, expected and work-in-progress amounts. Identify the cost-adjustment and cost-posting steps required by the configured process, and retain their results and exceptions.
Microsoft's inventory reconciliation guidance describes the Inventory - G/L Reconciliation page, which compares value-entry amounts with general ledger totals and supports drill-down. Where inventory costs are posted using the batch job, Microsoft says to run cost adjustment first. Review the test output and skipped entries; a job having run does not establish that every relevant value entry reached the general ledger.
Record the filters and explain any timing or scope difference. A reconciled cost balance does not establish that quantities physically exist or that the valuation policy is appropriate. Stock-count findings and accounting judgements remain separate inputs to the finance review.
Keep differences open until the evidence supports closure
Use one exception register across the pack. Each entry should show:
- a unique reference, reconciliation area and affected document or ledger entries;
- the amount, currency, original transaction date and date first identified;
- the known facts, unresolved question and evidence still needed;
- the responsible owner, next action and target review date;
- any approved correction and its posted reference; and
- the reviewer, decision date and evidence supporting closure or continued follow-up.
Age items from their original identification date rather than resetting their age each month. Let the finance owner set escalation criteria for value, age and risk. Preserve the distinction between an explained timing item, an approved correction and an unexplained difference.
An illustrative receivables exception
Suppose a fictional company has a customer closing balance of RM126,000 and a receivables general ledger balance of RM129,500. Assume both extracts have been produced using the same finance-owner-approved closing date, currency and account scope. The RM3,500 difference remains open while the preparer traces the entries.
The investigation identifies a RM3,500 direct general ledger posting with no corresponding customer entry. The pack records the document reference and evidence. It does not automatically reverse or reclassify the posting. The finance owner first approves the treatment and period; an authorised user then makes any required correction. The preparer reruns the affected extracts, and the reviewer confirms the resulting comparison before closing the exception.
This example illustrates the evidence route only. Its amounts, cause and approval sequence are fictional and must be adapted and approved by the responsible owners before operational use.
Sign off a defined version of the pack
The reviewer should be able to reproduce the totals, inspect the remaining exceptions and identify which adjustments changed the result. Record what was reviewed, by whom and when, together with the final decision to release the reporting pack, request further work or accept specified outstanding items for follow-up under the organisation's policy.
If a later posting changes an accepted balance, preserve the earlier pack, identify what changed and repeat the affected review. Keep the retained extracts, calculations, exception register and sign-off together under the organisation's approved access and retention arrangements. No universal materiality threshold or retention period is assumed here.
Discuss the reporting workflow
SCSB's Business Central Financial Reporting Automation service covers agreed report configuration, reconciliation workflows and testing with finance stakeholders. A useful starting point is one existing month-end pack, the report filters used and a list of recurring differences or manual steps.
This article is general technology and process information. Accounting policies, adjustments, financial-statement judgements and review acceptance remain with the organisation and its qualified advisers. A reconciliation workflow does not provide an audit opinion or establish MFRS or MPERS compliance. Implementation and support scope are agreed separately.
Microsoft and Dynamics 365 Business Central are trademarks of the Microsoft group of companies.