Work

Budgets and approvals

Budgets and approvals are the two guard rails a Work account can put on spend. Both are optional, and an admin turns them on from the Settings tab.

Monthly budgets

An admin can give any member a soft monthly budget: an amount and a currency. As work spend for the current month adds up, the Expenses tab shows how each budgeted member is tracking against their cap.

A budget is a guide rail rather than a gate. Going over it flags the member on the usage list; it never blocks an expense from being logged. Spend is compared in the budget's own currency with no conversion, so a budget set in one currency only counts spend in that currency.

Group budgets

A group (see Groups) can carry its own spend policy on top of the account's, set from the Team tab. Two figures are available, and a group can use either, both, or neither:

  • A group pot. One shared budget for everyone in the group combined; spend by anyone coded to that group counts against it.
  • A per-person allowance. A cap that applies to each person's own spend, but only within that group, separate from any account-wide monthly budget they have.

A blank figure means the group has no budget of its own. There is nothing to inherit here: the account-wide budget in Monthly budgets is set per person, not per group. Group budgets follow the same no-conversion rule: spend counts against a group budget only when it's in that budget's own currency.

With all of this available at once, a given overspend is always against one specific number. A person over their own account-wide monthly budget is flagged there regardless of which group the spend was coded to. A group over its shared pot is flagged on the group, regardless of who spent it. A person over their per-person allowance within a group is flagged on that group, for spend coded to that group only. It says nothing about their account-wide budget, and spend coded elsewhere doesn't count against it.

Approvals

Approvals let an admin sign off on spend before it's treated as processed. An expense lands in the queue two ways:

  • Require approval. When on, every new work expense starts as pending.
  • Approval threshold. A home-currency amount above which an expense needs sign-off even when blanket approval is off. Any expense at or over the threshold queues; smaller ones pass straight through. The comparison uses the account's home currency, so a home currency needs to be set for the threshold to apply.

Pending expenses collect in an approval queue on the Expenses tab, oldest first, and the account's admins are notified when a new one arrives.

Group approval thresholds

A group (see Groups) can also require approval or set its own threshold, from the same Team tab settings as its budgets. A blank threshold means the group leaves approval entirely to the account's own setting.

A group's threshold can only make approval stricter, never looser. If a group sets a lower threshold than the account's, expenses coded to it queue for approval sooner. A group threshold higher than the account's simply doesn't apply; the account's own threshold still governs, and setting the group's is refused at save time so it's never mistaken for having an effect. The same one-way rule applies to the require-approval checkbox: turning it on for a group adds an approval requirement on top of the account's, and turning it off never removes the account's own requirement.

The stricter-only rule is enforced whenever an expense is checked, not only when a group's threshold is saved. If the account's threshold is later lowered below a group's existing one, the group's threshold stops applying from that moment, with no change needed on the group's own settings; the account's lower figure takes over.

Approving and rejecting

From the queue, an admin can Approve an expense in one tap or Reject it. A rejection requires a written reason, and that reason stays on the expense so the traveller knows exactly what to fix. The person who logged the expense is notified either way.

Trip approvals

An account can also require trip approval. When it's on, a trip a plain member attributes to the Work account waits for an admin's sign-off before it counts as sanctioned work travel. Trips an admin or owner attributes are approved on the spot. See Team and domains for who holds which role.