What MyATOL does
One loop, end to end.
From the certificate to the CAA return, every capability is one beat of the same loop. Issue, stay within your licence, reconcile, lock in, then connect it to whatever you already run.
- 01
ATOL certificates
A protected certificate, issued the moment a booking is paid. Issue Single Contract, Multi Contract and Flight Only certificates, each carrying your ATOL number and a server-set issue time that cannot be backdated. - 02
Live licence limits
Live headroom as you issue, and a warning before you breach. Every certificate counts against your licence the moment it is issued. See your headroom at any time, and get warned at half and at full, well before the limit. - 03
Self-building returns
When a period closes, the figures are already reconciled, not re-keyed. Your ATOL return builds itself as you issue. Three-tier reconciliation, by booking type, on the departure basis, and every cell drills to the bookings behind it. - 04
Lock-in & discrepancies
An attested record of what was filed, and every later change flagged. Lock in what you filed as an immutable, attested snapshot. Anything that changes afterwards is flagged in plain English, with the exact delta against your filed figures.
Fits your setup
However you issue, the figures land in the same return.
-
Compliance API
The compliance layer slots in behind the booking system you already run.
Issue and reconcile through the MyATOL API. Keep your existing booking system; the compliance layer slots in, and the figures land in the same return.
Read more → -
MyATOL AI assistant
Practical ATOL answers, right inside MyATOL.
An AI assistant built into MyATOL for everyday certificate, APC, return, amendment and backdating questions. It keeps the answer close to the task, using MyATOL workflow guidance and ATOL source material.
Read more → -
POST /v1/certificates { "kind": "single", "passengers": 3, "protectedCost": 482000 } 201 · certificate issued · counted against licence · reconciled into Q3 return