Skip to content

A warning I disagree with

A WARNING-severity validation result appeared, and you believe the rule's complaint is unwarranted (the data is correct as stated).

What this means

Warnings do not block export — the gate ignores them. They are surfaced for human judgement.

When to document and proceed

If after inspection the data is correct and the rule is being unhelpful (e.g. flagging a perfectly legitimate "Profit Before Tax without an income-tax expense" when the entity is in tax-loss-carryforward territory), document on the filing log and proceed.

When to escalate

If the same warning recurs across multiple filings for similar reasons, file a constitution-level issue. The rule library is published by ACRA and revisions happen — a long-running warning that's always wrong is worth pushing back on.

When NOT to ignore

ACRA can reject a filing even when the platform's gate let it through. Warnings most likely to be regulator-rejection candidates:

  • cross_statement warnings (equity / cash-flow reconciliation mismatches)
  • sign_convention warnings on revenue / expense classifications
  • mandatory warnings (an INFO-priority element missing that the regulator expects)

When in doubt, fix the underlying data even though the gate would let you through.

Diagnose

sql
SELECT rule_id, category, message
  FROM xbrl_validation_results
  WHERE xbrl_filing_id = '<filingId>' AND severity = 'WARNING' AND passed = false
  ORDER BY rule_id;

Internal use only — BreezyCorp