FCC Controls

Run FCCS metadata validation through the REST API and review results in place — catch metadata errors before they break a consolidation.

A dashboard for opening and closing journal periods.

An advanced journal manager: search, drill to the line, then submit, approve, post or unpost through the REST API. POV fields are backed by the application's own metadata. FCCS journals carry four statuses — there is no "rejected" state to look for.

Four tabs for the operations that otherwise live in separate cards of the web UI:

• IC Matching Report — run a saved Intercompany Matching Report definition for one period or a Year + Period range.
• Consolidation — launch consolidation runs from Excel.
• Data Profiles — Clear Data and Copy Data profiles.
• Rulesets — consolidation ruleset export and import.

What does not match between IC partners, and where it concentrates. Available from the Admin Console and as an FCC-only module of App Analysis Reports:

• Gross and net imbalance, a breakdown per plug group, the entities and partners carrying it, and unmatched pairs ranked largest first.
• One-sided breaks are separated from genuine disagreements — they are different problems with different owners.
• Runs over a period range with a range digest and a per-period appendix; parsed reports are cached, so extending a range is cheap.
• Computed, not model-written. The analysis is complete with no AI provider configured; with one, analyst commentary is added on top.

Three modules of App Analysis Reports appear only when connected to an FCCS application:

• Close Cycle — how the close actually runs, cycle by cycle: on-time completion, overruns, rejections, who carries the late work, and whether the close is getting faster or slower.
• Consolidation Design — an architecture review of what this implementation added to the seeded model, judged against FCC conventions rather than generic Essbase rules.
• Intercompany Matching — the analysis described above, as a report.