For Corporate FP&A & Accounting

Explain forecast changes, mark review status, and pressure-test close-cycle assumptions.

Know why the forecast moved before the close meeting starts.

Same product, every capabilityHonest evidence boundaries

Workflow stack

  1. Compare Previous Version + MCI for forecast deltas
  2. Why This Number for the selected cell proof chain
  3. Audit Trail / Mark Cell for close-cycle review status
  4. Sensitivity + Model Health for driver testing and diagnostics

Handoff

A comparison/MCI explanation, audit-status sidecar, sensitivity output, signed certificate envelope or Evidence Pack for ledger state, and signed replay envelope when a changed output needs evidence.

These workflows explain workbook movement and review status. They do not replace accounting judgement, approval policy, or external audit.

Workflow proof

Each promise maps to commands, context, result, artifact, and limit.

No demo placeholder. These panels describe the actual command stack and the output a reviewer or model owner can expect to see.

  1. Answer why the forecast moved

    Situation

    A CFO or controller asks why revenue, EBITDA, cash, covenant headroom, or another forecast line changed since the last file.

    Commands used
    ModelXcel ProCompareCompare to Previous Version
    Compare ResultsExplain Output ChangeMCI
    ModelXcel ProProofWhy This NumberKeytipWN
    What the user sees
    • Prior-version selection, grouped changes, ranked drivers, dependency path, proof chain, and trust verdicts for the selected output.
    • Routes into TrustLens, review issues, audit marks, or export where the result needs follow-up.
    Output artifact

    MCI explanation report plus proof-chain context for the selected cell.

    Caveat / limit

    The tools explain workbook movement and proof state; they do not decide whether the business explanation is complete.

    Open related docs →

  2. Keep close-cycle review status attached to the workbook

    Situation

    Reviewers need to mark cells verified, questionable, or erroneous across weekly or monthly cycles.

    Commands used
    ModelXcel ProAuditAudit TrailKeytipAT
    ModelXcel ProAuditMark CellKeytipMC
    ModelXcel ProAuditHighlight AuditKeytipHA
    What the user sees
    • Cell statuses, reviewer notes, coverage summaries, and a toggleable color layer for reviewed cells.
    • A persistent audit trail loaded with the workbook path.
    Output artifact

    .mxaudit sidecar and optional audit-status workbook report.

    Caveat / limit

    The sidecar must travel with the workbook. A verified mark records reviewer judgement; it does not make the underlying number correct.

    Open related docs →

  3. Pressure-test assumptions before the meeting

    Situation

    The team needs a quick read on which assumptions matter and which workbook areas are risky.

    Commands used
    ModelXcel ProFormula ToolsSensitivityKeytipSAShortcutCtrl+Shift+S
    ModelXcel ProAuditModel HealthKeytipMH
    What the user sees
    • Sensitivity bars and copied data for selected outputs.
    • Formula counts, complexity distribution, error breakdown, volatile flags, hardcodes, and other model-health diagnostics.
    Output artifact

    Sensitivity data plus Model Health report for the close pack or internal review file.

    Caveat / limit

    Sensitivity is perturbation analysis and Model Health is diagnostics. Neither proves the forecast is right.

    Open related docs →

  4. Export proof when an output movement needs evidence

    Situation

    A changed number needs support beyond a verbal explanation or screenshot.

    Commands used
    ModelXcel ProProofReplay ProofKeytipRP
    ModelXcel ProProofCertificateKeytipCT
    What the user sees
    • Replay status, ranked changed drivers, residual, warnings, and export options.
    • Certificate coverage, ledger verdict, bindings, signatures, and signed blocks.
    Output artifact

    .mxreplay.signed for the selected output delta; .mxcert.signed or Evidence Pack for workbook proof-state handoff.

    Caveat / limit

    Replay Proof reconciles identified drivers under proof settings. Certificate covers ledger state; Replay Proof covers a specific output movement. Signed identities are self-asserted.

    Open related docs →

Outputs

Artifacts this workflow can hand off.

The artifact matters because the claim matters. A sidecar, certificate snapshot, map workbook, comparison packet, and signed replay envelope all prove different things.

Typical Corporate FP&A handoff set
  • MCI explanation reportForecast variance supportRanked drivers, dependency paths, residual, and links back into review actions.
  • .mxauditReview sidecarPersistent audit statuses and reviewer context that travel beside the workbook.
  • Sensitivity Copy DataMeeting packetRanked driver impact data for the chosen output metrics.

How to read the evidence

Useful, specific, and bounded.

What you seeCompare Previous Version + MCI for forecast deltas
What it meansThe page starts with the job this persona runs most often, not a generic feature pitch.
What to do nextOpen the matching workflow panel and inspect the command list before promising an outcome.
What you seeA comparison/MCI explanation, audit-status sidecar, sensitivity output, signed certificate envelope or Evidence Pack for ledger state, and signed replay envelope when a changed output needs evidence.
What it meansThe handoff is a package of evidence, not a blanket certification of the workbook.
What to do nextThese workflows explain workbook movement and review status. They do not replace accounting judgement, approval policy, or external audit.
What you seeCertificate, coverage, heatmap, issue set, or signed replay.
What it meansEach artifact answers a different review question.
What to do nextUse Certificate for proof-state snapshots and .mxreplay.signed only for externally verifiable output-delta replay.

Compare other use cases

Investment Banking & PEMove from inherited model review to client-ready handoff evidence.Project Finance & PPPKeep long-tenor infrastructure models navigable, source-bound, and change-aware.Audit & AssuranceDefine review scope, track issues, verify proof state, and export workpaper-ready evidence.