Finalisation
Finalisation is the step that finalises a booking’s financial consequences. Syndik8 reviews the booking’s usage logs, writes the resulting transactions to the ledger, applies any shortfall, and moves the booking’s status from confirmed to completed.
Before finalisation, usage is informational; money has not moved. After finalisation, the charges are real: they are on the member’s balance and appear on the statement.
Finalisation has four paths:
- Pilot’s close: the pilot closes their own booking after their last flight, seeing and accepting the charge, shortfall included. Available while the syndicate lets members close their own bookings (the default). Gated by the same look-back continuity check. Recipe: close a booking.
- Auto-finalise: the fallback sweep, 24 hours after a booking ends, for bookings the pilot left open. Gated by the look-back continuity check against the previous flight on the asset, and never used for a booking with a shortfall. Recipe: enable auto-finalisation.
- Admin bulk: prudent, admin-triggered from the unfinalised-bookings queue, gated by the same look-back continuity check against the previous flight on the asset, run in a batch. Used by syndicates that reconcile monthly. Recipe: finalise multiple bookings at once.
- Manual single: admin-triggered from a booking’s detail screen, no continuity check (admin trust). Recipe: finalise a booking.
Finalisation is atomic regardless of path: every charge, event fee, shortfall, and status change writes in one database transaction, or none of them do. A completed booking cannot be “unfinalised”; corrections are made by correcting the flight and then applying the difference as a new adjustment transaction. See correct a finalised booking.