Rivane

Accounting
made smart

ERP Use CasesTier 2Published June 19, 2026

SCIM 2.0 Automated User Provisioning and Deprovisioning

SCIM 2.0 Automated User Provisioning and Deprovisioning for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.

Security & Identity - SCIM Provisioning is where ERP discipline either begins or breaks.

SCIM 2.0 Automated User Provisioning and Deprovisioning looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.

The expected business outcome is specific: New employee has Rivane access within 5 min of HR action; terminated employee access revoked automatically, eliminating orphaned accounts.

The control flow a finance team actually needs.

Workflow map showing control steps, exceptions, and evidence for this ERP process.SCIM 2.0 Protoco...Start conditionPATCH Operations...Required checksDeprovisioning R...Owner and SLASCIM Bearer Toke...System updateUser Attribute S...Exception handlingAudit packetEvidence trailException loopSecurity & Identity - SCIM Provisioning should preserve every override and rejection.
Workflow map for this ERP process, including exception handling and audit evidence.

Step 1

SCIM 2.0 Protocol Compliance For Users...

Step 2

PATCH Operations Be Idempotent

Step 3

Deprovisioning Revoke Active JWTs...

Step 4

SCIM Bearer Tokens Are Org-Scoped And...

Step 5

User Attribute Schema Extensible Via...

The ERP surface involved.

Module

Security & Identity - SCIM Provisioning

Actors

Identity Provider (Okta / Azure AD), System Administrator, HR System

Tier

Tier 2

Finance area

Platform, Integration, Security, Administration & Analytics

Region lens

US and UK finance teams

Publication date

June 19, 2026

SCIM 2.0 protocol compliance (RFC 7644) for Users and Groups resources; PATCH operations must be idempotent; deprovisioning must revoke active JWTs within 60 s of SCIM request receipt; SCIM bearer tokens are org-scoped and rotatable without downtime; user attribute schema extensible via SCIM schema extensions; provisioning errors surface in an admin error log with retry capability; bulk SCIM operations supported for initial migration (≥1,000 users in a single request).

US and UK teams have different compliance hooks, but the same control problem.

US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.

The control matrix.

Control areaRequirementAcceptance proof
Control 1SCIM 2.0 protocol compliance (RFC 7644) for Users and Groups resourcesGiven SCIM 2.0 endpoint configured with bearer token
Control 2PATCH operations must be idempotent
when IdP pushes SCIM POST /scim/v2/Users for a new employee, then Rivane creates the user account, assigns roles from group mapping, and sends a welcome notification within 5 min
Control 3deprovisioning must revoke active JWTs within 60 s of SCIM request receipt
when IdP pushes PATCH /scim/v2/Users/{id} with active: false, then all active JWTs for that user are revoked via jti blocklist within 60 s and the account is disabled
Control 4SCIM bearer tokens are org-scoped and rotatable without downtimenegative) when a SCIM request is sent with an invalid bearer token, then 401 is returned and no account change is made.
Control 5user attribute schema extensible via SCIM schema extensionsNew employee has Rivane access within 5 min of HR action; terminated employee access revoked automatically, eliminating orphaned accounts.
Control 6provisioning errors surface in an admin error log with retry capabilityNew employee has Rivane access within 5 min of HR action; terminated employee access revoked automatically, eliminating orphaned accounts.

Audit evidence is a chain, not a folder.

Evidence layerWhat should be preserved
Business event
Administrator enables SCIM in Rivane, receives a bearer token and endpoint URL, and configures the IdP SCIM app. When HR adds a new employee in the HRIS, the IdP pushes a SCIM POST /Users to Rivane, which creates the user account, assigns roles from the SCIM group mapping, and sends a welcome notification. When HR terminates an employee, the IdP pushes PATCH /Users/{id} with active: false;
Rivane immediately revokes all active sessions via jti blocklist, disables the account, and writes a deprovisioning audit event. Group membership changes trigger incremental role updates.
Control rulesSCIM 2.0 protocol compliance (RFC 7644) for Users and Groups resources; PATCH operations must be idempotent; deprovisioning must revoke active JWTs within 60 s of SCIM request receipt; SCIM bearer tokens are org-scoped and rotatable without downtime; user attribute schema extensible via SCIM schema extensions; provisioning errors surface in an admin error log with retry capability; bulk SCIM operations supported for initial migration (≥1,000 users in a single request).
Acceptance proof
Given SCIM 2.0 endpoint configured with bearer token;
when IdP pushes SCIM POST /scim/v2/Users for a new employee, then Rivane creates the user account, assigns roles from group mapping, and sends a welcome notification within 5 min;
when IdP pushes PATCH /scim/v2/Users/{id} with active: false, then all active JWTs for that user are revoked via jti blocklist within 60 s and the account is disabled;
(negative) when a SCIM request is sent with an invalid bearer token, then 401 is returned and no account change is made.
Data record
user { user_id: string, org_id: string, email: string, scim_external_id: string, status: enum(ACTIVE,INACTIVE,DEPROVISIONED), external_id: string };
scim_group_role_mapping { scim_group: string, org_id: string, role_id: string };
provisioning_audit { event_id: string, action: enum(PROVISION,DEPROVISION,UPDATE), user_id: string, source: string(SCIM), timestamp: timestamp };
(reference, product may differ).
System event
POST /scim/v2/Users { userName, name, emails, groups } -> 201 { id, meta };
PATCH /scim/v2/Users/{id} { Operations: [{op, path, value}] } -> 200;
GET /scim/v2/Users/{id};
POST /scim/v2/Bulk -> 200 { Operations[] };
emits scim.user_provisioned and scim.user_deprovisioned events;
idempotent via SCIM id.
Lifecycle state
ACTIVE -> INACTIVE -> DEPROVISIONED;
guard: deprovisioning revokes JWTs within 60 s via jti blocklist;
PATCH operations are idempotent;
bulk operations supported for ≥1,000 users.

The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.

Implementation contracts.

Reference data model

`user` { user_id: string, org_id: string, email: string, scim_external_id: string, status: enum(ACTIVE,INACTIVE,DEPROVISIONED), external_id: string }; `scim_group_role_mapping` { scim_group: string, org_id: string, role_id: string }; `provisioning_audit` { event_id: string, action: enum(PROVISION,DEPROVISION,UPDATE), user_id: string, source: string(SCIM), timestamp: timestamp }; (reference, product may differ).

API and events

`POST /scim/v2/Users` { userName, name, emails, groups } -> 201 { id, meta }; `PATCH /scim/v2/Users/{id}` { Operations: [{op, path, value}] } -> 200; `GET /scim/v2/Users/{id}`; `POST /scim/v2/Bulk` -> 200 { Operations[] }; emits `scim.user_provisioned` and `scim.user_deprovisioned` events; idempotent via SCIM `id`.

State transitions

`ACTIVE -> INACTIVE -> DEPROVISIONED`; guard: deprovisioning revokes JWTs within 60 s via jti blocklist; PATCH operations are idempotent; bulk operations supported for ≥1,000 users.

Common implementation traps.

Treating the workflow as data entry

If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.

Hiding exception logic

Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.

Posting without recovery design

Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.

Skipping evidence design

A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.

Where Rivane fits.

Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.

References and source basis.

These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.

Back to ERP use cases