monetary_no_zero

Odoo's accounting screens print zero amounts as 0.00, which is correct and also visually loud: a matching table where most cells are zero becomes a wall of noise in which the actual amounts hide. monetary_no_zero fixes the display without touching the data.

The implementation is a 12-line subclass of the monetary widget that overrides one getter. Where the base value returns the field's number, this one first asks floatIsZero(value, decimals), using the currency's decimal places when a currency is loaded and 2 otherwise, and returns false for zeros. The formatter downstream renders that as nothing.

Everything else is inherited unchanged from the monetary descriptor: the currency symbol logic, the precision rules, and all four options, including the extractProps-only field_digits.

The widget was born for a specific accounting workflow: three-way matching between purchase orders and vendor bills. In that list every line carries a Billed and a Purchased column, and on any given line one of them is usually zero. Blanking the zeros turns the table into something a bookkeeper can scan diagonally: filled cells are the story.

The same pattern applies anywhere sparse amounts appear: commission columns that only some lines earn, discount columns used on a few orders, landed cost splits. If your users' first act in a list view is visually filtering out the zeros, this widget does it for them.

The important guarantee for finance teams: it is display-only. Stored values, column sums, exports and reports all still see the true zeros; nothing about the posting changes.

How core applies it in the bill matching list

<field name="billed_amount_untaxed" widget="monetary_no_zero" sum="Total Billed" string="Billed"/>
<field name="purchase_amount_untaxed" widget="monetary_no_zero" sum="Total Purchased" string="Purchased"/>
<field name="currency_id" column_invisible="1"/>

Note the invisible currency_id: it feeds both the symbol and the zero test's precision.

Using it on your own sparse column

<field name="commission_amount" widget="monetary_no_zero"
       options="{'currency_field': 'company_currency_id'}"/>

Combining with inherited options

<field name="margin" widget="monetary_no_zero"
       options="{'no_symbol': True, 'hide_trailing_zeros': True}"/>

A few source-level details define its exact behavior.

The override sits on the display getter, not the formatter. Because value itself returns false for zeros, every consumer of that getter blanks: the readonly cell, the tooltip and the input's initial content in edit mode. The stored field value is untouched; open the row for editing and typing a real amount works normally.

Near-zero equals zero. floatIsZero(0.004, 2) is true, so amounts below half the currency's smallest unit vanish along with true zeros. That is almost always what an accountant wants in a matching view; it is worth knowing when debugging why a residual 0.004 does not show.

Aggregates ignore the widget. List sum attributes aggregate raw field values server-side, so the totals row keeps counting the hidden zeros, which of course add nothing, and stays consistent with exports.

Name versus file. The registry name is monetary_no_zero; the file and directory are monetary_field_no_zero. Grep for the registration, not the filename, when hunting it in the source.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026, and the development branch may still change before then.

For this widget the branch shows no behavioral change: the only diff is the framework-wide migration to the new useProps API for component props. The zero test, the currency precision logic and the registration are identical. Inherited behavior tracks the base monetary widget, which is also stable on the branch. We re-verify against the shipped release.