Should you pay the SCIM tax at renewal? A playbook for IT and finance
Renewal is the one moment you can change plans without a fight. How to decide, app by app, whether to keep paying for the plan with SCIM, move down, or never move up.
Thomas Bieser, Cofounder and CEO ·
Most companies pay the SCIM tax for one of two reasons. Someone upgraded an app years ago to get provisioning, and nobody revisited it. Or someone is about to upgrade because an auditor asked how leavers are removed. Renewal is the moment to make that decision on purpose.
Two kinds of renewal
- Already paying. The app is on the plan that includes SCIM. The question is whether to stay.
- Not paying yet. The app is on a lower plan and provisioning is manual. The question is whether to move up.
The same five questions answer both.
Five questions for every app
- Do we require SSO for this app, and which plan includes it. If SSO and SCIM sit on the same plan and you require SSO, that plan is not optional. Stop here.
- What else on the higher plan do we use. Audit logs, data retention, granular admin roles, a support tier. If the answer is "nothing but SCIM", the plan is a SCIM tax.
- How many seats renew, and at what growth. The SCIM tax is charged on every seat, so it grows with headcount.
- How many joiners, movers and leavers touch this app a year. That is the manual work you take on, or automate, if you move down.
- Who removes access today, and how would we prove it. If the honest answer is "a ticket and a hope", fix that before the renewal, not after.
The decision
| Situation | Decision |
|---|---|
| SSO required and only on the SCIM plan | Stay. Negotiate seats, not plans |
| Higher plan features used beyond SCIM | Stay, and note it for the next renewal |
| Higher plan used only for SCIM | Move down and automate provisioning on the lower plan |
| Not paying yet, provisioning is manual | Do not move up. Automate on the plan you have |
Plan the calendar, not just the app
List every app with its renewal month. The two quarters ahead are where decisions are due. Give each one an owner in IT and one in finance. The SCIM tax calculator shows the renewal month for apps you already pay the top plan for, so the list is ready when procurement asks.
Keep provisioning automated when you move down
Moving down only works if provisioning keeps working. StitchOps carries the same joiner, mover and leaver events from your identity provider into the app on the lower plan, anywhere a person can log in and act. Each change is logged with evidence, so the auditor sees the same control on a cheaper plan.
Read the step by step guide to automating provisioning without SCIM upgrades, or see pricing.
Frequently asked questions
- When is the best time to stop paying the SCIM tax?
- At renewal. Moving to a lower plan mid contract rarely saves anything, and moving down at renewal needs no negotiation beyond the order form.
- Should we move down if SSO is on the same plan as SCIM?
- Usually not. If you require SSO and the vendor sells it only on the plan that includes SCIM, you would buy that plan anyway, so the SCIM part of the price is not avoidable.
- What do we lose by moving to a lower plan?
- List every feature on the higher plan you actually use, not just SCIM. Audit logs, data retention, admin roles and support terms are common reasons to stay.
- How do we keep provisioning automated after moving down?
- StitchOps carries your identity provider's joiner, mover and leaver events into the app on the lower plan, anywhere a person can log in and act, and logs every change.