Budgets and cost centres in Skyline Nexus ERP

What cost centres and budgets do together

A cost centre is a unit of the business, such as a department, team or function, to which costs are charged so that one manager can be held responsible for them; a budget is the plan those costs are measured against. Together they answer the question every finance manager is asked: who spent what, against which plan, and why it differs.

The two only work if they are designed together. A budget set by account but not by cost centre tells you that marketing costs overran but not whose marketing. Cost centres without budgets tell you who spent but not whether it was too much. This guide explains how to design the structure, then shows how Skyline Nexus ERP records cost centres on ledger lines, builds and approves budgets, and reports budget against actual.

Cost centre, account, project or branch?

Four dimensions often compete for the same job, and mixing them up is the most common design error. An account says what the money was spent on: rent, salaries, advertising. A cost centre says who is responsible for it: the sales team, the warehouse, the finance department. A project says what piece of work it was for, with a start and an end. A branch says where it happened. In Skyline Nexus ERP each journal line can carry a cost centre and a project, and each journal header carries the business location, so all four can be recorded on one posting without multiplying accounts.

The test for a good design is that each dimension answers one question only. If you find accounts called Salaries - Sales and Salaries - Warehouse, the cost centre is hiding in the chart of accounts; one Salaries account with two cost centres gives the same information and keeps the chart short. Our guide on designing a chart of accounts covers the same principle from the account side.

Designing the cost centre tree

Cost centres follow responsibility, which is why the approach is called responsibility accounting. Draw the tree from the organisation chart, not from the chart of accounts: each cost centre should have one named manager who can influence its costs. Keep it shallow, typically two levels, departments and teams, and create a cost centre only when someone will read its report.

• Level 1: Sales, Operations, Finance and Administration, Marketing
• Level 2 under Operations: Warehouse, Transport, Customer Service
• One named manager per cost centre, recorded in the budget pack
• Shared costs such as rent kept on a central cost centre and allocated by a documented key
• Revenue can carry a cost centre too, turning a sales team into a profit centre

Setting up cost centres in Skyline Nexus ERP

Cost centres are switched on with Enable Cost Centers in the Accounting settings and managed under Fiscal Authority, Cost Centers, which offers a list and a tree view, create and edit, and tools to reassign lines from one cost centre to another or bulk-assign lines that were posted without one. Where a cost centre is mapped to a business location, automatically posted documents from that location pick it up, so branch-based cost centres fill themselves.

To make cost centres mandatory where they matter, tick Requires Cost Center on the account in the chart of accounts. A manual journal line on that account is then rejected without a cost centre, which stops expenses from arriving unallocated at month end. Apply the flag to the expense accounts that managers are budgeted on, and leave it off balance-sheet accounts, where it adds friction without insight.

Building a budget

Budgets are created under Fiscal Authority, Budgets, New Budget. The form asks for a Budget Name, the Fiscal Year, the Budget Type (annual, quarterly or monthly) and optionally a Cost Center, then Budget Lines per account across the year's periods. Distribute Evenly spreads an annual figure across the periods, which is convenient for steady costs such as software subscriptions. For anything seasonal, enter the amounts by period instead: an evenly spread budget for a cost that falls in one quarter produces months of false variances.

Large budgets are easier to prepare in a spreadsheet and import. Budgets import from XLSX, XLS or CSV files using the provided template, and they can be exported for review. One budget per cost centre, named consistently, such as FY Marketing or FY Warehouse, keeps the Budget vs Actual report readable.

Approving the budget

A budget is a commitment, so it should be approved, not just saved. In Skyline Nexus ERP a budget is saved as a draft with Save as Draft, sent for approval with Save and Submit, and then approved or rejected. The permissions to view budgets and to manage budgets are separate, so department managers can be given view access to follow their budgets while preparation and approval stay with finance or the owner.

Keep the approved version fixed. When circumstances change mid-year, record a reforecast as a separate budget rather than overwriting the approved one; otherwise variances disappear because the plan was quietly moved to meet the actual.

Worked example: a marketing budget for the first quarter

A Dutch software company budgets its Marketing cost centre at EUR 144,000 for the year: advertising 96,000, events 36,000 and software 12,000. Distributed evenly, that is 8,000, 3,000 and 1,000 a month, EUR 12,000 in total, so the first-quarter budget is EUR 36,000. Actual spending in the quarter is advertising 27,500, events 4,000 and software 3,150, a total of EUR 34,650.

At total level, marketing is EUR 1,350 under budget and looks well controlled. By line, advertising is 3,500 over, software is 150 over, and events are 5,000 under only because the main trade fair is in September. The evenly distributed events budget turned a timing difference into an apparent saving that hides the advertising overspend. Phasing the events line, 4,000 in Q1 and the rest in Q3, would have shown Q1 events on budget and marketing 3,650 over, which is the conversation the manager actually needs to have.

• Advertising: budget 24,000, actual 27,500, over 3,500
• Events: budget 9,000, actual 4,000, under 5,000 (timing)
• Software: budget 3,000, actual 3,150, over 150
• Total: budget 36,000, actual 34,650, under 1,350
• Year-to-date utilisation of the annual budget: 34,650 / 144,000 = 24.1%
• With events phased at 4,000 for Q1: budget 31,000, actual 34,650, over 3,650

Allocating shared costs to cost centres

Some costs serve several cost centres at once: office rent, insurance, the finance system itself. Leaving them on a central cost centre is honest but makes departmental costs look lower than they are; allocating them gives managers a full-cost view but only if the key is fair and stable. Choose a key that reflects what drives the cost, document it in the budget pack, and budget the allocation too, so that budget and actual are compared on the same basis.

In Skyline Nexus ERP an allocation is a manual journal from New Journal Entry, with a Cost Center on each line. Suppose monthly rent of EUR 6,000 is posted to a central cost centre and allocated by floor area: the warehouse occupies 60%, sales 25% and finance 15%. The journal credits the rent account on the central cost centre with 6,000 and debits the same rent account on each departmental cost centre: 3,600, 1,500 and 900. The account balance does not change; only its split by cost centre does, which is exactly what an allocation should do.

• Dr Rent (Warehouse cost centre) 3,600
• Dr Rent (Sales cost centre) 1,500
• Dr Rent (Finance cost centre) 900
• Cr Rent (Central cost centre) 6,000
• Check: 3,600 + 1,500 + 900 = 6,000

Reading Budget vs Actual and Cost Center Analysis

The Budget vs Actual report under Fiscal Authority, Reports filters by Fiscal Year, Account and Cost Center and shows Total Budget, Actual Spent, the Variance marked Over or Under, and Utilization, with a trend chart and a status of Over Budget, Warning or On Track. Filter by cost centre for the manager's monthly pack and by account for the finance view across departments.

Cost Center Analysis, described as Analyze revenue and expenses across cost centers and departments, complements it by showing where revenue and costs sit across the tree, which is the view to use for allocations and for spotting costs posted to the wrong department. Look at both before the monthly review, and use the reassign tool to move misposted lines rather than explaining them away in the meeting.

Turning variances into decisions

A variance is a question, not an answer. Classify each significant variance before discussing it: timing, which will reverse; volume, where activity differed from plan; price, where costs per unit differed; or a genuine overspend. Only the last calls for corrective action, and each class calls for a different conversation. Set a threshold, such as 10% and EUR 1,000, below which variances are noted but not discussed, so the meeting spends its time on what matters.

Revenue-driven costs need a different comparison. If sales volume rose by 20%, packaging and shipping should have risen too, and comparing them with a fixed budget will flag an overspend that is actually efficiency. Our guide on budgeting and variance analysis explains flexible budgets and the price, volume and efficiency variances that make this comparison precise.

A monthly budget review cycle

Budgets change behaviour only when they are reviewed on a rhythm managers can rely on. A short, fixed monthly cycle, run straight after the period is soft-closed so the actuals no longer move, works for most businesses. Our guide on fiscal year and period close in Skyline Nexus ERP explains the close that should come first.

• Day 4 after month end: period soft-closed, actuals final
• Day 5: finance runs Budget vs Actual per cost centre and Cost Center Analysis
• Day 5: misposted lines corrected with reassign, not explained in the meeting
• Day 6: each manager comments on variances above the agreed threshold
• Day 7: owner or finance lead reviews Over Budget and Warning items
• Quarterly: reforecast saved as a separate budget; the approved budget kept unchanged

Common mistakes with budgets and cost centres

Most budget systems fail through a handful of recurring design and process errors rather than through the software. Each one below has an easy fix if it is caught at set-up.

• Cost centres created for every small team, so no report is ever read
• Expense accounts without Requires Cost Center, leaving costs unallocated
• Seasonal costs budgeted with Distribute Evenly, producing false variances
• The approved budget overwritten by a reforecast, so variances vanish
• Shared costs split by an undocumented key that changes each month
• Budgets owned by finance rather than by the manager accountable for the cost
• Variances discussed in total rather than line by line