Skip to content

Finance / AI use case

Understand numbers. Test explanations.

More text does not make a better report. Relevant changes and verifiable explanations do. NyxAI connects defined metrics with the underlying business records.

NyxAI · Workflow concept with illustrative examples

NYXAI / WORKFLOW CONCEPT
  1. 01

    Comparison data

    Actual + plan

    Period + definition

    Documented events

  2. 02

    Interpretation

    Calculated difference

    Relevant contribution

    Confirmed or open

  3. 03

    Report draft

    Prioritized variance

    Comment + source

    Focused review question

Visible sources. Approval within agreed boundaries.

The business question

Explaining the metric often takes more work than calculating it.

The dashboard shows a variance. Preparing the commentary still means aligning periods, finding one-off events and asking several departments what changed.

Different cut-off dates or metric definitions can put a convincing explanation on the wrong foundation. Calculation and interpretation need separate checks.

From input to output

How the workflow can work.

Calculations remain in approved queries, spreadsheets or an existing BI model. NyxAI adds preparation and links back to accessible records. The data timestamp, formula version and commentary sources stay attached to the result.

Required inputs
  • Approved actual, plan and comparison data with cut-off dates
  • Metric definitions, calculation rules and category mappings
  • Accessible transactions, orders or operational events providing context
  1. 01

    Establish comparability

    Check the period, unit, scope and data timestamp. Make inconsistent definitions or missing data deliveries visible before comparing figures.

  2. 02

    Calculate the change

    Defined formulas calculate variances and contributions by business area. The language model neither invents values nor chooses the calculation logic.

  3. 03

    Draft the commentary

    Connect documented events to the figures. Keep observations, possible explanations and confirmed causes distinct; assign unresolved questions to an owner.

The key review boundary

Events occurring together do not establish causation. Business owners confirm interpretations; finance owns the metrics and report release. Missing data is not hidden behind plausible commentary.

The resultA reviewable report draft with consistent figures, prioritized variances and source-linked commentary. The responsible teams address the real explanatory questions instead of repeating the underlying research.

One workflow. Three situations.

What changes when …?

Choose a situation and follow the handover. An illustration using fixed sample data, not live AI or a client project.

Choose an example situation
01 / Input

An example cost line exceeds plan. An approved additional service has a recorded amount and transaction reference.

02 / Check

Show the calculated contribution of that service and explain only the supported part of the variance.

03 / Handover

The commentary cites its source and explicitly leaves any remaining difference unresolved.

Ready for review

Start focused. Compare fairly.

What the pilot should be measured against.

Total reporting effort
Measure data reconciliation, commentary and professional corrections through to the approved version.
Reproducible figures
Check whether values and variances can be reconstructed from the recorded data snapshot and formula version.
Supported commentary
Assess evidenced statements, unresolved hypotheses and necessary corrections separately.

A practical initial scope

One recurring report, a small set of defined metrics and their accountable teams. Compare previous periods before preparing a current report alongside the existing process.

  • Agreed metric definitions and data snapshots
  • Earlier reports with reviewer corrections
  • Example events covering genuine and apparent variances

Agree acceptance criteria first

Figures must agree with approved calculations. Explanations are judged against evidence and domain review; faster drafting alone is not sufficient if verification creates more work.

Discuss a focused pilotThis use case will be selected in the enquiry form.

Common questions

Do we need a new BI system?

No. The approach can use existing models and reports. A pilot connects only the required metrics and authorized contextual records.

Does the language model calculate our metrics?

No. Defined formulas and queries provide the figures. Language models can retrieve relevant material and draft commentary whose claims are then checked.

Can the report be published automatically?

The described pilot produces a draft. Release, recipients and permissions are separate steps; internal details are not automatically distributed.