← Back to catalogue
Published

Budget, responsibility center and funding

EM-FIN-01 · em-fin-01

Funds plan, scenarios, limits, cost centers and responsibility. An organizational unit is not required to coincide with a financial center.

Enterprise profiles Enterprise subject EnterpriseFIN

Bundle → Layer → Finding → Questions Filled

2 bundles · 3 layers · 4 findings · 10 questions

Budget Planned funds, their versions and scenarios.

Budget versions

Original budget, revisions, forecasts and scenarios.

Budget version

A dated version with period and currency.

  1. Which budget version, period and currency does the figure belong to?
  2. How do the original budget, the latest forecast and the actuals compare?

Scenario

Alternative plans kept apart from the approved budget.

  1. Is this figure from an approved budget or from a scenario?
  2. Who approved the version now in force?
Responsibility and funding Who answers for funds and where they come from.

Cost centres

Financial responsibility centres and their history.

Cost centre identity

A cost centre as distinct from an organisational unit.

  1. Which cost centre carries the spend, and who is responsible for it?
  2. Does the cost centre match an organisational unit, or differ from it?
  3. How did a reorganisation affect the cost centre without changing past expenses?

Funding allocation

Allocation of funds from sources to uses.

Allocation rule

Base and remainder rule of each allocation.

  1. Which funding sources finance this project, and in what shares?
  2. Which base and remainder rule does the allocation use?
  3. Is any amount counted twice across the funding matrix?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterpriseFIN
Industry
Cross-industry
Tags
EM-FIN-01W1subjectBudgetBudgetVersionCostCentreFundingAllocationBudgetScenario

What it is Filled

Funds plan, scenarios, limits, cost centers and responsibility. An organizational unit is not required to coincide with a financial center.

Why it exists Filled

Funds plan, scenarios, limits, cost centers and responsibility. An organizational unit is not required to coincide with a financial center.

Distinguishing features Filled

  • Every budget figure has a period and a currency and belongs to a specific version.
  • A new plan version never changes recorded actuals.
  • A cost centre is a financial responsibility unit and need not coincide with an organisational unit.
  • Each funding allocation states its base and how the remainder is treated.

What robots and AI may and may not do Filled

Must not

  • Rewrite past expenses of a new cost centre after a department moves.
  • Change actuals when a new budget version is approved.
  • Allocate funds without a stated base and remainder rule.
  • Approve spend above a limit on behalf of the budget holder.

Only with a human decision

  • Approving a budget version or a revision.
  • Moving funds between cost centres or funding sources.

May

  • Compare budget, forecast and actuals by version and cost centre.
  • Check funding allocations for double counting.
  • Report spend against limits for a responsibility centre.

Moral aspects Filled

  • Budget decisions affect jobs, services and suppliers, and must be traceable to a responsible person.
  • Misallocated restricted funding can breach obligations to funders.

Who is affected

  • Budget holders and their teams
  • Funders and grant providers
  • Finance staff

Owners Filled

Steward

The chief financial officer or finance lead who answers for books, budgets and reporting.

Master systems

  • ERP
  • Accounting system
  • Banking system
  • Billing system
  • FinOps platform

Links to other meta-models Filled

neighbor

  • EM-FIN-05
  • EM-ORG-02
  • EM-PRD-01
  • EM-WRK-02

references

  • WM-ECO-012 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by budget identifier and version, with cost centres by their code in the chart of cost centres.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition optional Filled

  • A budget record names a version, a period, a currency and cost centres.
  • Often confused with the organisational structure or with recorded actuals.

Capabilities and actions required Filled

  • History of plans, forecasts and actuals reconciles across reorganisations.
  • Multi-source funding can be traced to each use.

Hazards and failure modes required Filled

  • Restated history after reorganisations.
  • Double counting of funds across sources and projects.
  • Plans mistaken for actuals in reporting.

Standards and interfaces required Filled

  • ISO 4217 currency codes.
  • XBRL from XBRL International for tagged financial data.

Context of use required Filled

  • Used in planning, budgeting and grant management across the organisation.
  • Public and grant funding often carries legal conditions on use and reporting.

Sources Filled

  1. FIBO: instruments, parties, transactions
  2. UBL/FOCUS: documents and costs; choose by contour
  3. XBRL and ERP/accounting-policy practice: books, periods, recognition and disclosure
  4. EDM Council Financial Industry Business Ontology (FIBO) - Checked live (HTTP 200) on 2026-10-07.
  5. FinOps Open Cost and Usage Specification (FOCUS) - Checked live (HTTP 200) on 2026-10-07.
  6. XBRL Specifications - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • How to compare the original budget, the forecast and the actuals?
  • How to avoid double counting in the funding matrix?
  • How does a cost center survive a reorganization?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-fin-01/brief.json, ver-cy/world-models/card-supplements/em-fin-01.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.