Unfinalised bookings

What it is

The Unfinalised Bookings screen is an admin queue of every confirmed booking whose end time has passed and which has not yet been finalised. Most carry a usage log; one nobody flew appears too, at zero hours. Each row summarises the booking (member, asset, date, hours, landings, touch-and-gos, shortfall if any) and links through to the booking detail for a single-booking finalise, or offers a Finalise No-Shortfall bulk action.

The top of the screen shows aggregate stats across the queue: Sessions, Hours, Landings, T&Gs, and With shortfall — so an admin can see at a glance how much work is queued and how many bookings need attention versus clean finalisation.

The rows come in two groups, Needs you first and then Waiting to be closed. A line under Waiting to be closed says who will close those bookings, which depends on the syndicate’s settings: pilots, who have 24 hours to close their own booking, when Pilots finalise their own bookings is on; auto-finalise, 24 hours after the booking ends, when Finalise automatically is on; or pilots first and then auto-finalise when both are. With neither setting on, nothing else will close a member’s booking, so every one is under Needs you, and the only row that can wait is a maintenance booking, which closes itself. See Groups below.

Who can use it

Admin and treasurer (admin) — full access.
Members — do not see this screen.

Where to find it

In the app:

Open the syndicate.
Go to the Admin tab.
Open Pending, the admin page pinned at the top (or tap the pending-actions icon at the top of the syndicate screen), and tap Review on its Finalisation section. The section is there whenever any booking is unfinalised. Under its heading it lists 1 needs you and 1 waiting to be closed on separate lines. The admin badge counts only Needs you; see Admin Pending page. There is no tile for this on the Dashboard.

Route: /syndicates/:syndicateId/unfinalised-bookings.

Fields / options

Summary chips

Chip	Shows
Sessions	Count of unfinalised bookings with usage logs.
Hours	Sum of logged hours across the queue.
Landings	Sum of landings across the queue.
T&Gs	Sum of touch-and-gos across the queue.
With shortfall	Count of bookings whose usage came in below the configured minimum usage, and so would incur a shortfall charge on finalise.

Groups

Group	Holds
Needs you	Bookings nothing else will finalise now: a member’s booking that ended more than 24 hours ago and is still not finalised, and, when the syndicate has neither Pilots finalise their own bookings nor Finalise automatically on, every booking that has ended. These are the bookings the Finalisation section of the Admin Pending page counts.
Waiting to be closed	Bookings that ended less than 24 hours ago, which the pilot can still close or auto-finalisation will pick up. They need nothing from you yet, though you can finalise them now if you want to.

The groups only order the list. Finalise No-Shortfall and Finalise All work across both groups, and a row in either group opens its booking for a single finalise. Maintenance bookings close themselves, so they are never counted on the Pending page.

Actions

Action	Effect
Finalise No-Shortfall ({count})	Bulk finalise every unfinalised booking in the queue that has zero shortfall. Opens a Confirm Finalisation dialog first, naming the count and warning that finalising posts charges to the ledger and cannot be undone.
Finalise All ({count})	Bulk finalise every eligible booking in the queue, applying the calculated shortfall where there is one. Opens a Confirm Bulk Finalisation dialog first, naming the total and how many of them carry a shortfall charge, and warning that finalising posts charges to the ledger and cannot be undone.
Open booking (tap a row)	Navigate to the booking detail, where the single-booking finalise flow lives.

Each row links through to the booking detail. Finalise No-Shortfall is not shown at all when the no-shortfall count is zero — it disappears rather than greying out. Its neighbour, Finalise All, stays put and greys out instead.

Behaviour rules

Every confirmed booking that has ended stays in this queue until it is finalised or cancelled. An empty booking shows No flight logged. Open it to log the flight or review whether to cancel the booking. It is excluded from bulk finalisation; an admin can still review it individually.

Each card shows one primary issue and +N more when other findings exist. Passed checks show no badge. Booking detail lists all established findings under Needs attention, with the recorded values, a next action and links to related bookings. The priority is No member, Possible duplicate, Meter mismatch, Departure mismatch, Missing previous log, Check failed, No flight logged, then Shortfall. Rare cases are labelled Earlier logs unclear for ambiguous earlier repeats, and No baseline reading when there is no earlier or opening reading to compare.

Meter and route checks run independently. An empty intervening booking does not block a later booking whose start matches the last genuine end. A lower start is a meter mismatch. A higher start waits for a missing previous log only when an unlogged booking intervenes. These checks never close or cancel the empty booking.

Needs you uses attention styling; Waiting to be closed is neutral. The configured grace period is unchanged, currently 24 hours. Admins can finalise eligible bookings early in either group. Both bulk actions include eligible bookings across both groups and recheck on the server before posting charges. A shortfall can be included by Finalise All, but not Finalise No-Shortfall. Maintenance remains unbilled.

Bulk finalisation is online-only. It writes to the financial ledger and cannot be queued, so both bulk buttons are disabled while the device is offline, and tapping one says “Settlements need a connection. Try again when you’re online.”

The queue updates live. A booking drops off once it is finalised, and the findings are checked again whenever a flight log changes anywhere in the syndicate, so a row can change badge while you watch.

When nothing is waiting, the screen shows All bookings finalised and “There are no past bookings awaiting finalisation.” in place of the summary and bulk buttons.

A late earlier log or correction that conflicts with a later logged booking is diagnosed on the changed earlier booking, including when the later booking is already finalised. The later booking is linked for comparison and its status and charges stay unchanged. See Meter continuity.