01
04 · Prove · Expected versus actual
Reconciliation & provisioning
Know whether every approved change was really made in the target system.
Reconciliation compares what policies and decisions intend with what the target system actually holds, grant by grant. Provisioning starts with safety limits. Failed writes are classified by cause, and a retry is possible only after the cause has changed.
What changes
What you get
02
Changes released in batches per system
03
Failed changes sorted by cause
04
Safety limits and a pause button
How it works
It works in three steps
Each step records its reason, and the next step uses it.
Compare
Compare expected access with what the system holds now.
Act
Make only the change that is needed, or hold it for release.
Prove
Keep the result, the reason and what still differs.
What we stand behind
RapidValue counts a change as done when the next read of the target system shows it. A successful API response alone is not enough.
Included
Included in every price
There is no module to buy for this. The price depends only on how many identities you govern.
Reconciliation & provisioning