From movement to invoice

Every charge an airport raises describes something that physically happened: an aircraft occupied a stand, a passenger departed, a service was delivered at a counter. Yet in many airports the operational record and the financial record are built by different teams, from different sources, and only meet at the end of the month. That gap is where the reconciliation work goes — and where disputes come from. An airline queries a line on an invoice, and answering it means reassembling the movement from operational logs that were never designed to support a financial question. Billing closes the gap by taking the operational record — flights handled, passengers carried, services delivered — and turning it into airport charges that can be issued, tracked and settled. Because the charge is derived from the movement rather than re-entered alongside it, any invoice can be traced back to the event that produced it. In practice that means fewer manual reconciliations between finance and operations, a faster billing cycle for airline charges, and a single record when an auditor asks. Passenger counts, bills and payment status sit together, organised by airline and flight. There is a management dividend as well. Once traffic and revenue are expressions of the same data, questions that used to take a week — which services actually pay, how a schedule change moved the month, where the development fee is coming from — become a report rather than a project.