Billing & Rates screen

What it is

The Billing & 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), the time capture mode, the billing basis, taxi minutes, the meter and clock-time labels, and — for single-asset syndicates — the per-scheme rate overrides.

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”, “Event Fees”, “Usage Capture and Billing”). 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

• Owner and admin (including treasurer admins) — 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

In the app:

1. Open the syndicate.
2. Go to Dashboard → Syndicate settings → Billing & Rates.

Route: /syndicates/:syndicateId/settings/billing.

On a multi-asset syndicate, per-asset overrides live on each asset at /syndicates/:syndicateId/assets/:assetId/billing. See Default and per-asset settings.

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

Field	Notes
Usage rate	The base rate per usage unit (e.g. per hour for aircraft, per night for a property). The full operating cost. Required. 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. Required.

Minimum Usage · Default Minimum Usage

Field	Notes
Weekday minimum	Expected usage units per weekday in a booking. Zero disables weekday shortfall.
Weekend minimum	Expected usage units per weekend day in a booking. Zero disables weekend shortfall.

Event Fees · Default Event Fees

Field	Notes
Landing fee (per landing)	Per-event rate added per counted landing on the usage log.
Touch & Go fee (per circuit)	Per-event rate added per counted touch-and-go.

Other event types (lock passages, for example) can be configured via the underlying event_fees list. See Asset billing config.

Usage Capture and Billing · Default Usage Capture and Billing

Field	Notes
Usage capture mode	Dropdown. What the usage log captures. See Time capture modes.
Billing basis	Dropdown. Which time measurement drives the hourly charge when both are captured.
Default taxi minutes	Numeric. Subtracted from block time to compute airborne hours when billing basis is clock time. See Taxi minutes.
Engine meter label	Dropdown/custom. The word used to refer to the engine meter on the usage log (presets: Tacho, Hobbs).
Clock time label	Dropdown/custom. The word used to refer to the clock-time start/stop on the usage log (presets: Brakes, Blocks, Chocks).

Per-Scheme Rates (single-asset only)

For single-asset syndicates, a Per-Scheme Rates table appears at the bottom of the screen. It lists each billing scheme defined on the syndicate and lets you set the per-scheme rate for the single asset directly here. Every syndicate has at least the default Member scheme (created automatically when the syndicate was created), so this table is never empty.

For multi-asset syndicates, this 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.

See Member rates (billing schemes) for how scheme modifiers combine with the base rate.

Behaviour rules

• Section labels track asset count. The Billing & Rates screen relabels its section headers based on assets.length. Single-asset → plain labels. Multi-asset → “Default …” labels.
• All billing fields live in the syndicate’s default_billing map. Per-asset overrides are rows in asset_billing_configs and only exist in multi-asset mode.
• Save merges editable fields into existing default_billing. Unedited fields (for example, currency, which is set on Payments & Schemes) 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 Payments & Schemes, not here. See Payments & Schemes.
• Minimum usage only applies to non-maintenance bookings. Maintenance bookings never carry a shortfall charge regardless of the configured minimums.

Learn

If you’re new to this screen, work through a tutorial end-to-end before diving into the reference:

• Set up your first syndicate — owner. 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

• 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).
• Payments & Schemes — where currency, units, 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.
• Time capture modes · Taxi minutes