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 two automatic paths and one manual one:
- Auto-finalise — eager, member-triggered, on usage-log submit, gated by a look-back continuity check against the previous flight on the asset. Used by pay-as-you-go syndicates. Recipe: enable auto-finalisation.
- Admin bulk — prudent, admin-triggered from the unfinalised-bookings queue, gated by a look-ahead continuity check against the next flight on the asset. 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 editing the historical log and posting a new adjustment transaction. See correct a finalised booking.