⚠️ Experimental endpoint — not yet a stable contract. This resource ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v1.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.

Update a reimbursement policy. The update is rejected with 409 while the requested change conflicts with the rate the policy resolves — selecting the charge_point rate source while an attached charge point has no electricity rate. That conflict clears only when the configuration changes: give the charge point a rate, or detach it from the policy.

Each rate source has its own reference: policy uses electricityRateId and integration uses integrationId. Changing electricityRateSource clears the reference the previous source used, whether or not the request sends that reference as null; sending it as null explicitly is accepted and produces the same result. Sending a non-null reference the selected rate source does not use is rejected with 422 keyed by that field. A policy whose rate source does not change keeps its stored reference when the reference is omitted, so an integration policy can be repointed by sending integrationId alone.

Every other rejection of the request body is reported as 422, keyed by the offending field — malformed or invalid field values, and changing partnerId on a policy that is already assigned to partner invites or has active charge point attachments, which returns a partnerId validation error rather than a 409. Deactivated attachments do not block the change.