Scenarios and versions
Base, optimistic and conservative, with versions that are cloned, submitted, returned, approved, activated and locked.
Formulate by scenarios and versions with monthly distribution, approve it through a clear lifecycle and lock it. Execution is captured from purchases, and every variance takes you down to the purchase document that caused it.
Without MKA
What you’ll measure
Sample indicators with illustrative data. In MKA they are computed live from your operation.
Try it right here
Finance compares the approved version with the reformulation; in "Execution" tap the red line and the purchases that pushed it over appear. The maintenance lead requests a transfer and management approves it: the variance adjusts. "Watch it run" plays it.
Example flow
The cycle opens with base, optimistic and conservative scenarios.
Benefits
Base, optimistic and conservative, with versions that are cloned, submitted, returned, approved, activated and locked.
Each line is spread by month, by hand or with the CSV import wizard.
Differences per line and in totals between two versions.
Execution snapshots with automatic capture from purchases.
From a line’s variance down to the purchase documents.
Transfers between lines and reformulations go through approval.
In detail
All-in-One
Data flows between modules on its own: no integrations, no exporting or importing.
An active version is locked; changes go through line transfers or reformulations that require approval.
They are captured as snapshots, including automatic capture from purchases, and every variance lets you drill down to the purchase documents.
More in Analytics & strategy
In 30 minutes we walk through your real flow: from sale to invoice, from stock to journal entry.