Override a low-confidence mapping

Who does this: FS Preparer · Senior Accountant · Platform Admin When: An AI-suggested mapping is wrong (you read the rationale and disagree) or auto-suggest returned UNCLASSIFIED for a row. Result: The row's taxonomyKey is set manually, isOverride = true, and mappingConfidence = MANUAL. The activity log captures the override.

Manual overrides are a first-class part of the workflow — the AI's job is to bulk-process the obvious 90%, the reviewer's job is to take a position on the rest. Don't apologise for overriding.

Before you start

• [ ] Engagement at TB_UPLOADED or TB_MAPPED (overrides are allowed in both).
• [ ] You hold OVERRIDE_FS_MAPPING.
• [ ] You know which SFRS taxonomy key the row should map to. If you don't, check the SFRS for Small Entities standard reference and the constitution sfrs_taxonomy.json.

Steps

1. Open the engagement → Mapping tab.
2. Find the row. Filter by confidence != HIGH to see candidates.
3. Click the row to open the override panel (or click the dropdown directly in the table).
4. Open the Taxonomy key dropdown. Type-ahead filters by key + label. The list is constrained to the SFRS constitution — you cannot type a free-form key.
5. Pick the correct key. The label and section preview update.
6. (Optional) Add a rationale in the Rationale text field. This appears on the audit log payload.
7. Click Save. The row's badge flips to MANUAL, isOverride = true. The activity log shows fs.mapping.overridden.

How to know it worked

1. The row's confidence chip is now MANUAL.
2. Hovering the chip shows your rationale.
3. The activity log shows fs.mapping.overridden with the row id and the new taxonomyKey.
4. If the override completed the mapping (no rows left unmapped), the engagement transitions to TB_MAPPED.

Common situations

If you see…	It means…	What to do
The key you want isn't in the dropdown	The SFRS constitution doesn't carry it	Pick the closest semantic match; document the rationale. If genuinely missing, file an issue to add the key to the constitution (qualified-accountant sign-off required). See Missing taxonomy key
The same row needs a different key after statements run	Generation surfaced a sign-flip anomaly	Re-open Mapping; override; regenerate. The status badge will not change
You overrode a HIGH-confidence row	You disagreed with Claude	Allowed; the audit trail captures the override and the reason. Re-running auto-suggest will not clobber it
Two preparers race on the same row	Last-write wins	Refresh the page before saving; coordinate on Slack

Related runbooks

• Run AI auto-suggest mapping — bulk path
• Generate statements — next step
• FS-03 userflow
• Financial Statements SOP §6 / Step 3.0
• Missing taxonomy key