Mapping dropdown doesn't show the key I want
You're trying to override a TB row to a specific SFRS taxonomy key, but the dropdown doesn't have it.
What this means
The mapping dropdown is constrained to the SFRS constitution (packages/financial-statements/constitution/sfrs_taxonomy.json). There is no free-form input by design — every key must be in the constitution.
Causes
- The key exists but is in a different section. Type the section name (e.g.
non_current_assets) into the type-ahead. The dropdown filters by key + label + section. - The key is a full SFRS concept not present in the SFRS for Small Entities subset, and your engagement is
SFRS_SE. Check the dropdown filter — it scopes byreportingStandard. If you need it, switch the engagement toFULL_SFRS(header edit). - The key is genuinely missing from the constitution. The constitution covers the bulk of SFRS but is not exhaustive. Decide:
- Map to the closest semantic match; document the rationale on the override.
- Or file a constitution-change request — qualified-accountant sign-off PR adding the key to
sfrs_taxonomy.json. This is governed; updates to the constitution affect all clients.
Diagnose
bash
# Verify the constitution contents
node -e "console.log(Object.keys(require('@breezycorp/financial-statements').loadSfrsTaxonomy().taxonomy.balance_sheet))"Or search:
bash
grep -i '"label"' packages/financial-statements/constitution/sfrs_taxonomy.json | grep -i 'lease'Fix
- If the key exists but the dropdown filtered it out: change the filter or pick a section from the section selector.
- If the key is missing and the closest semantic match is acceptable: pick it; document on the override.
- If a constitution add is genuinely required: open a PR with the new entry; reviewer should be a qualified accountant.