Payhawk SCIM guide

Pleo, the corporate cards and expense management platform, offers SCIM 2.0 provisioning but only through Okta integration and exclusively on Enterprise plans with custom pricing. While this integration supports user creation, attribute updates, and deactivation with schema discovery capabilities, it creates a significant accessibility barrier for most organizations. The combination of Enterprise-tier requirements and Okta-only support means teams using Azure AD, Google Workspace, or other identity providers—or those on Pleo's lower-tier plans ($39-179/month)—are completely locked out of automated provisioning. This limitation is particularly problematic for growing companies that need expense management automation but aren't ready for enterprise-tier commitments. Without SCIM provisioning, IT teams must manually create accounts for every employee who needs a corporate card, then manually deactivate access when they leave—creating both administrative overhead and security gaps in a system that handles company finances.

Ramp offers excellent native SCIM support across all plans, including their free tier. Users are automatically created, updated, and deactivated through standard SCIM protocols with major IdPs like Okta and Microsoft Entra. However, several operational limitations create gaps: SCIM deactivation doesn't actually delete users (they remain as "inactive"), corporate card termination requires manual intervention, and you can't run both SCIM and HRIS integrations simultaneously. These limitations matter most for financial compliance and offboarding workflows. When employees leave, their Ramp accounts stay in the system indefinitely, and any active corporate cards remain functional until manually terminated. For finance teams managing hundreds of users and cards, this creates audit trail concerns and potential security exposure from dormant accounts.

6sense, the B2B revenue intelligence platform, has paused SCIM provisioning for new customers until Q4 2026. While existing customers with SCIM enabled can continue using it, new implementations are limited to JIT (Just-In-Time) provisioning through SAML SSO. This creates a significant gap for IT teams managing revenue intelligence access, as JIT only creates users on first login and provides minimal attribute mapping (email, first name, last name only). For an enterprise platform with typical pricing of $55,000-$130,000 annually, the absence of automated user lifecycle management is a substantial limitation. The lack of SCIM until Q4 2026 forces IT teams into manual provisioning workflows for a platform handling sensitive revenue data. While SAML SSO handles authentication, it doesn't address user lifecycle events like role changes, department transfers, or offboarding. This creates compliance risks in revenue teams where access to prospect data and sales intelligence must be tightly controlled. The nearly two-year wait for SCIM restoration means organizations implementing 6sense today face manual user management for the foreseeable future.