How do I check the BSP billing against the agency's tickets and find the gaps before paying?
| Intagya ERP
Compare the billing with the tickets you recorded before you pay. In Intagya ERP you upload the billing analysis from BSPlink in BSP check, and the system finds each ticket by number and compares total, commission and status. Four figures show: matching, different, tickets on the file that you do not have, and tickets you have that are not on the file.
The BSP billing arrives on payment day. The finance manager sees the total and asks whether it is right. The accountant says it looks close to what we sold. The money goes out.
Two months later someone finds that the commission on a long-haul ticket was lower than the airline agreed, and that a voided ticket is still on the billing.
Why is a look at the total not enough?
Because small gaps hide inside a big figure. An extra ticket here and a short commission there, and the total still looks about right. The error only shows when you compare line by line, which nobody has time for before payment day.
My view is plain: do not pay a billing you have not checked against your tickets, even when the expected gap is small. This is not distrust of anyone; it is keeping your own books right.
How do I upload the BSP billing?
Download the period's billing analysis from BSPlink as CSV or Excel. In the travel app open Booking systems, then BSP check, and press New. Enter the start and end of the period and the IATA agency number, upload the file, then press Check against tickets.
The system reads the ticket number, transaction type, total, commission and net, and understands the usual transaction codes for issue, void and refund.
What do the four results mean?
- Matching: total, commission and status are as you have them.
- Different: you have the ticket, but the total, commission or status differs from the file, and the gap is written in the note.
- Not in the system: a ticket on the file you do not know, either not imported yet or not yours.
- Not in BSP: a ticket you issued in the period that is missing from the file.
A gap under 0.01 does not count, because files round their figures.
What if the agency works with more than one IATA number?
Each connection has its own agency number, and so does each check. When looking for tickets missing from the file, the system only looks at the tickets of the connection with that number, so another branch's tickets do not show as missing.
With several branches, create one connection per branch with its number, and check each billing against its number.
Does the check change the ticket itself?
Each ticket carries the result of its last check: matches BSP, differs from BSP, or not in BSP. The ticket list has a BSP differences filter that gathers what needs review.
The check changes no amount and posts no entry. It shows the gaps, and the accountant decides: claim from the airline, correct the ticket, or accept the billing.
Can I run the check again after fixing a ticket?
Yes. Press Check against tickets again and the lines are rebuilt from the same file, without duplicates.
On the next billing try this a day before payment: upload the file and open the different lines only. If there is no gap you gained peace of mind; if there is one, you gained the money.
Read the BSP check steps in the user guide
FAQ
Where do I get the billing file?
From BSPlink: the billing analysis of the period as CSV or Excel.
Does the check change any amount?
No. It only shows the gaps, and the accountant decides.
What if a ticket is on the file but not in my system?
It shows as Not in the system. Import the sales report that has it, or check whether it is yours at all.
Do I check each branch on its own?
Yes, enter the branch's IATA number on the check, so other branches' tickets do not show as missing.
Is this your business?
Want to see IntagyaERP on your own workflow?
Book a demo, tell us how your business runs, and watch the system handle a real scenario from your company.
Book a demo