- 2logins: Airline / GSA and Admin
- Statusupdates by itself at every step
- Depositadvance deposits settled against invoices
- .NETwith an SQL database
The challenge
Every flight needs a permission before it operates, and every permission has to be approved, billed and paid.
Every flight that lands, takes off or overflies needs a permission before it operates. The airline, or its General Sales Agent (GSA), applies, the authority reviews each application and approves it, and the permission is then billed. When this process runs on email, phone calls and separate records, it becomes slow and difficult to control.
Applicants cannot easily see where a permission stands. Staff have no single place to verify users, check pending applications and record each decision. Billing is a further burden: invoices have to be raised for every permission, payments followed up, and advance deposits and outstanding amounts tracked for each airline and GSA.
BANQ needed one controlled process, from the first application to the final payment, that both the airlines and its own staff could rely on.
What we built
Catabatic built one application for flight permissions for BANQ, with two logins. Airlines and GSAs apply, follow status and pay. The BANQ admin verifies users, approves permissions, and handles invoices and deposits.
Airline / GSA login
Built for airlines and GSAs.
Create permissions
Create a flight permission and send it for approval.
Track status
See the status of every permission. The status updates by itself as the admin takes each step.
Edit or delete
Edit or delete a permission any time before it is approved.
View approved permissions
View the full details of a permission after it is approved.
Pay bills
Pay permission bills and see the payment status.
Admin login
Verification, approval, invoices and deposits.
User approval
Unapproved Airline / GSA users are listed. The admin verifies them and approves them, and only then can they log in.
Masters
Airport, Airline / Operator, Aircraft registration, Aircraft type, GSA, Rate, Approval list (to define the approval number) and Commission masters.
Pending permissions
See the list of pending permissions and take action: view, reject or process to the next step. The system updates the permission status by itself, and the Airline / GSA sees it.
Approved permissions
See the list of approved permissions and send an email at any time.
Invoices
Generate invoices against an Airline / GSA and see the generated invoices.
Deposits
Take a deposit in advance from an Airline / GSA and settle invoices against it later. See the deposit amount and the balance, and every invoice settled against the deposit.
Outstanding
See the outstanding invoices of each Airline / GSA.
Ground handling
Manage ground handling and its bills.
How it works day to day
- 1
Register
An Airline / GSA user registers. The admin verifies the user and approves it. Once approved, the user can log in.
- 2
Apply
The Airline / GSA creates a flight permission and sends it for approval. Until it is approved, it can still be edited or deleted.
- 3
Review
The admin sees the pending permissions and views, rejects or processes each one. The status changes automatically, and the Airline / GSA sees it.
- 4
Approve and inform
Approved permissions appear in the approved list. The Airline / GSA can view the details, and the admin can send an email at any time.
- 5
Bill and settle
The admin generates the invoice. The Airline / GSA pays it and sees the payment status. Deposits, balances and outstanding invoices are always visible.
In use
Where it runs
Built for BANQ.
Who uses it
Airlines and GSAs, who apply and pay. BANQ staff, as admin, who verify, approve and bill.
Technology
Built on .NET with an SQL database.
Need permits and billing in one flow?
Tell us how your permissions are approved and billed. We will reply with how we would build it.