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.

Who can use it

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

Where to find it

In the app:

1. Open the syndicate.
2. Go to the Admin tab.
3. Open Pending, the admin workbench pinned at the top, and use its unfinalised-flights section. 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.

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.
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 whose end time has passed appears here, whether or not anybody logged usage against it. completed (finalised) bookings drop off. A booking nobody flew therefore sits in the queue at 0.0 hours, and an admin has to decide whether the pilot forgot to log the flight or the flight never happened. Finalising it as it stands charges nothing for flying but does apply the minimum for any day the booking qualified on, so cancel it rather than finalising it if the aircraft never moved.
• Auto-finalisation shrinks the queue automatically. If the syndicate has auto-finalisation on, clean bookings are finalised without an admin touching them, and only bookings with shortfalls or unresolved tacho-continuity conflicts queue up here.
• Maintenance bookings pass through this queue rather than sitting in it, whatever the syndicate’s auto-finalise setting. A trip to the engineer is not billed to anybody, so there is no charge for an admin to review and nothing the finalisation sweep can get wrong by closing it. It does exactly that, on the first sweep after the booking’s end time — including in a syndicate that has auto-finalisation switched off, because that setting governs whether a member’s flying becomes a charge and this never does. You will usually only catch a maintenance row here between its end time and the next pass, or when a ferry flight’s meter reading disagrees with the flight before it and the continuity check holds it back like any other booking.
• Both bulk buttons confirm before they write. Tapping one opens a dialog naming how many bookings it is about to finalise; nothing reaches the ledger until the admin confirms, and cancelling leaves the queue untouched. Finalise No-Shortfall is not the safe half of the pair — it is the same append-only posting on fewer bookings, so it asks in the same terms Finalise All does.
• The bulk Finalise No-Shortfall action writes one transaction set per booking, except for a maintenance booking, which writes none. For a personal booking it is equivalent to opening it and pressing Finalise: the usage charge and any event fees land on the ledger. A maintenance booking simply closes — flying to the engineer is met through the monthlies, not billed per flight, so there is nothing to post.
• Bulk finalise is online-only. Both bulk buttons disable when the device is offline and surface Settlements need a connection. Try again when you’re online if tapped. They re-enable automatically when the connection returns. Single-booking finalisation (from the booking detail screen) follows the same rule.
• The queue is live. Members logging usage or admins finalising individual bookings update the list in real time.
• Empty state. When there is nothing to finalise, the screen reads “All bookings finalised” and the bulk button is hidden.

See also

• Expense approvals — the companion admin queue.
• Finalisation rules — what finalisation actually does.
• Auto-finalisation — the setting that keeps this queue short.