A fast month-end close is valuable, but speed alone is not a sign of a strong close. Financial controllers need a process that produces complete, accurate, reviewable results—with clear ownership, timely reconciliations, controlled journal entries, and evidence that key reviews actually occurred.
For organisations using SAP S/4HANA, many of these activities can be supported through workflow, ledger reporting, and standardised close procedures. The exact apps and configuration vary by deployment model and release, so the control design should be mapped to the company’s own SAP environment rather than assumed from a generic checklist.
This guide outlines eight practical controls controllers can review before the next close, including what to look for in SAP and what evidence to retain.
Why the close needs a control framework
The close brings together activity from general ledger, accounts payable, accounts receivable, payroll, fixed assets, inventory, treasury, tax, and other systems. A missed accrual, unreconciled account, late interface, or unsupported manual journal can affect more than one financial statement line.
A useful close framework connects each risk to a specific control, an accountable owner, a defined deadline, and retained evidence. For SEC registrants subject to applicable internal-control reporting requirements, management’s assessment of internal control over financial reporting is particularly important. The SEC and PCAOB materials linked below describe the relevant context; applicability and attestation requirements depend on the issuer and its circumstances.
1. Define a close calendar with owners and dependencies
Start with a close calendar that states the task, preparer, reviewer, due date, source system, dependencies, and escalation path. Separate critical-path tasks—such as subledger completion and interface validation—from activities that can safely occur later.
Controller check: Does every material close task have one accountable owner? Are late tasks escalated rather than silently carried forward? Are changes to the calendar version-controlled?
Evidence to retain: The approved calendar, task-completion status, reviewer sign-offs, and documented explanations for overdue or rolled-forward items.
2. Reconcile high-risk balance-sheet accounts
Prioritise reconciliations based on risk and materiality. Common examples include cash, accounts receivable, accounts payable, inventory, payroll liabilities, fixed assets, debt, intercompany balances, and significant accrual accounts.
A reconciliation should explain the balance, link to reliable supporting information, identify reconciling items, assign an owner and resolution date, and show an independent review. An unexplained difference should not be treated as acceptable merely because it is old or below an arbitrary threshold.
SAP angle: Use the reporting and line-item analysis available in your SAP release to support general-ledger-to-subledger checks and investigate unusual postings. Where appropriate, reconcile SAP balances to bank statements, third-party statements, operational records, and source-system totals.
Evidence to retain: Reconciliation, source reports, supporting documents, review notes, and proof that aged items were followed up.
3. Control manual journal entries
Manual and top-side journals deserve particular attention because they can bypass the normal transaction flow. Define which journal types require supporting documentation and independent approval, with risk-based rules for unusual account combinations, sensitive periods, material amounts, and entries posted by privileged users.
SAP S/4HANA provides journal-entry verification workflows in supported configurations. SAP documents the ability to define workflow preconditions and approval steps; confirm availability and setup for your deployment and release before relying on a specific app or feature.
Controller check: Can the preparer approve their own entry? Are late-period entries reviewed for business purpose and support? Are reversals and recurring journals checked? Are rejected or failed workflow items monitored?
Evidence to retain: Journal support, approval history, posting details, rationale for estimates and adjustments, and any exception approval.
4. Review access and segregation of duties
Access that allows one person to create a vendor, enter an invoice, change bank details, post a journal, and approve payment can undermine several controls at once. Review incompatible duties across finance and related processes, not only within the general ledger.
At close, confirm that access changes for joiners, movers, and leavers have been completed; privileged and emergency access is logged and reviewed; and access exceptions have an approved compensating control. In SAP, role and authorisation design should be assessed against the actual business process and risk—not merely against a list of job titles.
Evidence to retain: Periodic access review, conflict analysis, approved exceptions, emergency-access logs, and remediation tracking.
5. Validate interfaces and subledger completeness
Automated postings are only as reliable as the data and interfaces behind them. Reconcile source totals to records accepted by the target system, investigate failed or duplicate messages, and check that rejected transactions are corrected and reprocessed with traceable evidence.
For each material interface, define expected volumes or control totals, ownership, failure notifications, and a deadline for resolution. When a feed is late, document how the accounting team determines whether an accrual or other temporary treatment is necessary.
Controller check: Can you demonstrate that all material transactions expected from payroll, billing, procurement, inventory, or other systems reached the ledger once—and only once?
6. Review estimates, accruals, and recurring entries
Accruals and estimates often rely on judgement, operational inputs, contracts, or models. Establish documented methodologies, named preparers and reviewers, source-data checks, and comparisons of prior estimates with actual outcomes.
For material estimates, record the key assumptions and sensitivity to changes. Recurring journals should be reviewed for continued validity rather than rolled forward automatically without challenge. Reversals should be monitored so they do not create duplicate expenses or leave liabilities understated in a later period.
Evidence to retain: Calculation files, source data, assumptions, reviewer challenge, actual-versus-estimate analysis, and reversal or true-up entries.
7. Reconcile intercompany balances and consolidation inputs
Groups with multiple legal entities should align close cut-offs, due-to/due-from balances, currencies, and transaction matching. Investigate differences by counterparty and transaction type, not only at a consolidated total level. Establish clear ownership of both sides of each material intercompany difference.
Before consolidation, confirm that entity submissions use the correct period, currency, ledger, and reporting basis. If the group reports under more than one accounting framework, maintain a controlled bridge for material policy differences rather than assuming that one ledger automatically satisfies all reporting needs.
Evidence to retain: Entity close certification, intercompany confirmations or matching reports, variance explanations, consolidation journals, and review sign-off.
8. Monitor late postings, unusual movements, and close exceptions
A close is not controlled simply because every task is marked complete. Review unusual account movements, significant manual entries, unexpected period-end spikes, negative or dormant balances, old reconciling items, post-close adjustments, and repeated exceptions.
In SAP S/4HANA, available general-ledger reporting and journal-analysis capabilities can help controllers investigate postings by fields such as company code, period, G/L account, posting date, or other supported dimensions. Validate report scope, ledger, filters, and completeness before relying on an output.
Keep a close-exception log with an owner, root cause, financial exposure, remediation date, and escalation threshold. Repeated exceptions should trigger a process improvement or control redesign—not just another month of manual follow-up.
A practical close-control dashboard
A weekly or daily dashboard during close can summarise control execution without replacing the underlying review.
| Control area | Example indicator | Escalation trigger |
|---|---|---|
| Close calendar | Critical tasks completed by deadline | Critical-path task overdue |
| Reconciliations | Accounts reconciled and reviewed | Material balance unreconciled or aged item unresolved |
| Journal entries | Entries pending approval; late entries | Entry posted without required approval or support |
| Interfaces | Failed, duplicate, or unprocessed records | Unexplained difference in control totals |
| Access | Open access conflicts or privileged-access reviews | Unapproved conflict or overdue remediation |
| Consolidation | Unmatched intercompany balances | Material difference without owner or resolution plan |
| Post-close | Number and value of late adjustments | Repeated material adjustment or recurring root cause |
Set thresholds according to the organisation’s materiality, transaction profile, risk appetite, and close timetable; there is no universal threshold that fits every entity.
Monthly controller checklist
- Confirm that close responsibilities, cut-offs, and escalation contacts are current.
- Review completion and independent approval of high-risk balance-sheet reconciliations.
- Inspect manual, late, unusual, and privileged-user journal entries.
- Validate critical interfaces and resolve failed, duplicate, or missing transactions.
- Review access conflicts, privileged access, and emergency-access activity.
- Challenge significant accruals, estimates, and recurring entries.
- Clear or assign material intercompany differences and consolidation exceptions.
- Review late adjustments and recurring close issues for root cause.
- Confirm that evidence is complete, accessible, dated, and linked to the control performed.
Official resources
- SAP Help: Manage Workflows for Journal Entry Verification in General Ledger — capabilities and configuration for journal-entry verification workflows in supported on-premise releases.
- SAP Help: Verify General Journal Entries — the verification process described for SAP S/4HANA General Ledger.
- SEC: Management’s Report on Internal Control Over Financial Reporting — staff guidance and FAQs related to ICFR reporting.
- PCAOB Auditing Standard 2201 — auditor requirements and guidance for integrated audits of internal control over financial reporting, where applicable.
Conclusion
A reliable month-end close is built on repeatable controls, not heroic last-minute effort. Financial controllers can improve both speed and confidence by assigning clear ownership, strengthening reconciliations and journal-entry review, validating interfaces, controlling access, and monitoring exceptions through resolution.
SAP S/4HANA can support elements of this framework, but technology does not replace sound control design, independent review, or evidence. Start with the risks that could materially affect reporting, confirm the capabilities and configuration in your own environment, and use close exceptions to drive continuous improvement.
Disclaimer: This article is for general informational purposes only. It is not accounting, audit, legal, or SAP implementation advice. Applicability depends on the entity, reporting obligations, SAP deployment and release, and internal policies. Validate control design with your accounting, IT, risk, and audit teams.