How service credits work on a connectivity SLA

A service credit is the refund a provider owes when it misses an agreed service level. It is calculated from the contract, the threshold that was breached, the monthly recurring charge for the affected service, and the credit formula the SLA sets, and done properly it is deterministic: the same inputs, measured against the same rules, give the same figure every time. In practice most organisations only calculate credits on their strategic suppliers, and only by hand, so the rest of the estate goes unclaimed.

How are service credits calculated on a connectivity SLA?

A service credit is calculated from four things: the service level that was breached, the degree or duration of the breach, the monthly recurring charge for the affected service, and the credit formula the contract sets, usually a percentage of that charge that steps up with the severity of the miss. Done properly the calculation is deterministic, the same measured inputs against the same contract rules producing the same figure every time. The hard part is rarely the arithmetic; it is having an independent, measured record of what the service actually did, rather than relying on the provider’s own report.

Can I calculate service credits across all my suppliers, or just the strategic ones?

There is nothing in principle that limits credit calculation to strategic suppliers; the same four inputs apply to every line in the estate. In practice most organisations only do it for a handful of large contracts because each calculation is done by hand from the provider’s own reports. Once the measurement and the rule are applied consistently, the calculation can run across every supplier and every circuit, not just the ones big enough to justify the manual effort.

Why do most companies only claim service credits from their biggest suppliers?

Because the work does not scale. Each claim means noticing a possible breach, gathering evidence, reconciling it against the provider’s figures and arguing the result, which is only worth doing where the contract is large. Smaller contracts are left alone even when they breach, so credits that are genuinely owed on the long tail of the estate go uncalculated and unclaimed.

How much money do companies lose by not calculating credits on every supplier?

There is no reliable published figure, and any single number would be misleading, because it depends on the size of the estate, the service levels in place and how often they are missed. What can be said is directional: credits that are never calculated are never claimed, and the uncalculated long tail of smaller suppliers is where most of the unclaimed value sits, precisely because it is the part no one measures by hand.

Is MTTR a service level or a KPI?

Mean time to repair is usually a key performance indicator, not a credit-bearing service level. It describes average repair performance over a period and is useful for managing a supplier, but it is rarely the thing an SLA pays a credit against. Credit-bearing service levels are typically specific, measurable thresholds such as availability, packet loss or delay, measured per service over a defined window.

What evidence do I need to claim a service credit from a carrier?

You need an independent, time-stamped record of the service’s performance over the period, showing the threshold that was breached and when, mapped to the specific service level in the contract, together with the calculation from that evidence to the credit. The stronger the claim, the less it rests on the carrier’s own reporting and the more it rests on measurement you hold yourself. For a Layer 2 service the same applies when you verify a carrier Ethernet SLA against its frame-delay and frame-loss thresholds.

What is the difference between network monitoring and SLA assurance?

Network monitoring tells you whether the network is up and raises alarms when something fails. SLA assurance is a different question: whether the service met the levels it was contracted to, and whether you can prove it. Monitoring is about operational awareness; assurance is about accountability, turning measured performance into a defensible position on whether a service level was met and what is therefore owed.

How can I hold a connectivity supplier to account on their SLA?

By measuring the service independently of the supplier, applying the contract’s rules to that measurement, and presenting the result as evidence rather than assertion. When both sides are reading the same reproducible figures from an independent record, a service review stops being a contest of reports and becomes a reading of shared evidence, which is a far stronger position to hold a supplier from.

Can service-credit calculation be automated?

Yes. Once the measurement is continuous and the contract rule is written down, the path from a period of data to a credit figure is mechanical, so it can be computed automatically for every service rather than assembled by hand for a few. Automation is what makes calculating credits across the whole estate practical instead of only the strategic contracts.

What is a deterministic SLA calculation, and why does it matter?

A deterministic SLA calculation is one where the same measured inputs, applied to the same fixed contract rule, always produce the same result. It matters because it removes the argument: the breach and the credit are reproducible from an independent record rather than asserted by the party being measured, so a disputed month is settled on evidence instead of negotiation.

What should a service-credit evidence pack contain?

A defensible evidence pack contains the measured performance data for the period, the specific service level and threshold that was breached, the breach events with their timestamps, the credit calculation shown step by step against the contract formula, and enough provenance that someone else could reproduce the figure from the same source. The test is simple: could an independent party run the pack and reach the same number.

Who is responsible for recovering service credits?

Responsibility for recovering credits sits with the customer, usually in procurement, vendor management or finance, because the provider is rarely incentivised to flag its own breaches. The supporting discipline is to calculate and evidence what is owed, so that whoever owns the commercial relationship can claim it. Measurement and calculation make the case; recovering the credit is a commercial action the customer takes.

How does XVOLV Parallax help with service credits?

Parallax calculates service credits from independently measured performance and produces the evidence pack behind each one, so a credit is computed by rule rather than argued. It applies the same deterministic calculation across every supplier and circuit, not only the strategic contracts, which is what lets an organisation see the credits owed on the long tail it would otherwise never calculate. Parallax calculates and evidences what is owed; claiming and recovering the credit remains the customer’s commercial decision.

Sources

• MEF, carrier Ethernet service performance and service OAM standards (frame delay, frame delay variation, frame loss). mef.net
• ITU-T Y.1540 and Y.1541, IP packet transfer performance parameters and network performance objectives. itu.int
• TM Forum, SLA Management Handbook (GB917), service level lifecycle and the basis for service-credit (liquidated-damages) terms. tmforum.org