account_pick_currency_date

A foreign currency invoice carries a rate, and by default that rate comes from the invoice date. Sometimes it should not: a contract may fix the rate at the order date, or an accountant may need to match a bank statement that converted on a different day.

This widget makes that a two-click operation. It puts a date picker beside the rate; picking a date asks the server for the rate that applied then, using the invoice's own company and currency, and writes the answer onto the invoice.

It then saves the record, so the change is committed rather than left pending.

Rate disputes are one of the more tedious categories of month-end query, and most of them come down to which date the rate was taken from. Making that an explicit choice on the invoice, rather than an implicit consequence of the invoice date, removes the ambiguity.

Worth deciding as policy: which date your business considers authoritative. The widget makes any date available, so without a rule it becomes a judgment call per invoice, which is the opposite of what you want in a reconciliation.

Placing it

<widget name="account_pick_currency_date"/>

No attributes. It reads the company and currency from the record.

What is sent to the server

get_currency_rate(
  record id, company id, currency id, chosen date
)

The date is sent as a plain date, without time.

Then

# the returned rate is written and the record saved

No separate save step.

The picker is configured as date only. That is a deliberate narrowing, because an exchange rate in Odoo is defined per day and a time component would be meaningless.

What is sent to the server is worth reading closely: the record identifier, the company identifier and the currency identifier, all taken from the invoice, plus the chosen date. Passing the company matters in a multi-company database, because rate tables are per company and the correct answer depends on whose books the invoice belongs to.

The apply handler is asynchronous end to end. It awaits the server call, writes the returned rate to the invoice's rate field, then awaits the save. Because the write and the save are chained, an error in either leaves the form in a state the user can see rather than silently half-applied.

The props declaration adds an optional record on top of the standard set, which is unusual for a view widget and reflects that the component guards against being rendered without one.

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.

Substantially rewritten. The development branch reworks the component with a large diff. The concept, a date picker that fetches and applies a rate, is what to expect to survive; the mechanics are being reshaped.