Every FBO has customers who do not pay at the counter. Hangar tenants owe rent on the first of the month. Corporate flight departments get billed for fuel and services after the fact. Flight schools run tabs for students. These are account customers, and managing their billing is one of the most time-consuming parts of running an FBO if you are doing it by hand.

I have watched FBOs manage account billing every way imaginable - from handwritten ledgers to Excel spreadsheets to QuickBooks invoices typed from scratch. Every one of those methods breaks down at scale. When you have 40 hangar tenants, 15 corporate accounts, and a flight school with 60 students, you need software that handles recurring charges, tracks balances, ages receivables, and sends statements without someone spending two days a month on it.

Key Takeaways

  • Account customers - hangar tenants, corporate flight departments, and flight schools - represent a significant and predictable portion of FBO revenue that requires systematic billing.
  • Automated recurring billing eliminates the manual creation of monthly invoices for fixed charges like hangar rent, tie-down fees, and fuel minimums.
  • Aging reports and account statements must be generated automatically to keep receivables from going stale and to give customers clear documentation of what they owe.
  • On-account payments need to apply against the oldest outstanding invoices first, following standard accounting practice, without manual allocation by staff.

Who Are Account Customers?

Account customers fall into a few distinct categories, and each has its own billing rhythm.

Hangar tenants are the most straightforward. They owe the same amount every month - hangar rent, sometimes with additional charges for electricity, insurance surcharges, or common area maintenance. The amount rarely changes unless there is a lease renewal. These charges should generate automatically on the same day each month with zero human intervention.

Corporate flight departments are more complex. A company might base two aircraft at your field, have a fuel discount agreement, and want a single monthly invoice that covers all fuel uplifts, landing fees, overnight hangar charges, and miscellaneous services across both tail numbers. Their accounting department expects a detailed statement that breaks down every transaction by date and aircraft.

Flight schools operate on a different model entirely. Students may prepay into an account balance and draw it down with each lesson, or they may run a tab and settle weekly or monthly. The flight school itself might be an account customer of the FBO, purchasing fuel in bulk and reselling it through their aircraft rental rates.

Tie-down customers pay monthly fees for ramp space. Like hangar tenants, their charges are fixed and predictable, but the amounts are smaller and the customer list tends to change more frequently as aircraft come and go.

The Problem with Manual Billing

Here is what manual billing looks like in practice. On the first of the month, someone pulls out a spreadsheet or a stack of lease agreements. They create an invoice for each hangar tenant, typing in the amount, the description, and the customer information. Then they do the same for tie-down customers. Then they go through the previous month's fuel tickets and create invoices for each corporate account, manually totaling the charges.

This process takes one to three days depending on the number of accounts. During that time, the person doing the billing is not available for other work. Mistakes happen - a tenant gets billed the wrong amount because the lease renewal was not updated in the spreadsheet, or a fuel ticket gets missed because it was filed in the wrong stack.

The worst part is what happens after the invoices go out. When a payment comes in, someone has to look up the customer, figure out which invoice the payment applies to, record it, and update the balance. When a customer calls asking about their statement, someone has to dig through records to answer the question. When the FBO owner wants to know how much is outstanding in receivables, someone has to add it all up.

None of this is complicated. It is just tedious, error-prone, and completely unnecessary when software can do it automatically.

How Automated Recurring Billing Works

In a properly designed FBO billing system, you set up each recurring charge once. You specify the customer, the product or service, the amount, the frequency (monthly, quarterly, annually), and the day of the month it should generate. From that point forward, the system creates the invoice automatically on schedule.

For hangar rent, you configure the charge when the tenant signs their lease. Every month, the invoice appears in the system, ready to be emailed or printed. If the rent changes at lease renewal, you update the recurring charge template and the new amount takes effect going forward.

For fuel minimums, the system can calculate automatically. If a customer's agreement requires them to purchase at least 500 gallons per month, the system checks their actual fuel purchases at the end of the month. If they bought 350 gallons, it generates an invoice for the 150-gallon shortfall at the agreed rate.

The real power is batch processing. On the first of the month, the system generates all recurring invoices at once - 40 hangar invoices, 25 tie-down invoices, 10 fuel minimum invoices - in seconds. Each one has the correct amount, the correct tax treatment, and the correct customer information. No typing, no looking up lease amounts, no missed charges.

Credit Card on File and Automatic Payment

The next step beyond automated invoice generation is automated payment. Many FBOs now require hangar tenants to keep a credit card on file. When the monthly invoice generates, the system automatically charges the card, records the payment, and emails a receipt. The tenant never has to write a check or remember to pay, and the FBO never has to chase the payment.

This changes the economics of account management dramatically. Instead of billing 40 tenants and then spending weeks collecting from the slow payers, the FBO gets paid on the same day the invoice generates. Cash flow becomes predictable. The accounts receivable balance drops. The time spent on collections approaches zero for customers with cards on file.

Card-on-file billing requires PCI compliance and secure token storage. The actual card number is never stored in the FBO system. Instead, the payment processor issues a token - a reference number that can be used to charge the card without exposing the card data. This is the same technology that lets you save a card in any online store.

Accounts Receivable and Aging

Not every account customer pays automatically. Corporate flight departments typically want to review invoices before paying. Some tenants prefer to mail checks. For these customers, accounts receivable management is essential.

An aging report shows every outstanding invoice grouped by how long it has been unpaid: current (0-30 days), 30-60 days, 60-90 days, and over 90 days. This is the single most important report for managing account customers. It tells you who is falling behind before the balance gets out of control.

Good FBO software generates aging reports automatically and makes them available in real time - not just at month end. When a customer calls to dispute a charge, you should be able to pull up their complete account history in seconds: every invoice, every payment, every credit, and the current balance.

Statements go out monthly, showing all activity on the account. A statement is not an invoice - it is a summary of all invoices, payments, and credits for the period. The customer uses it to reconcile their records against yours. When statements are generated automatically from the same data that drives the aging report, discrepancies are rare.

On-Account Payments

When a payment comes in from an account customer, the system needs to apply it correctly. Standard accounting practice is to apply payments against the oldest outstanding invoices first - this is called FIFO (first in, first out) payment application. A $5,000 check from a corporate account should pay off the oldest unpaid invoices until the money runs out.

Some customers specify which invoices they are paying. Their check stub or remittance advice lists specific invoice numbers and amounts. The system should support both automatic FIFO application and manual allocation to specific invoices.

Overpayments create credit balances that apply against future invoices. Underpayments leave partial balances that carry forward. Short payments on specific invoices (where the customer disputes part of the amount) need to be flagged for follow-up rather than silently aging in the receivables.

Integration with the Rest of the Operation

Account management does not exist in isolation. Every invoice generated by recurring billing flows into the same reporting and accounting systems as counter transactions. Fuel sold to account customers shows up in fuel reconciliation. Revenue from hangar rent appears in financial reports alongside fuel sales and ramp fees. Tax collected on taxable services posts to the correct tax liability accounts.

When the FBO exports data to QuickBooks or another accounting system, account transactions should flow automatically alongside everything else. The goal is one set of books, not a separate tracking system for account customers. For more on how FBO operations connect to accounting, see The Complete Guide to FBO Software.

What to Look for in Billing Software

If you are evaluating FBO software with account management in mind, the features that matter most are: flexible recurring charge templates that support different frequencies and amounts, batch invoice generation, automatic credit card billing with PCI-compliant token storage, real-time aging reports, automatic statement generation, and FIFO payment application. Everything else is secondary to getting those fundamentals right.

The measure of a good billing system is simple: your office manager should spend hours per month on account management, not days. If they are still creating invoices by hand or manually tracking who owes what, the software is not doing its job.

Frequently Asked Questions

How does recurring billing handle mid-month lease changes?

When a tenant moves in or out mid-month, the system should support prorated billing. You update the recurring charge with the new effective date, and the system calculates the partial amount for the first or last month automatically. Future months generate at the full amount.

What happens if a card on file is declined during automatic billing?

The system flags the failed transaction and creates the invoice as unpaid. The customer is notified to update their payment method. The invoice then ages normally in accounts receivable until it is paid manually or with an updated card.

Can account customers see their invoices and statements online?

Many FBO software systems offer a customer portal where account customers can view invoices, download statements, and make payments online. This reduces phone calls and gives customers 24/7 access to their account information.

How do fuel minimums work with recurring billing?

The system tracks fuel purchases throughout the billing period. At the end of the period, if the customer's actual purchases fall below the contracted minimum, the system automatically generates an invoice for the shortfall quantity at the agreed fuel price.