Budget, responsibility center and funding
Funds plan, scenarios, limits, cost centers and responsibility. An organizational unit is not required to coincide with a financial center.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
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 Derived, awaiting review
- Period and currency are mandatory
- A plan version does not change the actuals
- An allocation has a base and a remainder rule
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: Moving a department rewrites the past expenses of the new center.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
Финансовый руководитель
Master systems
- ERP
- бухгалтерия
- банк
- биллинг
- FinOps
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 Incomplete
Identity and identifiers required Derived, awaiting review
- Budget
- BudgetVersion
- CostCentre
- FundingAllocation
- BudgetScenario
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- FIBO: instruments, parties, transactions
- UBL/FOCUS: documents and costs; choose by contour
- XBRL and ERP/accounting-policy practice: books, periods, recognition and disclosure
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
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.