account_document_state

Electronic invoicing flows, Greece's myDATA, Romania's E-Factura and friends, track each submission in a document record with a state selection and a free-text message holding whatever the government API answered. This widget displays both without spending two columns.

It extends the standard selection field, so the state itself renders unchanged: the label of the current selection value, with whatever row decorations the list adds. The subclass contributes one thing, an fa-info-circle anchor rendered after the value whenever the record's message field holds text. Clicking it opens a popover anchored to the icon, positioned above, that prints the message with line breaks preserved and offers a clipboard button; copying shows a Text copied toast and closes the popover, and clicking the icon again toggles it shut.

Registration spreads the base selectionField descriptor with only the component swapped, which is why everything about the selection behavior, including its quirks, carries over verbatim.

When a tax authority rejects an invoice, the difference between a cryptic Failed state and the actual error text is a support ticket versus a self-service fix. This widget keeps the rejection reason one click from the status, and the copy button exists for exactly the workflow you expect: paste the raw government error into a search, a helpdesk ticket or an email to the accountant.

The pattern is just as useful outside localizations. Any custom integration that records a status plus a response payload, payment gateways, EDI bridges, shipping APIs, can reuse this widget as-is on its own document model: name the text field message, load it invisibly next to the state, done.

The full pattern, from the myDATA documents list

<list>
    <field name="message" column_invisible="1"/>
    <field name="datetime"/>
    <field name="state" widget="account_document_state"/>
</list>

The invisible column is the load trigger; without it the widget has no message to show.

On a custom integration log model

state = fields.Selection([...])
message = fields.Char(readonly=True)  # the name is the contract

Any model with this pair can use the widget; the field must be named message, nothing else is read.

The popover mechanics are small but deliberate. The component keeps the popover's close function on itself: clicking the icon while open closes it, so the icon is a true toggle rather than a stacker. The popover mounts with closeOnClickAway and position: "top", prints the message inside a white-space: pre-wrap span so multi-line government responses keep their formatting, and the copy button writes the raw message to navigator.clipboard, which quietly requires a secure context, HTTPS or localhost, to function.

The inheritance detail worth knowing: because the descriptor spreads selectionField, the widget also inherits selection's extractProps, which enables autosave in kanban cards, and its declared placeholder_field option, which the base extractProps never reads, a dead declaration this page's sibling selection page documents. Neither matters in the embedded readonly lists core uses, but both travel with the widget if you deploy it elsewhere.

And the core inconsistency, verified in 19.0 and still present on the development branch: l10n_ro_edi's E-Factura documents list applies the widget without loading message, so Romanian invoice errors are only reachable through the move's message history, not the popover. The Romanian e-Transport modules, which subclass this widget, do load it correctly.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. We compared the widget's file on the public development branch at the time of writing, with the usual caveat that the branch is unstable until release.

Byte-identical to 19: component, popover and registration are unchanged, and the base selection descriptor it spreads is also unchanged for this widget's purposes. Even the unloaded message in the E-Factura list is still there. We re-verify once Odoo 20 ships.