Cost centres, projects and budgets

Slicing results by department or project and comparing them with the plan.

Baca dalam Bahasa Indonesia

On this page
  1. Cost centres
  2. Projects
  3. How dimensions get onto journals
  4. Budgets
  5. Budget control on purchase orders
  6. Reporting by dimension
  7. Checklist

The chart of accounts tells you what money was spent on: salaries, electricity, spare parts. It does not tell you where or for what: which department, which production line, which customer project. Companies on spreadsheets often solve this by multiplying accounts ("Electricity – Plant 1", "Electricity – Plant 2", "Electricity – Office"), and within a year the chart of accounts has 600 lines and nobody can read it.

ERPs separate the two questions. The account stays generic, and the "where" is a second tag on each journal line called a dimension. SAP calls the main one a cost centre; others are projects, profit centres or segments.

Cost centres

A cost centre is a part of the organisation that is responsible for costs: a department (finance, sales, HR), a production line, a warehouse, a workshop. Each has a manager who answers for its spending.

Good cost centre design follows the organisation chart, not the chart of accounts:

  • One cost centre per unit that has a responsible manager and a budget.
  • A hierarchy, so you can roll up: Line A and Line B under Production, Production under Plant Cikarang.
  • Stable codes. Renaming is fine; reorganising codes every year destroys comparisons.
  • Not too fine. If a cost centre has three transactions a month, it probably belongs to its parent.

Then every expense posting carries a cost centre, and one account ("Electricity") produces a report by department.

Projects

A project is something with a start and an end that you want to see the full cost (and sometimes revenue) of: a customer engineering job, a plant expansion, an ERP implementation. Projects cut across cost centres: the expansion project uses people from engineering, purchasing and production.

The test for which dimension to use: if it lives forever and has a manager, it's a cost centre; if it finishes, it's a project.

How dimensions get onto journals

Dimensions are only useful if they're filled in consistently. The best practice is to default them from the source rather than asking people to type them:

  • A work centre belongs to a cost centre, so production postings inherit it.
  • A purchase order carries a cost centre (and a project), and its receipt and bill inherit it.
  • Manual journals let the accountant set them per line.

Budgets

A budget is the plan expressed in money: how much each cost centre expects to spend, per account, per month or for the year. Its value comes from comparing it with actuals regularly, so managers see an overrun while they can still do something about it.

A budget versus actual report for the maintenance department might look like this at the end of March:

AccountBudget Jan–Mar (Rp)Actual Jan–Mar (Rp)Variance (Rp)% used of year
Spare parts90,000,000112,000,000(22,000,000)31%
Contract services60,000,00041,000,00019,000,00017%
Electricity150,000,000148,500,0001,500,00025%

Spare parts are 24% over plan after a quarter. That is the conversation to have in April, not in December.

Practical rules:

  • Budget where you post. Use the same accounts and cost centres for the budget as for actual postings, or the comparison is meaningless.
  • Monthly phasing for seasonal costs. An annual amount spread evenly is fine for rent; it is misleading for anything seasonal, such as overtime before Lebaran.
  • Count commitments, not just actuals. An approved purchase order not yet received is money already promised. A budget check that ignores it lets managers overspend.
  • Freeze the approved version. Re-forecast separately; don't overwrite the budget every time reality changes, or there's nothing left to compare against.

Budget control on purchase orders

The strongest form of budget discipline is a check at the moment of commitment. Voltrus can check a purchase order when it moves from draft to approved: it adds actuals, other approved but unreceived POs (open commitments) and this PO, and compares the total with the annual budget for the PO's cost centre and its parents. The company setting Budget check on purchase orders decides what happens on an overrun:

SettingEffect
Off (default)No check
WarnThe PO is approved; the overrun is recorded in the audit trail
BlockThe approval is refused

Reporting by dimension

The question managers actually ask is "show me my P&L". Finance → P&L by cost centre or project answers it: pick a date range and switch between By cost centre and By project. Each row shows revenue, expense and net, cost centres also show the net including their children, and opening a row lists its accounts. Lines posted without a cost centre or project appear as Not assigned: if that row is large, dimensions are not being filled in at the source. Export to CSV or Excel for the monthly management pack, and use the journal browser for line-level detail.

Checklist

  • Draw your cost centre hierarchy from the organisation chart, with one manager per cost centre.
  • Use projects for anything with an end date; don't create accounts per project.
  • Set the cost centre on every work centre so production postings carry it automatically.
  • Load the year's budget per cost centre and account before January, phased monthly where costs are seasonal.
  • Review budget versus actual with each manager monthly.
  • Decide whether purchase orders should warn or block on a budget overrun, and set the budget check accordingly.
  • Review the Not assigned row of the P&L by cost centre each month and fix its source.

Run it in Voltrus ERP

Everything in these guides is built in: documents that post to the ledger as they happen, Indonesian tax, MRP and costing, with AI agents that propose and people who approve.

See Voltrus ERP