RRAQOZ
Sign in

Troubleshooting guidance

Make a controlled correction

Correct an error with an attributable event instead of erasing the earlier record.

FOR
Organisation administrator, Procurement, Finance
OUTCOME
Use RAQOZ to correct an error with an attributable event instead of erasing the earlier record.

Before you begin

  • The affected organisation, record and user are known.
  • You can describe the expected and actual state without sharing credentials.

Guidance

  1. 1

    Confirm the source record is wrong and identify the correct value or state.

  2. 2

    Use the product's available correction path and give a clear reason.

  3. 3

    Obtain independent approval where the configured control requires it.

  4. 4

    Verify both the original event and correction remain visible in history.

Evidence RAQOZ retains

  • Original record
  • Correction, actor and reason
  • Approval and resulting state

Common issues

The problem continues after these checks.

Record the organisation, affected record ID, expected state, actual state and time, then contact support without sending passwords, one-time codes, bank credentials or confidential documents.

A workaround would bypass the control.

Do not use the workaround. Keep the blocked or exceptional state visible and escalate through the accountable product or support path.

Related articles

Resolve matching exceptionsInvestigate differences among invoice, order and receipt evidence before payment approval.Troubleshoot an evidence exportCheck access, filters, record completeness and provenance when an export is missing or incomplete.

Last reviewed 2 September 2026. Review against the current production release before relying on exact screen behavior.