Quick answer
An actionable ERP month-end close checklist should identify what must be completed, who owns it, when it is due, what it depends on and what proves completion. Sequence work from transaction cutoffs through subledger processing, reconciliations, adjustments, financial review and posting restrictions. Treat “prepared,” “reviewed” and “period locked” as separate milestones.
Use the sample below as a starting template—not a universal timetable or accounting policy.
1. Build a checklist that defines “done”
Start with one checklist for each legal entity and accounting period. Assign a named person to every task; department names alone leave responsibility unclear.
Use these fields:
| Field | What to record |
|---|---|
| Task ID and scope | Entity, period, ledger and relevant account or process |
| Deliverable | A specific result, such as “AP control account reconciled” |
| Owner and backup | Named preparer and replacement |
| Reviewer | Person authorized to approve the work |
| Deadline | Date, time and time zone |
| Dependencies | Tasks or inputs required first |
| Completion evidence | Report, reconciliation, journal reference or approval record |
| Status | Not started, in progress, blocked, prepared or reviewed |
| Exception | Unresolved issue, impact, decision owner and next deadline |
This is a recommended operating template, not a claim that every ERP provides these fields.
For a product-specific example, Dynamics 365 Finance supports close-task assignments, relative due dates, dependencies and attachments. Its workspace records completion timestamps and prevents a dependent task from being marked complete until its prerequisites are complete. Those features track the work; your checklist should separately define what acceptable evidence looks like. (learn.microsoft.com)
Practical check: replace “Review cash” with “Reconcile every in-scope bank account to the ledger, explain outstanding items and obtain reviewer approval.”
2. Set transaction cutoffs and confirm input completeness
Before closing transactions, publish the deadlines for supplier invoices, customer billing, goods receipts, inventory movements, expenses, payroll inputs and journal requests. Record the relevant time zone and the person handling late submissions.
For each input stream, ask the owner to confirm:
- Which source systems and interfaces are included?
- Have expected files or batches arrived?
- Are rejected, held or unapproved items identified?
- Which transactions need a cutoff decision?
- Who will notify finance if another batch arrives?
Keep document date, receipt or service date, and accounting date distinct in the exception log. Do not make a next-period accounting date the automatic answer to a missed administrative deadline. Route the treatment to the authorized accounting reviewer.
Oracle’s documented Payables close process includes importing invoices, resolving rejected records and holds, completing approvals, validating invoices and reviewing accounting-process output. Its transaction-sweep guidance expressly conditions moving accounting dates on whether the organization’s accounting practices permit it. (docs.oracle.com)
Owner: the relevant AP, AR, payroll or inventory lead.
Completion evidence: cutoff communication, interface-status report, exception listing and owner confirmation.
Common mistake: interpreting “no more invoices accepted” as “nothing else needs recognition.” Instead, require the cutoff review to identify missing documents and unresolved obligations for accounting assessment.
3. Complete subledgers before final ledger reconciliation
Separate transaction processing from accounting completion. In the checklist, require confirmation that transactions have reached the required stages: approved, accounted, transferred and posted, where those stages apply.
For each subledger, capture:
| Area | Suggested owner | Completion evidence |
|---|---|---|
| Payables | AP lead | Invoice/payment registers, accounting output and exception disposition |
| Receivables | AR lead | Billing and receipt reports, unresolved-item listing and posting confirmation |
| Inventory | Inventory accountant | Relevant valuation/costing output and receipt/invoice exceptions |
| Fixed assets | Asset accountant | Additions, disposals and depreciation output |
| Payroll | Payroll accountant | Approved payroll summary and ledger posting reference |
| Cash | Treasury accountant | Bank statements, payment status and reconciliation support |
Adapt the inventory and costing tasks to the business and ERP configuration rather than adding an unexplained “inventory close” checkbox.
Microsoft’s period-end guidance places completion of other modules and verification of posted journals among the steps preceding final financial statements. Oracle likewise distinguishes creating and transferring Payables accounting from subsequent reconciliation activities. (learn.microsoft.com)
A useful dependency map is:
Cutoff decisions + complete source inputs
↓
Subledger processing and accounting
↓
Required transfer and GL posting
↓
Reconciliations → approved corrections
↓
Refresh affected reconciliations and reports
↓
Financial review and approval
↓
Posting restrictions and evidence archive
Some work can run in parallel. Prepare bank reconciliations or accrual schedules while other streams finish, but do not approve a final reconciliation against an unfinished ledger.
4. Reconcile balances using consistent scope and fresh data
For each reconciliation, specify the entity, ledger, period, currency basis, account range and relevant dimensions. Save those parameters with the report output.
Require the preparer to document:
- The ledger balance.
- The supporting subledger or external balance.
- Each reconciling item.
- Its cause, owner and resolution date.
- The remaining unexplained difference.
- Reviewer approval or an explicit unresolved status.
Investigate a difference rather than posting an unexplained balancing entry. Oracle identifies potential causes including unaccounted transactions, accounts outside the report range, journals from non-Payables sources, and subledger journals not transferred or posted to the ledger. (docs.oracle.com)
Illustrative reconciliation: assume a supplier subledger shows a $125,000 liability while the corresponding GL control account shows $128,000, expressed as positive liability balances.
GL liability balance $128,000
Less identified manual GL-only journal $3,000
Balance comparable with subledger $125,000
Supplier subledger balance $125,000
Unexplained difference $0
This explains the difference; it does not establish that the manual journal is correct. Ask the reviewer to assess its authorization, account classification and required correction.
For Oracle Fusion Cloud Financials, the Payables to Ledger Reconciliation report requires the preparation process to generate its data. Oracle also warns that later activity can create summary/detail discrepancies and directs users to rerun preparation after corrections. (docs.oracle.com)
Practical check: after a posting changes a reconciled balance, refresh the affected evidence and obtain renewed review.
5. Control adjustments and escalate late supplier invoices
Create separate tasks for applicable accruals, prepayments, depreciation, allocations, foreign-currency revaluation and other adjustments. Microsoft lists revaluation, allocations and manual period-end adjustments among possible closing activities; which tasks apply depends on the organization. (learn.microsoft.com)
For every adjustment, require a calculation, accounting rationale, approval, posting reference and reversal or settlement instruction.
Worked example: a supplier invoice misses cutoff
Assume, solely for illustration:
- A service was completed in the closing month.
- Its approved estimated cost is $10,000.
- No invoice or existing accrual has been recorded.
- The controller determines that the company’s accounting policy requires an accrual.
- Tax, foreign currency and capitalization issues are excluded.
The approved illustrative entry is:
| Account | Debit | Credit |
|---|---|---|
| Service expense | $10,000 | — |
| Accrued expenses | — | $10,000 |
At the cutoff deadline, AP should mark the invoice exception blocked, attach the service confirmation and estimate, and escalate it to the controller—not silently mark AP complete.
The controller’s decision record should identify the treatment, approver, journal reference, affected reconciliations and follow-up owner.
If the invoice later arrives for $10,300, flag the $300 difference for review. Link the invoice to the accrual so the team can clear or reverse the accrual under the approved process and avoid duplicate expense recognition. Do not assume an automatic reversal is configured.
If the invoice arrives after locking, use the approved post-close adjustment or reopening procedure. Do not bypass posting restrictions.
6. Schedule the close around dependencies, not dates alone
The following is an illustrative calendar, not a benchmark or promised close duration. “D” means period-end; subsequent days mean working days.
| Timing | Deliverable | Owner | Dependency | Evidence |
|---|---|---|---|---|
| D−3 to D | Publish cutoffs; collect missing-input risks | Close coordinator | Calendar agreed | Cutoff notice and risk log |
| D+1 | Complete transaction processing | Subledger leads | Inputs and cutoff decisions | Registers and exceptions |
| D+2 | Finish accounting, transfers and GL posting | Subledger/GL accountants | Processing complete | Job output and posting references |
| D+3 | Prepare reconciliations and adjustments | Account owners | Relevant postings complete | Reconciliations and journal support |
| D+4 | Review corrections and refresh reports | Controller | Adjustments posted | Updated evidence and review notes |
| D+5 | Approve reporting and restrict posting | Controller; authorized administrator | Reviews complete | Approval and period-status evidence |
Set a specific escalation trigger for each critical task. For example: “If the service confirmation is unavailable by D+1 at noon, AP alerts the controller and records the reporting impact and next decision time.”
That deadline is a proposed operating rule, not an accounting requirement.
Dynamics 365 Finance supports templates with relative deadlines and working-day calendars, including holidays. Configure the calendar deliberately: Microsoft notes that task deadlines use all days of the week when no calendar is defined. (learn.microsoft.com)
Common mistake: leaving downstream dates unchanged after a prerequisite slips. Reassess affected tasks and tell their owners which evidence is no longer final.
7. Review the final reporting package, then restrict posting
Make final review a distinct deliverable. Ask the controller or designated reviewer to check:
- Financial reports agree with the approved ledger balances.
- Significant movements have supported explanations.
- Unposted journals and interface exceptions have documented dispositions.
- Reconciliations reflect the final postings.
- Outstanding issues have explicit decisions and follow-up owners.
- The issued package has identifiable versions and approval evidence.
Archive the reports, relevant parameters, reconciliations, journal references and approvals together. Keep sensitive payroll or supplier information in appropriately restricted locations.
Next, verify the actual posting controls—not merely the checklist status. In Dynamics 365 Finance, Microsoft recommends placing ledger periods On hold to prevent further posting, or restricting a period to a user group during close. It warns that Permanently closed periods cannot be reopened. These are product-specific controls, not interchangeable labels for every ERP. (learn.microsoft.com)
Use a final release gate:
Close approved: required work is reviewed, exceptions are explicitly resolved or approved for follow-up, reporting reflects final postings, and posting restrictions are verified.
For any later reopening, require authorization, a reason, a record of new postings, refreshed affected reports and confirmation that restrictions were restored. The checklist should preserve what changed after the original approval—not overwrite the history.