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 last actually-flown reading on the asset, looking past any booking that recorded no usage (a no-show or an empty maintenance grounding). The outcomes:
- No earlier flight on the asset → finalises (this is the first flight).
- Start matches the last flown reading (within 0.01 h tolerance) → finalises. This includes the case where the booking just before was a no-show or grounding that never moved the tacho.
- The immediately preceding flight is logged and its end disagrees with my start → skips, fires a meter-continuity notification to the submitter and admins, leaves the booking in the unfinalised queue.
- The immediately preceding booking has no log and the meter has jumped since the last flown reading (real flying went unlogged, or an out-of-order log is still to come) → waits silently. The log is saved; finalisation re-attempts later when the missing log lands.
The toggle’s full meaning 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.