Skip to content
Budgeting

A budget that compares itself against actuals.

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

  • The budget lives in a spreadsheet with ten "final_final" versions.
  • Comparing budget to spend is a separate month-end close.
  • You see a line went over, but not which purchase pushed it over.

What you’ll measure

YTD execution
71,4 %+3,2 pts
of annual budget through September
Lines over budget
7−5
Total variance
Bs 186 K−Bs 94 K
Days to approve the version
12 días−9 días

Sample indicators with illustrative data. In MKA they are computed live from your operation.

Try it right here

Compare versions and drill into a variance.

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

From base scenario to monthly control

Step 1/6

Cycle and scenarios

The cycle opens with base, optimistic and conservative scenarios.

Benefits

Why Budgeting in MKA

Scenarios and versions

Base, optimistic and conservative, with versions that are cloned, submitted, returned, approved, activated and locked.

12-month distribution

Each line is spread by month, by hand or with the CSV import wizard.

Compare versions

Differences per line and in totals between two versions.

Actuals come from purchasing

Execution snapshots with automatic capture from purchases.

Variances down to the document

From a line’s variance down to the purchase documents.

Transfers with approval

Transfers between lines and reformulations go through approval.

In detail

Everything included

Formulation

  • Budget cycles
  • Base, optimistic and conservative scenarios
  • 12-month distribution per line
  • CSV import wizard

Versions and approval

  • Lifecycle: create → clone → submit → return → approve → activate → lock
  • Version comparison per line and in totals
  • Line transfers and reformulations with approval

Execution

  • Actual execution snapshots
  • Automatic capture from purchases
  • Variance analysis with drill-down to purchase documents

Collaboration and reports

  • Comments and attachments
  • Budget dashboard
  • Reports in CSV, PDF and Excel

All-in-One

Connects with

Data flows between modules on its own: no integrations, no exporting or importing.

FAQ

Can I change an approved budget?

An active version is locked; changes go through line transfers or reformulations that require approval.

Where do actuals come from?

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

See Budgeting with your data.

In 30 minutes we walk through your real flow: from sale to invoice, from stock to journal entry.