Asset billing config

Where these settings live

Read this first: the same fields appear in different places depending on the syndicate’s asset count.

Single-asset syndicate: the money settings below live on the syndicate’s Asset rates screen under plain section labels (“Billing”, “Minimum Usage”, “Home airfield fees”); the capture settings (captured measures, billed measure, taxi minutes, labels) live on the Usage capture screen. There is no separate asset-level billing screen.
Multi-asset syndicate: the same settings appear on the Admin tab → Asset rates (under Money) under “Default …” labels and act as defaults. Each asset additionally gets its own billing screen at /syndicates/:syndicateId/assets/:assetId/billing where any field can be overridden for that asset only.

The rest of this page documents the fields themselves; the semantics are identical in both modes. For the location-and-override mechanics, see Default and per-asset settings.

What it is

The asset billing config is the financial rule set for an asset. It defines the asset’s base usage rate, its shortfall rate, any event fees (for example landing fees or touch-and-go fees), minimum usage expectations, how time is captured on a usage log, and which time measurement drives hourly billing.

Every field is optional at the asset level (multi-asset only). When a field is empty, the asset inherits the value from the syndicate’s default billing settings.

Who can use it

Admin: read and edit.
Treasurer (admin): read and edit.
Member: not editable. Rates a member actually pays show up on the usage-log estimate and on finalised transactions.

Where to find it

See the box above. The short version:

Single-asset: open the syndicate and go to the Admin tab, then tap Asset rates (under Money).
Multi-asset: tap Admin tab → Asset rates for the defaults; for an asset override, open the asset and tap Billing Settings.

Fields / options

Field	What it sets
Usage rate	Cost per usage unit (e.g. per hour for aircraft). Used as the base rate, the starting point for every member’s effective rate.
Shortfall rate	Rate per unit applied when a booking uses less than the configured minimum. See finalisation-rules.
Weekday minimum usage	Expected usage per weekday in a booking. Zero disables weekday shortfall.
Weekend minimum usage	Expected usage per weekend day in a booking. Zero disables weekend shortfall.
Event fees	Per-event rates (e.g. landing fee, touch-and-go fee). Each entry carries a counter key, a display label, and a rate. Charged only at the home airfield; see Behaviour rules below.
Default taxi minutes	Estimated one-way taxi time used to prefill the log’s bracketing times. A data-entry aid only; it does not affect any charge. Defaults to 0 when unset.
Captured measures	Which time measures the usage log records, as independent tick-boxes: engine meter, block time, airborne time. At least one must be ticked.
Bill on (billed measure)	Which one of the captured measures the usage rate prices. Shown only when more than one measure is captured.
Measure labels	Display label for each captured measure: “Engine meter label” (e.g. “Hobbs”, “Tacho”), “Clock time label” (e.g. “Brakes”, “Blocks”), and “Airborne time label”.
Fuel unit	Unit the asset’s fuel uplifts are recorded in (Litres, US gallons, Imperial gallons).
Fuel rate per unit	Fixed reimbursement rate paid to a pilot per fuel unit when they buy fuel personally (the “home airfield rate” model). Empty means receipt-total mode: pilots are reimbursed whatever the receipt shows. Any positive value puts the asset in fixed-rate mode: pilots are reimbursed `rate × litres` regardless of pump price, insulating the group from premium-airfield costs. A rate of 0 is rejected at input; leave the field blank for receipt-total mode.

Each field shows its inherited effective value as hint text and starts empty. Typing a value pins an asset-level override; clearing the field reverts to the inherited default.

The fuel rate intentionally diverges from the equality-collapses-to-null pattern below: typing the same value as the syndicate default still pins it as an asset-level override. Fuel rate is a mode flip (fixed vs receipt), not a tracking number; explicit pinning needs to work even when the value matches what’s currently inherited.

Behaviour rules

The usage rate is the asset’s base rate. Members on different member rates pay a rate derived from this base via the rate resolution chain.
When a usage log is saved, the effective rates in force at that moment are snapshotted onto the log. Later edits to the asset billing config do not retroactively change what that log will charge at finalisation.
Minimum usage applies only to non-maintenance bookings. Maintenance bookings never carry a shortfall charge.
Event fees are stored as a list. Every active counter on the usage log (landings, touch-and-gos, lock passages, etc.) is matched to an entry by its counter key.
Event fees are home-airfield fees. For aircraft, event fees are charged only when the flight’s arrival matches the asset’s home airfield (the asset’s configured home airfield, or a syndicate-wide default if one is set). An away arrival, or no home airfield configured, means no event fees for that log; the time-based usage charge is unaffected. The match ignores case and surrounding spaces.
Taxi minutes never affect a charge. The default taxi value only prefills the log’s bracketing times. Airborne time is the measured Landing − Takeoff; it is zero when the wheels times are not captured.
Entering the same value as the inherited effective value saves as null (no override pinned), so the asset keeps tracking the syndicate default if the default later changes.
Rates are stored in the syndicate’s currency. They are displayed and recorded without VAT.