Unfinalised bookings

What it is

The Unfinalised Bookings screen is an admin queue of every confirmed booking that has a usage log recorded against it but has not yet been finalised. 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

• Owner, 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 Dashboard tab.
3. Open Unfinalised Bookings (admin-visible tile).

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. One-tap clearing of clean bookings.
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. The bulk-finalise button at the top is disabled when the no-shortfall count is zero.

Behaviour rules

• Only confirmed bookings with a saved usage log appear here. Bookings without usage, or completed (finalised) bookings, do not appear.
• 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.
• The bulk Finalise No-Shortfall action writes one transaction set per booking. It is equivalent to opening each no-shortfall booking and pressing Finalise, then moving on.
• 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.