How the operator overview should total money when a deployment bills in several currencies #79

New Issue

2026-09-21T07:18:24Z

cgalo5758 commented

2026-09-21 07:18:24 +00:00

The question

The overview's monthly recurring headline and the outstanding-invoices caption sum money per currency and show only the largest bucket, acknowledging the rest as a count of further currencies. That is honest and incomplete: a deployment that genuinely bills in several currencies reads a headline that understates what it takes in. Showing one number means converting, and converting needs a rate source, a staleness rule and a way of writing an approximate total that nobody mistakes for an exact one. None of the three exists, deliberately.

What depends on the answer

Whether the console grows a rate source of its own, and whether the overview's headline numbers stay exact sums or become approximations.

Options known so far

Keep the per-currency split and show every bucket rather than the largest one.
Convert with rates an operator enters by hand, each stamped with when it was entered.
Convert with rates pulled from a public reference feed, refusing to convert when they are too old.
Read the totals from the payment provider's own reporting, which already converts, instead of holding rates in the console at all.

Whichever converts, the display convention has to mark an approximation as one. Single-currency deployments, the expected case, are unaffected by every option.

Decided when

The billing model states where a converted total's rate comes from, how stale a rate may be, and how an approximate total is written.

Migrated from status/issues.md at b7a0e15

## The question The overview's monthly recurring headline and the outstanding-invoices caption sum money per currency and show only the largest bucket, acknowledging the rest as a count of further currencies. That is honest and incomplete: a deployment that genuinely bills in several currencies reads a headline that understates what it takes in. Showing one number means converting, and converting needs a rate source, a staleness rule and a way of writing an approximate total that nobody mistakes for an exact one. None of the three exists, deliberately. ## What depends on the answer Whether the console grows a rate source of its own, and whether the overview's headline numbers stay exact sums or become approximations. ## Options known so far - Keep the per-currency split and show every bucket rather than the largest one. - Convert with rates an operator enters by hand, each stamped with when it was entered. - Convert with rates pulled from a public reference feed, refusing to convert when they are too old. - Read the totals from the payment provider's own reporting, which already converts, instead of holding rates in the console at all. Whichever converts, the display convention has to mark an approximation as one. Single-currency deployments, the expected case, are unaffected by every option. ## Decided when The billing model states where a converted total's rate comes from, how stale a rate may be, and how an approximate total is written. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

design

area/billing area/operator-ui labels 2026-09-21 07:18:24 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#79