The customer activation platform.Every interaction becomes a qualified contact. Book a demo

Override decisions

Use validate, reject, and amend actions to correct receipt outcomes after submission.

Operators can override most non-terminal receipt outcomes from the receipt action modal. This is what makes Transactions practical in real activations where OCR is helpful but not perfect.

The three operator actions

Action	What it does
`Valider`	Forces the receipt into a valid state.
`Refuser`	Forces the receipt into a rejected state.
`Modifier`	Edits the extracted merchant and amount, then re-evaluates policy.

What amendment really does

Modifier is not just a cosmetic edit. After the operator changes the merchant or amount, OmniLab re-applies the acceptance policy from scratch.

That means the amended receipt can end up as:

VALID if policy passes and validation is automatic
PENDING if policy passes and validation is manual
REJECTED if the amended values still fail policy

Good reasons to override

OCR missed one digit in the amount
the merchant name is obviously readable to a human but OCR parsed it badly
a genuine receipt was rejected because the data extraction was incomplete
a duplicate or invalid result needs a confirmed human decision

Good reasons not to override

the receipt clearly belongs to the wrong merchant
the amount or date does not meet the public challenge rules
the participant is trying to reuse the same proof of purchase intentionally

Manual validation queue

See where these actions sit in the broader operator workflow.

Review flagged receipts

Understand which statuses most often lead to manual overrides.

Common acceptance failures

Fix the policy itself when operators are overriding the same issue too often.

On this page

The three operator actions What amendment really does Good reasons to override Good reasons not to override Related