Why a Nominal Code cannot be deleted after Moving Transactions

Even if you’ve moved or re‑posted all visible transactions off a nominal code, BrightBooks may still prevent deletion if any of the following apply:

1. The code is still in use in settings or defaults
   • The nominal is set as a default account in:
     • General setup (e.g. default sales, purchases, bank charges, rounding, etc.)
     • VAT or tax settings
     • Product or service defaults
   • The code is used in:
     • Recurring invoices/receipts/payments
     • Bank feed rules
     • Templates or system mappings
2. The code is still referenced by “hidden” or system transactions
   • Historical or system‑generated entries (e.g. opening balances, year‑end journals, VAT adjustments) may still reference the code.
   • These may not be obvious in day‑to‑day transaction lists but still exist in the ledger.
3. The code is part of a locked period or year
   • If the code has any entries in a locked period or a closed year, BrightBooks will not allow deletion.
   • Even if you’ve moved current‑year activity, older locked entries can still be tied to that code.
4. The code is used in reports or structures
   • The nominal may be part of:
     • A reporting group or structure
     • A custom layout or mapping
   • While this alone doesn’t always block deletion, in some setups it can contribute to the code being treated as “in use”.