Fiskal Accounting

Check the BSP bill, ticket by ticket

Every billing period the BSP statement arrives, and somebody has to check it against the invoices line by line — or nobody does. Fiskal Accounting lines up every ticket number three ways and puts the ones that do not agree at the top.

Three sources, side by side

For each ticket number: what you entered in your own books, what Sabre or Amadeus issued, and what BSP actually charged you. You read one row per ticket instead of three documents.

What comes to the top, in red

  • A BSP charge with nothing in your books to match it
  • A ticket you billed for less than BSP charged you
  • A ticket in the GDS that never became an invoice
  • Voids and reissues recognised, not counted twice

Why it is worth doing every period

A charge nobody invoiced is money you paid and never billed. A ticket billed below its BSP cost is margin you gave away. Neither shows up in a monthly total — they only show up one ticket at a time, which is exactly where nobody has time to look by hand.

Where the ticket rows come from

Sabre and Amadeus already write an interface record for every ticket to a folder on the office PC. Those records are picked up from that PC and turned into rows, with nothing to upload by hand. BSP and your own invoices are checked whichever GDS a ticket was issued on.

Supplier statements get the same treatment

A supplier sends a statement as a PDF, an Excel file or a photo of a printed page. Upload it and it is lined up against your ledger for the same period, line by line: matched, amount differs, only in their file, or only in your books.

Questions

We issue on both Sabre and Amadeus. Does that work?

Yes. Both are read today, and the BSP bill and your own invoices are checked whichever GDS a ticket was issued on.

Are voids and reissues counted as extra charges?

No. They are recognised, so a voided or reissued ticket does not show up as a second charge.

What about Galileo?

Galileo files are collected by the same agent from the same PC; reading them into rows is next.