FI / FICOadvanced

FICO Period-End Closing Part 6: Advanced Financial Closing — Orchestration, Dependencies and Evidence

Key takeaway

Orchestrate the close with tooling: task lists and templates, dependencies and scheduling of programs, manual tasks with approvals, monitoring across systems, and audit-ready evidence — the concepts behind SAP's closing cockpit and advanced financial closing solutions.

Explanation

📌 KEY POINTS
✅ Close templates define tasks, owners, programs with variants and dependencies.
✅ Task lists are generated per period and company code; automated tasks run when predecessors finish.
✅ Manual tasks capture completion, comments and approvals.
✅ Monitoring shows status across entities and systems; logs and approvals form evidence.
⚠️ A template that nobody maintains drifts from reality — review it after each close.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 5 covered judgment tasks. Now orchestration.

━━━━━━━━━━━━━━━━━━━━
▶ 1. TEMPLATES

Task hierarchy by entity; programs and variants.

━━━━━━━━━━━━━━━━━━━━
▶ 2. DEPENDENCIES

Predecessors; automatic start.

━━━━━━━━━━━━━━━━━━━━
▶ 3. MANUAL TASKS AND APPROVALS

Checklists, evidence upload, approval steps.

━━━━━━━━━━━━━━━━━━━━
▶ 4. MONITORING

Status dashboard; error handling.

━━━━━━━━━━━━━━━━━━━━
▶ 5. CONTINUOUS IMPROVEMENT

Template updates; KPIs.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Build a template for one company code.
Add dependencies and approvals.
Run a close and review the monitor.

✅ CHECKPOINT: each task shows status, owner and evidence.

Code example

ABAP Code

===== TEMPLATE EXAMPLE =====Company code 1010: [AFAB] → [FAGL_FCV] → [FAGLF101] → [KSU5] → [KO88] → [Review TB] (manual, approval) → [OB52 close]Each program: variant, predecessor, responsible, evidence (log) ===== MONITOR =====Status: planned / released / in process / completed / error

Real project scenario

A company used an orchestration template but ran settlements before allocations due to missing dependencies. Adding predecessors fixed the order, and error notifications cut waiting time.

Common mistakes

Missing dependencies.
Unmaintained templates.
No approvals.
Ignoring errors.
Orchestrating everything at once.

Best practices

Model dependencies.
Review templates.
Approvals for key tasks.
Error alerts.
Start with bottlenecks.

Interview angle

Questions: "What is close orchestration?", "How are dependencies modeled?", "What evidence do auditors need?"
Strong answer: templates, dependencies, manual tasks/approvals, monitoring, improvement.

Practice this lesson

Quick check

1. Why review close templates after each period?

2. In close orchestration, what prevents a program from running on incomplete data?

3. What forms audit evidence in an orchestrated close?

Interview questions

1. What are the most important design decisions, trade-offs, and best practices in Period-End Closing?

Answer it in your own words first, then compare.

2. How would you implement close orchestration with dependencies and audit evidence?