nemhandel_verification_code

Registering for Danish e-invoicing involves a code sent by SMS, and codes like that are conventionally shown as separate boxes rather than one input. The convention exists because it makes the length obvious and lets each character be corrected without retyping the rest.

This widget implements that. Six boxes, focus that advances as you type, and backspace that steps back when the current box is already empty.

It also handles the way people actually enter codes from a phone: pasting. Rather than dropping the whole string into one box, the paste handler distributes the characters forward from wherever the paste landed.

Two-step registration flows fail at the code entry step more often than anywhere else, and almost always for interface reasons: the paste does not work, the focus does not move, or a mistyped character means retyping everything. This widget removes all three.

The wider point is that a compliance flow is only as good as its worst screen. E-invoicing registration is a one-off task done under mild pressure, and the difference between a smooth code entry and an awkward one is whether it gets finished in one sitting.

The usual usage

<field name="verification_code"
       widget="nemhandel_verification_code"/>

The field name matters: the widget writes that name literally when all six boxes are filled.

What pasting does

# paste "482913" into the third box
# fills boxes 3, 4, 5, 6 with 4, 8, 2, 9

Characters are distributed forward from where the paste landed, and any surplus is discarded.

The plain alternative

<field name="verification_code"/>

One input, no focus handling and no distributed paste.

Three handlers make up the widget, and each is small.

The paste handler stops the default paste, splits the clipboard text into characters and walks forward from the box that received the paste, assigning one character to each remaining box. Anything left over is dropped, and if the paste is shorter than the remaining boxes the rest are cleared. A comment in the source names the intention: letting users copy the code straight from the SMS.

The key handler moves focus forward when a box has one character and is not the last, and backward when backspace is pressed on an already empty box that is not the first. That is the standard behavior for code inputs, and getting the empty check right is what makes correcting a mistake feel natural.

The save is the strict part. The widget joins the six values and writes the field only when the result is exactly six characters long, so a partial code never reaches the record and the server never sees something it would reject.

The field it writes is named literally rather than taken from the widget's own field, which is why this is a single-purpose widget despite the behavior being generic.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable and this may still change; we re-verify this page after the release.

The widget moves module. On the development branch the file and its wizard live in the Danish localization itself rather than in the separate Nemhandel module, while the registered widget name is unchanged.

View XML naming the widget keeps working provided the new module is installed, but a custom module depending on the old one purely to get this feature should depend on the localization instead.