Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Allocating hosting costs across departments or clients: inventory, tags and chargeback

Technical article
Hosting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

To split a hosting bill fairly, start with an accurate list of every server and service, label each one with the department or client it serves, and agree in advance how shared items such as firewalls, backup and support are divided. Then decide whether to show each group its share for awareness or charge it back to their budget. Agree the rules for shared costs before the first split, and keep the inventory current, or the numbers will be argued over every month.

Why it matters

When one hosting bill pays for servers used by several departments, or a software vendor hosts several clients on shared infrastructure, someone eventually asks who is using what. Without agreed rules, the answer depends on who does the spreadsheet. With them, each group can see its cost, question it with evidence, and make better choices about what it keeps running.

How it works

What the FinOps Foundation describes

The FinOps Foundation, an industry body for cloud financial management, describes allocation as strategies "to assign and share cost and usage using accounts, tags, labels, and other metadata, creating accountability among teams and projects within an organization". Its activities include to "Define how to identify subsets of cost that are shared" and to "Define mechanisms to share costs for each shared cost item".

On methods, it notes: "Allocation of shared costs can be performed in a variety of ways including fixed allocations, proportional or by using proxy metrics to determine a variable proportion." The framework was written with public cloud in mind, but the same ideas apply to a managed hosting bill.

Labels

A label, or tag, attaches the owner to each item. Microsoft's Azure documentation gives one description: "Tags are metadata elements that you apply to your Azure resources. They are key-value pairs that help you identify resources based on settings that are relevant to your organization." Other platforms and hosting portals offer similar fields, or none; where none exist, the inventory spreadsheet holds the label instead.

What to choose and why

Build the inventory first

For each server or service, record: name, purpose, owner (department or client), environment (production, test), size, and the line on the bill it appears in. Reconcile the inventory with the bill monthly. Anything on the bill that is not in the inventory, or the reverse, is a finding to resolve.

Classify each cost

Cost type Example Allocation rule (illustrative)
Direct A server used only by one client 100% to that client
Shared, measurable Backup storage Proportional to each group's stored data
Shared, hard to measure Firewall, monitoring Fixed percentage or even split, agreed yearly
Central Provider account management Not allocated; held centrally
Idle or unowned A server nobody claims Flagged for review, not spread silently

The rules are illustrative; choose ones the groups accept as fair and can check.

Show or charge

Showback reports each group's share without moving money; it builds awareness and is a sensible first step. Chargeback bills each group's budget or client invoice. For a software vendor charging clients, chargeback may be part of pricing; then the method should be written into client agreements so it can be explained.

The FinOps Foundation lists these uses side by side: allocated costs may feed "showback to various teams, chargeback to finance, or allocation to cost centers". The same allocation data supports any of them; the choice is about how the business wants to use it.

Keep it simple at first

Start with direct costs and two or three shared categories. Add detail only when a group asks a question the current split cannot answer.

Write the rules down

Put the allocation rules on one page: categories, the method for each shared item, the review date and who decides disputes. Review the rules once a year, or when a large change such as a new client or a retired application alters the shape of the bill. Changing a rule mid-year without notice undermines trust in every figure that follows.

Illustrative example

A software vendor hosts eight clients: five on dedicated application servers, three sharing one. It allocates dedicated servers directly, divides the shared server by each client's user count, and splits backup by stored data. Firewall and support are divided evenly across all eight. A monthly reconciliation finds a test server left running after a project; it is removed, not shared out. The example is illustrative.

Risks and limits

  • Inaccurate inventories make unfair bills. Reconcile monthly.
  • Precision can cost more than it saves. Very detailed splits take time to run and explain.
  • Rules need owners. Name who maintains the inventory and who settles disputes.
  • Licensing and tax may apply. Recharging costs to clients can have licensing and GST consequences; check with your adviser.

Sources

Opened 15 November 2026.

Related service: Cloud hosting.

Learning notes

  • Build and reconcile a server inventory before splitting costs.
  • Label each item with its owner; use the inventory where the platform has no labels.
  • FinOps: shared costs can be split by fixed, proportional or proxy-based rules.
  • Showback builds awareness; chargeback moves cost to budgets or invoices.
  • Flag unowned items for review instead of spreading them.