Service credit calculation: documents to prepare
Service credit calculation converts a missed service level into a contractual deduction. Before the calculation can proceed, you need the service level schedule, the monitoring data, the notice history and the invoice period in question. Missing one document delays the exercise and weakens the resulting claim. This page sets out what to prepare, in what order, and who ultimately decides the figure.
What changes once the file is complete
A service credit claim only becomes calculable once the underlying data exists in a checkable form. Most technology contracts tie the credit to a defined measurement period, usually a calendar month or a billing cycle. Once that period closes, the clock on any claim window usually starts running.
A complete file shortens the negotiation with the supplier and reduces the room for dispute over the underlying numbers. An incomplete file invites a challenge to the method rather than the outcome, which is slower to resolve and harder to close.
| Document | Stage | Who provides it |
|---|---|---|
| Signed contract with the service level schedule and credit formula | Preparation | Contract owner |
| Monitoring or reporting logs for the affected period | Preparation | Operations team |
| Incident tickets and support correspondence | Verification | Support team |
| Prior service credit notices, if any were sent | Verification | Contract manager |
| Invoice for the affected billing period | Calculation | Finance |
| Draft credit calculation and cover letter | Submission | Contract manager |
What to do
- The contract owner pulls the service level schedule and the credit formula from the signed agreement.
- The operations team exports monitoring logs for the disputed period from the monitoring platform used to track uptime.
- The contract manager cross-checks those logs against incident tickets and any support correspondence from the same period.
- Finance applies the formula to the verified downtime or failure figures and produces a draft number.
- Legal reviews the notice history to confirm the claim falls within any window set by the contract.
- The contract manager sends the completed calculation, with supporting documents, to the counterparty for review.
Who decides
The two parties negotiate the figure first, usually through the contract managers named in the agreement. If they cannot agree, the contract's own escalation or dispute resolution clause determines the forum, whether that is a senior management review, an expert determination process or a formal dispute procedure. The contract, not either party's internal policy, decides the timeline for each stage.
Where this typically forks
- If the monitoring data comes only from the supplier's own platform, request an independent export or a shared dashboard log before finalising a figure. Relying on one-sided data invites a challenge later.
- If the contract sets a claim window, check the date the notice was actually filed. A calculation prepared correctly but submitted late risks being barred by the contract's own terms, regardless of the underlying facts.
- If the counterparty disputes how the formula should be read rather than the numbers themselves, escalate through the named contract manager under the escalation clause. Recalculating unilaterally at that point rarely moves the discussion forward.
Source and limit
This page does not calculate a specific figure, resolve a live dispute, or confirm whether a particular contract's claim window has already closed. Those questions depend on the wording of your agreement and on facts we cannot see from a general procedure page. Where the underlying dispute turns on a counterparty's standing, our report on Counterparty in Austria and what to prepare covers what can be established for a party based there.
Where the contract or the disputed document sits under French law, our report on Document in France explained sets out how that kind of document evidence is typically treated.
Verified
This procedure reflects our internal working method for technology contract disputes and is reviewed periodically by the technology contracts team. It does not reference any specific statute, regulation or directive, because the applicable rule depends on the governing law chosen in each contract. For the general policy behind how we source and tier our procedural pages, see Sources by tier and delivery route overview and who.
Related publications
A service credit calculation often runs alongside other technology contract mechanics that require their own document trail. See our procedure on Escrow set-up technology contract documents to prepare for a comparable checklist.
Frequently asked questions
How long does service credit calculation take in practice?
Once the measurement period closes and the documents above are assembled, most calculations take one to two weeks to draft and check internally. Negotiation with the counterparty adds further time, depending on how quickly they respond and whether they dispute the method.
Which documents are needed to start?
At minimum, you need the signed contract with its service level schedule, the monitoring logs for the affected period and the invoice covering that period. Everything else in the table above strengthens the file but is not required to begin drafting.
What happens if the other side does not respond?
Most contracts set a response period for a service credit notice. If that period lapses without a reply, check the contract for a deemed-acceptance or escalation provision before assuming the claim stands unopposed. Silence is rarely the same as agreement.
Next step
If the dispute in front of you also touches a tokenised asset rather than a straightforward service contract, the mechanics differ from the point the incident is recorded. See When a fork duplicates the token step by step for the first steps in that scenario.