Reporting and exports

When reporting ambiguity needs escalation

A reporting question needs escalation when definition uncertainty or value interpretation becomes serious enough to affect a real decision.

Who this is for: Users deciding when reporting ambiguity has become too consequential to leave at the help or ordinary verification layer.

Last reviewed 2026-04-30 · Source of truth: broader help library · Languages: en, es

Article metadata

Product area: reporting and exports

Owner: Reporting truth

Parity reviewer: Bilingual launch review

Retrieval-ready: Yes

What to expect next

Escalate once reporting ambiguity becomes serious enough to affect a real decision.
Use narrower support or guided follow-up when the meaning cannot be resolved safely through help and ordinary verification alone.

When the ambiguity is no longer small

Escalate when uncertainty about a report, export, or definition could change a financial conclusion, operational action, stakeholder confidence, or another decision that should not rest on guesswork.

The issue is not only whether the report feels confusing. The issue is whether the confusion now changes what someone might decide or do.

What to preserve when escalating

Preserve the report context, the definition you are trying to interpret, and the consequence of getting it wrong.

That makes the follow-up more useful than simply saying the report felt unclear.

Escalation path

If the uncertainty could change a real decision, preserve the consequence clearly and escalate rather than normalizing the ambiguity.

Related next steps

Read when a reporting question is low risk Open structured support intake Open Spanish version Back to help center