Cost & Profit Centers
Can we model our controlling structure — who is responsible for which costs and results?
Cost centers and profit centers are maintained as structured master data: each carries a unique reference, a validity window, its controlling area, department, category, and the user and person responsible for it. Cost centers link to the profit center they roll up to.
Referenced across3 other parts of continON
How it works
A cost center record holds its name and reference, a validity from/to window, controlling area, department, cost-center category, currency, hierarchy, functional, and business area assignments, the responsible user and person, and its linked profit center. Profit centers carry the same discipline on the results side — reference, validity, controlling area, status, category, segment, department, and responsibility.
Today these records serve as the controlling structure of the organization: they name the units, responsibilities, and rollups your finance conversations happen in. Individual ledger rows are not tagged with a cost or profit center, so center-level profit-and-loss segmentation of transactions is not something the current product computes — plan the master data as structure and responsibility mapping, not as a transactional P&L cube.
What the table carries
| # | Maintained | Resolved against it |
|---|---|---|
| 01 | Cost center master record | Reference, validity window, controlling area, department, category, currency, area assignments, responsible user and person, and linked profit center. |
| 02 | Profit center master record | Reference, validity, controlling area, status, category, segment, department, and responsibility on the results side. |
| 03 | Validity windows | Centers are valid from/to dates, so reorganizations are modeled as records rather than overwritten names. |
| 04 | Responsibility, named | Every center names the user and person responsible — the same people the organization model already knows. |
What this touches
See cost & profit centers running in continON.
A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.