Expenses
Plan operating costs from a source you don't maintain by hand.
Operating costs arrive from an accounting system, not from typing — the job is reading it correctly, not entering it.
Expenses works differently from Revenue and Headcount: its Master Data comes from an external source shown right on the page — DATEV GDPdU in this tenant — with a Last updated date and an Update button to pull in anything new. Generate expense object types turns that raw feed into planning objects. Contracts hold recurring obligations — rent, subscriptions — each with an Amount, Start date, Frequency and Status; a Transactions tab holds individual bookings, and a Projections tab holds what those contracts and transactions imply going forward.
The rule that separates Expenses from Headcount: a mid-year hire is a Headcount event, never an expense contract, because only Headcount carries the department and timing logic a hire needs.

- 1Chart split by department
- 2Merge plans and New plan — the same pattern as Revenue and Headcount
- 3Plan library
ValueWorks 2026.08

- 1Source and Last updated
- 2**Generate expense object types**
- 3A notice that data is pending update — press Update first
- 4Contracts, Transactions and Projections tabs
- 5The Contracts table — Amount, Frequency, Status and cost centre per contract
ValueWorks 2026.08
Takeaways
Expenses Master Data pulls from an external source — check Last updated and press Update before trusting it.
Contracts are recurring; Transactions are one-off; Projections is what they imply going forward.
A hire is always a Headcount event, never an expense contract.
Surfaces covered
- Liquidity
Also taught in the Academy
Module 6 · Liquidity and runway
Take it as lesson 6.6 in Business Analyst & FP&A