Payments & Schemes screen
What it is
Section titled “What it is”The Payments & Schemes screen is the admin’s second billing screen. It covers the settings that apply to the whole syndicate rather than to rates: the currency, the fuel unit and oil unit used on usage logs and expenses, and it is the navigation home for Billing Schemes — the named packages that combine dues and a usage-rate modifier.
Unlike the Billing & Rates screen, nothing here cascades per asset (other than currency, which in practice is always syndicate-level). The fields here are syndicate-wide.
Who can use it
Section titled “Who can use it”- Owner and admin (including treasurer admins) — view and change all fields; navigate to Billing Schemes.
- Members — do not see the Payments & Schemes screen.
Where to find it
Section titled “Where to find it”In the app:
- Open the syndicate.
- Go to Dashboard → Syndicate settings → Payments & Schemes.
Route: /syndicates/:syndicateId/settings/payments.
The Billing Schemes navigation opens at /syndicates/:syndicateId/billing-schemes.
Fields / options
Section titled “Fields / options”The screen is divided into three areas: Currency & units, Payment collection, and Billing Schemes.
Currency & units
Section titled “Currency & units”| Field | Notes |
|---|---|
| Currency | ISO 4217 code (e.g. GBP, EUR, USD). Used for every monetary display across the syndicate. Default: GBP. Stored in the nested default_billing.currency. |
| Fuel unit | Litres, US gallons, imperial gallons. Used on expense receipts and consumable tracking. |
| Oil unit | Litres, quarts. Used on expense receipts and consumable tracking. |
Payment collection
Section titled “Payment collection”The Payment Collection card surfaces the syndicate’s payment-provider account: connect status, the verification state (in-flight, verified, action-required), and the controls to start or resume in-app onboarding. Payment-provider integration is not yet live in production — until it is, this section is informational and the in-app actions are limited to the onboarding flow itself.
The current behaviour for admins:
| State | What you see | What you can do |
|---|---|---|
| Not connected | ”Set up payment account” CTA. | Tap to start the onboarding flow at /syndicates/:syndicateId/payment-onboarding/setup, which iterates through the provider’s required sections (business details, bank account, identity verification, etc.) one screen at a time, saving each section as you go. |
| Connecting / verifying | ”Verification in progress” status with the section the provider is reviewing. | Resume the flow to fill any section the provider has marked incomplete, or wait for the provider’s webhook to flip the state to verified. |
| Action required | The provider has rejected or asked for more information for one or more sections. | Re-open the onboarding flow; the screen will scroll directly to the section needing attention. |
| Verified | ”Payment account active” with the provider’s account ID. | The account is ready to take collections — once provider integration is live in production. |
Until provider integration goes live, payments are recorded manually by an admin or treasurer adjusting the relevant transactions outside the app; there is no in-app self-service path for members. The mechanics of the resulting transaction are described under the Payment row of Transaction types.
For the Direct Debit collection model that ships alongside the card flow, the schema and the four DD screens are wired but not yet menu-linked — the full reference page is published when the member-facing menu entries land.
Billing Schemes
Section titled “Billing Schemes”A card links to the Billing Schemes screen, which lists every scheme defined on the syndicate and lets admins add, edit, delete, or promote a scheme to the default.
Each scheme carries:
| Field | Notes |
|---|---|
| Name | Display label. Examples: Equity member, Renter, Founder. Used on member detail rows, on usage-log estimates, and on statements. |
| Default | One scheme is marked the syndicate default. New members land on it unless admins reassign them. |
| Dues amount and dues interval | The periodic charge for members on this scheme. Interval options: day, month, year. Stored in the syndicate’s currency. |
| Rate modifier type | How the scheme adjusts the asset base rate: none (base rate unchanged), fixed (adds or subtracts a fixed amount), percent (scales by a percentage), override (replaces the base rate outright). |
| Rate modifier value | The numeric value applied according to the modifier type. |
For the full semantics of how the modifier combines with the asset’s base rate, see Member rates (billing schemes) and Rate resolution chain.
Behaviour rules
Section titled “Behaviour rules”- Scheme definitions are syndicate-wide. There is no per-asset scheme definition. The same set of schemes applies across every asset.
- Per-asset scheme rates are a separate concept. The actual rate that results from “scheme X × asset Y” is set in the asset’s billing configuration — on the Billing & Rates screen for single-asset syndicates, and on each asset’s own billing screen for multi-asset syndicates. See Default and per-asset settings.
- The default scheme cannot be deleted without first promoting another scheme. The syndicate must always have exactly one default scheme. The delete action is disabled on the default row.
- Changing the currency does not convert historical amounts. Past transactions keep their original currency; future charges use the new one. For this reason, the currency change confirmation warns admins and is typically set once at syndicate creation and left alone.
- Fuel and oil units are display-only. They affect how amounts on expense receipts are labelled and entered; they don’t alter any billing calculation.
See also
Section titled “See also”- Billing & Rates — where the actual rates live.
- Member rates (billing schemes) — the full worked-example treatment of schemes.
- Rate resolution chain — precedence rules.
- Default and per-asset settings.