Auto-finalise
Auto-finalise is the per-syndicate option that says “this is a pay-as-you-go syndicate”. When auto-finalise is on, finalisation runs the moment a member submits a usage log — provided a look-back continuity check against the previous flight on the same asset succeeds.
The look-back check compares the new log’s start meter to the immediately preceding booking’s last log end. There are four outcomes:
- No previous booking on the asset → finalises (this is the first flight).
- Previous booking has no log yet → waits silently. The log is saved; finalisation re-attempts later when the predecessor lands.
- Previous log’s end matches my start (within 0.01 h tolerance) → finalises.
- Previous log’s end disagrees with my start → skips, fires a
tacho_continuity_detectednotification to the submitter and admins, leaves the booking in the unfinalised queue.
The toggle’s full meaning, after the asymmetric-correctness change, is “this syndicate finalises eagerly via look-back”. Syndicates that prefer end-of-month admin reconciliation leave it off and use the look-ahead admin bulk path instead — see finalise multiple bookings at once.
Auto-finalise is off by default. Turning it off does not reverse any finalisations it has already run; existing completed bookings stay completed. When an eagerly-finalised booking later turns out to have been wrong, the recovery is admin-driven and forward-only — see correct a finalised booking.