Handle a client revision request

Who does this: XBRL Preparer · XBRL Reviewer · Senior Accountant · Platform Admin When: The client opened the portal and chose Request revision. Result: Filing is back-routed to MAPPING_IN_PROGRESS; you address the comment, re-run validation, re-export, and re-send the portal link.

Steps

1. Open the filing → activity log. Find the xbrl.client.revision_requested event; read the comment in full.
2. The filing has already transitioned EXPORTED → MAPPING_IN_PROGRESS.
3. Identify the upstream step:
   • Mapping wrong? → Override a tag mapping.
   • Validation rule failed but you forced through earlier? Cannot happen with the gate; this scenario implies the underlying data is wrong. Fix at mapping.
   • Wrong period / entity type? The filing header was set at create time and is partly immutable (taxonomy version is fully so). If the client genuinely needs a different period, create a new filing.
4. Re-run validation → on pass, re-export.
5. Re-dispatch the portal link with the new export.

Related runbooks

• Dispatch the XBRL portal link
• Run validation
• X-06 userflow