Reference & Data Model
Cost event (cost_occurrence)
A cost event is a cost position that has actually been incurred; it is never changed or deleted, only reversed.
Purpose
Section titled “Purpose”Cost events form the cost journal of a cost item (project data). Entered manually or posted by the system from time approval, ordered purchase, stock withdrawal, occurred risks and measures. All actual-cost KPIs sum up this table.
Where in the app
Section titled “Where in the app”Detail view of the cost item › section „Kosten“ (Costs) › list „Ist-Buchungen“ (Cost events) with totals row, „+“ („Ist-Buchung hinzufügen“, Add cost event), context menu „Details“ / „Korrigieren“ (Correct). Double-click opens the dialog „Ist-Buchung“. See Guides › Financial performance.
Fields
Section titled “Fields”| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Amount | cost_value |
Amount | yes | Incurred costs; negative for reversals | locked after creation |
| Occurred on | occurred_at |
Date | yes | Posting date | locked after creation |
| Description | description |
Text | yes (may be empty) | Label | the only editable field of manual rows |
| Creation kind | generated_from_system |
Yes/No | yes | „Manuell“ (manual, blue) or „Systemgeneriert“ (system-generated, grey) | System |
| Source | rule_key, source_id |
Reference | no | Rule and source row | System; shown as text and link |
Relations
Section titled “Relations”| Related to | Kind | Required | On archive | On delete |
|---|---|---|---|---|
| Cost item | belongs to | yes | archived along | deleted along |
| Project | belongs to | yes | archived along | deleted along |
Rules & automation
Section titled “Rules & automation”- Journal principle: the server rejects every change to amount, date, cost item, project and source, as well as deletion. For manual rows only the description remains editable; system rows are completely locked.
- „Korrigieren“ (for manual and system rows): creates a reversal record with a negative amount, the same date and the description „Storno:
“; with „Korrigierte Buchung anlegen“ (Create corrected record) checked, additionally a new record with amount, date and description of your choice. Both rows are „Manuell“. The original stays. - Generating rules:
- Time log approved → „Personalkosten aus Zeiterfassung“ (personnel costs from time tracking), hours × hourly rate (project member, otherwise employee); only on the first approval (Rule)
- Purchase from „Bestellt“ (base class ordered or delivered) → „Materialkosten aus Einkauf“ (material costs from purchase), net amount; kept current, a void status („Storniert“, „Abgelehnt“, …) removes it (Rule)
- Stock request „Erledigt“ (done) → „Materialkosten aus Lagerentnahme“ (material costs from stock withdrawal); kept current, „Fehlgeschlagen“ (failed) removes it (Rule)
- Risk occurred (date and incurred damage set) → „Risiko eingetreten“ (risk occurred); once (Rule)
- Risk/opportunity measure on an occurred risk or occurred opportunity → „Risiko-Präventionsmaßnahme (System)“, „Risiko-Reaktionsmaßnahme (System)“, „Chancen-…“; kept in sync when the costs or status of the measure change (Rule)
Actual costs (card, column, scoreboard, server KPI projectActualCosts), total costs (= actual costs), profit, ROI, material costs, personnel costs, cost breakdown by category, AC in EVM. See Budget KPIs, Value KPIs, EVM.
See also
Section titled “See also”Planned cost · System-generated record · Guides › Log time → approve → project costs