Asset rates screen
What it is
Section titled “What it is”The Asset rates screen is the central place to configure how a syndicate charges for usage. It covers the asset’s usage rate (“wet rate” in aviation), the shortfall rate (“dry rate”), weekday and weekend minimum usage, event fees (landing, touch-and-go), and (for single-asset syndicates with more than one billing tier) the per-scheme rate overrides.
Usage capture (which time measures the log records, which one it bills on, taxi minutes, the per-measure labels) is configured separately, on the Usage capture screen. This screen owns only the money.
The section labels on this screen change depending on whether the syndicate has one asset or more than one. Single-asset syndicates see plain labels (“Billing”, “Minimum Usage”, “Home airfield fees”). Multi-asset syndicates see the same fields under “Default” labels (“Default Billing”, and so on), because those values act as defaults that each asset can override on its own billing screen.
Who can use it
Section titled “Who can use it”- Admin (including treasurer admins): can view and change every field.
- Members: do not see this screen. They see the resulting rates on the usage-log estimate and on their statement.
Where to find it
Section titled “Where to find it”In the app:
- Open the syndicate.
- Go to the Admin tab.
- Under Money, tap Asset rates.
On a multi-asset syndicate, per-asset overrides live on each asset’s own billing screen. See Default and per-asset settings.
Fields / options
Section titled “Fields / options”The screen is divided into four sections. All labels below are shown in the single-asset form; the multi-asset label (in italics) is the same field with the “Default “ prefix.
Billing · Default Billing
Section titled “Billing · Default Billing”| Field | Notes |
|---|---|
| Usage rate | The base rate per usage unit (e.g. per flying hour). The full operating cost. The only compulsory field on the screen: saving is refused while it is empty, and the field is marked at that point. Shown with the syndicate’s currency symbol. |
| Shortfall rate | The rate applied to the difference between expected minimum usage and actual usage. Usually lower than the usage rate. Optional, and labelled Shortfall Rate (optional) to say so. Left blank it saves as zero, and a zero rate raises no shortfall charge at all, whatever the minimums below are set to. Reopen the screen after that and the box reads 0.00 rather than being empty; clearing it again saves zero again. |
Minimum Usage · Default Minimum Usage
Section titled “Minimum Usage · Default Minimum Usage”| Field | Notes |
|---|---|
| Weekday minimum | Expected usage units for each qualifying weekday a booking covers. Zero disables weekday shortfall. |
| Weekend minimum | Expected usage units for each qualifying Saturday or Sunday a booking covers. Zero disables weekend shortfall. |
A day only qualifies when the booking covers at least eight hours between 08:00 and 20:00 on that day, so a minimum bites on a booking that holds the aircraft for most of the working day and not on a short one. The rule and its worked consequences are in Finalisation rules.
Home airfield fees · Default home airfield fees
Section titled “Home airfield fees · Default home airfield fees”| Field | Notes |
|---|---|
| Home airfield | The ICAO code the fees below are charged at, entered in upper case (for example EGMC). Leads the section, because the fees mean nothing without it. An asset can override it in its own settings. |
| Landing fee (per landing) | Per-event rate added per counted landing on the usage log. Disabled until a home airfield is set. |
| Touch & Go fee (per circuit) | Per-event rate added per counted touch-and-go. Disabled until a home airfield is set. |
With no home airfield, both fee boxes are greyed out and a line under the airfield field says why: a fee with nowhere to charge it would never bill anything, so the screen refuses to let one be entered rather than accepting a rate that silently does nothing.
Other event types (lock passages, for example) can be configured on the asset’s billing config. See Asset billing config.
For aircraft, event fees are home-airfield fees: they are charged only when the flight’s arrival matches the asset’s home airfield. An away arrival, or no home airfield set, means no event fees for that log.
Usage capture
Section titled “Usage capture”Which time measures the log records, which one the usage rate bills on, the taxi-minutes prefill, and the per-measure labels are configured on the separate Usage capture screen (Admin → Usage capture). The usage-capture redesign decoupled capture from money, so it no longer lives here.
Per-Scheme Rates (more than one tier)
Section titled “Per-Scheme Rates (more than one tier)”The Per-Scheme Rates section only appears once the syndicate has more than one billing tier. Every syndicate starts with just the default Member tier, so by default there is nothing to vary per scheme: the usage rate and event fees above are the rate everyone pays, and no per-scheme section is shown. Add a second tier on the Billing schemes screen and the section appears.
When it does appear, the rates above are framed as the default tier’s rate; other tiers adjust from it. For single-asset syndicates the per-scheme table is shown directly on this screen and lets you set each tier’s rate for the single asset. For multi-asset syndicates the section is replaced with a note: per-scheme rates are configured on each asset’s own billing screen, because schemes can have different rates on different assets.
Each per-scheme row carries a tag showing where its rate came from: from default (the tier pays the default rate), from modifier (the tier’s scheme modifier produced it), or overridden (an explicit per-asset rate is pinned for that tier). Event-fee rows show from default or overridden.
See Member rates (billing schemes) for how scheme modifiers combine with the base rate.
Behaviour rules
Section titled “Behaviour rules”- Section labels track asset count. The Asset rates screen relabels its section headers based on how many assets the syndicate has. Single-asset → plain labels. Multi-asset → “Default …” labels. Because those headings are a statement about how many aircraft the syndicate holds, the form waits for the aircraft list before it draws, and says so if the list cannot be read, rather than showing the multi-asset labels to a single-aircraft syndicate and rewriting them a moment later.
- The usage rate is the only compulsory field, and it is checked on save. Nothing is marked as missing while you fill the form in; tapping Save with an empty usage rate refuses the save and marks that field. Every other box on the screen may be left blank.
- A blank shortfall rate charges no shortfall. Blank saves as zero, and a zero shortfall rate produces no shortfall charge at finalisation even when a weekday or weekend minimum is set — so a minimum entered without a shortfall rate costs an under-flying member nothing. Blank means “inherit the value above” only on an asset’s own billing screen in a multi-asset syndicate; on this screen there is nothing above to inherit from.
- All billing fields live as syndicate defaults. Per-asset overrides exist only in multi-asset mode and are configured on each asset’s own billing screen.
- Save merges editable fields into the existing defaults. Unedited fields (for example, currency, which is set on the Payment account screen) are preserved rather than wiped. The form handles this for you; there is no global save that clobbers other screens.
- The snapshot rule applies to every charge. When a usage log is saved, the resolved rates at that moment are stored on the log. Later changes to the syndicate default or per-asset override do not back-date prior bookings’ charges. See Finalisation rules.
- Currency is shown as a symbol throughout the screen. It is set on the Payment account screen, not here. See Payment account and Billing.
- A minimum only counts the days a booking effectively takes for the whole day. Each calendar day a booking touches is judged on its own, and contributes its minimum only if the booking covers at least eight hours between 08:00 and 20:00 on that day. Hours outside 08:00–20:00 count towards nothing. A weekday booking from 09:00 to 13:00 therefore expects nothing and can never raise a shortfall, whatever you set the weekday minimum to; nor can one from 05:00 to 13:00, which is eight hours long but holds only five of the core ones. Set a minimum expecting it to price short flights and it will do nothing. See Finalisation rules for the full rule and the multi-day case.
- Minimum usage only applies to non-maintenance bookings. Maintenance bookings never carry a shortfall charge regardless of the configured minimums.
If you’re new to this screen, work through a tutorial end-to-end before consulting the reference:
- Set up your first syndicate (admin): takes a fresh account through to a syndicate with one aircraft and a configured usage rate.
- Finalise your first month (treasurer/admin): once rates are set, this tutorial walks the end-of-month flow that consumes them.
See also
Section titled “See also”- Usage capture: the captured measures, billed measure, taxi minutes, and meter labels, configured on their own screen.
- Default and per-asset settings: the cascade that makes this screen behave differently for single vs multi-asset syndicates.
- Asset billing config: the underlying per-asset row (multi-asset syndicates only).
- Payment account and Billing: where currency, the billing cycle, and scheme definitions live.
- Member rates (billing schemes): how the modifier interacts with the base rate.
- Rate resolution chain: the precise precedence of override → scheme modifier → base rate.
- Captured measures and the billed measure · Taxi minutes