SUBSTRATE AUDIT OS
Meridian
Portfolio
ASSESSMENT
Overview01
Workflow map02
Exceptions03
Human perimeter04
Controls05
Governance report06
Scenario
▾
Record-to-Report
Close / reconciliation · Record-to-Report
Meridian · Operational Governance Intelligence
Northstar Components
Governance
Intelligence
Report
Close / reconciliation — R2R
49/ 100
Fragile
Assessment date: 10 September 2026 · Prepared by Meridian · Confidential
Governance report
Scorecard, priorities, and leadership-ready actions for the next 90 days
Demo org: Northstar Components
EXECUTIVE ASSESSMENT
FRAGILE
Northstar's close process is operationally functional but commercially exposed to key-person dependency.
Operationally functional but commercially exposed. Critical controls are informal and institutional knowledge sits with individuals. Remediation must precede automation work.
KEY FINDINGS
—Critical reconciliations rely on individual availability and judgement during compressed close windows.
—Late journal activity creates downstream reporting pressure and reduces control effectiveness.
—Variance explanations and approval rationale are inconsistently documented across reporting cycles.
RECOMMENDED FOCUS
Reduce key-person dependency by documenting decision logic, standardising variance commentary, and introducing governed reconciliation sign-off workflows.
POTENTIAL BUSINESS IMPACT
Compressed close timelines and key-person dependency increase the probability of reporting errors, reduce time available for analytical review, and create material risk during audit or executive reporting cycles.
Why this score
What is being measured
The Governance Score is a composite measure of how well this process is actually governed — weighting governance gap (30%), governance drift (30%), automation failure probability (20%) and key person dependency (20%). It scores the process as it runs today, not as it is documented.
What drives the score
The score moves with four forces: the gap between documented and actual practice, the rate at which controls decay from their documented state, the probability that automation would fail on the current structure, and how much the process depends on specific individuals.
What this score means here
At 49, Close / reconciliation carries structural governance failure. Decisions are made without documented authority, evidence, or consistent escalation. Automating this process in its current state would industrialise its weaknesses. The current governance gap represents an estimated €319k in annual governance debt for this process.
What needs to change next
Stabilise before anything else: establish documented decision rights, a minimum evidence standard, and a formal escalation route. No automation investment is defensible until the score clears 50.
COMPLIANCE EXPOSURE
Estimated regulatory and audit exposure derived from governance scores, drift signals, and dependency concentration.
SOX EXPOSURE
Moderate
Audit Trail 43 · Fidelity 49 · GDI 0
ICFR EXPOSURE
High→ Moderate
Audit Trail 43 · KPDI 91 · GDI 0
IFRS REPORTING RISK
Moderate
Fidelity 49 · AIFP 84% · GDI 0
AUDIT READINESS
Limited→ Strong
Audit Trail 43 · GDI 0 · KPDI 91
SOX / ICFR IMPLICATIONS
SOX Moderate
Some control weaknesses present. Monitoring and documentation improvements recommended.
ICFR High→ Moderate after remediation
Dependency concentration increases ICFR exposure. Knowledge transfer required.
IFRS / AUDIT IMPLICATIONS
IFRS Moderate
Some documentation and process gaps present. Variance commentary controls recommended.
Audit Limited→ Strong after remediation
Evidence gaps may create difficulties under external review. Documentation remediation advised.
Compliance exposure derived from audit trail completeness, flow fidelity, drift index, and key-person dependency scores. Directional assessment — not a legal or audit opinion.
AUTOMATION READINESS
AUTOMATION FAILURE RISK
84%
critical risk
AUTOMATION READINESS SCORE
16
/ 100
AUTOMATION VERDICT
Not Ready
high confidence
AUTOMATION RISK ASSESSMENT

The close and reconciliation process is critically dependent on specific individuals who hold undocumented process knowledge. Manual journal entries are approved without independent review, and sign-off evidence is not consistently retained. Automation deployed here would inherit single-person dependency, operate without a governance basis, and face immediate failure risk if key personnel are unavailable.

Why this score
What is being measured
Automation Failure Probability estimates the likelihood that automation deployed on this process, as it is currently structured, fails — producing wrong outcomes, unhandled exceptions, or ungoverned decisions. It measures the process's readiness to be automated, not the quality of any automation tool.
What drives the score
The probability rises with undefined decision logic, unstructured exception handling, missing evidence capture, and informal escalation — the conditions under which automation fails silently rather than loudly.
What this score means here
At 84%, automation failure in Close / reconciliation is the expected outcome, not the tail risk. The process lacks the structured decisions, defined exceptions, and evidence trail that any automation — agentic or scripted — requires to operate safely. At current volumes this represents an estimated €735k in annual automation exposure.
What needs to change next
Stop any automation plan for this process. The remediation sequence is: structured decision definitions, exception taxonomy, evidence capture, escalation rules — then re-score before revisiting automation.
AGENT READINESS INDEX
21/ 100
No AI
Full breakdown in Agent Operating Licence below
AUTOMATION BLOCKERS
✕Single-person sign-off dependency
✕Undocumented manual journal adjustments
✕No independent review workflow
✕Inconsistent evidence retention across close team
RISK DRIVERS
Single-person close dependency
Automation fails immediately if key reviewer is unavailable
Undocumented journal adjustment logic
Automation cannot replicate or audit manual override decisions
Missing independent review
No governance check on automated journal processing
Inconsistent sign-off evidence
Automation output cannot be independently verified
AGENT OPERATING LICENCE
No AI
Meridian's assessment of which agent interactions are safe for this process and where human control must remain.
LICENCE SUMMARY

Close / Reconciliation is not currently licensed for operational AI agent use. The process is fragile, critically dependent on specific individuals, and lacks documented close logic, independent review, standardised sign-off evidence, and governed escalation paths.

PERMITTED AGENT USE
✓Assist with drafting close runbook documentation from human-provided inputs
✓Summarise close task lists, deadlines, and owner information
✓Identify missing reconciliation evidence
✓Highlight incomplete sign-off records
✓Draft variance commentary templates for human review
✓Suggest documentation gaps in close procedures
✓Flag manual journal entries lacking support or review evidence
✓Prepare reconciliation checklist drafts
✓Summarise recurring close bottlenecks for management review
RESTRICTED AGENT USE
✕Post manual journals
✕Approve manual journal entries
✕Perform final reconciliation sign-off
✕Approve balance sheet reconciliations
✕Override close cut-off rules
✕Approve late journal activity
✕Change reported balances
✕Resolve reconciliation differences
✕Approve variance explanations
✕Submit reporting packs
✕Close the period
✕Suppress control exceptions
✕Replace independent review
AGENT READINESS INDEX — SCORE BREAKDOWN
Agent readiness measures whether an AI agent can safely operate inside this process. Driven by decision traceability, evidence completeness, escalation formality, exception structure, and human override coverage.
Decision traceabilityManual journal approval logic and variance rationale not consistently documented; an agent would inherit undocumented decision patterns.
4/20
Evidence completenessSign-off evidence inconsistently retained and not standardised across the close team; evidence is outside the system of record.
5/20
Escalation formalityNo structured escalation path exists for close exceptions or adjustment disputes; escalation is entirely informal.
3/20
Exception structureClose activities exist operationally but no reliable runbook defines sequence, owners, deadlines, or exception handling.
7/20
Human override coverageNo deputy reviewer coverage; the close is critically dependent on one or two individuals with no succession plan.
2/20
Agent Readiness Index
21/100No AI
AI CONTROL BOUNDARY
WHAT THE AGENT CAN SEE
·Close calendar and task list
·Reconciliation schedules
·Manual journal entry listings
·Variance commentary drafts
·Prior close checklists
·Balance sheet reconciliation status
·Approval workflow status
·Supporting documents
·Evidence attachments
·Open close exceptions
·Late journal logs
·Reviewer assignment data
·Reporting timetable
·Prior period variance explanations
WHAT THE AGENT CAN DECIDE
·Missing evidence required
·Incomplete reconciliation support
·Unreviewed manual journals
·Draft runbook steps
·Recommended close task owner
·Recommended escalation trigger
·Likely variance commentary category
·Potential duplicate or unsupported journal pattern
·Whether a reconciliation requires human review before sign-off
·Whether close documentation is incomplete
WHAT THE AGENT CAN CHANGE
·Draft close runbook text
·Draft reconciliation checklist
·Draft variance commentary
·Suggested evidence checklist
·Suggested escalation note
·Risk flag recommendation
·Suggested next action only (recommend only — cannot execute close action)
WHAT THE AGENT MUST ESCALATE
·Any unsupported manual journal entry
·Any journal posted after cut-off
·Any reconciliation without independent review
·Any missing sign-off evidence
·Any balance sheet reconciliation discrepancy
·Any variance lacking explanation
·Any material reporting adjustment
·Any close task owned by a single unavailable person
·Any recurring late adjustment pattern
·Any unresolved close exception
·Any attempt to bypass review
·Any case requiring accounting judgement
WHAT THE AGENT MUST RETAIN
·Input data used for recommendation
·Documentation gap identified
·Evidence reviewed
·Evidence missing
·Confidence score
·Recommended owner
·Escalation reason
·Human reviewer identity
·Final human decision outcome
·Timestamped audit trail
·Any overridden recommendation and reason
·Close checklist draft and approval record
·Variance commentary draft and approval record
PROHIBITED ACTIONS
✕Manual journal posting
✕Manual journal approval
✕Reconciliation sign-off
✕Balance adjustment
✕Period close execution
✕Reporting pack submission
✕Cut-off override
✕Late journal approval
✕Variance approval
✕Independent review replacement
✕Suppression of close exceptions
✕Control alert suppression
✕Autonomous action on incomplete evidence
✕Any accounting judgement without human approval
WHAT THE AGENT MUST NOT LEARN FROM
⊘Prior close shortcuts used under deadline pressure
⊘Manual journal workarounds without documented rationale
⊘Single-reviewer approval patterns
⊘Undocumented variance explanations
⊘Late adjustments made outside governed cut-off
⊘One-off reporting accommodations
⊘Decisions made during compressed close windows without evidence
DECISION REGISTER
DECISION
ACCOUNTABLE OWNER
HUMAN TODAY
AI POTENTIAL
RISK
REQUIRED CONTROL
Classify close exception
Controller
Close Analyst
Medium
High
Human review sample and documented taxonomy
Identify missing reconciliation evidence
Close Lead
Close Analyst
High
Medium
Evidence checklist and reviewer confirmation
Draft variance commentary
Finance Manager
Close Analyst / Finance Manager
Medium
Medium
Human approval before use in reporting pack
Approve manual journal
Controller
Controller / Finance Manager
None
Critical
Not permitted for agent
Post manual journal
Finance Manager
Finance / GL Accountant
None
Critical
Prohibited for close agent
Sign off reconciliation
Controller
Reviewer / Controller
None
Critical
Independent human review required
Accountable Owner is the human role who bears final accountability if an agent-assisted decision causes a control failure.
AGENT FAILURE SCENARIO
If the agent fails here, these are the operational, control, and audit consequences.
FAILURE SCENARIO

A Close / Reconciliation agent recommends that a reconciliation is ready for sign-off because the balance agrees to source data, without identifying that a late manual journal was posted outside cut-off, lacks independent review, and has no documented variance rationale.

POTENTIAL IMPACT
✕Incorrect reconciliation sign-off
✕Late adjustment enters reporting without governed review
✕Material reporting error
✕Audit evidence failure
✕Variance explanation cannot be reconstructed
✕Compressed close timeline becomes further delayed
✕Manual rework by Finance and Reporting teams
✕Loss of confidence in AI-assisted close activity
REQUIRED SAFEGUARDS
✓No operational close agent until runbook is documented
✓Human approval required for all manual journal activity
✓Independent review required before reconciliation sign-off
✓Late journal cut-off rule enforced
✓Mandatory evidence capture before any recommendation is surfaced
✓High-value or material adjustment escalation
✓Confidence threshold gate for all close recommendations
✓Complete audit trail retained for every recommendation and human decision
✓Post-incident review for unsupported journal or reconciliation failures
LICENCE VERDICT

Close / Reconciliation is not approved for operational AI agent use. AI may assist only with documentation support, evidence-gap identification, checklist drafting, and variance commentary preparation for human review.

TO PROGRESS FROM
No AI
TO
Human-in-the-Loop Required
MERIDIAN REQUIRES:
Documented close runbook
Named owners for all close tasks
Deputy reviewer coverage for all critical roles
Independent review workflow for manual journals
Standardised reconciliation evidence requirements
Decision-level audit trail for close judgements
Why this score
What is being measured
The Agent Readiness Index measures whether this process can safely support AI agent operation, scored across five control dimensions — decision traceability, evidence completeness, escalation formality, exception structure, and human override coverage — each 0–20. It answers a prior question to tool selection: where is AI safe to operate?
What drives the score
The score is held down by Decision traceability, Evidence completeness, Escalation formality, Exception structure and Human override coverage. Each dimension measures a precondition for delegating decisions to an agent — where a dimension is weak, the corresponding class of agent action must remain restricted or human-approved.
What this score means here
At 21, Close / reconciliation cannot support AI agents in any capacity. The process lacks the decision traceability and evidence structure needed even to supervise an agent, let alone trust one. The licence verdict is No AI.
What needs to change next
Build the preconditions before any agent conversation: decision traceability and a minimum evidence standard first. The path to a licence starts at process structure, not model selection.
KEY PERSON DEPENDENCY
KPDI SCORE
91
critical risk
CONCENTRATION
critical
5 critical factors
PRIMARY FACTOR
Single reviewer controls entire close cycle with no deputy or documented runbook
DEPENDENCY RISK ASSESSMENT

The month-end close process is critically dependent on one or two individuals who hold undocumented process knowledge, approval authority, and decision logic for manual journal entries. No runbook exists. No deputy has been designated. Loss of a key person during close would halt the process entirely and create material reporting risk.

This process carries critical key-person dependency risk. Loss of a key individual would cause immediate operational disruption and is likely to accelerate governance deterioration.
Why this score
What is being measured
The Key Person Dependency Index measures how much of this process's correct operation depends on knowledge held by specific individuals rather than encoded in the process itself. Higher is worse.
What drives the score
The index rises wherever decision criteria, exception judgement, or institutional context live in individual memory instead of documented, enforced process — undocumented approval logic, tribal knowledge of exceptions, and single-owner reconciliations.
What this score means here
At 91, Close / reconciliation is a single-point-of-failure process. Its effective controls exist only in the heads of specific individuals. A resignation, illness, or reorganisation doesn't degrade this process — it decapitates it. The exposure attributable to key-person risk in this process is estimated at €341k annually.
What needs to change next
Treat this as an active continuity risk: immediately document the decision logic held by key individuals and embed it into enforced process controls. This must precede any automation — an agent cannot inherit knowledge that was never written down.
Knowledge Documentationcritical
82/ 100
No close runbook exists. Process sequence, deadlines, and escalation paths are held entirely in individual memory.
Decision Rule Capturecritical
91/ 100
Manual journal adjustment logic, variance thresholds, and sign-off rationale are entirely undocumented.
Deputy Coveragecritical
95/ 100
No deputy designated for any critical close role. Single reviewer controls entire sign-off process.
Process Concentrationcritical
93/ 100
Close cycle entirely dependent on one primary reviewer. No distribution of critical close knowledge across team.
Succession Riskcritical
96/ 100
Extreme succession risk — reviewer absence during close window would halt the process and create material reporting failure.
GOVERNANCE COST CALCULATOR
Estimated annual cost of current governance conditions, and projected saving from full remediation.
Annual revenue:
GOV gap 51AIFP 84%KPDI 91Revenue band €250M
ANNUAL GOVERNANCE COST
€1.4M
Estimated annual cost across rework, failed automation, and dependency exposure
PRIMARY FINANCIAL EXPOSURE
Automation Exposure
€735k53% of total governance cost
AFTER REMEDIATION
€780k
projected annual cost
POTENTIAL SAVING
€615k
REDUCTION
44%
GOVERNANCE DEBT
€319k→ €175k
23% of total
Rework, exception handling, audit prep, decision latency
€144k recoverable
AUTOMATION EXPOSURE
€735k→ €455k
53% of total
Cost of deploying automation into ungoverned processes
€280k recoverable
KEY PERSON RISK
€341k→ €150k
24% of total
Disruption cost if critical personnel are unavailable
€191k recoverable
Estimates derived from governance gap, automation failure probability, and key-person dependency scores relative to annual revenue. Order-of-magnitude model — not a financial audit.
REMEDIATION SEQUENCING
Ranked remediation actions by payback speed. Implement in sequence to maximise governance recovery per euro invested.
TOTAL IMPLEMENTATION COST
€44k
across 4 actions
TOTAL ANNUAL BENEFIT
€515k
governance cost reduction
BLENDED PAYBACK
1m
average across all actions
1
Document the close runbookLow effortGovernance
Capture step-by-step close sequence, owners, deadlines, and escalation paths in a single accessible format.
IMPL. COST
€10k
ANNUAL BENEFIT
€185k
PAYBACK
1m
ROI
1850%
SCORE IMPACT
GOV+8
GDI-12
AIFP-10
KPDI-20
2
Enforce cut-off disciplineLow effortDrift
Define and communicate hard cut-off — route all late journals through a governed exception process.
IMPL. COST
€8k
ANNUAL BENEFIT
€110k
PAYBACK
1m
ROI
1375%
SCORE IMPACT
GOV+5
GDI-8
AIFP-7
KPDI-4
3
Standardise variance commentaryLow effortAutomation
Introduce templates for common variance types to reduce preparation time and improve consistency.
IMPL. COST
€6k
ANNUAL BENEFIT
€75k
PAYBACK
1m
ROI
1250%
SCORE IMPACT
GOV+4
GDI-5
AIFP-6
KPDI-3
4
Build deputy reviewer coverageMedium effortDependency
Train and designate deputies for all critical sign-off points to remove single-person dependency.
IMPL. COST
€20k
ANNUAL BENEFIT
€145k
PAYBACK
2m
ROI
725%
SCORE IMPACT
GOV+6
GDI-7
AIFP-9
KPDI-24
Implementation costs and benefit estimates are directional. Actual outcomes depend on process complexity, team capacity, and execution quality.
SCENARIO INVESTMENT CASE
Projected financial return from fully implementing all remediation actions for this process.
TOTAL INVESTMENT
€44k
across 4 actions
ANNUAL BENEFIT
€515k
governance cost reduction
PAYBACK PERIOD
1m
blended across all actions
3-YEAR NET VALUE
€1.5M
after implementation costs
3-YEAR ROI
3411%
return on investment
INVESTMENT SUMMARY

An investment of €44k is projected to reduce annual governance cost by €515k, generating approximately €1.5M in net value over three years. The remediation programme reaches payback within 1 month. The highest-return action is Document the close runbook (€10k investment, €185k annual benefit), which should be prioritised first.

GOVERNANCE DIGITAL TWIN
Model the governance outcome under three funding decisions. All projections derive from this scenario's remediation data.
SCENARIO A
Fund Top 2 Actions
Document the close runbook + Enforce cut-off discipline
INVESTMENT
€18k
PAYBACK
1m
METRIC PROJECTIONS
Governance score49→62Developing
Automation risk (AIFP)84%→67%
Key person dependency91→67
ANNUAL GOVERNANCE COST
€1.4M→€1.1M
€320k annual saving
SCENARIO B · RECOMMENDED
Full Remediation
All 4 actions · complete programme
INVESTMENT
€44k
PAYBACK
1m
METRIC PROJECTIONS
Governance score49→72Governed
Automation risk (AIFP)84%→52%
Key person dependency91→40
ANNUAL GOVERNANCE COST
€1.4M→€780k
€615k annual saving
SCENARIO C · RISK PATH
Automate Without Remediation
€0 governance investment · automation deployed on ungoverned substrate
INVESTMENT
€0
PAYBACK
None
METRIC PROJECTIONS (6-month drift)
Governance score49→47Fragile
Automation risk (AIFP)84%→100%
Key person dependency91→91unchanged
ANNUAL GOVERNANCE COST
€1.4M→€1.5M
+€153k additional annual exposure
TWIN SUMMARY
Funding the top 2 actions (€18k) captures approximately 52% of the full programme saving at 41% of the cost. Automating without remediation adds an estimated €153k in annual exposure as automation failure risk compounds on ungoverned processes.
Digital Twin projections are scenario models derived from remediation impact data. Actual outcomes depend on execution quality and organisational context.
AUTOMATION BLUEPRINT
For each remediation action: implementation objective, governance prerequisites, recommended tooling, implementation pattern, and safe-to-automate conditions.
1
Document the close runbook
Low effort2–3 weeksOwner: Financial Controller / Close Manager
IMPLEMENTATION OBJECTIVE
Capture the complete close sequence — steps, owners, deadlines, and escalation paths — in a single accessible document that removes reliance on institutional memory.
RECOMMENDED TOOLING
Document Control
ConfluenceSharePointNotion
GOVERNANCE PREREQUISITES
▸Close process fully mapped
▸All owners identified
▸Deadlines confirmed with controller
IMPLEMENTATION PATTERN
1
Close period opens
2
Runbook distributed to all owners
3
Steps completed in sequence
4
Completion confirmed by each owner
5
Controller sign-off obtained
6
Runbook updated post-close if issues identified
✓ SAFE TO AUTOMATE AFTER
✓Runbook used for minimum two full close cycles
✓No steps completed outside documented sequence
✓Close completed on time using runbook without controller intervention
PREREQUISITES CHECKLIST
All close steps documented
Owners and deputies named
Deadlines agreed
Escalation contacts listed
Runbook published and version-controlled
2
Enforce cut-off discipline
Low effort2–4 weeksOwner: Financial Controller / Close Manager
IMPLEMENTATION OBJECTIVE
Define and communicate a hard cut-off for late journals, routing all post-cutoff entries through a governed exception process with documented rationale and controller approval.
RECOMMENDED TOOLING
Workflow Automation
SAP Business WorkflowPower AutomateOracle Workflow
GOVERNANCE PREREQUISITES
▸Cut-off time agreed and communicated
▸Exception process defined
▸Controller approval authority confirmed
IMPLEMENTATION PATTERN
1
Cut-off deadline reached
2
Late journal attempt blocked in system
3
Exception request raised
4
Business rationale provided
5
Controller approval obtained
6
Journal posted with exception code
7
Exception reported post-close
✓ SAFE TO AUTOMATE AFTER
✓Cut-off enforced in system for minimum two close cycles
✓All late journals processed via exception workflow
✓Late journal rate trending down
PREREQUISITES CHECKLIST
Cut-off time defined and system-enforced
Exception request form created
Approval workflow configured
Finance team communicated and trained
3
Standardise variance commentary
Low effort1–3 weeksOwner: Management Accountant / Close Lead
IMPLEMENTATION OBJECTIVE
Introduce structured variance commentary templates for common variance types to reduce preparation time, improve consistency, and support audit readiness.
RECOMMENDED TOOLING
Document Control
ConfluenceSharePointGoogle Workspace
GOVERNANCE PREREQUISITES
▸Variance types catalogued
▸Template structure agreed
▸Reviewer expectations defined
IMPLEMENTATION PATTERN
1
Variance identified
2
Template selected by type
3
Commentary prepared using template
4
Peer review completed
5
Commentary submitted to controller
6
Controller sign-off
7
Archived with close pack
✓ SAFE TO AUTOMATE AFTER
✓Templates used for 100% of variances above materiality threshold
✓Commentary quality reviewed and confirmed adequate by controller
✓Variance commentary completed within SLA for two consecutive closes
PREREQUISITES CHECKLIST
Templates created for top 10 variance types
Peer review process defined
Team trained on template use
Templates accessible in close workspace
4
Build deputy reviewer coverage
Medium effort4–6 weeksOwner: Financial Controller
IMPLEMENTATION OBJECTIVE
Train and designate deputies for all critical sign-off points to remove single-person dependency and ensure close continuity during absence.
RECOMMENDED TOOLING
Document Control
SharePointConfluenceHRMS
GOVERNANCE PREREQUISITES
▸Critical sign-off points identified
▸Deputy candidates available and willing
▸Training plan agreed
IMPLEMENTATION PATTERN
1
Close starts
2
Primary sign-off holder absent
3
Deputy identified from register
4
Deputy accesses runbook and sign-off instructions
5
Sign-off completed
6
Incident log updated
7
Handback on return
✓ SAFE TO AUTOMATE AFTER
✓Deputy coverage in place for all critical sign-off points
✓Deputy successfully completed sign-off during absence
✓No unresolved single-person dependencies in close process
PREREQUISITES CHECKLIST
Deputy register complete for all sign-off points
Cross-training completed
Deputies have system access
Deputy performance tested in dry run
Tool recommendations are indicative. Final selection depends on existing technology stack, licensing, and implementation capacity. Safe-to-automate conditions are governance readiness gates, not technical prerequisites.
NEXT STEP
Architecture Blueprint
Target operating model, recommended tool stack, delivery roadmap, and automation readiness gates for Close / reconciliation.
View Architecture Blueprint →
90-DAY PRIORITIES — CLOSE / RECONCILIATION
1
Document the close runbook
Capture step-by-step close sequence, owners, deadlines, and escalation paths in a single accessible format.
2
Enforce cut-off discipline
Define and communicate hard cut-off — route all late journals through a governed exception process.
3
Build deputy reviewer coverage
Train and designate deputies for all critical sign-off points to remove single-person dependency.
4
Standardise variance commentary
Introduce templates for common variance types to reduce preparation time and improve consistency.
SCORECARD
49
Fragile
Foundational governance gaps. Remediation required before any automation.
Documented flow fidelity49/100
Documented process diverges materially from actual exception path.
Audit trail completeness43/100
Approvals and overrides often happen outside core systems.
Automation suitability57/100
Useful automation possible, but governance gaps need attention first.
Operational resilience46/100
Key knowledge remains concentrated in individuals and side channels.
Northstar Components · Meridian Governance Intelligence Report · Close / reconciliation · 10 September 2026 · Confidential