Preparing for Your First Financial Close in a New ERP. Rehearse balances, reconciliations, reporting and review.
The first financial close after an ERP transition brings together work that may have been tested separately: opening balances, operational cutoffs, subledger processing, reconciliations, adjustments, reporting, and review. Each component can appear ready while the complete sequence remains unproven.
A close rehearsal gives the controller a way to test that sequence before the live deadline. The useful result is a dependency map, a reviewable evidence pack, and an explicit decision for each unresolved issue. Completing a checklist without proving those connections offers limited assurance.
The rehearsal should use representative scenarios and the people who will prepare and review the live close. Its design must reflect the organization's accounting policies, reporting obligations, materiality judgments, and control requirements. Those decisions belong to the controller and relevant specialists; a generic rehearsal cannot prescribe them.
Identify the reports and account reviews the first close must support. For each, work backward through the required ledger balances, subledger results, operational events, data feeds, and approvals. Add the moment when each dependency must become reliable enough for the next task to proceed.
For example, an inventory-related account review may depend on recorded receipts and shipments, completed costing activity, exception resolution, and a defined inventory cutoff. An accounts-payable reconciliation may depend on invoice processing, receipt information, and controlled treatment of unmatched items. The controller should determine the applicable accounting treatment; the rehearsal tests whether the agreed process can produce and explain the evidence.
Build the dependency map around handoffs. Record the sender, receiver, expected output, acceptance check, and escalation time. “Warehouse complete” is ambiguous. “Warehouse owner has confirmed the defined movement population and logged unresolved exceptions” gives finance something it can review.
Mark dependencies outside finance, including operational teams and external information providers. A close calendar that assigns every problem to accounting may conceal the actual source of delay.
Choose scenarios by their effect on the close, not solely by transaction volume. Include ordinary processing, consequential exceptions, opening positions, and activities near the period boundary. Where relevant, consider returns, late invoices, unapplied cash, intercompany activity, different currencies, and corrections to prior entries.
Use an approved nonproduction environment with controlled, appropriately protected data. Record the environment version, configuration, roles, and dataset. A rehearsal performed against obsolete mappings or exceptional access may produce reassuring results that do not carry into the live close.
Define what the exercise can prove. A reduced dataset can test accounting logic and handoffs without demonstrating full processing duration. A full-volume dataset can test timing but still miss an unusual exception. If both forms of evidence matter, plan complementary tests rather than pretending that one exercise covers everything.
Agree expected outcomes before execution. The preparer and reviewer should know what they are checking and which differences require explanation. Do not let the current system output become the expected result merely because it is available. The expected outcome must be grounded in approved requirements and supporting records.
Opening-balance validation should connect migrated balances to the records and mappings that support them. Check the relevant account, entity, currency, period, and other reporting dimensions. Where a subledger supports a control account, establish how the two reconcile within the agreed scope.
Then test representative movement after opening. A correct opening position does not prove that the next transaction will post to the correct account or reporting dimension. Reconcile a controlled sequence of opening position, period activity, adjustments, and closing position so reviewers can explain how the result was formed.
Separate a data migration difference from a timing difference or an intentional accounting adjustment. Each has a different owner and resolution path. A single undifferentiated reconciliation variance encourages teams to patch the total without correcting the cause.
Preserve the approved opening evidence. If mappings or loaded data change during rehearsal, identify which reconciliations and reports must be rerun. The evidence pack should state which version was reviewed and avoid mixing results from different data states.
Build one evidence record for each important reconciliation or close assertion. Another qualified reviewer should be able to understand the work without a verbal explanation from its original preparer.
Include:
The record should distinguish a report that ran successfully from one whose definition was validated. Check filters, period selection, date basis, entity scope, and treatment of excluded or incomplete records. A clean report can be misleading if it omits the population under review.
Give reviewers their intended access. They should be able to inspect supporting detail and record conclusions without using the preparer's account or borrowing project-level privileges. If the review depends on a separate export, confirm how that file is controlled and how its relationship to the underlying report remains clear.
A first close needs a workable path when the original transaction is wrong or information arrives late. Include these conditions deliberately rather than treating them as interruptions to a successful test.
Ask who identifies the issue, determines the accounting treatment, approves the correction, and checks its downstream effects. Test the agreed routes for adjustments, reversals, and period controls where they apply. Confirm that permissions and review responsibilities support those routes without weakening required separation of duties.
Include a scenario in which a period has already been restricted or closed. The exercise should establish who can decide whether further action is appropriate and which evidence the decision needs. It should not normalize reopening periods or posting unsupported adjustments simply to finish the calendar.
Watch for work that moves outside the new system. A manual calculation or controlled supporting schedule may be part of the intended process. An undocumented parallel ledger or private reconciliation file may indicate a missing design decision. Record the purpose, owner, source data, review, and retention requirements of every material manual step.
The close team needs more than a defect list. Some issues prevent reliable reporting; others can proceed under a controlled interim arrangement; some require an accounting judgment rather than a technical fix.
For each unresolved issue, record the affected assertion or close activity, evidence, business consequence, owner, required decision, and latest useful decision time. Add the selected action, approval, retest condition, and effect on downstream work.
Use clear decision categories: resolve before live close, accept a specific interim control, defer a noncritical improvement, or escalate an unresolved reporting concern. The controller determines which conditions are acceptable. The project team should not make that decision implicitly by leaving an item open after the rehearsal ends.
Review issues across accounts and entities. Several small variances may share one mapping problem. A late feed may affect both a reconciliation and a management report. The dependency map helps the team see that correcting one symptom may leave other outputs unreliable.
Consider a hypothetical manufacturer preparing its first month-end close in a new ERP. The opening inventory balance reconciles, and ordinary receipts and shipments have passed transaction testing. During rehearsal, the finance reviewer notices a difference after a late receipt is processed near the period boundary.
The team traces the affected records through the dependency map. The operational report and the finance extract use different date bases. Both reports are running as configured, but the reconciliation population is inconsistent. An immediate journal adjustment would conceal the mismatch rather than explain it.
The controller and process owner agree the correct population definition for the intended review. The reporting owner updates the extract, the warehouse owner confirms the cutoff process, and finance reruns the affected reconciliation. The reviewer checks the detail and records the conclusion against the revised report version.
A related scenario remains untested: a receipt correction arriving after the period restriction. The issue log gives it an owner, an approved rehearsal case, and a completion condition before the live close. The team has learned something more useful than whether the original checklist was completed on time.
Translate the results into a revised calendar with actual dependencies, named preparers and reviewers, evidence locations, and escalation points. Include the time needed to resolve exceptions and review work, not just to run processing jobs.
Do not transfer rehearsal timings mechanically. Explain differences in data volume, staff availability, environment performance, and operational workload. Where duration remains uncertain, provide a range and a contingency that the close owner can evaluate.
At the final readiness review, ask three questions: can the team produce the necessary results, can reviewers explain them, and can unresolved conditions be handled within approved controls? A successful rehearsal should leave clear answers and visible limitations.
Start with one high-consequence reconciliation and follow it all the way from source event to review. That single chain will reveal whether the first-close plan is an executable operating process or a collection of tasks waiting to discover their dependencies under deadline pressure.