Why datacentre billing accuracy starts with better asset data

Key takeaways

• Accurate billing starts with accurate asset data. Knowing what is installed, where it is and which customers it supports provides a reliable foundation for billing.
• Every operational change can have a commercial impact. Power upgrades, cross-connects, rack changes and smart hands activity can all affect what customers should be charged.
• Connecting contracts, operations and billing reduces revenue leakage. Aligning what was agreed with what has been delivered makes it easier to identify missed or inaccurate charges.
• Reducing manual reconciliation improves billing confidence. Connected data helps teams identify discrepancies earlier and spend less time reconstructing changes across multiple systems.
• Better data supports more than billing accuracy. A trusted view of assets, customers and capacity can also help operators identify available capacity and new commercial opportunities.

Datacentres and telecommunication are becoming increasingly complex commercial environments. Operators are managing buildings, data halls, rooms, cages, racks, power infrastructure, connectivity and a growing range of customer services, often across multiple sites and regions. At the same time, customers are changing their requirements more frequently, with new equipment, additional power, cross-connects, smart hands services and other changes being delivered throughout the life of a contract.

That creates a challenge that is easy to underestimate: the datacentre changes every day, but the commercial record does not always keep pace.

When a rack is added, power is upgraded, a cross-connect is installed or equipment is decommissioned, there is a commercial consequence. If that change is not accurately captured and connected to the relevant customer contract and billing process, the result can be under-recovery, billing disputes or revenue that is simply never invoiced. The problem may only become visible weeks or months later, when finance teams are forced to reconcile information across multiple systems and spreadsheets.

This means billing accuracy is not simply a finance or billing-system issue. It starts much earlier, with having confidence in what exists across the estate, who it belongs to, what has been agreed with each customer and what services have actually been delivered.

The commercial record needs to keep pace with the physical estate

For datacentre operators, the physical estate is constantly evolving. Customers move equipment, increase their power requirements, order additional connectivity and request services. Operational teams install, relocate, maintain and decommission infrastructure. Contractors and engineers make changes on-site that may need to be reflected in both operational and commercial systems.

These activities can affect what a customer should be charged.

The difficulty is that operational and commercial information is often managed separately. Asset information may sit within an operational platform, customer contracts may be held elsewhere, and billing may be managed through another system entirely. When these records are not connected, there is no reliable way to establish whether the services being billed still reflect what is actually being delivered.

The result is what could be described as data drift: the gradual divergence between the physical reality of the datacentre and the information used to manage its commercial performance. The value proposition developed for the datacentre market identifies this as a central problem: location, rack, cage, power, network, connectivity and contract information needs to remain accurate continuously, rather than only being checked during periodic audits.

That distinction is important. An annual audit might establish what exists at a particular point in time, but it cannot necessarily account for everything that has happened since. Revenue assurance therefore needs a more continuous foundation: information that is updated as changes occur and can be connected directly to the commercial processes that depend on it.

Revenue leakage can hide in everyday activity

Revenue leakage does not necessarily come from a major error in the billing system. In many cases, it can begin with something much smaller: a service being delivered without the corresponding commercial record being updated.

Consider a customer that occupies several racks and subsequently requires additional power. The operational team provisions that capacity and the customer begins using it. If the change is not accurately recorded and passed through to the relevant billing process, the operator may continue charging according to the previous arrangement.

The same principle applies to connectivity. A new cross-connect can be installed to meet a customer’s requirements, creating an additional service that should form part of the customer’s charges. If the operational change is recorded by an engineer but never reaches the commercial record, the service has been delivered but not necessarily billed.

Smart hands activity creates another potential source of leakage. A customer may request engineering support, equipment may be moved or additional work may be completed on their behalf. If that activity is managed through operational processes without a reliable connection to customer billing, it becomes difficult to establish whether the associated charge has been raised.

The same applies in reverse when services are removed. Decommissioned equipment, retired connectivity or reduced capacity can leave outdated information in commercial records, creating billing discrepancies and unnecessary administration.

The datacentre revenue assurance materials identify many of these activities as potential points of divergence, including:

• Rack deployments
• Smart hands requests
• Power upgrades
• New circuits
• Network changes
• Cross-connect installations
• Equipment moves
• Decommissioning

None of these activities is unusual. That is precisely why they matter. When an estate is changing constantly, even small gaps in information can accumulate into a significant commercial problem.

Why manual reconciliation is becoming increasingly difficult

Historically, manual reconciliation may have been a practical way of managing these discrepancies. A finance or commercial team could periodically compare customer records, operational information and invoices, investigate exceptions and make corrections.

As datacentres grow in scale and complexity, however, this approach becomes harder to sustain.

The challenge is not simply the volume of data. It is the number of relationships that need to be understood. A single customer may have multiple locations, racks, power commitments, connectivity services and charging arrangements. Those arrangements may change overtime through service orders, amendments, renewals and customer requests.

This creates three connected areas of uncertainty:

• What has been agreed with the customer
• What has actually changed or been delivered across the estate
• Whether the resulting charges have been captured accurately

When those three sources of information do not align, billing teams are left relying on manual checks and reconciliation to establish what should have been billed.

Manual reconciliation also tends to be retrospective. By the time a discrepancy appears in a month-end review, the underlying change may have happened some time ago. Teams then have to reconstruct what happened, identify which customer or asset was affected, establish when the change took place and determine whether the appropriate charge was raised.

A more effective approach is to reduce the amount of reconstruction required in the first place by creating a reliable connection between what is happening operationally and what needs to happen commercially.

Better asset data provides the operational foundation

Accurate billing starts with knowing what you have. For a datacentre operator, that means having confidence in the physical estate.

• Which buildings and data halls exist
• Which rooms and cages are occupied
• Where racks are located
• What assets are installed
• How power and connectivity are configured
• Which customers are associated with them

This is where accurate asset data becomes commercially important.

Asset management is sometimes viewed primarily as an operational discipline, concerned with knowing where equipment is and maintaining it effectively. In a datacentre environment, however, that information can also provide the evidence needed to support accurate commercial decisions.

If the operational record shows that a customer has a particular rack, power allocation or connectivity service, that information can be compared with the customer’s commercial commitments. If the record changes, the relevant commercial processes can be triggered rather than relying on someone to discover the discrepancy later.

Assetspire is positioned within the datacentre proposition as the operational truth layer: maintaining a live view of buildings, data halls, rooms, cages, racks and assets, alongside power, network topology, connectivity and cross-connects. It can also capture moves, adds, changes and decommissions as part of the operational workflow.

The value is not simply having more accurate asset records. It is being able to use those records as part of a connected commercial process.

Understanding the customer contract is equally important

Knowing what exists is only half of the equation. A customer may occupy a particular rack, consume a certain amount of power and have several connectivity services installed, but that does not automatically tell an operator what should be billed. To determine that, the operational reality needs to be considered alongside the commercial commitments that have been agreed with the customer.

Customer information can be spread across contracts, service orders, amendments, renewals and change requests. Different customers may also have different charging structures, with some services fixed and others dependent on usage or activity.

This makes contract intelligence an important part of billing accuracy. Before an operator can determine whether a charge is correct, it needs to understand the underlying obligation.

Questions might include:

• Which customer occupies which rack, cage or room?
• What power capacity has been committed?
• Which cross-connects are included?
• Which services are chargeable?
• Which charges are fixed and which are variable?
• What service obligations apply?

Understanding the customer contract is equally important. Customer agreements, service orders, amendments and renewals can contain a wide range of commercial commitments, from space and power to connectivity and additional services. MRI Contract Intelligence helps transform this complex contract information into structured, actionable data that can be connected to operational and billing processes, making it easier to establish what has been agreed and ensure those commitments are reflected in the commercial record.

This creates an important distinction between simply storing contracts and making the information within them useful. A contract that sits in a document repository may be accessible, but it does not necessarily provide a practical charging baseline. Structured contract information can help establish what was agreed so that it can then be compared with what is actually being delivered.

What was agreed is not necessarily what was delivered

One of the most important principles in revenue assurance is that contractual information and operational information need to be considered together.

A customer contract may state that a particular service will be provided, but operational circumstances can change. Conversely, the operational team may deliver something that was not part of the original arrangement and which subsequently needs to be incorporated into the customer’s commercial record.

This is particularly relevant in environments where customers make frequent changes.

• A customer may require additional capacity as they take on more datacentre space.
• A customer may increase their power requirement or request additional connectivity.
• A rack may be moved to another location.
• Additional smart hands work may be completed.
• Cross-connects may be added or removed.
• Equipment may be decommissioned.

These are operational events, but they can also be commercial events.

Without a reliable way of connecting the two, operators can end up with three different versions of reality:

• What the contract says
• What the datacentre contains
• What the billing system says

None may be completely wrong, but they may no longer agree with one another.

That gap is where commercial exposure sits. A connected approach allows operators to establish what was agreed, verify what has actually been delivered and then determine what should be recovered.

The revenue assurance model developed by MRI and Assetspire describes these as distinct but connected stages:

• Knowing what you have
• Knowing what was delivered
• Knowing what should be recovered
• Knowing what capacity remains available

Billing accuracy depends on connecting the information

Once the underlying information is reliable, the billing process has a much stronger foundation.

Datacentre billing can involve:

• Rack, cage and room charges
• Power
• Cross-connects
• Utilities
• Service activity
• Other customer-specific arrangements

Where those charges depend on information that changes operationally, maintaining accuracy requires more than simply processing invoices efficiently.

The important question becomes whether the billing process has access to the information it needs to validate those charges.

For example, if a customer has additional power provisioned, the billing process should be able to recognise that change. If a cross-connect is installed, the corresponding commercial record should be updated. If a service is removed, the billing position should reflect that too.

MRI Horizon is positioned as the billing and revenue assurance layer that connects contractual commitments and operational data, helping operators validate charges, reconcile what was agreed against what was delivered and identify potential leakage earlier.

This changes the role of revenue assurance. Rather than relying primarily on retrospective investigations, operators can create a more structured process for identifying exceptions and validating the relationship between customer commitments, operational activity and billing.

The result is not simply more accurate invoices. It can also reduce the amount of manual effort required to produce them.

Revenue assurance is also about protecting customer relationships

Billing accuracy matters for more than revenue. When a customer receives an invoice that does not clearly reflect the services they are receiving, the operator may need to spend time investigating and explaining the discrepancy. Finance, commercial and operational teams can all become involved in resolving the issue. This creates unnecessary friction for both sides.

A more reliable commercial record provides a stronger basis for customer conversations. When the operator can demonstrate what services are installed, what was agreed and how the resulting charge has been calculated, billing becomes easier to explain and defend.

This is particularly valuable in complex customer environments, where billing disputes can otherwise require teams to search across contracts, operational systems and historical records to establish what happened.

The objective is not to eliminate every exception. Changes and disputes will still occur. The objective is to make them easier to identify, investigate and resolve because the underlying information is connected and traceable.

That can help move billing conversations away from uncertainty and towards evidence.

The same data that protects revenue can reveal capacity

Improving billing accuracy can also provide a clearer picture of the estate itself.

Once operators have confidence in what assets exist, where they are located, how they are being used and which customers they are associated with, the same information can support capacity planning.

This matters as operators balance customer demand with available rack space, power and connectivity. If records are inaccurate, apparently unavailable capacity may already be allocated, while capacity that appears to be occupied may no longer be in use.

The datacentre value proposition therefore links revenue assurance with capacity confidence. Knowing what is installed, sold, reserved and billable can also help operators understand what remains genuinely available and where further commercial opportunities exist.

This creates a wider business benefit. Better data gives finance greater confidence in billing accuracy, while also helping operational and commercial teams understand where capacity is available and identify new opportunities to sell.

For asset managers and investors, it can also provide greater visibility of capacity, utilisation and return across sites, customers and contracts.

The challenge grows with the estate

The need for connected information becomes even more important as operators manage multiple facilities, regions and customer arrangements.

A process that works for one site may become difficult to maintain across a portfolio when different teams use different systems, regional billing practices vary and customer information has accumulated over many years.

Legacy environments can be particularly challenging. Historical customer records may contain inconsistencies, operational changes may have been captured differently over time, and information inherited through acquisitions may not follow the same structure as newer records.

The answer is not necessarily to replace every existing system. In many cases, the more important step is establishing how the relevant information can be connected and maintained so that operational, contractual and financial teams are working from a consistent baseline.

That is why the datacentre proposition focuses on bringing together three disciplines:

• Understanding what was agreed
• Understanding what exists and has been delivered
• Recovering what is contractually owed

Together, these provide a more practical foundation for managing commercial performance across a complex estate.

Moving from retrospective checks to proactive revenue assurance

The fundamental shift is from asking whether an invoice was correct after it has been produced to creating the conditions that make accurate billing more achievable in the first place.

That starts with capturing operational changes when they happen. It continues with maintaining structured customer contract information and ensuring that commercial commitments can be compared with operational reality. Finally, billing processes need to use that information to validate charges and identify exceptions.

In this model, revenue assurance becomes part of the wider operating model rather than a task reserved for finance at month end.

It also changes where responsibility sits.

• Operations has an important role because it is closest to the physical changes taking place in the estate.
• Commercial teams need confidence that customer commitments are represented accurately.
• Finance needs reliable information on which to base billing and revenue reporting.

Connecting these disciplines creates a shared view of the commercial position.

• For CFOs, that can mean moving away from extensive manual reconciliation towards more evidence-based billing.
• For COOs, it means capturing changes at the point of work and ensuring they reach the commercial record.
• For senior leaders, it provides greater confidence that revenue and capacity decisions are based on what is actually happening across the estate.

Building confidence in the commercial performance of the estate

Accurate billing is often treated as the final stage of the revenue process. In reality, it is the outcome of everything that happens beforehand.

If the operator does not know exactly what assets it has, where those assets are or which customers they support, the commercial picture will inevitably contain uncertainty. If customer commitments are not structured and accessible, it becomes harder to establish what should be charged. And if operational changes are not captured consistently, billing teams are left trying to reconstruct events after the fact.

The answer is to connect these sources of information so that the commercial record reflects the operational reality of the datacentre.

MRI Software and Assetspire’s revenue assurance model brings together contract intelligence, operational truth and billing confidence to establish a trusted charging baseline, reduce manual reconciliation, improve billing accuracy and identify leakage earlier.

For datacentre operators, that can provide something more valuable than a more efficient billing process: confidence that the revenue being reported reflects the services actually being delivered, the commitments customers have made and the assets that are genuinely being used.

Ultimately, billing accuracy comes down to having confidence that every charge reflects what is actually happening across the datacentre. Can you demonstrate that the revenue being billed matches the services delivered, the customer commitments in place and the assets being used?

How MRI Software can help

MRI Software and Assetspire bring together commercial, contractual and operational information to help datacentre operators establish a more reliable foundation for billing and revenue assurance.

Assetspire provides a live view of the physical estate, including assets, power, connectivity and operational changes. MRI Contract Intelligence helps structure customer contracts and commercial commitments, while MRI Horizon connects this information to billing, reconciliation and revenue assurance processes.

Together, these capabilities can help operators move from fragmented records and retrospective reconciliation towards a connected view of what has been agreed, what exists, what has been delivered and what should be billed.

At MRI Software, we provide intelligent solutions designed to help datacentre operators manage complex estates, connect operational and commercial information, and improve billing accuracy. To find out how our solutions can help reduce revenue leakage and give you greater confidence in your billing, contact us today.