Service credits in ICP contracts: how they are triggered and calculated

Service credits are the usual remedy when an in-country partner (ICP) misses an agreed service level. They are simple in principle. They go wrong in the details. This FAQ covers how credits are triggered and how they are calculated, so your team can write clauses that work in practice.

This article does not quote rates or thresholds. Those belong in your own contract and depend on your volumes and risk.

What is a service credit?  

A service credit is a reduction in the fees you pay the ICP. It applies when the ICP fails to meet a defined service level. It is not a penalty and it is not damages. It is a pre-agreed price adjustment for a known type of failure.

Most contracts say credits are the sole remedy for the specific service level breach. Check this wording. If credits are the sole remedy, you cannot also claim damages for the same event. If they are not, say so clearly.

What triggers a credit?  

A credit is triggered when a measured service level falls below its target in a defined period. Three things must be clear in the contract:

• The metric. For example, payroll inputs processed by the cut-off, statutory filings submitted on time, or queries answered within the response window.
• The target. The level the ICP promises to meet.
• The measurement period. The window in which performance is counted, such as a payroll cycle or a calendar month.

If any of these is vague, the trigger is vague. Disputes follow.

Who measures performance?  

The contract should name the source of truth. Good options are timestamps in a shared system, submission receipts from the authority, or a log both parties can read. Weak options are one party’s internal report that the other cannot check.

Agree the data fields up front. Agree how each event is time-stamped and in which time zone. Many credit disputes are really data disputes.

Does the ICP have to report breaches?  

It should. A good clause requires the ICP to report any miss within a set time after the period closes. It also requires a short root-cause note. Do not rely on the client to find every miss.

Also decide what happens if the ICP does not report. A common answer is that the credit applies automatically once the platform shows the miss in the shared data.

What are the usual exclusions?  

Credits normally do not apply when the miss is caused by something outside the ICP’s control. Typical exclusions are:

• Late or incorrect inputs from the platform or the client.
• Missing documents from the employee.
• Outages at an authority or a bank.
• Changes requested by the platform after the cut-off.

Keep the list short and specific. A long, loose list lets the ICP excuse almost any miss. Also require the ICP to show that the exclusion caused the failure.

How is a credit calculated?  

There are three common models.

Percentage of fees. The credit is a percentage of the fees for the affected period or service. It is easy to compute. It scales with the size of the account.

Fixed amount per event. Each miss costs the ICP a set sum. This works for discrete failures, such as one missed filing.

Tiered credits. The credit grows as performance gets worse. A small shortfall gives a small credit. A severe shortfall gives a larger one.

Whatever model you pick, write the formula in the contract with a worked example. State the base the percentage applies to. Is it the monthly fee, the fee for the affected service line, or the fee for the affected employees only? The base changes the result a lot.

Is there a cap?  

Most contracts cap total credits in a period. The cap is usually a share of the fees for that period. A cap protects the ICP. It also tells you the maximum value of the remedy.

If the cap is low, credits will not change behaviour. Pair credits with a right to terminate for repeated or severe failures. Credits alone rarely fix a weak partner.

How are credits applied?  

Two methods are common. The credit is deducted from the next invoice, or the ICP pays it out as a refund. Deduction is faster and avoids a separate payment flow. State a deadline for applying the credit. State what happens at contract end if credits are still owed.

What about repeated misses?  

Single misses are manageable. Patterns are the real risk. Add a clause that treats repeated misses of the same metric as a material issue. It should trigger a remediation plan, a review meeting and, if needed, an exit right.

How do you dispute a credit?  

Give each side a short window to raise a dispute. Name the evidence that counts. Set an escalation path with named roles. Keep the process light. A heavy process means nobody uses it.

A practical checklist  

• Each metric has a clear definition, target and period.
• The source of truth is shared and both sides can read it.
• Exclusions are few and specific.
• The formula is written out with an example.
• The cap and the sole-remedy wording are explicit.
• Reporting duties and deadlines are set.
• Repeated failure leads to a defined escalation.

Credits work when both sides can see the same data and agree what it means. That is a data-exchange question as much as a legal one.

Partnership teams can request the data-exchange specification.