Finance close system blueprint
This system coordinates the month-end close across the general ledger, sub-ledgers, bank accounts, and supporting schedules. It reconciles balances, routes unexplained differences to accountable owners, and prepares a review-ready close package without replacing finance approval.
- Business function
- Finance & Risk
- Operating context
- Across the business
- Primary owner
- Group Financial Controller
Operating brief
What starts the system
The accounting period reaches its close date or the controller starts an interim close.
Segregation of journal preparation and approval
Operating sequence
How the system works
1. Ingest period balances and match transactions across ledgers, banks, and supporting schedules.
2. Classify differences, apply approved tolerances, and route unresolved exceptions to named account owners.
3. Consolidate approved reconciliations, journals, and sign-offs into the close package.
Inputs
- General-ledger and sub-ledger balances
- Bank statements and reconciliation rules
- Close calendar, ownership, and materiality thresholds
Outputs
- Account reconciliation and exception register
- Review-ready close package with sign-off status
Controls
- Segregation of journal preparation and approval
- Immutable evidence and approval trail for every reconciliation
Source landscape
Examples of systems it may connect to
- SAP S/4HANA Finance
- Oracle NetSuite
- Microsoft Dynamics 365 Finance
- BlackLine
- Fortnox
Reusable core
What can carry across companies
The reusable core is period orchestration, matching, exception routing, and evidence capture.
Your installation
What must be adapted
Account structures, close calendars, tolerances, approval limits, and consolidation rules are configured for each company.
Start with the closest pattern–or start from your process.
The catalogue represents reusable operating shapes, not fixed off-the-shelf applications.