Allocating costs by project, building, and unit without tagging every line by hand

Finance manager Marcus logs in four hours before his shift starts, a mug full of coffee in one hand, the other hovering over four hundred unsorted rows. All untagged invoices, waiting for his cost allocation by project, building, and unit.

That's the horror movie that's on repeat every month. It's one that your finance team (and Marcus) deserve a way out of. This blog covers cost allocation structures, the shared cost rule for clean audits, and ways to end the monthly tagging marathon.

What are you trying to see when allocating costs?

Before you allocate a single dirham, figure out what question you're actually trying to answer. Not where a cost landed on the ledger, but which building, project, or unit is actually making you money this month. That's the real point of the exercise, not the tagging itself.

• Profitability by building: which property is actually earning its keep, once every shared security contract and maintenance call has landed on it fairly.
• Profitability by project: whether a specific job ran over or under what it was priced for, the number that decides if you win the next bid.
• Profitability by unit: the margin that matters when it's time to price the next sale or explain a number to an owner.

Following just one cost centre often ends up lumping a refurb, a lease renewal, and a security contract under one tidy "Maintenance" tag. One ledger can never answer all three questions or reveal which building actually drove the spend.

What structure should you have for project cost allocation?

Before you allocate a single cost, decide what you need to report on. Your structure should answer questions such as, “How much did Building A cost this month?” or “Is Project B on budget?”

Smart cost allocation starts with a structure that reflects how your business operates and makes decisions. Let's look at what details belong at each level.

1. Projects

Use the project level for work with its own budget, timeline, or profitability target.

Example: Project: Marina Residences

This helps developers and contractors track the total cost of a specific project or headline workloads.

2. Buildings

Use the building level when a project contains multiple properties requiring separate reporting.

Example: Project: Marina Residences → Building: Tower A

This helps you see whether costs are concentrated in one building. Costs also don't disappear into the overall project total.

3. Units

Go down to the unit level only when the business genuinely needs that visibility.

Example: Tower A → Unit 1204

This gives you unit-level tracking for calculating individual costs or profitability. If this detail does not affect decisions, avoid creating hundreds of unnecessary codes.

4. Cost codes

Use cost codes to describe what the money was spent on, rather than where it was spent.

Example: Tower A → Unit 1204 → Plumbing and Tower A → Unit 1204 → Electrical

These codes show both where the cost belongs and what it was spent on.

That said, don't make the structure more detailed than necessary. If every invoice requires choosing from 200 similar codes, site teams may skip the coding. Your structure only works when everyone can understand and maintain it, even if they aren't fluent in your chart of accounts.

What direct costs fall under cost allocation by project, building, and unit?

Direct costs are the line items that belong cleanly to one project, building, or unit. Think of a contractor invoice for Tower A's plumbing, or materials delivered to a single site. Nobody has to debate who owns them.

While it is the easy half of cost allocation, you've got to capture the code the moment cost is incurred. Leave it for three weeks later, and someone in finance is squinting at a supplier name and guessing.

Direct costs work because the invoice is honestly one project's problem. That holds less often than you'd think, and the exceptions are where allocation gets interesting.

Pro tip: Tie the cost code to the person spending the money. That's the only moment the information is still free.

How do you split shared costs across multiple buildings?

Tough times start when you're expecting a cleaning bill but spot security costs hiding in the same invoice. Things get trickier with security contracts and maintenance services, since they usually span multiple sites.

Shared costs rarely find an easy home, leaving finance teams with more to untangle. Before the spreadsheet drops into chaos, try a few approaches that focus on the nature of the cost.

By floor area

When space drives the cost, square metres give you a sensible way to divide it.
This works well for security, cleaning, and utilities, where larger buildings typically consume more.
It also avoids treating headcount or revenue as the main driver when neither reflects usage.

Carpet area in action: A 10,000 sq. ft. building gets 20% of a shared cost across 50,000 sq. ft.

By headcount

Some costs follow people rather than property, making employee numbers the better yardstick.
This works for shared staff, roaming maintenance teams, and communal facilities.
A smaller site with more employees may consume more resources than a larger, quieter one.

People power: A building with 40% of the portfolio's employees gets 40% of the shared staff cost.

By revenue

When costs follow business scale, revenue can provide a more useful measure than space or people.
This suits head office charges and portfolio-level management fees, where operations matter more.
A revenue-based split can therefore better reflect each building's share of the business.

Mapping the numbers: A building generating 30% of total revenue gets 30% of the shared management fee.

Let's split one: one invoice, four buildings

Consider a single monthly invoice of AED 80,000 covering security, cleaning, and maintenance across four buildings. Looking closer, cleaning was specifically for Buildings A and B. Security and maintenance cover all four buildings.

The buildings also differ in size and headcount:

Untangling each cost based on what drives it:

• Security: AED 40,000 split across all four buildings by floor area. That means 20%, 30%, 40%, and 10%, respectively.
• Cleaning: AED 18,000 split by floor area ratio for just A and B. Here, A gets 40%, and B gets 60%.
• Maintenance: AED 22,000 split across all four buildings by headcount. That means A takes up 20%, B 30%, C 40%, and D 10%.

What the quick number-crunch shows:

With clear, well-reasoned splits, the once-messy AED 80,000 invoice now has a clear home across all four buildings.

Whichever basis you choose, do it consistently and document why it fits the cost. Any changes without explanation may get you flagged during a purchase audit.

Your fix: Move allocation to the point of spend

Manual tagging is a brutally slow way to answer a question the spender already knew weeks earlier. By month-end, finance is left reconstructing where each expense belongs from receipts and memory.

Move that decision closer to the moment the money is spent. Here's where that can happen.

• When the spend method is fixed: Give each project or building a dedicated, pre-coded corporate card. Every swipe already carries its destination, so finance does not need to guess where that spend belongs later.
• Once the project is chosen: Let the person making the purchase select the project or building at checkout. The allocation is captured immediately, so finance does not have to reconstruct the spender's intent afterwards.
• When the code travels with the receipt: Attach the project or building code when the receipt is uploaded, rather than adding it later. The resulting export is ready to use, without another round of manual tagging.

Moving it to real-time data capture makes the month-end closing a quick check, not detective work. Finance verifies that the spend is tagged correctly and allocation work happens when the information is fresh.

Quick benchmarks: What does good reporting look like?

Good reporting should pass a quick sanity check by eye. Here are the signs your allocation process is working and ones that must pass:

• Numbers that agree: Building-level totals should match project-level totals. If they don't, something was dropped or double-counted.
• Mid-month readiness: You should be able to pull a report any day, not just at month-end. That requires allocation at the point of spend.
• A consistent basis: Shared costs should use the same documented basis each time. Consistency is what makes allocations easier to defend during an audit.
• No follow-up questions: Nobody should need to ask which building a cost belongs to. If they do, the coding failed upstream.

If any of these checks fail, you'll find yourself patching gaps manually, usually because something went wrong upstream. The way forward is a spend management platform with accounting automation and real-time transaction recording.

Simplify allocation with intelligent spend management

Getting cost allocation right is all about mapping it to when someone knows the answer. That means at the point of spend, when the project is selected, or when the code travels with the receipt.

But even with those choke points covered, allocation gets tedious without the right tool.

Alaan steps in to solve that and let you breathe. Its Supercard has instant spend capture, with controls down to the transaction level. Alaan also has AI-native workflows to automate approvals and routine processes, with accounting integration from the get-go.

End your cost allocation crash course with smarter coding and cost capture. Start with Alaan today.

FAQs

What are the main types of cost allocation?

Cost allocation generally covers direct and shared costs. Direct costs can be traced to one project, building, or unit, while shared costs span multiple areas. Shared costs need an allocation basis, such as floor area, headcount, or revenue, depending on what actually drives the expense.

How do you calculate a cost allocation?

Start with the total shared cost and choose a basis that reflects what drives the expense. Divide each project's share of the allocation basis by the total basis, then multiply that percentage by the shared cost. For example, a building representing 20% of total floor area gets 20% of a space-driven cost.

What methods are available for allocating shared costs?

The right method depends on the nature of the cost. Floor area suits space-driven expenses such as security and cleaning. Headcount works for people-driven costs, such as shared staff or maintenance. Revenue can suit costs linked to business scale, such as head office charges or portfolio-level management fees.

How do you handle a cost that spans several projects?

First, identify what actually drives the shared cost. Then choose a suitable basis, calculate each project's share, and document the method. For example, split security by floor area if space drives the service. Keep the same basis consistent across reporting periods unless there is a clear reason to change it.

‍