How to Build a Month-End Close Checklist Around Your Finance ERP

Quick answer

Build your month-end close checklist around dependencies and evidence—not just dates. Give every task an owner, reviewer, deadline, prerequisite, and completion requirement. Complete transaction processing, reconcile balances, post approved adjustments, review the financial statements, and then restrict further posting. Treat an ERP task marked “complete” as a workflow status, not proof that the underlying accounting work is correct. Oracle explicitly warns that NetSuite Quick Close marks tasks complete without running them. (docs.oracle.com)

The checklist below is a suggested operating model for controllers, accounting managers, and ERP administrators. Product examples come from official Microsoft Dynamics 365 Finance and Oracle NetSuite documentation; they are not features you should assume every ERP includes.

1. Define what “complete” means for each close task

Start with a recurring task register. For each task, record:

• Scope: legal entity, accounting period, ledger or book, and relevant currency.
• Owner and backup: the people responsible for execution.
• Reviewer: the person who accepts the result.
• Deadline: working day, time, and time zone.
• Dependencies: work that must finish first.
• Evidence: reports, journal references, reconciliations, or approvals.
• Exception rule: what blocks completion and who decides the next action.

Use separate preparation and review tasks when your control design requires independent review. Avoid an ambiguous task such as “Finish cash.” Prefer “Prepare operating-account reconciliation” followed by “Review operating-account reconciliation.”

An ERP close workspace can help organize this structure. Dynamics 365 Finance supports assigned tasks, relative deadlines, dependencies, attachments, and historical completion information. Its dependencies prevent a task from being marked complete before its prerequisites are complete. These capabilities support coordination; they do not replace your evidence requirements. (learn.microsoft.com)

Suggested statuses are not started, in progress, blocked, ready for review, and approved. If your ERP offers fewer statuses, record review and exception decisions in linked tasks or a controlled supporting register.

2. Turn the checklist into a dependency-based close calendar

Microsoft’s documented period-end sequence includes completing other modules, posting journals, processing relevant adjustments, producing financial statements, and restricting further posting. Use that sequence as a starting point, then adapt it to your business. (learn.microsoft.com)

The following calendar is synthetic. D0 means the accounting period-end date; D+1 means the next working day. It is not an industry benchmark or a promised close duration.

Target	Task	Suggested owner	Dependency	Evidence required before approval
D−3	Confirm cutoffs, scope, and task assignments	Controller	Reporting requirements agreed	Approved calendar and cutoff instructions
D+1	Check payroll, billing, purchasing, and other interfaces	ERP administrator with process owners	Source-system cutoff reached	Batch results, rejected-item list, source-to-ERP totals
D+1	Complete AP and AR processing	AP and AR leads	Relevant interfaces checked	Unposted-item review and cutoff exceptions
D+2	Prepare bank reconciliations	Treasury or cash accountant	Statements available; cash postings checked	Reconciliation and outstanding-item support
D+2	Process assets, accruals, and prepayments	Responsible accountants	Supporting schedules and transaction inputs ready	Reviewed calculations and posted journal references
D+3	Reconcile subledgers and other balance-sheet accounts	GL accountant	Relevant postings completed	Reconciliations and exception register
D+4	Review results and applicable consolidation	Controller or group finance	Entity balances reviewed	Financial statements, variance explanations, review record
D+5	Approve close and restrict posting	Authorized approver and ERP administrator	Review complete; exceptions dispositioned	Close authorization and period-access record

Set a deadline within each day rather than giving everyone the same end-of-day target.

Also distinguish accounting periods from scheduling calendars. In Dynamics 365 Finance, close-task scheduling uses a working-day calendar; without a specified calendar, task dates use all days of the week. Check holidays and time-zone behavior before generating the schedule. (learn.microsoft.com)

3. Complete transaction flows before relying on balances

Make transaction completeness an explicit checkpoint before reconciliation.

For each relevant interface or posting process, ask the owner to confirm:

1. Which source transactions belong in the period?
2. Did the expected files or batches arrive?
3. What posted successfully, and what remains rejected or unposted?
4. Do source totals agree with accepted and posted totals?
5. Who owns any remaining difference?

Treat “file received,” “import successful,” and “journal posted” as separate checklist checkpoints. Require evidence appropriate to each stage rather than a single success screenshot.

Next, reconcile the applicable subledgers—such as accounts payable and accounts receivable—to their general ledger control accounts. Microsoft recommends reconciling ledger and subledger every period and notes that built-in reports may need extending for local requirements. (learn.microsoft.com)

For your comparison, document the entity, cutoff date, currency basis, accounts, and filters. If a difference remains, investigate its cause rather than immediately posting a balancing journal.

Be especially careful after configuration changes. In Dynamics 365 Finance, changing a posting profile does not update previously posted transactions and can disrupt reconciliation. Microsoft recommends nonproduction testing and reconciliation before and after such changes. (learn.microsoft.com)

4. Separate bank matching from reconciliation approval

Dynamics 365 Finance’s advanced bank reconciliation supports statement imports, matching rules, side-by-side transaction review, and reconciliation statements. Its documented validation checks include account and currency agreement, statement continuity, and whether opening balance plus statement movements equals closing balance. (learn.microsoft.com)

Build your cash checklist around three separate outcomes:

• Input checked: the statement covers the intended account and dates.
• Differences explained: unmatched items have support and an owner.
• Reconciliation reviewed: the adjusted balances agree and the reviewer accepts the explanation.

For example, consider this hypothetical reconciliation, with all amounts in USD:

Item	Amount
Bank statement closing balance	$100,000
Add: supported deposit in transit	$12,000
Less: supported outstanding payments	($8,000)
Adjusted bank balance	$104,000
ERP cash balance before adjustment	$104,250
Less: verified bank fee not yet recorded	($250)
Adjusted ERP cash balance	$104,000

The balances agree after the assumed fee adjustment. Before approving, verify that the deposit and payments are genuine timing items and that the fee has not already been recorded.

Attach the statement, outstanding-item schedule, fee support, posted journal reference, and review record. Keep timing items on a follow-up list.

Check the exact workflow in your environment: Microsoft documents differences depending on whether Modern bank reconciliation is enabled. (learn.microsoft.com)

5. Make accruals and fixed assets separate preparation-and-posting tasks

For accruals and prepayments, use a supporting schedule with these suggested fields:

• Nature of the expense or balance.
• Supporting document and service period.
• Calculation and assumptions.
• Account and financial dimensions.
• Preparation and approval records.
• Posted journal reference.
• Reversal or release instruction, where appropriate.

The ERP can support adjustment posting, but your checklist should assign the accounting assessment and approval to named people. Microsoft includes manual period-end adjustments among its documented close activities; it does not prescribe a single adjustment list for every organization. (learn.microsoft.com)

Apply the same distinction to fixed assets. In Dynamics 365 Finance, the documented depreciation process separates proposal creation from reviewing journal entries and posting them. A generated proposal is therefore not, by itself, evidence of a posted journal. (learn.microsoft.com)

Suggested asset checks include additions, disposals, the selected depreciation date, excluded assets, journal review, posting confirmation, and agreement to relevant GL balances.

Confirm that you are reconciling the correct asset book. Dynamics 365 Finance allows books that do not post to the general ledger, so comparing the wrong book with GL balances can produce a misleading difference. (learn.microsoft.com)

6. Review exceptions and results before authorizing the close

Create an exception register alongside the checklist. Require each unresolved item to show:

• Affected entity, account, and period.
• Amount, or an explicit statement that the amount remains unknown.
• Cause and available evidence.
• Proposed action.
• Owner and resolution deadline.
• Approver’s decision and rationale.
• Reports or reconciliations requiring refresh after correction.

Use a clear decision rule: resolve, explicitly approve the proposed treatment, or block the close. Do not let a deadline silently convert an unresolved issue into an accepted one.

Avoid inventing a universal dollar threshold. Have the controller establish escalation criteria consistent with the organization’s policies and reporting responsibilities.

For the results review, use this suggested checklist:

• Explain significant movements and unusual balances.
• Trace material adjustments to their support and approvals.
• Review applicable intercompany differences and consolidation outputs.
• Confirm that final reports include the approved postings.
• Refresh affected reconciliations after late adjustments.

The documented Dynamics 365 close process places reconciliation, currency revaluation, consolidation, and financial-statement preparation before period closure. Your review tasks should make the acceptance of those outputs explicit. (learn.microsoft.com)

A common mistake is treating dashboard completion as review evidence. NetSuite Quick Close is a concrete warning: it marks checklist tasks complete without executing the underlying close work. (docs.oracle.com)

7. Verify posting restrictions and control any reopening

Separate three decisions: the work is complete, finance has approved the results, and the ERP is restricted against further posting.

Do not assume that products use “locked” and “closed” interchangeably:

• Dynamics 365 Finance: an On hold period prevents posting but can be reopened. Permanently closed cannot be reopened. Microsoft’s period-end guidance recommends On hold rather than permanent closure for the routine process. (learn.microsoft.com)
• NetSuite: preliminary locks limit posting during close preparation; a Closed period prevents GL posting by anyone. Users with Override Period Restrictions can make certain posting changes in a locked period, so a lock should not be treated as equivalent to final closure. (docs.oracle.com)

Before applying restrictions in production, validate the intended behavior in a sandbox with representative user and integration roles. Check an ordinary posting, an approved adjustment, and an interface transaction against the intended period.

For final authorization, require:

• Approved reconciliations and adjustment evidence.
• An explicit decision for every open exception.
• Final report versions and reviewer sign-off.
• Confirmation of the correct entity, book, and period.
• A record of the posting restrictions applied.

If reopening becomes necessary, require a documented reason, approver, permitted changes, and re-close owner. Refresh affected reports and reconciliations before approving again.

The practical goal is a checklist that lets another authorized reviewer see what was done, what remains unresolved, who accepted the result, and what prevents further changes.