Override a tag mapping

Who does this: XBRL Preparer · XBRL Reviewer · Senior Accountant · Platform Admin When: The suggestion engine's top candidate is wrong, or you previously confirmed and need to change. Result: The row's elementId updates to your choice; confirmedById and confirmedAt are set to you.

Override is the same action as confirm, just with a different elementId. There is no "unconfirm then confirm" two-step required.

Steps

1. Open the filing → Mappings tab.
2. Click into the row.
3. Three paths:
   • Pick from alternatives[] — fastest if the right element is in the top-N list.
   • Search the taxonomy — type the label / element ID; the dropdown filters by entry point and statement section.
   • (Reviewer / Senior only) tick Save as synonym if the label is canonical.
4. Click Confirm (or the equivalent button labelled "Save").

How to know it worked

• Row chip is Confirmed (or MANUAL if the previous confidence was AI-suggested).
• Activity log shows xbrl.mapping.confirmed with the new elementId.

Common situations

If you see…	It means…	What to do
The element you want isn't in the search results	The entry-point or section filter is over-active	Clear filters; or check the element exists in the pinned taxonomy version
You override a confirmed row after validation	Filing returns to MAPPING_IN_PROGRESS	Re-run validation
Override drives the same line item to two different elements across reviewers	Last-write wins	Coordinate; the audit log preserves both

Related runbooks

• Confirm tag mappings
• Save a new synonym
• Run validation
• XBRL Filing SOP §6 / Step 3.0