Override a rate for an asset

Override a rate for an asset

A billing scheme’s modifier normally applies across every asset. If one asset should carry a different rate for members on a particular scheme, set a per-asset override that replaces the scheme’s modifier for that asset only.

Before you start

• You must be an admin.
• The Per-Scheme Rates section only appears once the syndicate has more than one billing tier. With just the default tier there is nothing to vary per scheme, so the section is hidden. Create a member rate first.
• For a single-asset syndicate, the Per-Scheme Rates table lives on the syndicate’s Asset rates screen. Edits there are overrides for that single asset.
• For a multi-asset syndicate, the Per-Scheme Rates table lives on each asset’s own Billing screen.
• The override takes precedence over the scheme’s modifier; see the rate resolution chain: override → scheme modifier → base rate.

Steps for a single-asset syndicate

1. Open the syndicate.
2. Go to the Admin tab, then tap Asset rates.
3. Scroll to the Per-Scheme Rates table.
4. In the row for the scheme you want to override, enter the effective rate for this asset.
5. Tap Save Rates.

Steps for a multi-asset syndicate

1. Open Syndicate → Assets → [asset] → Billing.
2. Scroll to the Per-Scheme Rates table.
3. In the row for the scheme you want to override, enter the effective rate for this asset.
4. To revert a row to the scheme’s computed rate, tap the reset icon on that row.
5. Tap Save Rates.

Each row carries a tag showing where its rate came from: from default (the tier pays the default rate), from modifier (the scheme modifier produced it with no override set), or overridden (an explicit per-asset rate is pinned for that tier).

Example

A two-aircraft syndicate has a Cessna 172 (base £180/hr) and an SR22 (base £260/hr). Members on the Renter scheme pay £220 on the 172 via a scheme-level override = £220. For the SR22, set a per-asset override of £300 on the Renter row, leaving the Cessna row to use the scheme’s override.

Overriding event fees for a scheme

Event fees (landing fees, touch-and-go fees, and any other configured counter fees) have their own per-asset, per-scheme override. It works the same way as the usage-rate override on this page, but lives in a separate table: the Event Fees section of the asset’s Billing screen. Use it to waive landing fees for a founder scheme (enter 0), raise them for a renter scheme, or do both at once.

1. Open Syndicate → Assets → [asset] → Billing.
2. Scroll to the Event Fees table. It lists one row per (scheme, counter) pair.
3. In the row for the scheme and counter you want to override, enter the effective fee. 0 waives the fee for that scheme on that asset.
4. Tap Save Event Fees. Reset All stages a delete of every saved override and reseeds the fields with the asset’s base fees; it still needs Save Event Fees to commit.

There is no modifier layer for event fees: either there is an override (used) or there isn’t (base fee from the asset applies). See Member rates, Example 5 for worked cases.

If it goes wrong

• On a multi-asset syndicate, the Asset rates screen shows a note instead of the Per-Scheme Rates table. Configure the rate on each asset’s Billing screen instead.
• A saved override does not change a past booking’s charge; rates are snapshotted at usage-log time. See Finalisation rules.

See also

• Rate resolution chain: the full precedence order, override → modifier → base rate
• Asset billing config: the underlying per-asset row
• Member rates (billing schemes): how the modifier works by default
• Default and per-asset settings: the cascade for all billing fields