Executive Summary
The close is ready for management review except for one AR tie-out exception caused by a manual journal posted directly to the AR control account, bypassing the subledger.
Management reading: a fast close is a byproduct of a monitored close.
Pipeline runs succeeded
47 / 48
One controlled rerun pending
Tie-out checks passed
11 / 12
One failed check explained
Data freshness
< 24h
All reporting sources current
Close blockers
3
Assigned to owner roles
Reconciliation Checks
The failed AR check is the textbook control-account break: a direct general-journal posting hit the AR control account without a matching customer subledger transaction. Corrective action is reverse and repost through the subledger; preventive action is to restrict direct posting to control accounts. The bank, VAT, and intercompany checks tie directly to the Thirteen-Week Cash Flow Forecast and the Revenue Reconciliation Statement.
| Entity | Check | Expected | Actual | Difference | Status |
|---|---|---|---|---|---|
| MB-NL1 | AR subledger to control | EUR 6.20m | EUR 6.20m | EUR 0k | Pass |
| MB-BE1 | AR subledger to control | EUR 1.80m | EUR 1.80m | EUR 0k | Pass |
| MB-BE2 | AR subledger to control | EUR 1.05m | EUR 1.09m | EUR 40k | Fail |
| Group | AP subledger to control | EUR 15.5m | EUR 15.5m | EUR 0k | Pass |
| Group | Inventory to control | EUR 18.2m | EUR 18.2m | EUR 0k | Pass |
| Group | Revenue bridge residual | EUR 0.0m | EUR 0.0m | EUR 0k | Pass |
| Group | Open PO control | EUR 7.4m | EUR 7.4m | EUR 0k | Pass |
| Group | Operations open work count | 1,284 | 1,284 | 0 | Pass |
| Group | Intercompany balances eliminate to zero | EUR 0.0m | EUR 0.0m | EUR 0k | Pass |
| Group | Bank balance to ledger cash accounts | EUR 2.8m | EUR 2.8m | EUR 0k | Pass |
| Group | VAT payable control to Q2 return | EUR 1.1m | EUR 1.1m | EUR 0k | Pass |
| Group | Dimension readiness load | 9 entities | 9 entities | 0 | Pass |
Freshness And Period Status
Ages measured at the close readiness review, 1 July 2026 08:00.
| Source | Last successful run | Age at snapshot | Status |
|---|---|---|---|
| Revenue bridge extract | 30 Jun 2026 23:40 | 8h 20m | Succeeded |
| AR/AP subledger snapshot | 30 Jun 2026 23:55 | 8h 05m | Succeeded |
| Inventory valuation snapshot | 01 Jul 2026 00:25 | 7h 35m | Succeeded |
| Operations work status | 01 Jul 2026 00:35 | 7h 25m | Succeeded |
| Nightly export | 30 Jun 2026 22:14 | 9h 46m | Partially succeeded |
| Entity group | Period status | Close implication |
|---|---|---|
| MB-NL1 | On hold | Final postings blocked after close checks passed |
| MB-BE1 | On hold | Aligned with group close schedule |
| MB-BE2 | Open | Left open only for the AR control-account correction |
| Small entities | On hold | No open close blockers |
Run Log Excerpt
Data jobs are shown in business words: Succeeded, Partially succeeded, or Failed. Batch runs are described as waiting, executing, or ended in error. Raw status codes are not printed.
| Run time | Status | Finding | Resolution | Retry result |
|---|---|---|---|---|
| 30 Jun 2026 22:14 | Partially succeeded | Nightly export skipped a subset of records that failed validation while the good records loaded | Skipped records assigned for correction; rerun scheduled | Pending rerun |
| 30 Jun 2026 23:02 | Ended in error | Inventory movement refresh exceeded normal batch window | Automatic retry completed | Recovered |
| 01 Jul 2026 00:18 | Succeeded | Schema check confirmed the expected field set after refresh | No action required | Recovered |
Close-Blocking Items
| Priority | Blocking item | Owner role | Due date | Status |
|---|---|---|---|---|
| 1 | Classify MB-BE2 AR manual journal difference | Finance controller | 08 Jul 2026 | Open |
| 2 | Approve final AR rerun evidence | Close manager | 08 Jul 2026 | Waiting |
| 3 | Release close pack after rerun | Reporting owner | 09 Jul 2026 | Waiting |
Data Basis
| Item | Applied basis |
|---|---|
| Report period | Month-end close, June 2026. |
| Snapshot and generation | Snapshot 30 June 2026; freshness ages measured at the readiness review on 1 July 2026 08:00; report generated 7 July 2026. |
| Scope | Close-readiness control view across finance and operations; owner roles only, never user names. Fictional trading and services group operating in NL/BE/LU. |
| Currency and posting layer | EUR only; accounting currency equals reporting currency. Current posting layer only. |
| Business domains used | Scheduled data jobs, batch run outcomes, freshness checks, subledger-to-control-account tie-outs, bank and VAT controls, intercompany eliminations, period status, and the close blocker register. |
| Definitions applied | Pipeline success is measured by completed scheduled runs. Tie-out pass means actual and expected values are inside tolerance. A partially succeeded job loaded valid records and skipped invalid records for correction. |
| Dimension usage | Slicing follows the dimension reliability tiers from the Financial Structure Deep Dive: core and strong operational dimensions only; the legacy Klant dimension, Employee, and Vehicle are excluded. |
| Aggregation and privacy | Aggregate view only. No names, account numbers, voucher or document identifiers, or contact details are displayed; traceability is to controlled local evidence. |
| Rounding | EUR rounded for reporting; every table foots to its headline KPI or carries an explicit basis note. |
| Control statement | Generated on 7 July 2026 from fictional aggregated demo data. Read-only reporting view; no personal data, contact details, transaction identifiers, or real client references are displayed. |