many2many_tags_salary_bank

Odoo 19 lets an employee's salary be split across bank accounts, by percentage or fixed amount. The employee form shows those accounts as tags, and this widget's job is to make each tag carry its share: (30%) before the account's display name for percentage splits, (1500.00$) style for fixed amounts.

It extends the color-editable variant of many2many_tags and overrides getTagProps to build the prefixed text. The amounts come along invisibly: a relatedFields declaration injects the salary amount, the percentage flag and the currency symbol into every tag record fetched, so the view needs no extra columns.

The prefix has a gate: the widget reads has_multiple_bank_accounts off the parent employee record, by literal name, and only decorates tags when it is truthy. One account means no split, so tags render clean.

Salary distribution is a payroll-critical setting: get a split wrong and someone's rent account receives the wrong amount at the end of the month. Encoding the split into the tag itself means HR sees the current distribution every time they glance at the form, not only inside the account records.

The aggressive save behavior serves the same goal. Editing an account through its tag dialog can change the split; the widget responds by saving the whole employee record and reloading it, so the percentages you see are always post-recompute, never stale. The cost is that unrelated pending edits on the form get saved along the way, worth knowing before you open a tag mid-edit.

Core also wraps the field with guardrails: it is read-only until the employee record is saved once, and quick-create from typed text is disabled in favor of the full account dialog, since a bank account needs more than a name to be payroll-ready.

How core applies it (employee form, multi-account block)

<field name="bank_account_ids" widget="many2many_tags_salary_bank"
       context="{'default_partner_id': work_contact_id}"
       options="{'color_field': 'color', 'no_quick_create': True, 'edit_tags': True}"
       readonly="not id"/>

Each piece is deliberate: the context routes new accounts to the employee's work contact, no_quick_create forces the full dialog, edit_tags makes a tag click open the account for editing, and readonly="not id" disables the field until the employee exists.

The visible result

Percentage split:  (30%) BNP Paribas ...1234   (70%) ING ...5678
Fixed amount:      (1500.00$) Chase ...4321
Single account:    Chase ...4321

Percentages above 100 are treated as invalid and render without the prefix; fixed amounts print with the account currency's symbol when available.

Three overrides carry all the behavior, and each has an edge worth knowing.

getTagProps builds the label. It starts from the base tag props and rewrites text. Percentage mode only prefixes when the amount is at most 100, using a whole-number format; amount mode prints two decimals plus the currency symbol when one is loaded. If the parent's has_multiple_bank_accounts field is missing from the view, the gate reads undefined and prefixes never show, silently.

openMany2xRecord is wrapped. The original opens the account dialog; the wrapper awaits it, then checks whether the form's root record is dirty, saves it if so, and reloads the record. That is what keeps split percentages coherent after edits, and also what commits unrelated pending changes on the employee form as a side effect.

extractProps hardcodes the create field. After delegating to the base, it sets nameCreateField = "acc_number", so any created account lands with the typed text as its number rather than a name. In core this path is mostly moot, quick create is disabled in the views, but custom views omitting no_quick_create will feel it.

Templates are forced backward. The class pins web.Many2ManyTagsField and a TagsList pinned to web.TagsList, undoing the color-editable variant's templates. Colors still tint the tags via color_field; the editing affordance is what disappears.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026, and the development branch can change until release. This widget moves more than most:

Rebased off the color-editable variant onto plain Many2ManyTagsField, with color_field explicitly filtered out of the supported options; the employee views switch their tag click behavior to the new on_tag_click: 'open_form' option and drop edit_tags.

Focus saves the record. A new onFocusIn override saves the employee record the moment the field is focused on an unsaved form, replacing 19's readonly="not id" guard in the views, the field becomes usable immediately at the price of an implicit save.

The create field renames from acc_number to account_number, tracking the server-side field rename on bank accounts. We re-verify all three against the shipped release.