Tickets from the GDS, without retyping
Sabre and Amadeus already write an interface record for every ticket to a folder on the PC. Fiskal Accounting picks those records up and turns them into rows — nothing to upload, nothing to type twice.
What happens to each ticket
- Read from the folder the GDS already writes to
- Turned into a row with its ticket number
- Lined up against the invoice that sold it
- Flagged when it never became an invoice
Retyping is where mistakes come from
A ticket number copied by hand from the GDS screen into an accounting program is a ticket number that can be wrong by one digit — and then nothing matches at the end of the period. Reading the record the GDS already produced removes that step.
Then checked against BSP
The same ticket rows are compared with the BSP bill and with your invoices, so a charge with no invoice or a ticket billed below cost comes to the top. See how the BSP check works.
Which systems
Sabre and Amadeus are read today. Galileo files are collected by the same agent from the same PC; reading them into rows is next.
Questions
Do we have to upload the ticket files?
No. The records Sabre and Amadeus already write to a folder are picked up from that PC automatically.
What if a ticket was issued but never invoiced?
It is flagged: a ticket in the GDS that never became an invoice comes to the top of the comparison.