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 settings below live on the syndicate’s Billing & Rates screen under plain section labels (“Billing”, “Minimum Usage”, “Event Fees”, “Usage Capture and Billing”). There is no separate asset-level billing screen.
Multi-asset syndicate: the same settings appear on Syndicate → Settings → Billing & Rates 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

Owner and 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: Syndicate → Settings → Billing & Rates.
Multi-asset: Assets → [asset] → Billing settings at /syndicates/:syndicateId/assets/:assetId/billing, with defaults on Syndicate → Settings → Billing & Rates.

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.
Default taxi minutes	Minutes to subtract from block time to compute airborne hours. Defaults to 10 when unset.
Time capture mode	Which time fields the usage log prompts for: `engine_meter`, `clock_time`, or `both`.
Billing basis	Which time measurement drives the hourly charge: engine meter or clock time.
Max advance booking days	How far in advance a member can book.
Engine meter label	Display label for the engine meter (for example “Hobbs” or “Tacho”).
Clock time label	Display label for clock times (for example “Brakes” or “Blocks”).

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.

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.
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.